So i recently got the prompt to install zui 11.5 on my phone and got it installed relatively fine. Download took around 15 minutes and required 1 gb of storage. After downloading, i installed the OTA update and my phone did its thing. After around 3 minutes, the installation was done and my phone is now stuck at the lenovo logo. I have been waiting for around 30 minutes but it does not boot up properly yet? I have a CN rom and is the not a custom rom whatsoever so im not sure what caused the problem. Any help would be greatly appreciated.:crying:
Before the update, does your phone show a warning screen? If so, the bootloader was unlocked previously.
You might need to unlock the bootloader again as some OTAs relock the bootloader. However if you unlock the bootloader, it will factory reset the phone.
No i did not see any warning before. My phone previously came with an unlocked bootloader and had a global rom. I flashed a CN rom to receive OTA and it worked fine as I was able to receive updates. But when I received the Zui 11.5 update, it told me that my bootloader was locked whenever i booted into fastboot.
batgoon said:
My phone previously came with an unlocked bootloader and had a global rom. I flashed a CN rom to receive OTA and it worked fine as I was able to receive updates. But when I received the Zui 11.5 update, it told me that my bootloader was locked whenever i booted into fastboot.
Click to expand...
Click to collapse
Expected behavior, this is also reported in the 4PDA thread. That's why the update from 11.1.021 to 11.5.xxx relocks bootloader.
5.134/5.141/5.223 can be done directly from 1.021, while 1.021 -> 5.141 -> 5.182 -> 5.199 can be done sequentially. But all will have the effect of relocking the bootloader.
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
batgoon said:
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
Click to expand...
Click to collapse
Do you have a solution?
batgoon said:
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
Click to expand...
Click to collapse
From 4PDA: http://fmdl.ota.lenovomm.com/dls/v6...145.1_Q_ZUI_11.5.223_ST_200401_WC1D538160.zip
Haven't tested so am not sure if stock recovery would allow this. I myself am still on 5.182 because I don't want an update to relock the bootloader and I don't want to reformat my phone when I unlock the bootloader again.
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
How the steps you done?
How the Steps you've done already?
batgoon said:
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
Click to expand...
Click to collapse
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing.
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing (E.G like flashing the wrong rom or unsupported rom)
Try so many times but not helped
I try so many times using thats tutorial but I stucked in Sahara Fail,
How to resolve this? I have tried so many times.
batgoon said:
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing (E.G like flashing the wrong rom or unsupported rom)
Click to expand...
Click to collapse
Standard QFIL Troubleshooting
Adapted from 4PDA using Google Translate
0) Check if Qualcomm drivers are properly installed
1) QFIL must be run in Administrator mode
2) The path to the folder with the firmware is too long/contains special characters -- unzip the firmware in C: /
3) Use the original cable
4) Change the USB port
5) Redownload QFIL version 2.7.453 from another site, uninstall existing QFIL , clean Program Files (x86) \ Qualcomm, ProgramData \ Qualcomm, AppData \ Roaming \ Qualcomm folders, install QFIL
6) In Device Manager, the hardware item may have a triangle with an exclamation mark. Reinstall drivers using the "Disable driver signing enforcement" mode and try QFIL again without rebooting
7) The file system type in QFIL is by default on emmc. Change to ufs, restart QFIL and try again
8) Turn on flight mode
9) Turn off antivirus
10) In the Configuration check “Use verbose”
Some steps need some more Googling. Hope this helps.
Same problem here
Bailey00 said:
I try so many times using thats tutorial but I stucked in Sahara Fail,
How to resolve this? I have tried so many times.
Click to expand...
Click to collapse
I cant get out of sahara fail too the first time i did it 2 months ago it worked first time. someone have any ideas how to make it work again ? edit: Factory reset would help? edit2:after unlock the bootloader again he did boot normaly and now I have android 10 hope it helps anyone.
I also got the sahara error on my first time. If you got the sahara error, you just have to make sure you press the volume Up, Down and Power button all at the same time. Afterwards, it is very important to quickly connect your phone to the cable attached to the Pc. The sahara error occurs when you are too slow at that process.
I've done this around 5 times and successfully flashed other firmware on my phone. You could also try changing the cable or port that you are using. Checking if you installed the drivers correctly and followed the options in Qfil.
But from what I saw from other threads, sahara error mostly occurs if you are not fast enough at connecting the cable after pressing the buttons.
batgoon said:
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
Click to expand...
Click to collapse
Can you give me the steps to update zui 11.5 like you did, pls...
I followed the steps stated in here but instead of using the stock firmware, I used the Zui 11 stock firmware.
https://forum.xda-developers.com/z5-...ro-gt-t3915945
After flashing the Zui 11, check your system update again and it should prompt you to install Zui 11.5. If you got into a boot loop again, I would recommend to reflash the Zui 11 stock firmware again. Flashing it again fixed the bootloop. Goodluck:good:
Related
https://support.t-mobile.com/docs/DOC-28979
Pushed out December 5th, H81120x, just over 79MB, described as "Google monthly security enhancements".
I've forgotten where OTA update files are downloaded too. Can anyone refresh my memory?
Thanks!
This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.
pizzaboy192 said:
This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.
Click to expand...
Click to collapse
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.
raptorddd said:
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.
Click to expand...
Click to collapse
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.
pizzaboy192 said:
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.
Click to expand...
Click to collapse
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.
raptorddd said:
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.
Click to expand...
Click to collapse
I just checked and no updates yet. Maybe Xposed and magisk are messing with it.
Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.
thejaredhuang said:
Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.
Click to expand...
Click to collapse
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
is there a KDZ available yet? maybe you need to do a refurbished flash of KDZ. 20x
pizzaboy192 said:
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)
Click to expand...
Click to collapse
I'm not rooted so no worries. Its there a stock recovery image somewhere or do i need to extract one from the 20v kdz
So is there a directory where the OTA is downloaded to? I have the KDZ for 20v but I can't get a valid cab file to extract the DZ when I use LGExtractor (this is when I'm trying to extract the stock recovery.img).
Update file
Here is the update file for 20x, i extracted it from the /cache directory. I tried to flash it via TWRP but there is some ID checker that errors out and fails to install on TWRP
https://1drv.ms/u/s!AvCSuR2bvtpdg9tZBW-m9yVP6gYGng
For help about root
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x
Somnathdey said:
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x
Click to expand...
Click to collapse
THIS MIGHT FACTORY RESET YOUR PHONE. BE SURE YOU ARE OKAY WITH THAT.
1: make sure you've enabled Developer Options in settings (go to About Phone, tap the Build Number a bunch until it pops up saying you've enabled developer options.
2: Make sure you've enabled bootloader unlock in Developer options
3: make sure your device's ADB drivers are installed. The phone comes with the resource CD built in, so you can always use that to make sure it is set up
4: run ADB on your computer, type adb reboot fastboot to get into fastboot mode. The phone should reboot. If it does not, recheck steps 1, 2, and 3.
5: type "fastboot oem unlock". This it should report it as OK or Success. If so, type fastboot reboot. It may or may not factory reset your phone at this point. It didn't with mine but YMMV.
6: once Android has booted, follow the steps to install TWRP. Same steps as above but you'll be booting a TWRP image instead and then flashing it.
For help about root
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb
Somnathdey said:
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb
Click to expand...
Click to collapse
Sure thing. You'll get more help though posting a new thread instead of on one unrelated.
gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
No problem here, try to reset the phone or at least clear the cache of camera.
So my phone finally presented me with the OTA, but it fails to install because of TWRP (expected). I grabbed the update.zip and did the basic modification to allow me to flash it via TWRP but it still fails. LG Bridge doesn't get past checking software version. I am running stock, rooted with Magisk, RCTD removed and some minor root-free debloat (The "uninstall apps for user 0" trick)
What LG OEM apps are required to get LG Bridge to work?
Edit: Could I dirty flash a full stock ROM over it (including stock recovery) to get the OTA to work and then just debloat again?)
Does the KDZ file only come from LG? I wonder if I can update and then somehow extract KDZ to share with everyone...
Hi, after receiving the phone today i tried following this guide to install custom ROM -
. I got stuck at trying to unlock the bootloader and after trying that for the 3rd time i got a notification that the system is corrupted (or something along those lines) and now it is in bootloop. It can be detected in XiaoMiToolV2, I can also hear that my PC detects it when i plug it in, but i can't find a way to unbrick it. I read that i should wait a week to be able to unlock the bootloader. When trying to unlock it (while in bootloop) I'm getting the same message as before, when the system was still working. Does that mean that I could just wait 7 days and then it would allow me to unlock the bootloader and progress with installing another ROM? Or should I try something else?
Hazoq said:
Hi, after receiving the phone today i tried following this guide to install custom ROM -
. I got stuck at trying to unlock the bootloader and after trying that for the 3rd time i got a notification that the system is corrupted (or something along those lines) and now it is in bootloop. It can be detected in XiaoMiToolV2, I can also hear that my PC detects it when i plug it in, but i can't find a way to unbrick it. I read that i should wait a week to be able to unlock the bootloader. When trying to unlock it (while in bootloop) I'm getting the same message as before, when the system was still working. Does that mean that I could just wait 7 days and then it would allow me to unlock the bootloader and progress with installing another ROM? Or should I try something else?
Click to expand...
Click to collapse
Try flash stock - the same rom you had with miflash.....thats the best way for now....can you enter fastboot mode? Volume down+power? If so you are saved then
I tried many times, but whenever i do that it just shows Xiaomi logo and them shows the fastboot image.
About that flash stock - can i do that with locked bootloader? I did try installing another rom and the phone itself is detected but the bootloader prevents me from installing it. I think I'll just wait those 2-3 days left until it's been week since adding the phone to my account and will try to unlock the bootloader. That should work, right?
Hazoq said:
I tried many times, but whenever i do that it just shows Xiaomi logo and them shows the fastboot image.
About that flash stock - can i do that with locked bootloader? I did try installing another rom and the phone itself is detected but the bootloader prevents me from installing it. I think I'll just wait those 2-3 days left until it's been week since adding the phone to my account and will try to unlock the bootloader. That should work, right?
Click to expand...
Click to collapse
Yes, you can flash the MIUI stock ROM with a locked bootloader. I'd recommend doing that first.
So yesterday i managed to unlock the bootloader and install the fastboot rom from xiaomi.eu. Everything works great, but I have one question - after the installation i can see that there is newer version in miui system update. Is it safe to update it from there or should i just stick to official roms from xiaomi.eu? Will updating this way revert everything to chinese version (Suggested update is 3.9GB, with the name on MIUI 12.5 V12.5.13.0.RKBCNXM)
Hazoq said:
So yesterday i managed to unlock the bootloader and install the fastboot rom from xiaomi.eu. Everything works great, but I have one question - after the installation i can see that there is newer version in miui system update. Is it safe to update it from there or should i just stick to official roms from xiaomi.eu? Will updating this way revert everything to chinese version (Suggested update is 3.9GB, with the name on MIUI 12.5 V12.5.13.0.RKBCNXM)
Click to expand...
Click to collapse
You need install twrp recovery and then update to 12 5.13eu
Hazoq said:
So yesterday i managed to unlock the bootloader and install the fastboot rom from xiaomi.eu. Everything works great, but I have one question - after the installation i can see that there is newer version in miui system update. Is it safe to update it from there or should i just stick to official roms from xiaomi.eu? Will updating this way revert everything to chinese version (Suggested update is 3.9GB, with the name on MIUI 12.5 V12.5.13.0.RKBCNXM)
Click to expand...
Click to collapse
The update is directly from xiaomi.eu it will not revert you backcto stock
Hi recently I tried to install TWRP on my xiaomi 12 pro but instead it made my phone stuck on fastboot, I used mi flash to flash it to the normal rom but it said something about it being not supported so I picked wipe date on the phone and tried to install a different version but, now apparently the phone is locked and I do not know how to unlock it to flash it again. any help will be appreciated please.
Things I've tried
fastboot oem unlock
fastboot flashing unlock
Mi flash - I cant flash because the device is locked and I have not logged in with a Mi account.
XiaoMiTool v2
Flashing twrp again
Ritual224 said:
Hi recently I tried to install TWRP on my xiaomi 12 pro but instead it made my phone stuck on fastboot, I used mi flash to flash it to the normal rom but it said something about it being not supported so I picked wipe date on the phone and tried to install a different version but, now apparently the phone is locked and I do not know how to unlock it to flash it again. any help will be appreciated please.
Things I've tried
fastboot oem unlock
fastboot flashing unlock
Mi flash - I cant flash because the device is locked and I have not logged in with a Mi account.
XiaoMiTool v2
Flashing twrp again
Click to expand...
Click to collapse
Which version?
So as not to make the same mistake again if we manage to save the phone.
Which TWRP and which command.
For Miflash you have probably left the flash and lock box checked.
If you could post the Miflash log (Miflash log folder)
I used this guide to install twrp
I put global rom instead of europe rom which came with my phone
I do have another xiaomi device I was wondering it I could somehow transfer the account to my bricked phone then flash it that way
Ritual224 said:
I used this guide to install twrp
I put global rom instead of europe rom which came with my phone
I do have another xiaomi device I was wondering it I could somehow transfer the account to my bricked phone then flash it that way
Click to expand...
Click to collapse
Is the version of your phone Chinese with a Xiaomi EU rom?
I bought it from Here
It says in the description that 'The initial Chinese version has been updated to a global ROM.'
so I'm not sure when I got it I checked the rom and it said the Europe version I tried to update the version but when it was ready to install it said 'your device supports twrp' and I clicked ok to the instructions and when the device booted back up it was in recovery mode and I pressed restart and no updates were made.
Ritual224 said:
I bought it from Here
It says in the description that 'The initial Chinese version has been updated to a global ROM.'
so I'm not sure when I got it I checked the rom and it said the Europe version I tried to update the version but when it was ready to install it said 'your device supports twrp' and I clicked ok to the instructions and when the device booted back up it was in recovery mode and I pressed restart and no updates were made.
Click to expand...
Click to collapse
It is a Chinese version.
post the Miflash log (Miflash log folder) so I can check what you did.
The log is between 20 and 25 KB and starts like this
[23:28:45 eeab043a]:MiFlash 2020.3.14.0
[23:28:45 eeab043a]:vboytest index:1
[23:28:45 eeab043a]:idproduct: 53261 idvendor: 6353
I think I deleted the one that I used I was on my i've just given up after hours of trying to fix it
Ritual224 said:
I think I deleted the one that I used I was on my i've just given up after hours of trying to fix it
Click to expand...
Click to collapse
You have used Miflash look here if you have ticked the right box.
The last paragraph.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Yes I selected that clean and lock device after that I restarted then it went to the recovery mode and gave me the rom isnt supported on your device and I clicked wipe data now were here. I'm trying to get out of this mode idk how I can
Ritual224 said:
Yes I selected that clean and lock device after that I restarted then it went to the recovery mode and gave me the rom isnt supported on your device and I clicked wipe data now were here. I'm trying to get out of this mode idk how I can
Click to expand...
Click to collapse
As you have on my tutorial, this is the mistake not to do with a Chinese device.
Now to be sure, flash a Chinese rom with Miflash by checking the Clean all box.
Either the phone works again or not, Miflash will give you the error, surely 'lock state'
yes it says failed remote: erase is not allowed in lock state, im trying to get out of that mode I need help with that
Ritual224 said:
yes it says failed remote: erase is not allowed in lock state, im trying to get out of that mode I need help with that
Click to expand...
Click to collapse
I will send you a PM.
NOSS8 said:
I will send you a PM.
Click to expand...
Click to collapse
Hi! I have the same exact issue. Any help would be really appreciated.
toulan said:
Hi! I have the same exact issue. Any help would be really appreciated.
Click to expand...
Click to collapse
I will send you a PM.
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
Developer options USB debugging is activated?
Search for flashing instructions in this forum for your preferred ROM and it's easier to flash Roms, in my opinion, with orange fox recovery (or TWRP)
Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?
flashernoob said:
Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?
Click to expand...
Click to collapse
Perhaps you find here ideas
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com
The Complete Guide to Flashing Factory Images on Android Using Fastboot
If your phone has an unlocked bootloader, you can use Fastboot commands to flash factory images. That may sound like a bunch of technical jargon, but when it comes down to it, this is the best method for updating a rooted device, fixing a bricked phone, reverting to stock, or even getting new...
android.gadgethacks.com
Thank you very much, your first link had a hint on the solution, thanks a lot!
I used the latest google/android fastboot 33.0.3, but tried another as to the thread posted, and the years old fastboot 1.4.3 from https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/#post-42407269 did the trick!
Never would i have thought that a 4 year old hack would work better than the latest official google file....
flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
I solved my soft brick using the 13 image files on my RN11. This got me out of a perpetual fastboot loop. (It should also work on the RN10P)
i.e. fastboot flash boot boot.img, fastboot flash super super.img etc for all 13 images.
I tried the flash_all.bat several times but it just kept borking at different spots and I needed to get out of that fastboot loop hell.
The flash_all bat works like a charm for me, there's no sense in typing all the lines one for one.
The exe seems to bork at the size of the super image, the RN8 hadn't such a thing, the RN10 has a 7G file the exe couldn't stand, obviously.
At least it did CRC error repeatedly, with different ROMs, all at the 7 of 10 or 7 of 11 stage...
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.