Related
I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp
Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
same for me!
g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.
Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded
There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix
I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.
I flashed my Zenfone 5 to CM 13.1. For the first few week of usage it was perfectly fine and had no issue after after a while the phone was acting weird so I rebooted it, while it was booting up it was stuck in the Cynogenmod logo and I figured out it was a bootloop. I tried many method to bring it back to stock but failed, i even tried the methods which i used when i was suing CM 12.1.
Issues I found:
I could flash from a tool called "Zenfone Assist" and could flash from adb but when I tried to wipe from TWRP it said failed to mount /cache /system etc and many other partitions.
I tried to lock the boot loader and change the recovery back to stock, it did say "okay" in the flashboot but nothing chnaged in the phone. The bootloader was not locked and the recovery was still TWRP. I tried many methods but it stays the same. The only thing that i could wipe was the /system.
I tried to restore using the jelly bean .raw file and still no luck, it showed 2 partitions failed ( one being OEM the other I'm not sure) and its still the same, the same unlocked bootlaoder and TWRP recover.
One member here suggested that my internal storage might be corrupted.
If it is , is there any alternative way out of it and is there any other methods I could use that might work.
Much thanks for responses.
Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works
leonardohenrique10 said:
Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works
Click to expand...
Click to collapse
didnt work, it said unable to repair /data and error repairing file system.
zaris47 said:
didnt work, it said unable to repair /data and error repairing file system.
Click to expand...
Click to collapse
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?
leonardohenrique10 said:
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?
Click to expand...
Click to collapse
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4
zaris47 said:
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4
Click to expand...
Click to collapse
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
leonardohenrique10 said:
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.
zaris47 said:
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.
Click to expand...
Click to collapse
Well, your phone is really f*cked up
You already tried xfstk method?
leonardohenrique10 said:
Well, your phone is really f*cked up
You already tried xfstk method?
Click to expand...
Click to collapse
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?
zaris47 said:
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
leonardohenrique10 said:
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
Click to expand...
Click to collapse
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?
zaris47 said:
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?
Click to expand...
Click to collapse
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)
leonardohenrique10 said:
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)
Click to expand...
Click to collapse
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened
zaris47 said:
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened
Click to expand...
Click to collapse
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone
leonardohenrique10 said:
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone
Click to expand...
Click to collapse
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?
zaris47 said:
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?
Click to expand...
Click to collapse
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.
leonardohenrique10 said:
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.
Click to expand...
Click to collapse
I had errors with that 15 sec adb install drivers but the ones I've downloaded worked too I guess, I sued that to flash to CM13.1 in the first place
@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.
zaris47 said:
@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.
Click to expand...
Click to collapse
Try from another computer, preferably using Windows 7.
leonardohenrique10 said:
Try from another computer, preferably using Windows 7.
Click to expand...
Click to collapse
tried and it showed the same error, although this time i noticed that the two drivers with the asus device in device manager, one of them has a problem, the adb one it said (altho adb worked fine)
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!
I wanted to uninstall magisk so I like a dummy I pressed uninstall . The phone started bootlooping
I decided to flash the N fastboot ROM from the website and get it flash via Miflash
Miflash finishes the process in 1 second and does nothing. Neither does running the script directly. Any fixes?
SOLVED: I moved both the image folder and miflash folder to the desktop. Mi flash still didn't work
Ran the script via CMD and it worked!!
KalolParty said:
I wanted to uninstall magisk so I like a dummy I pressed uninstall . The phone started bootlooping
I decided to flash the N fastboot ROM from the website and get it flash via Miflash
Miflash finishes the process in 1 second and does nothing. Any fixes?
Click to expand...
Click to collapse
make sure it isnt sep build, because i'm facing random reboots after flashing sep build.
select "flash_all_except_storage" from the fastboot folder you have downloaded.
maybe it will help
Rawwr said:
make sure it isnt sep build, because i'm facing random reboots after flashing sep build.
select "flash_all_except_storage" from the fastboot folder you have downloaded.
maybe it will help
Click to expand...
Click to collapse
Solved! check the OP
problem is with Mi flash version 2017-7-20-0 which is downloaded from miui forum in thread about mi A1 fastboot update. I you want to flash stock rom use mi flash version 2016.08.30.0, extract ROM with 7zip on C: in folder with short name (i.e. Tissot) and make sure that you granted permission for pc to connect to your device. When you connect device to pc start cmd and type adb devices and if you see list of connected devices with serial number then you are good to go, put device to Fastboot mode and so on.
Problem is with folders containing space in their name, flashing script will fail in such case.
the problem with me was the folder name, it had white space in it " new folder".
Rawwr said:
make sure it isnt sep build, because i'm facing random reboots after flashing sep build.
select "flash_all_except_storage" from the fastboot folder you have downloaded.
maybe it will help
Click to expand...
Click to collapse
Thanks!!!!!!!!
A little late, but it might help somebody
Bruno Wagner said:
Thanks!!!!!!!!
Click to expand...
Click to collapse
I was stuck and tried to wipe all data under the Mi-boot menu (on the phone). Seems to have solved the issue with the flash not working. Using flash tool 2016.08.30.0. It took approximately 461 seconds - so about 7.6 minutes. Reboots automatically and that takes several minutes. you'll need to enter the password associated with your phone and you'll be good to go (I've had several anxious hours stuck at that menu!).
---------- Post added at 10:31 AM ---------- Previous post was at 09:46 AM ----------
Bruno Wagner said:
Thanks!!!!!!!!
Click to expand...
Click to collapse
Rookie mistake and I didn't create a backup under TWRP so I was stuck on the Mi-Boot menu (I think that's what it's called) so after getting into the fastboot mode I tried to flash with the Mi Flash Tool with no luck. I figured I was already doomed, so I took leap and selected the option to wipe all data under the Mi-boot menu. That solved the issue with the Mi Flash tool not working. I am using flash tool 2016.08.30.0 because I read somewhere that it worked better - apparently that's true.
Flashing took approximately 461 seconds - so about 7.6 minutes. Reboots automatically and that takes several minutes. You'll need to enter the password associated with your phone to activate (not the screen unlock code, the password you set up with Xiaomi to unlock) and you'll be good to go (I've had several anxious hours stuck at that menu!).
One thing I've found that isn't really mentioned in any of the tutorials - after you install the adb drivers, etc. reboot your computer.
Hope this helps!
THANK YOU!
moved all files and folders to C:\
and now it flashed properly.
before on E:\ djust 1s....then nothing
How to run it through cmd??
KalolParty said:
I wanted to uninstall magisk so I like a dummy I pressed uninstall . The phone started bootlooping
I decided to flash the N fastboot ROM from the website and get it flash via Miflash
Miflash finishes the process in 1 second and does nothing. Neither does running the script directly. Any fixes?
SOLVED: I moved both the image folder and miflash folder to the desktop. Mi flash still didn't work
Ran the script via CMD and it worked!!
Click to expand...
Click to collapse
How to run it through cmd??
MIHIR_1999 said:
How to run it through cmd??
Click to expand...
Click to collapse
There are .bat scripts once you extract the images.
Just open CMD
Navigate to the folder using the cd command
Type the name of the file and press enter. For example :
clean_install.bat
Flash success in 1s error
I tried to flash miui 9.2.4.0 neimiek for my redmi note 5 pro (whyred).
I used official mi flash tool but I got nothing and flashing is done in 1s.
I tried to move the stuffs to c:/drive but nothing worked...
Please help me.
KalolParty said:
There are .bat scripts once you extract the images.
Just open CMD
Navigate to the folder using the cd command
Type the name of the file and press enter. For example :
clean_install.bat
Click to expand...
Click to collapse
Didn't work
KalolParty said:
I wanted to uninstall magisk so I like a dummy I pressed uninstall . The phone started bootlooping
I decided to flash the N fastboot ROM from the website and get it flash via Miflash
Miflash finishes the process in 1 second and does nothing. Neither does running the script directly. Any fixes?
SOLVED: I moved both the image folder and miflash folder to the desktop. Mi flash still didn't work
Ran the script via CMD and it worked!!
Click to expand...
Click to collapse
Could you please tell me how you flash via CMD. around 7 hours today trying to flash with mi flash tool I am on note 11 just need know how flash by CMD method
Hey,
so yesterday I tried to install TWRP recovery.
While trying I assume that I hard bricked the phone and got the message that the current image has been destroyed and cant boot.
I've tried using MSM but the device wasnt recognized, I installed the qualcomm usb drivers and it worked for some time but still wasnt recognized in MSM.
Now I have the problem that when I plug it in, it only shows the above mentiond message. When I shut it off and press vol +/- it then goes into fastboot but cycles through it and is still only shown as android device in the device manager.
I'm using the usb 2.0 and original OP cable. Build number was IN2023...c.36, A12 and OOS12
ADB does not work, fastboot commands still work while it is in the fastboot cycle.
Does someone have any solutions for that?
Thanks
How did you "install" twrp?
via fastboot? or through booted twrp? Because from what i read, twrp or orangefox likes to patch boot image instead of flashing recovery partition.
So my suggestion is to flash via fastboot original boot.img and recovery.img
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
w4rdl0rd said:
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
Click to expand...
Click to collapse
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Thank you, it finally works
ShadoV90 said:
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Click to expand...
Click to collapse
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
w4rdl0rd said:
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
Click to expand...
Click to collapse
Wait... system can't boot up?
ShadoV90 said:
Wait... system can't boot up?
Click to expand...
Click to collapse
yeah, it goes always back to recovery
Hmm... Then i'm afraid that MSM is now your only option. Sincerely, i never used that, so i found thread with guide how to do it.
Look please here, read carefully, and i hope you will be able to recovery your device.
I guess it will rollback your system to OOS11.
PS. Give feedback if it was succesfull (or not).
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
w4rdl0rd said:
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
Click to expand...
Click to collapse
I hope it will work.
BTW, next time when you will try recovery like twrp or orangefox, don't flash it but boot it via fastboot.
fastboot boot <drag file of twrp/orangefox>
If it will work, and everything will work, then use fastboot flash recovery <drag file of twrp/orangefox>
Don't flash it via twrp/orangefox, because like i said, it will probably try to patch boot partition and in result boot will be unusable.
thanks for the advice, I'll try it next time or when I get it running again
w4rdl0rd said:
thanks for the advice, I'll try it next time or when I get it running again
Click to expand...
Click to collapse
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
ShadoV90 said:
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
Click to expand...
Click to collapse
I tried/am trying to get MSM working. It connected now in edl, in MSM it still freezes. No matter what I do it has the status "waiting for communication".
If I remember correctly then there was somethin with ..._b. But since I've closed the command prompt I can't look it up anymore.
I'll try to change slots and let you know if there will be a result.
With MSM there is one problem. After succesful operation your phone will be locked. I mean bootloader will be locked.
I did as you wrote...it works fine now. I think. There is still A12 and OOS12 installed but it is lagging a bit.
I attached a screenshot of the terminal with the slots. Does having switched them pose some problem? Do I have to switch them back?
Just check if you have an update. If you have, then install it via system update. For now, you have working system. Now you have much more possibilities to use. Like if you don't have update you can apply manually one which you downloaded. In system ofc.
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
w4rdl0rd said:
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
Click to expand...
Click to collapse
So, this is C36 installed?
yeah there is c36 installed