I just received my Mi5s and like others it comes with 8.0.3.0 pre-installed
after hours of stress, I almost give up and want to make a DF cable... but I finally found the light :angel:
the trick is simple, just manual update to Global Stable to 8.2.1.0
grab the zip file, put it on your phone and update it via phone updater app.
now you will have Mi Unlock Status on Developer Settings, just go there and click the add button
finally run the unlock tool, and viola ...
is this really working? it's a good news! i tried different ways to unlock my BL and posting comments in different threads but still no use. Maybe this would help. Thank you for creating this guide. God bless!
PS. it says "Coudn't verify update package". Im using updater app. How did you flash yours?
What is your current version?
You can't update with updater app if your ROM is unofficial ROM like 8.0.10.0
is your zip file manipulated in any way? I updated manually yesterday and tried to add account in mi unlock status but it's telling me to connect to the internet and try again althouh I have internet connection via wifi and also network..
No... The zip is from xiaomi. Its official 8.2.1.0 without any modification.
You should already add your mi account before you press the add button
Im using global stable 8.0.3.0.
rhp_engcoy said:
Im using global stable 8.0.3.0.
Click to expand...
Click to collapse
Should be smooth upgrade from 8.0.3.0 to 8.2.1.0
Just tap the updater app, 3 dots, choose update package, then choose the downloaded zip.
Check the zip, it might corrupted...
aabenroi said:
No... The zip is from xiaomi. Its official 8.2.1.0 without any modification.
You should already add your mi account before you press the add button
Click to expand...
Click to collapse
hmm I'm using the official 8.2.1.0 also and I have my mi account added beforehand.. it is still saying "connect to the internet and try again"
I'm in Germany btw. if that's important in any way
aabenroi said:
Should be smooth upgrade from 8.0.3.0 to 8.2.1.0
Just tap the updater app, 3 dots, choose update package, then choose the downloaded zip.
Check the zip, it might corrupted...
Click to expand...
Click to collapse
Should I upgrade to 8.2 using ota first before I flash the zip? Because i tried everything you've said but always error. I'm now using 8.2 stable. Just updated earlier from the ota
Updating to 8.2 is to get the "mi unlock status" option in developer settings, if yours is already 8.2 then you should have it.
aabenroi said:
Updating to 8.2 is to get the "mi unlock status" option in developer settings, if yours is already 8.2 then you should have it.
Click to expand...
Click to collapse
I have 8.2 i have unlocked in developer options, but still when i choose zip file I get Cant't verify update. It's not allawed to upgrade to unoficcal ROM package.
if you already have the unlocked in developer options, you're good to go ...
just add mi account, press the add button on mi unlock status and run mi unlock.
the zip is for those who still stuck on 8.0.3.0
Thanks for the help sir. I will now try to use mi unlock. Gonna update later if successful. God bless!
aabenroi said:
What is your current version?
You can't update with updater app if your ROM is unofficial ROM like 8.0.10.0
Click to expand...
Click to collapse
unfortunatly both of my phones have this damn 8.0.10.0 ROM Version on it - how do I upgrade it to a proper Global Rom?
Viper780 said:
unfortunatly both of my phones have this damn 8.0.10.0 ROM Version on it - how do I upgrade it to a proper Global Rom?
Click to expand...
Click to collapse
I just got my phone last week, I hadn't realised 8.0.10.0.0 wasn't official - and I downloaded the new 8.2.1.0 global , and started the manual update process (from the download folder). The upgrade started, but when 8.0.10.0.0 said I was downgrading, I backed out. When I later found 8.0.10.0.0 was unofficial, I tried to do it again, but kept getting "couldn't verify update package" - with both 8.0.3.0 and 8.2.1.0 downloads.
The solution......
I did a factory reset, copied the file over again, and manually started it. This time it decrypted and worked..... I just accepted the "downgrade", and everything went through. I'm now on 8.2.1.0 Stable.
To people that has 1008 erro please use FlyVPN and connect to shanghai server. I use this method and others report it working without error
aabenroi said:
if you already have the unlocked in developer options, you're good to go ...
just add mi account, press the add button on mi unlock status and run mi unlock.
the zip is for those who still stuck on 8.0.3.0
Click to expand...
Click to collapse
Hi, I'm precisely stuck on 8.0.3.0 global, no OTA offered (not even 8.2), and I'm getting the "could not verify" error. What could I do ?
Regards
bawbagg said:
I just got my phone last week, I hadn't realised 8.0.10.0.0 wasn't official - and I downloaded the new 8.2.1.0 global , and started the manual update process (from the download folder). The upgrade started, but when 8.0.10.0.0 said I was downgrading, I backed out. When I later found 8.0.10.0.0 was unofficial, I tried to do it again, but kept getting "couldn't verify update package" - with both 8.0.3.0 and 8.2.1.0 downloads.
The solution......
I did a factory reset, copied the file over again, and manually started it. This time it decrypted and worked..... I just accepted the "downgrade", and everything went through. I'm now on 8.2.1.0 Stable.
Click to expand...
Click to collapse
Did exactly this but still have the same issue. You did factory reset through the settings menu?
DotcomL said:
Did exactly this but still have the same issue. You did factory reset through the settings menu?
Click to expand...
Click to collapse
Yes. Exactly that.
fradav said:
Hi, I'm precisely stuck on 8.0.3.0 global, no OTA offered (not even 8.2), and I'm getting the "could not verify" error. What could I do ?
Regards
Click to expand...
Click to collapse
My issue as well. I don't see anything we can do besides EDL through Deep Flash. This sucks.
Related
Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?
I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)
fies76 said:
I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)
Click to expand...
Click to collapse
good news!
TopTomy said:
Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?
Click to expand...
Click to collapse
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.
zute333 said:
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.
Click to expand...
Click to collapse
Thanks for sharing!
New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.
I hope, with the release of the Yota 3 and 2c, that the price of the YD201 falls down. They can't update neither Yota 1 and 2. I still got the first one, but just because I live in Brazil and got from a nice guy that agreed to sell and send his Yotaphone 1 to me from India.
Anyone inclined to sell your Yota2 please talk to me.
zute333 said:
New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.
Click to expand...
Click to collapse
Woot??
You got a new firmware OTA?
mine shows nothing!
TopTomy said:
Woot??
You got a new firmware OTA?
mine shows nothing!
Click to expand...
Click to collapse
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).
zute333 said:
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).
Click to expand...
Click to collapse
Thanks for the info!
I only believe it when it is real, but according to info from tech support, also the EU firmware will get an update this month...
BTW, lollipop isn't too bad, I switched back from marshmallow on my nexus 7 - too much battery drain. if Google could get it right the first time, you wouldn't need monthly bug fixes. not saying that an update for the yota isn't overdue...
Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error
TKPL said:
Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error
Click to expand...
Click to collapse
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?
zute333 said:
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?
Click to expand...
Click to collapse
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...
Provide you my flash method, manually. Use the fastboot.exe in cmd, and type command line below
****************************************************************************
fastboot.exe flash aboot firmeare/emmc_appsboot.mbn
fastboot.exe flash boot firmware/boot.img
fastboot.exe flash -S 512M system firmware/system.img
fastboot.exe flash recovery firmware/recovery.img
fastboot.exe flash cache firmware/cache.img
fastboot.exe flash modem firmware/radio/NON-HLOS.bin （flash the radio）
fastboot.exe flash sbl1 firmeare/radio/sbl1.mbn
fastboot.exe flash rpm firmware/radio/rpm.mbn
fastboot.exe flash aboot firmware/emmc_appsboot.mbn （flash again, just do it.）
fastboot.exe flash userdata firmware/userdata.img （notice this is for the user data, including app data and SD）
fastboot.exe reboot (reboot and wait, about 20 min stuck on logo, it's ok.)
Thank you xingshi.
I'll try.
How long does the entire process take?
TKPL said:
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...
Click to expand...
Click to collapse
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.
TKPL said:
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.
Click to expand...
Click to collapse
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...
TKPL said:
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...
Click to expand...
Click to collapse
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate
lexman941 said:
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate
Click to expand...
Click to collapse
I have the 1.60 EU.
You can make a NAND backup and then flash the newest firmware, trying maybe the 1.99 RU. Even if you flash the 1.60 EU, is not sure that you'll have my same problem, there's people who flashed without issues...
PLK-L01C432B190 (for B180): http://update.hicloud.com:8180/TDS/data/files/p3/s15/G939/g104/v51796/f1/full/update.zip
Just put the .zip file in your dload folder and do local update.
This update fixes issues related to icons and input methods and improves system security with the latest Google security patches. [Fixes] Fixed an issue where the Google input method can't be used when the system language is set to Serbian. Fixed an issue where the icon for the calendar downloaded from the Google Play Store and system calendar icon are the same. [Optimizations] Deleted the Huawei browser (with the Google browser remaining unchanged) for a better user experience. All user data from the Huawei browser, except for bookmarks, will be deleted. Bookmarks will be imported to the Google Chrome after you update your device. Improved device security with the latest Google security patches. Deleted quick sharing of application installation packages and images to ensure their legal use. [Update notes] 1. Before the update, make sure your phone has not been rooted. If you experience any issues during the update, please go to http://consumer.huawei.com/ or visit an authorized service center for assistance. 2. This update will not erase your personal data, but we recommend that you back up any important data before updating.
Click to expand...
Click to collapse
Hello,
Did you tried it ? 'Cause except for the security patch, i dont' think this update worth it, am i right ?
I think people who were in that version didn't got any update to B37x.
To my (limited) knowledge B180>B370 excluding betas.
in my case failed at 9% and I do not want to reset phone... staying at b180
Kikito94 said:
Hello,
Did you tried it ? 'Cause except for the security patch, i dont' think this update worth it, am i right ?
Click to expand...
Click to collapse
Yes, the screenshot taken from my phone
@zinko_pt I got B371 update notification 1.18 GB in size.
@Ing.King really strange, i did it without any issue.
By the way guys, I just released it. It's up to you, updating or not..
We who had only B371 couldn't either update. Where and when will we get B30?
Sent from my PLK-L01 using XDA-Developers mobile app
---------- Post added at 07:08 PM ---------- Previous post was at 06:44 PM ----------
Forget the comments
Sent from my PLK-L01 using XDA-Developers mobile app
memht said:
Yes, the screenshot taken from my phone
@zinko_pt I got B371 update notification 1.18 GB in size.
@Ing.King really strange, i did it without any issue.
By the way guys, I just released it. It's up to you, updating or not..
Click to expand...
Click to collapse
Well ? You made this release or it's an official one ?
Kikito94 said:
Well ? You made this release or it's an official one ?
Click to expand...
Click to collapse
Of course official :laugh: it's from hi-cloud servers. It means "I found it and shared it".
memht said:
Of course official :laugh: it's from hi-cloud servers. It means "I found it and shared it".
Click to expand...
Click to collapse
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Kikito94 said:
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Click to expand...
Click to collapse
Really soo weird, I installed it at once without facing any problem.
It doesn't need a clean B180 rom because I installed it over my usual rom. It wasn't clean.
Something must be wrong in somewhere... but where?
Back here again..
No good news, tried to instal via sd, same issue, fail at 6%
But, but, but there might be a reason, i flashed the sdk21 of xposed, and idk how to remove it.. maybe this is the cause of it....
When you installed, you had to : unroot & put the recovery back ? Or you where "clean"
I'll try tomorrow, with a rest head
Kikito94 said:
Back here again..
No good news, tried to instal via sd, same issue, fail at 6%
But, but, but there might be a reason, i flashed the sdk21 of xposed, and idk how to remove it.. maybe this is the cause of it....
When you installed, you had to : unroot & put the recovery back ? Or you where "clean"
I'll try tomorrow, with a rest head
Click to expand...
Click to collapse
Oh, when I was saying "not clean" I meant installed apps and my all data
And yes, my rom was clean if we consider root and recovery condition.
memht said:
Oh, when I was saying "not clean" I meant installed apps and my all data
And yes, my rom was clean if we consider root and recovery condition.
Click to expand...
Click to collapse
Hi,
Hmmm so maybe the xposed package.rar i've flashed made this error
Well, i'll try when i receive the H8
Or maybe i had to put the recovery of B100 instead of B180 :/
Edit 1 : When i check the local.prop, there is "ro.dual.sim.phone=false" or the PLK-L01 is a dual sim, so i don't understand ^^
Edit 2 : Flash with TWRP =
MD5's missing
coming from B180 stock /rooted /xposed.....
1.) i flashed all possible partitions i had extracted (HuaweiExtractor) from B180. (system; cust; boot; recovery)
2.) reboot
3.) i flashed full rom B180 from folder dload (vol up&down&power) to be sure to get really all parts of firmware!
4.) reboot
5.) local update b190.zip from folder dload
6.) reboot
7.) i flashed twrp rc3 with fastboot to recovery partition
8.) had rooted and installed xposed now
all works as expected! Now i am on B190.
at least i had to install some modifications to system again and recover my data partition (twrp)
all in all nearly 1 hour hard work!
non-toxic said:
coming from B180 stock /rooted /xposed.....
1.) i flashed all possible partitions i had extracted (HuaweiExtractor) from B180. (system; cust; boot; recovery)
2.) reboot
3.) i flashed full rom B180 from folder dload (vol up&down&power) to be sure to get really all parts of firmware!
4.) reboot
5.) local update b190.zip from folder dload
6.) reboot
7.) i flashed twrp rc3 with fastboot to recovery partition
8.) had rooted and installed xposed now
all works as expected! Now i am on B190.
at least i had to install some modifications to system again and recover my data partition (twrp)
all in all nearly 1 hour hard work!
Click to expand...
Click to collapse
Hi,
In fact you just cleaned up your B180 in order to instal the 190 ?
The "real" B180
Pure stock if i could say ? Sure, it will work, but i tried to install it without getting back to stock^^
uff 1 hour to achieve upgrade... pity that I have to do factory reset to make upgrade to b190, no root no open bootloader no changes to firmware despite all this I cannot upgrade normal way... very sad, bad job honor(huawei)
because i had made a backup of my apps and data with the HUAWEI backup app (update to version from PlayStore is necessary!) recovery was easy! Had to remove some blood ware and unused apps only!
then reinstalled PMplus; managed autostart and apps they should stay on if screen is off.
reinstalled my google account
all in all a little bit more than 1 hour like i told you
now i am on b190 rooted; xposed and xprivacy activ on; and of curse Viper4Android for better sound.
real easy!
Kikito94 said:
Hehe 'cause u said "i released"
Okay okay thank's for sharing
I will try it, maybe one day
Edit 1 : i decided to install it, so i removed su, put recovery stock back but error too, i don't think a miss something, keep trying...
Click to expand...
Click to collapse
How did you update it? if you were rooted then you have to flash img files manually first before doing a three button update.
DigiGoon said:
How did you update it? if you were rooted then you have to flash img files manually first before doing a three button update.
Click to expand...
Click to collapse
Hi,
I tried a lot a thing, but i prefer stay in B180 i got backup corrupted, i thought it was due to the switch version but no, so, tried via sd, internal, 3 buttons, after that an error occured, "recovery partition missing"
Well i've reset everything from B100 to get back to B180, after that, tried ota researching, but it only find the B371 doesn't matter ^^
Kikito94 said:
Hi,
I tried a lot a thing, but i prefer stay in B180 i got backup corrupted, i thought it was due to the switch version but no, so, tried via sd, internal, 3 buttons, after that an error occured, "recovery partition missing"
Well i've reset everything from B100 to get back to B180, after that, tried ota researching, but it only find the B371 doesn't matter ^^
Click to expand...
Click to collapse
Yes, as B371 is the latest one so they will push B371 only, now there are no incrementals. But I have put up a thread here, maybe sometime later I'll post the OTAs too.
Sent from my PLK-L01 using Tapatalk
Hi friends
Today I'm going to help you in unlocking the bootloader officially...
Many of us(including me) had problems in unlocking the bootloader...
It used to get stuck at 50 percent..
I had the same problem....
But here's what I did to unlock my bootloader....
Prerequisites:
1) MIUI 7.2.1 6 global beta ROM
2)mi unlock permissions on your mi account
3)Mi unlock tool
4)adb drivers
And of course RN4
Procedure:
First of all download global beta ROM from
http://en.miui.com/extra.php?mod=rom/download&r=309&mobile=no#468
It's a recovery ROM so flash it using updater app...
It will WIPE all of your internal storage so take a backup beforehand...
After flashing the beta ROM login using the same account where you've got the unlocking permission on your phone...
Now enable developer options and select USB debugging and OEM unlock
Now install the adb drivers on your pc from here
http://xiaomitips.com/download/adb-setup-v1-4-3/
After installing adb drivers download mi unlock tool from here http://en.miui.com/thread-204866-1-1.html
IMPORTANT
Now If you are using Windows 8 and above, disable the driver signature verfication on your PC... Its easy just Google it...
Now enter your RN4 into fastboot mode by pressing volume down and power button after switching off your phone...
Open MI unlock tool and login using the same account that is present on your phone..
NOTE: Dont use usb tethering of your RN4 phone for logging in to the MI unlock tool...it may result in you losing your unlocking permission... I dont know if its a bug or something but it happened twice with me when I used my RN4 for usb tethering...
I may be wrong but its always good to be on the safer side :laugh:
Now MI tool will check if your account has the unlocking permissions....
If it does then it will tell you to connect your phone to pc...
Connect it using USB cable in fastboot mode....
Wait for a few seconds as the drivers will be installing on your pc...
When the drivers are installed A "Connected" message will be displayed...
Now we are good to go...
Just press on unlock option...
Now If you followed all the steps carefully and also if you are lucky,your bootloader will be unlocked...
the process may take upto 10-15 seconds
IF IT STILL DOESNT UNLOCKS,
Switch on your phone and enable find device on your phone....
Go to i.mi.com and login to your MI account
click on find device option...
Enable data connection on your phone...
Now click on your device on find device page....
It will start locating your device...
once it is located properly try to unlock your bootloader again using MI unlock tool...
IF IT STILL DOESNT UNLOCKS,
then try again after 7 days...
because PATIENCE IS BITTER,BUT THE FRUIT IS SWEET!!!
Precautions/Notes:
1) I flashed Global Beta ROM because l was unable to unlock my bootloader on Global Stable version... First try in Global stable again after 4-5 days before flashing a Beta ROM...
2)I unlocked my bootloader on the same day I flashed the Beta ROM....If you are unable to unlock then use the Beta ROM for atleast 2-3 days then try again....
3)You may use older versions of MI unlock tool if the latest tool doesnt unlock your device... I also used an older version of MI unlock tool...
4)Dont forget to disable the driver signature verfication on your pc if you are using Windows 8 and above..
5)Also check if adb drivers are installed properly;to do so connect the phone in fastboot mode,open the command window and type "adb devices" without (" ") this.. if your phone is displayed it means adb drivers are installed properly... usually the phone name will be something like 0147BDD and so on.... it will be a colection of numbers and alphabets... every device has a unique id..
if your phone is not displayed then uninstall and reinstall adb drivers....
Please note that this method has worked for me but MAY or MAY NOT work for you...
P.S. Sorry if the thread is too BIG
I hope that your bootloader will be unlocked after following these steps :good:
ALL THE BEST Fellow MIUIans :good: :laugh:
can i get ota updates after bootloader unlocked on global stable rom?
Bro!!!! hoila unlocked successfully. using the dev rom
not working. already on beta ROM from past few days
On global developer ROM from a week, yet no success. I try everyday but everytime at 50% stucks
blueandro said:
can i get ota updates after bootloader unlocked on global stable rom?
Click to expand...
Click to collapse
I'm not sure but I guess you probably will...
Else you can manually update by downloading recovery rom and flashing it.... :laugh:
janajackie said:
Bro!!!! hoila unlocked successfully. using the dev rom
Click to expand...
Click to collapse
Congratulations bro :good:
Kapiljhajhria said:
not working. already on beta ROM from past few days
Click to expand...
Click to collapse
Sorry to hear that...
Try to link your account to the device in developer options...
It may work hopefully...
ramsaicharan said:
On global developer ROM from a week, yet no success. I try everyday but everytime at 50% stucks
Click to expand...
Click to collapse
I would recommend you to link your account to your device in developer options...
leo_pard2331 said:
I would recommend you to link your account to your device in developer options...
Click to expand...
Click to collapse
I have enabled USB debugging, OEM unlocking and I do link everytime before unlocking, yet it gets stuck there
Try after five days. It will work
leo_pard2331 said:
Sorry to hear that...
Try to link your account to the device in developer options...
It may work hopefully...
Click to expand...
Click to collapse
unlocked without linking the device from developer option. changed sim cards and used only one sim card. maybe it was luck or using the registered sim in slot 1 and as the only sim did the trick.
Kapiljhajhria said:
unlocked without linking the device from developer option. changed sim cards and used only one sim card. maybe it was luck or using the registered sim in slot 1 and as the only sim did the trick.
Click to expand...
Click to collapse
Way to go bro!!!
Congo...
ramsaicharan said:
I have enabled USB debugging, OEM unlocking and I do link everytime before unlocking, yet it gets stuck there
Click to expand...
Click to collapse
Just remove all the SIM cards and insert the registered SIM in slot 1...
It worked for Kapiljhajharia who have commented on this thread... If it still doesn't work then try again after 4-5 days...
All the best :good:
@leo_pard2331 the global beta ROM link is not working on the avob
Can I download the latest one v7.3.2 from the below link??
http://en.miui.com/download-309.html
Triggered from rn3
amitroutray said:
@leo_pard2331 the global beta ROM link is not working on the avob
Can I download the latest one v7.3.2 from the below link??
http://en.miui.com/download-309.html
Triggered from rn3
Click to expand...
Click to collapse
Yes you can...
Any beta ROM will work...
All the best!!! :good:
leo_pard2331 said:
Yes you can...
Any beta ROM will work...
All the best!!! :good:
Click to expand...
Click to collapse
sorry bro, newby question,..
when i need disable the driver signature verfication, "before install all the driver" or "after install driver, (disable driver sig.) then open mi unlock,."
thanks bro...
teguhwidi said:
sorry bro, newby question,..
when i need disable the driver signature verfication, "before install all the driver" or "after install driver, (disable driver sig.) then open mi unlock,."
thanks bro...
Click to expand...
Click to collapse
Disable it before opening mi unlock tool...
The order doesn't matter but I recommend you to disable it before installing all the drivers...
Configure account mi cloud / new insert account mi cloud ?
Akta_ar said:
Configure account mi cloud / new insert account mi cloud ?
Click to expand...
Click to collapse
Sorry bro I didn't get your question...
Please be more specific....
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
luizflb said:
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
Click to expand...
Click to collapse
Whats the link for the manual download, ill experiment with it when i can update
Sm0k3r83 said:
Whats the link for the manual download, ill experiment with it when i can update
Click to expand...
Click to collapse
i used this link: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.245707268.1656347377.1488140054
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
same issue here. I can't update both with trwp and stock recovery. Originally my zenfone 3 was TIM SKU. Should be that the reason?
Hai.... someone could help me, I need recovery.image for asus ze520kl
zulfikarbugis said:
Hai.... someone could help me, I need recovery.image for asus ze520kl
Click to expand...
Click to collapse
mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Same issue here =(
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Updating thru TWRP results in an Error 7.
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
You did not understand, I installed the original recovery, both the last version of 6.0 and the version of 7.0, all install the update without error, but when it goes online does not work and I have to go back to the previous version
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
I have the same problem .. is there who can help?
`same problem can't update to nougat but my error is signature verification
hope someone can help us both
---------- Post added at 11:00 AM ---------- Previous post was at 10:48 AM ----------
Sm0k3r83 said:
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
Click to expand...
Click to collapse
Did you unlocked before updating?
same problem here....i downloaded the update and put it in internal storage...it automatically detected system update but when i try to update it it failed during installation....anyone help pls
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
ExperienceTesla said:
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
Click to expand...
Click to collapse
This works well? I have unlocked the bootloader and root my device. if this works for it?
zulfikarbugis said:
This works well? I have unlocked the bootloader and root my device. if this works for it?
Click to expand...
Click to collapse
The solution to the picture is Flash through the course
JadeKubPom said:
The solution to the picture is Flash through the course
Click to expand...
Click to collapse
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
zulfikarbugis said:
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
Click to expand...
Click to collapse
mine does the same even with the right update-script.
When i try to update using stock recovery i get failed signature message
Folks - Please do read carefully
One UI 4 Beta is live for Note 20 Ultra in US (Unlocked devices)
This Beta is for SM-N986U1 only
Open up the Samsung members app it will show if there is an update available. Update the app.
After update see the top banners as in my screenshot. Tap on that and sign up for Beta. In case you don't get the sign up banner, see below.
Beta 1 - I was able to capture One UI4 Beta 1 OTA link
Beta 2 - This enables esim on U1 (Unlocked) - One UI4 Beta 2 OTA link
Beta 3 - One UI4 Beta 3 OTA link
Google pay is not working on Beta 1, 2 and 3.
Pre-requisite - To flash Beta 1 you need to be on firmware N986U1UES2DUJ7
Beta 2 should only be flashed after you are on Beta 1
Beta 3 should be flashed only when you are on Beta 2
Just download by clicking the link rename it to update.zip and flash it either through recovery or by using ADB.
If you don't want to download using OTA link, rename etc our good friend @kangi26 has uploaded the beta versions along with the instructions to flash here in the post 3 of his thread along with many other firmwares.
Fair warning flashing through recovery or ADB may wipe your device.
To avoid Wipe (ATT users on U1 firmware) do the following: (Thanks @DevVorteX
Remove SIM
open phone app, dial *#272*IMEI#
Replace IMEI with your IMEI number which you can copy from settings
This brings up service menu
Select XAA
Click Install
Select "Sales&Network Code Change"
Hit the "OK" button
Your phone will restart
When it came back up, I checked in software info and it was XAA/XAA/ATT,XAA (whatever that means)
Reboot to recovery
Sideload the beta via adb
Let it do it's thing and reboot (keep sim out the whole time)
When it boots up, you're good to go
Put the SIM back in, and it'll prompt you to reboot
That's it. No more wipes.
Beta registrations are closed for now as it's full.
That's not available to me yet. And the link doesn't appear to go anywhere for me
I was able to download the .bin file, Will try to get a flash (or will wait until I get the beta sign up option)
kangi26 said:
I was able to download the .bin file, Will try to get a flash (or will wait until I get the beta sign up option)
Click to expand...
Click to collapse
That's correct you should be able to rename it update.zip and flash. Try cleaning members app cache and data And restart the app.
kangi26 said:
I was able to download the .bin file, Will try to get a flash (or will wait until I get the beta sign up option)
Click to expand...
Click to collapse
For those having trouble downloading it, just copy and paste the link into ADM
@warriorvibhu thanks man! Much appreciated
warriorvibhu said:
That's correct you should be able to rename it update.zip and flash. Try cleaning members app cache and data And restart the app.
Click to expand...
Click to collapse
Grazie, I might give the update.zip a shot.
I did the clear cache/and did the Data too, no joy
Well, pulled the trigger. Lets see if I break anything
I'll report back when it's done updating (Still no joy on the Samsung Members)
So it took about 5-10 min to update, and it DOES wipe. But looks good so far, setting up now. I suspect that without signing up for the Beta, it MAY not get updates. It's been a LONG time since I've run a beta and it's hard to remember
kangi26 said:
So it took about 5-10 min to update, and it DOES wipe. But looks good so far, setting up now. I suspect that without signing up for the Beta, it MAY not get updates. It's been a LONG time since I've run a beta and it's hard to remember
Click to expand...
Click to collapse
Can you check if Google Pay is working?
T33H00 said:
Can you check if Google Pay is working?
Click to expand...
Click to collapse
I'll take a look when if finishes updating everything.
Also as a side note, it appears that there is a BP app available in the Samsung app store for Sammy Watches "My BP Lab"
warriorvibhu said:
That's correct you should be able to rename it update.zip and flash. Try cleaning members app cache and data And restart the app.
Click to expand...
Click to collapse
Is there any chance this'll wipe my device. I'm on the unlocked (U1) firmware, but on an ATT device on an ATT sim. I know there used to be something dumb where ATT somehow forced wipes for sideloaded updates. Since I flashed U1 via oden I shouldn't have to worry about that right?
What firmware are you in? is it DUJ7?
kangi26 said:
Also as a side note, it appears that there is a BP app available in the Samsung app store for Sammy Watches "My BP Lab"
Click to expand...
Click to collapse
OH doesn't look like a Sammy app. Looks like a third party app.
DevVorteX said:
Is there any chance this'll wipe my device. I'm on the unlocked (U1) firmware, but on an ATT device on an ATT sim. I know there used to be something dumb where ATT somehow forced wipes for sideloaded updates. Since I flashed U1 via oden I shouldn't have to worry about that right?
Click to expand...
Click to collapse
I have no idea why I quoted you, sorry.
T33H00 said:
Can you check if Google Pay is working?
Click to expand...
Click to collapse
It's not working for me. Samsung pay works fine.
DevVorteX said:
Is there any chance this'll wipe my device. I'm on the unlocked (U1) firmware, but on an ATT device on an ATT sim. I know there used to be something dumb where ATT somehow forced wipes for sideloaded updates. Since I flashed U1 via oden I shouldn't have to worry about that right?
Click to expand...
Click to collapse
If you use the Update.zip method, it will 100% wipe, I can't speak to updating via the Samsung Members
kangi26 said:
If you use the Update.zip method, it will 100% wipe, I can't speak to updating via the Samsung Members
Click to expand...
Click to collapse
No wipe via Samsung members app.
So it seems update.zip method wipes. (did you do ADB or recovery)
I was in older firmware upgraded to DUJ7 and its flashing. so far so good.
kangi26 said:
So it took about 5-10 min to update, and it DOES wipe. But looks good so far, setting up now. I suspect that without signing up for the Beta, it MAY not get updates. It's been a LONG time since I've run a beta and it's hard to remember
Click to expand...
Click to collapse
It's been so long since I've beta tested, I can't remember. Does it come with the Samsung Members Beta apk? What happens when you log in to it?