Related
Hi All,
You guys must be thinking why i'm sharing this recovery when we already have Official TWRP Recovery
actually this Recovery is Lil bit modified (One of my friend Found it somewhere)
via this Recovery you guys will able to Flash any MIUI Rom without Modifying/Patching Boot.img (I tested it my self)(i flashed miui global stable 7.2.3 and global dev 6.4.28)no patched boot.img required
Note:- I'm Not responsible for any kind Of damage caused to your device
Orignal Link => https://drive.google.com/file/d/0B6zD6Bewl4FmQVJGVVBOdzRmT2M/view
Password to the zip :- www.cofface.com
Instructions to flash
download the zip file (link provided)
extract The TWRP recovery.img (password given)
and flash it via flashify or Fastboot
Fastboot Command "Fastboot flash recovery "image-name.img"
yoo done
BUG:- Its not a major bug its not even a bug(i'm just considering it as a bug) but kinda annoying once you flash this recovery this recovery will change your device name from KENZO to CM_KENZO(this not gonna affect anything) but if you will try flash AOSP v4 or anyother AOSP build that verifies the Product name will give some errors
that "This build is for kenzo devices not for Cm_kenzo device"
Solution :- Open the zip in winrar and edit the updater script just change the Kenzo word with CM_Kenzo and it will work (alot of work to do right)
Another solution (this one is better i guess)
when ever you wanna flash MIUi official firmware flash this reocvery via Flashify.
flash the miui rom...
boot it up again flash the official TWRP recovery(so that you will able to flash other roms)
WARNING:- Dont flash miui rom via official TWRP recovery it will not boot untill you flash the Modify boot.img
Update
Bug fixed ===> "This build is for kenzo devices not for Cm_kenzo device"==>No Error now
Link(bug fixed) => https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Credits
Developer :- Cofface
Source :- http://www.miui.com/thread-3941604-1-1.html (orignal thread)
Special Thanks to @Rajdip for solving the bug
pls hit thanks if you guys found it helpful
what about the emmc_appsboot file ? should be remove from official rom ?
What is the zip password?? Can you share some screen shot
Anands3 said:
What is the zip password?? Can you share some screen shot
Click to expand...
Click to collapse
read my post zip password is already provided
wawan20 said:
what about the emmc_appsboot file ? should be remove from official rom ?
Click to expand...
Click to collapse
if your device is unlocked officially then No need to remove EMMC_appsboot file
but if your device is unlocked unofficially then yeah you have to dlt that file otherwise it will relock
Please add credits and source links
Rajdip said:
Please add credits and source links
Click to expand...
Click to collapse
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Ashish0077 said:
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Click to expand...
Click to collapse
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Rajdip said:
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Click to expand...
Click to collapse
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Ashish0077 said:
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Click to expand...
Click to collapse
Yeah I tested my build.. thanks
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Nice work, i will test it. Thx.
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Rajdip said:
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Click to expand...
Click to collapse
Nice to know. TWRP asked the same thing (again apparently) when I rebooted from menu to system. It also provided the option to install SuperSU (or rather install the SuperSU Installer - whatever that was worth). I'm confirmed rooted now and recovery is still TWRP after many reboots. :good:
But is 3.0.0.0
I don't understand that
meangreenie said:
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Click to expand...
Click to collapse
No it will not fix that.... actually the thing Is When we unlock Bootloader with Official method it will not get relock while flashing any rom(via recovery)(miflash can still do that) in unofficial Method we replaces the emmc file with the modified one(and when we flash any official rom this file get replaced as this one is modified and (update. Zip/miuirom.zip) does not verify that emmc and relocks the boot loader....
What This recovery does is...
Miui roms inculde some recovery verification On The first boot
Which means it will replace twrp with the stock miui recovery which will cause bootloop...
For this we need to flash the patched/modified boot.img
But This recovery is Lil modified (it auto patches the boot.img and and our recovery does not get replaced and yoo thats how this recovery successfully flashes miui without a patched boot.img
Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
Mine was in english Only on first Boot too?? But yeah i didnt use fastboot to flash was not in mood to turn on my pc.... I flashed it vai flashify and it the recoverg was in english by default and ymyou can flash it via twrp itself..
Anyways Thnx For Reporting This and giving solution
jujusito said:
But is 3.0.0.0
I don't understand that
Click to expand...
Click to collapse
Does that really matter?? Actually i dint face any problem with this recovery and atleast we can flash Miui roms without patching Boot?? And what you dont uderstand??
Its just an old version of twrp as iwas unablefound any updated one
As soon as i get it i will update here...
can I flash this recovery in current TWRP?
Sent from my kenzo using Tapatalk
Hello all, i unlocked the bootloader on the xiaomi mi A2 , and i was trying to follow this guide :https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475 to install the gmcam, but after the point 5. i just rebooted the phone from the recovery, just cause i wanted to try it, after that is stucked in android 8.1 animation, but i have access to the recovery (even if the tool shouldnt have installed it), but dunno what can i do from the recovery, and the device can go in fastboot mode but is not recognized by adb, what can i do?
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
What version of software was your Mi A2, if it was V9.6.13.0.ODIMIFE, then download the full stock ROM from here
http://en.miui.com/download-353.html
In fastboot mode, adb is not working, fastboot commands works there.
Extract boot.img from images of downloaded ROM.
Put the boot.img in adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
it should start normally
If not, then flash every image like in this post.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
fuffy841 said:
Thanks for the help, but, I don't know why, ADB driver were not working properly, didnt recognize the phone so I couldnt follow this guide, and i couldnt switch off the phone either, it was stuck in bootloop, the only thing I was able to do is to put the device in fastboot mode using the button combination..
Luckly the Mi Flash tool was able to recognize the device so I flashed the stock rom with that and now everything is back to normal, I've just a question, the phone sais that the bootloader is still unlocked, is that true? Even if I've flashed from zero the stock rom?
Click to expand...
Click to collapse
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
---------- Post added at 06:16 PM ---------- Previous post was at 05:31 PM ----------
rt1279_isBITW said:
I am stuck on the exact same issue. Can you explain in detail all the steps you followed.
Mine was updated to September patch and it is Indian variant.
Click to expand...
Click to collapse
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option.
Daniesz said:
Yep, it's true. You have to relock the bootloader, but this cause full wipe. IMO there's no need to relock the bootloader if you not enable the usb dev mode.
Also, theres an option in mi flash tool to lock the bootloader after flash. Something like flash_all_lock
DO NOT use flash_all_lock_crc. This will cause dead wifi and Bluetooth modem.
Click to expand...
Click to collapse
Nono i want to keep the bootloader unlocked, that's why I asked ! Thanks man.
Nvm I was able to flash that rom but now after the phone locks once the touch is gone until I reboot the device.
Are there any hardware differences in my indian variant or did I just flash it wrong?
I used flash_all.bat and clean all option
Click to expand...
Click to collapse
I used the same option, cause it didnt work with the other ones.. I didnt have any issue so far tho, and I dont know about hardware differences, but I dont think a bad flash can cause this kind of problem, not sure tho. Maybe now that everything is working try to flash again a stock rom.
Here I present you my toolkit for flashing TWRP and rooing Redmi Y2/S2/YSL.
Requirements
1. PC
2. Fastboot Drivers
3. Unlocked Bootloader (Guide)
4. Flashing TWRP Toolkit
5. Magisk flashable file
Steps for Flashing TWRP
1. Download the file. Link given in the end of the threads.
2. Boot your device into Fastboot mode (in power off state press power button + volume down button).
3. Connect your device from pc.
4. Now open the downloaded folder and run the file "Flash.bat".
5. Then press any key to continue.
6. Now your phone will automatically boot into TWRP.
7. Now you have sucessfully flashed Twrp.8. Before rebooting your device do flash lazyflasher-no-verity-opt-encrypt.zip.
Note :-
* If you don't flash Lazy Flasher then the Custom recovery will be replaced with stock recovery in next Boot.
Steps for Rooting
1. Download and place the Magisk zip fiile into your device.
2. Boot your device into TWRP Recovery (in power off state press power button + volume up button).
3. Select the option of 'Install' and then locate the directory where you have placed the Magisk file and select it.
4. After selecting the file, swipe the arrow loacted at the bottom.
5. When the flashing is completed click on 'Reboot System'.
6. After the phone has booted successfully install magisk apk.
Congrats you have rooted your device !!
Note :-
* This is Exclusively for Redmi Y2/S2/YSL and if you try this on any other device probably you may be bricking your device!!
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* First boot may take upto 15-20 mins. So don't panic.
Links :-
* TWRP Toolkit - Click here
* Lazy Flasher - Click here
* Magisk - Click here
will try this as soon i am able to unlock my bootloader, thanks!
(i hate xiaomi for locking the device for 1 month....!! )
Flashing LF ends in endless boot. No loop but endles bootscreen 1,2,3 dots endlessly! Any ideas ?
So I got stuck on Bootscreen.
I flashed MIUI with TWRP and was back on stockrom with stockrecovery.
Then I booted TWRP temporarely with ADB. (adb command: fastboot boot twrp.img )
Now I installed Magisk and I am happy now
Just DON´T install TWRP. Boot it temporarely !
I used MIUI from here: https://www.theandroidsoul.com/download-miui-10/
Screen asking for PASSWORD.
The TWRP screen asks for password. Default password does not work and after format data the files are not displayed. Same case in clicking cancel.
use xiaomi eu roms they dont ask twrp password
twrp password
Twrp asks for password. What kind of password is this? How to use twrp without the password? How to use this twrp?
Has anybody got rooted redmi s2 finally?
In particular, with stock rom?
finally yes
When TWIRP asks for password nothing helps. The only thing I could do is to wipe ALL THE PARTITIONS except for external SD card, of course. Yes , you loose everything on your phone. Now, you flash the ROM you want (I flashed the stock ROM). After that, you flash the Magisk file. It is important not to reboot in between. After rebooting you have the new system installed. After initial configuration, you have to manually install the Magisk Manager apk.
P.S. the Lazy thing is not needed. TWRP persists.
Want mbn file of unlock bootloader redmi y2
i need emmc_appsboot.mbn file of unlocked Redmi y2(s2) 's bootloader.
If someone has unlocked y2 then please send me the file.
This TWRP for Custom ROM, and if you flash on RI MIUI will not work with any method as well. Especially if you Flash LazyFlaser will certainly be bootloop (stuck on logo)
sumit17 said:
i need emmc_appsboot.mbn file of unlocked Redmi y2(s2) 's bootloader.
If someone has unlocked y2 then please send me the file.
Click to expand...
Click to collapse
for bypass UBL you can try this
Pass : firmware firmware27
danigp75 said:
for bypass UBL you can try this
Pass : firmware firmware27
Click to expand...
Click to collapse
It will bypass only or unlock it too?
sumit17 said:
It will bypass only or unlock it too?
Click to expand...
Click to collapse
unlock too
danigp75 said:
unlock too
Click to expand...
Click to collapse
Bro it is unable to detect my device. But adb commans are recognizing my device and Mi Unlock tool also detect my device.
But this Soft is not able to detect my device. Giving me error
sumit17 said:
Bro it is unable to detect my device. But adb commans are recognizing my device and Mi Unlock tool also detect my device.
But this Soft is not able to detect my device. Giving me error
Click to expand...
Click to collapse
to be able to use this application you must enter EDL mode or "TEST POINT". After devices are detected 9008 on PC, proceed with running the application. Don't forget to enter the "firmware27" password.
Hopefully it can help for UBL redmi YSL without having an official UBL.
danigp75 said:
to be able to use this application you must enter EDL mode or "TEST POINT". After devices are detected 9008 on PC, proceed with running the application. Don't forget to enter the "firmware27" password.
Hopefully it can help for UBL redmi YSL without having an official UBL.
Click to expand...
Click to collapse
For test points i have to dissemble my device. Lol, If you can give me emmc_appsboot.Mbn from unlocked device then it may can help me.
Skyfire1 said:
So I got stuck on Bootscreen.
I flashed MIUI with TWRP and was back on stockrom with stockrecovery.
Then I booted TWRP temporarely with ADB. (adb command: fastboot boot twrp.img )
Now I installed Magisk and I am happy now
Just DON´T install TWRP. Boot it temporarely !
I used MIUI from here: https://www.theandroidsoul.com/download-miui-10/
Click to expand...
Click to collapse
from where did you downloaded the ROM ?
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
shiva sandeep said:
use xiaomi eu roms they dont ask twrp password
Click to expand...
Click to collapse
Where can I download the EU roms ?
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
Novikovmex said:
When TWIRP asks for password nothing helps. The only thing I could do is to wipe ALL THE PARTITIONS except for external SD card, of course. Yes , you loose everything on your phone. Now, you flash the ROM you want (I flashed the stock ROM). After that, you flash the Magisk file. It is important not to reboot in between. After rebooting you have the new system installed. After initial configuration, you have to manually install the Magisk Manager apk.
P.S. the Lazy thing is not needed. TWRP persists.
Click to expand...
Click to collapse
from where did you download the rom ?
Israelleite said:
from where did you downloaded the ROM ?
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
Where can I download the EU roms ?
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
from where did you download the rom ?
Click to expand...
Click to collapse
From the official Xiaomi site
Israelleite said:
from where did you downloaded the ROM ?
Click to expand...
Click to collapse
The link is in the quote in the line above your question. Or am I misunderstanding you ?
https://www.theandroidsoul.com/download-miui-10/
It is about midpage, the last in the list of phones, just above the section where it says
"How to install the MIUI 10 update"
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
There is now an official version available (xda post). Go use that.
Thanks for your work
---------- Post added at 10:43 PM ---------- Previous post was at 10:37 PM ----------
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
How can I know if my device Tianma display or not?
yamabokra1 said:
How can I know if my device Tianma display or not?
Click to expand...
Click to collapse
Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer.
I don't know if it actually matters. I read here that it affects devices when using the Redmi 8a recovery. Since I forked the code and have a Tianma display I can't really look in to the problem.
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
pulka103 said:
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
Click to expand...
Click to collapse
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
pulka103 said:
Have you got MTP working while at TWRP?
Click to expand...
Click to collapse
I recompiled TWRP with MTP enabled and it seems to show up as a device but i can't access data from the device.
I installed the image via a sd-card, but usb-otg or adb push should also work.
pulka103 said:
TWRP shouted that it couldn't mount /system partition.
Click to expand...
Click to collapse
Okay I changed the default mounting point of the system partition. Try again with the new image.
yamabokra1 said:
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
Click to expand...
Click to collapse
I do have a Tianma display. Problem isn't with controls but with the TWRP itself in my case.
Just tried new image, same problem "Checking /system. /system is not mounted! Trying to mount /system RW. /system cannot be mounted. [...] Installation will be aborted."
I am using Mi-Globe right now, gonna try with "clean" Xiaomi.eu.
And still can't access storage through Windows Explorer (but device itself is seen, tested with adb).
So Xiaomi.eu installed kinda. No errors and stuff but won't boot up. After one try it just goes back into TWRP. Using V11.0.3.0 for HM8 (as described by Xiaomi.eu)
luckily, mine has TIANMA display, I'll try while my rm8 is unlocked, thanks bro
@seprode, Reading your post and seen your work, I decided and today I ordered a Redmi 8 (olive) for my self , too.
I am very thankful that there are people like you, pioneers, who open the path, for all of us to follow.
Thank you again for what you are doing for us.
I hope, soon enough, some developer will pay attention to our new phone and , maybe , we will be also able to see new Android (Q ?) roms for it.
I am active involving so far in Samsung NOTE 2(exynos) and Note 4 (snapdragon) and also Xiaomi Redmi 5 plus community
I will do my best and see, if any of these groups will be able , in the future, to do something for our little brother here.
But the path you have open, is the very important first step to it.
KUDOS
:good::good:
@pulka103 You want to try again? I made some changes and got MTP working.
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
.
Click to expand...
Click to collapse
Thank for your work !
What about vbmeta as mentioned at milankragujevic ?
And do we need something against dm_verity ?
Edit:
I did the described "simple" way and it works !!!
No need to flash anything else !!!
Great job, Thanks again :good:
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
I have a problem and maybe some of you can help me. I flashed last recovery.img. After flashing phone reboot itself and boot to system. Next, perform reboot to recovery and it boot to mi-recovery, not twrp. Then I cant boot to system. I have to flash again and then it boot to system.
===EDIT====
Ok, I managed this. After "fastboot flash recovery recovery.img" you have to type "fastboot reboot"
Great Great work I hope you continue updating. Thank you ?
good afternoon, this twrp this worked on redmi 8 olive, if it worked I will for now, obg and thank you already.: D
Ok, so ive tried to install latest xiaomi.eu rom for the redmi olive after flashing twrp, following all the steps from here and other posts, and all I get was reboot everytime. how do i go back to stock? miflash is not working and i dont find any .img to flash back
seprode said:
@pulka103 You want to try again? I made some changes and got MTP working.
Click to expand...
Click to collapse
hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
Download also i did a PR on your github with the needed changes so your next version will have this fix
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
[email protected] said:
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
Click to expand...
Click to collapse
you should try miui eu
unlock Bootloader
how can i unlock Bootloader for Redmi 8 with out Official Tool