Related
Hi y'all!
I'm really having trouble flashing an official stable rom on my device. The rom archive is miui_HM3_V7.3.2.0.LHPCNDD_6a5e1bc33c_5.1.zip.
I downloaded it and copied it to a folder (downloaded_rom) on the internal storage of my redmi 3. After selecting it in the updater app I get asked whether it's OK to delete all data, because the rom I'm updating to is older than the one installed. My phone's miui version is MIUI 77. Stable 77.1.1.0 (LHPCNCK). The doble 7s seem odd to me and may be part of my problem (I bought the phone like that). Then, the device is rebooting and I can see some kind of progression bar for a couple of seconds on the botton of the screen but then it just reboots into android and nothing changed
I also tried to flish it via Mi PC suite. Here, after connecting the device in fastboot mode, I got the message that my device isn't supported.
I also believe that the bootloader is locked and I already got the "permission" from xiaomi to unlock it but I had no luck with this either. The Mi unlock tool is telling me, that the "current account is different from the account info on the device" which wasn't the case after I double checked.
Am I missing something here?
kind regards
lunatikk
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Ice Zodiac said:
yes.
because you are currently in modified rom (rom supplier or seller, etc, etc) you cannot update or do anything about it
flash the official rom using miflash method
after that you can update using updater program
Click to expand...
Click to collapse
I'll try that and report back. Thanks!
Okay, finally I managed to flash my phone with the newest miui.eu rom. What I did was:
- Flashing the official Xiaomi Rom (MiFlash package) via MiFlash (1st try in Win32 wasn't working. 2nd try on Win64 did the job)
- I had to update to the newest official stable OTA, because somehow, I wasn't able to unlock my bootloader with the older version.
- I unlocked the bootloader using the MiFlashUnlocker.
- Updated to the official MIUI 8 dev rom using updater app on my phone
- On dev rom I granted root acces to flashify and flashed the twrp recovery image on my device (which gets wiped from my device every time I reboot - anyone knows why??)
- Reboot into recovery and flash the MIUI.eu zip which is now running on my device.
Thanks for the help guys!
Hi.
I am having the same problem, with pre-installed rom: MIUI 77.1.1.0 Stable. The updater app obviously doesn't work (now i know why) and the MiFlash software doesn't seem to work either. It doesn't recognise the phone, browsing to the downloaded rom does nothing. Am i missing something?
Update, it now recognises the phone, but miflash is saying it can't find the file specified (0x80070002: Execute flash_all.bat)
Thanks for any assistance you can give.
Update 2. Just found out you need a different version of the Rom for fastboot. available from http://en.miui.com/a-234.html for anyone searching.
Okay so Miflash began the process when i had the Fastboot rom, but failed at about 2 percent as the device is locked.
Although i have permission the Mi unlock tool won't unlock my phone as it says the accounts don't match that on the phone, although i have quadruple checked them.
Research suggests it might be a problem with the custom rom on my phone, or that i need to be on the China Dev rom to unlock?
But i can't flash the China Dev Rom!!!
Is there any way to get my device to stock rom?
Sorted.
For the benefit of anyone searching, i followed the instructions here: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=242867&pid=4510751
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
x23are said:
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
Click to expand...
Click to collapse
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
GENiU5 said:
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
Click to expand...
Click to collapse
tnx for reply but my problem is i cant flash.
my bootloader is locked and i cant flash fastboot rom.
therefor i must use edl mode or updater app but both of them don't work as a said in first post.
You don't need an unlocked BL to flash official fast boot miui ROMs
GENiU5 said:
You don't need an unlocked BL to flash official fast boot miui ROMs
Click to expand...
Click to collapse
mi flash show me : bootloader unlock in flashing process
x23are said:
mi flash show me : bootloader unlock in flashing process
Click to expand...
Click to collapse
You may try the steps on this link http://en.miui.com/thread-235865-1-1.html
Skip the EDL thing and go directly to the part where they explain how to use the miflash tool to flash a fastboot ROM
I should have asked this first... what's the state of your phone right now? Does it boot, stuck on boot loop, or are you able to boot into some ROM.
maybe u have a vendors rom, flash the fastboot rom using edl
finally a downloaded adb 1.4.3 and installed it and i flashed dev rom in EDL mode.
but now i have some questions:
can i change kernel with locked bootloader?
if i change kernel does fingerprint work?
You just dont have proper drivers installed im 100% sure, else it would go via edl
Hehe was right������
And why dont you ask for official unlock approval? Its approved in less than a day, anyone saying otherwise have old news
Or you can always use a method in this forum...
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
Hi all,
had for a few weeks already installed the Pixel Experience Rom on my Redmi Note 10. Unfortunately, the phone could not be started yesterday (Google logo has not stopped loading), so I wanted to install the Xiaomi EU Rom via TWRP. I had probably done a lot wrong at the time of installation and that is now avenged.
About ADB / Fastboot I managed to get TWRP on my phone, but that was it. I can not get the ZIP "xiaomi.eu_multi_HMNote10_V12.5.4.0.RKGMIXM_v12-11.zip" directly from the PC to the phone. Then I put it on a SD card.
When installing I get the following errors...
Can you please help me somehow?
Thank you very much!
Best regards
sephra
sephra said:
Hi all,
had for a few weeks already installed the Pixel Experience Rom on my Redmi Note 10. Unfortunately, the phone could not be started yesterday (Google logo has not stopped loading), so I wanted to install the Xiaomi EU Rom via TWRP. I had probably done a lot wrong at the time of installation and that is now avenged.
About ADB / Fastboot I managed to get TWRP on my phone, but that was it. I can not get the ZIP "xiaomi.eu_multi_HMNote10_V12.5.4.0.RKGMIXM_v12-11.zip" directly from the PC to the phone. Then I put it on a SD card.
When installing I get the following errors...
Can you please help me somehow?
Thank you very much!
Best regards
sephra
Click to expand...
Click to collapse
First you must format the data
Twrp/Wipe/format data write YES(if red ligne error,reboot twrp and format again)
reboot twrp
flash zip rom
reboot system
If it does not work use this tool https://forum.xda-developers.com/t/guide-use-xiaomi-flash-tool.4262425/
worked perfectly with that tool, thank you so much
I used this tutorial:
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Nice
I had same problems here, but the Flash tool saved my day.
But from now on I get an message: "Gerätespeicherbeschädigung festgestellt. Das Gerät ist jetzt unsicher."
Don't know what this mean so be back on cDroid.