Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.
Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...
Thanks for the link to that service firmware!
_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?
Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!
Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?
For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem
sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10
Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.
_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/
CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?
_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds
Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.
After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?
Related
Complete Beginners Guide To Flash Custom ROM on Xperia S | 2011 Devices
This Guide Is Made Easier To Understand The Basics To Install / Flash Custom ROM (Specifically On Xperia Phones). You will not need to go to any annoying links and go on reading lengthy descriptions everything required is provided here. :victory:
Everything is Step By Step.
Just Follow Them And Everything Will Work Fine
Now Lets Get Down To Business.
This Tutorial is Specially For
For Complete Beginners
For Newcomers to Android
For Those Who Want To Learn Flashing ROM Easy Way
People who did not had any encounters with Programming
Click to expand...
Click to collapse
Thanks To All The Senior Developers For Providing Us The Knowledge In Developing Modding And Flashing And Amazing Guides Through Out XDA Forum. Without You People This Guide Would Not Have Been Complete
Click to expand...
Click to collapse
This Guide Is Covered in Next 4 Posts With Every Step As Described Below.
NOTE : I Will Explain This Thread For Flashing Custom ROM Cyanogenmod 10 for Xperia S.
Link here---> https://sites.google.com/site/projectfreexperia/
You can download any Stable ROM The Procedure is Same For All.
Step by Step Process Tree
Step 1. Rooting Xperia SStep 2. Unlocking BootloaderStep 3. Installing CWM RecoveryStep 4. Flashing A Custom ROMStep 5. That's it! You will Have The Custom Rom Running.
Click to expand...
Click to collapse
Step 1 : Rooting Your Xperia S
Step 1 : Rooting Your Xperia S
This is done by Using A Root Tool Provided by Our Senior Developer @Bin4ry. Please Press His Thanks Button For Helping Out For The Amazing TooL!
Just Download The Tool By Clicking Here : Root_with_Restore_by_Bin4ry_v30
For Xperia S 2.55 Firmware look in this thread: http://forum.xda-developers.com/show...php?p=39498268
But Don't Start Running The Tool Yet. Before That you need to Do A Couple Of Things, :angel:
Before Rooting What You Need?
1.) Install Your Phones Software Driver, ---> PC Companion Will Do The Job Just Connect The Phone And Check If It Detects!
2.) Activate USB Debugging, Setting ---> Developer Options
3.) Activate Unknown Sources, Setting ---> Security
4.) Connect Your Phone via USB
5.) Confirm That Your Device Is Connected Properly In Device Manager.
Only Then,
6.) Proceed With Rooting Tool Kit.
Click to expand...
Click to collapse
How To Use It?
1.) Download Attached File.
2.) Extract it Using Winrar
3.) Double click the RunMe.bat and follow instructions!
Xperia phones with "older" firmware = Normal mode
Sony Tablet and similar = Special mode
Xperia phones with JB Firmare = Mode 3 (Goroh_kun mode)
Click to expand...
Click to collapse
Complete Video Tutorial: https://www.youtube.com/watch?v=7EpkrCq1gfM
Just Follow The On Screen Instructions. (Its really easy like installing a game :laugh
After The Software Finishes Its Work! Your Phone Must BE Rooted By Now!
Step 2 : Unlocking Bootloader on Xperia S
Step 2 : Unlocking Bootloader on Xperia S
Procedure To Unlock Bootloader of Sony Xperia S LT26i :
1.) Installation of Fastboot USB Drivers (Xperia S)2.) Unlocking Bootloader of Xperia S
Click to expand...
Click to collapse
Now, We Will Unlock The Bootloader,
Why to Unlock Bootloader?
1.) You can flash custom ROMs/Kernels
2.) You don't need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT Your device
[ Before We Begin Unlocking Bootloader ]
Get the IMEI code for ur device: type *#06# in phone dialer to find it out, note only the digits (no dashes)
Make Sure The Fastboot Drivers Are Installed.
Make sure u have a windows PC with USB cable to connect the phone
Power down ur phone and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows
Will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder
Once drivers are installed just disconnect cable and power on device.
[ How to Unlock ] (Official Way)
Video Link ---> http://www.youtube.com/watch?v=LRH3pC7MhEA
For better understanding, I highly recommend you to watch the above video along with the instructions below:
1.) Download ‘Fastboot Drivers And Pacakges File For Xperia S’ file from → Here
2.) Extract the file you downloaded above on your PC. You’ll get the following three files:
drivers.zip
fastboot_with_Android_USB_file.zip
3.) Go to: http://unlockbootloader.sonymobile.com/ and read everything!
This will open a web page in your default browser. Scroll to the bottom of the Instructions on the page and you’ll see a link like “Continue”, click on it.
In the pop-up window click “Yes, I’m sure” and then in the next window click on both the checkboxes, and then click “I accept”.
4.) Now insert the details as per the instructions:
First 14 digits of your IMEI No. Do NOT enter the last digit (15th) in the box. To know your IMEI No. dial *#06# on your Xperia Arc.
Your Name
Your Email Address
Click Submit.
5.) You’ll get a KEY to unlock boot loader. Write it down somewhere you can remember, it will be used later.
6.) Switch off your phone.
7.) Now extract the “fastboot_with_Android_USB_file.zip” file you got in Step 2.2.
8.) Pick up your phone (it must be switched off) and hold the “Menu” button (the key at the bottom right of your phone), now while holding the “Menu” button connect your phone to your PC with an USB cable.
9.) Once connected — the LED light near the phone’s USB plug will turn blue. If it doesn’t — repeat the Step 8.
10.) Now to install the drivers do the following:
Extract the “drivers.zip” file you got in Step 2.1
Open “Device Manager” on your PC and look for “S1Boot Fastboot” under the head “Other devices”
Right-click on “S1Boot Fastboot” and select “Update Driver Software…”
Now select “Browse my computer for driver software” and select the folder where you’ve extracted all the three files you got in Step 2. Once done — click Ok.
Now click Next (Make sure you’ve ticked the “Include subfolders” checkbox).
If you see any Windows security warning box, don’t worry . Just select “Install this driver software anyway”
Wait for “Windows has successfully updated your driver software” message to appear on your screen. Now click Close.
11.) Open the “fastboot” folder from the file we extracted in Step 7.
12.) Now hold Shift and press mouse right click (Shift + Mouse Right Click) anywhere on the empty white space inside the “fastboot” folder. And then select “Open command window here” from the context menu.
13.) Now in the command prompt window type/paste the following:
fastboot.exe -i 0x0fce getvar version
14.) It should return a value like “0.3”. This ensures that your device is correctly connected.
15.) Now type/paste the following line in the command prompt window:
fastboot.exe -i 0x0fce oem unlock 0xKEY
IMPORTANT! Replace the word “KEY” from the above line with the KEY that you received in Step 5. Then Hit Enter.
Click to expand...
Click to collapse
16.) Now wait for the process to complete. Command prompt will show a “Finished” message when it will be completed.
17.)Once it’s done, disconnect the USB cable from your phone and switch it ON.
18.)Your phone’s boot loader should now be Unlocked.
(The above videos and some steps are for Xperia 2011 devices, but most the steps are same for Xperia S/P/U/Sola)
Click to expand...
Click to collapse
Step 3 : Installing ClockWorkMod Recovery With RoceoverX
Step 3 : Installing ClockWorkMod Recovery With RoceoverX
We Will Install Recovery Using RecoverX Software.
Download The Software from Here ----> RecoverX v1.6.8.0
You just have to select your device and the recovery, click "Install" and RecoverX does the rest !!! It's that simple!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4 : Flashing ROM
Step 4 : Flashing ROM
Assuming you have already downloaded your required file, let’s proceed.
ROM Flashing
1.) Copy Paste update on Phone
Copy update- copy update-xxx-xxx-xxx.zip coresponding to your device to sdcard
Copy GAPPS. Download Link [Here]
2.) Flash CM kernel
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (Extract The boot.img file from zip)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
Click to expand...
Click to collapse
3.) Boot into Recovery
While FXP logo is displayed (and lights are lit) press several times volume up to enter CWM (recovery)
4.) Flash ROM
To update main rom select
Install zip from sdcard
Choose zip from sdcard
Select your update (copied at step 2)
To flash gapps redo steps a-c and select gapps package
Use gapps version designed for your android version !!! Link ---> Here, Gapps
5.Wipe device
Whip Cache
Whip Dalvik Cache (Advanced Option)
Cache Partition
If after boot you experience ForceClose then is recomended to reboot to recovery and wipe device
Click to expand...
Click to collapse
6.) Partition format
7.) Reboot and Enjoy :victory:
Troubleshooting
If you experience a bootloop (phone constantly reboots and reboots on the boot screen) or a soft brick (powering on the phone shows an orange triangle with a phone and computer), don’t be afraid. XDA to the rescue!
For a bootloop:
Hold The Power Button And Volume Up Button
If You Hold For 3 Seconds = Soft Reset = 1 Viberation
If You Hold For 10 Seconds = Hard Reset = 3 Viberations***
Power on the Phone Again, Keep pressing Volume Up Button
Your phone will boot into recovery.
Select “Wipe data/ Factory reset”. (Volume Up for going up and Volume down to go down)
After the reset is done, select “Reboot system now”.
The phone will reboot and you should be all fine.
***Do Not Try Hard Reset Untill And Unless The Phone is Facing Major Problems,
For a soft brick:
You probably flashed some faulty firmware or firmware not meant for your device.
The File You Downloaded Must Be Incomplete.
Download the correct firmware and flash again.
Feedback And Corrections
Please Feel Free To Message Me About Any Dead Links Or Corrections
Feedbacks Are Welcome!
Which is the best way to flash / install a custom ROM / gapps ? With Flashtool or through TWRP / CWM ?
I'm now on stock ROM, Xperia ZL. Do i have to wipe / factory reset / cache / Dalvik cache if i use TWRP ?
Every advice is welcome, thank you
xperia s 2013 jelly bean
I have a question for xperia s jellybean 4.1.2 , i already root it using some other easy method and i wanna know how to flash rom on to that , i have no idea how to flash a rom and i m scared if i try this something might happen so i m asking for help?:laugh:
I know its ment to be straight forward but I have become stuck...
In step 4 - "Click 6/7" when using the Xperia Flasher where do I find the boot.img i need to put on my phone?
Thanks
---------- Post added at 01:37 AM ---------- Previous post was at 12:45 AM ----------
chuckie987 said:
I know its ment to be straight forward but I have become stuck...
In step 4 - "Click 6/7" when using the Xperia Flasher where do I find the boot.img i need to put on my phone?
Thanks
Click to expand...
Click to collapse
It would appear the ROM i downloaded didnt have a kernel.img but now i have a differant ROM and it has a boot.img so all good again!
Can i follow this method on xperia sl and also can i flash xperia s roms to xperia sl.....my boatloader is unlocked but phone isnt rooted so i guess i will skip unlock boatloader method.....which kernel should i flash for slimbean 4.3...it will be great help if someone answer these questions
Please Help
Hi, I searched a lot for the way to flash a custom rom on my Xperia S. But now halfway through, I've got a problem. My device says it does not allow to unlock bootloader, so does that mean that there is no way I can flash a custom rom on my phone? :crying:
mjk123 said:
Hi, I searched a lot for the way to flash a custom rom on my Xperia S. But now halfway through, I've got a problem. My device says it does not allow to unlock bootloader, so does that mean that there is no way I can flash a custom rom on my phone? :crying:
Click to expand...
Click to collapse
You can use only Stock based ROM for locked bootloaders, not the unlocked bootloaders one.
This is very nice thread. For begginers like me in the rooting this.... loved it. i wast to ask a question
can we flash any zip file using flashtool or there are onle few specific files?
mr.sky10295 said:
This is very nice thread. For begginers like me in the rooting this.... loved it. i wast to ask a question
can we flash any zip file using flashtool or there are onle few specific files?
Click to expand...
Click to collapse
You cannot flash .zip files using flashtool. You can flash only Firmwares or kernel files using flashtool.
Mirhawk said:
You cannot flash .zip files using flashtool. You can flash only Firmwares or kernel files using flashtool.
Click to expand...
Click to collapse
ohh...then is there any other method to flash zips otherthan going into recovery?
i am asking because my recovery is not working. when i go into recovery, blank black screen comes up. and it gets stuck there. i waited for very long time to make sure that it is stuck
mr.sky10295 said:
ohh...then is there any other method to flash zips otherthan going into recovery?
i am asking because my recovery is not working. when i go into recovery, blank black screen comes up. and it gets stuck there. i waited for very long time to make sure that it is stuck
Click to expand...
Click to collapse
Which recovery are You using? The 2.8.1.0? It doesn't work with Xperia S. Use the 2.8.0.1 version.
Mirhawk said:
Which recovery are You using? The 2.8.1.0? It doesn't work with Xperia S. Use the 2.8.0.1 version.
Click to expand...
Click to collapse
Wait i will let you know the complete story.
so what happened is
first i was on CM11 for few mnths then switched to MIUIv5 for 1 month. everything was working fine
but when day before yesterday i flashed PA rom i am not able to access the recovery now (previously there was TWRP in my XS). now i can't flash any zip file
when i reboot to recovery it gets stuck on black blank screen. Even the recovery apps like twrp are not working. when i tried to install recovery through app, the app crashes.
As recovery is not working i cant even switch to other roms or any zip file.
i am totally stuck on this ROM
i asked this que on sony mobile group on FB (created by some sony fans), one of the member said "probably this is not ROM fault but the kernel fault. consider trying new kernel"
mr.sky10295 said:
Wait i will let you know the complete story.
so what happened is
first i was on CM11 for few mnths then switched to MIUIv5 for 1 month. everything was working fine
but when day before yesterday i flashed PA rom i am not able to access the recovery now (previously there was TWRP in my XS). now i can't flash any zip file
when i reboot to recovery it gets stuck on black blank screen. Even the recovery apps like twrp are not working. when i tried to install recovery through app, the app crashes.
As recovery is not working i cant even switch to other roms or any zip file.
i am totally stuck on this ROM
i asked this que on sony mobile group on FB (created by some sony fans), one of the member said "probably this is not ROM fault but the kernel fault. consider trying new kernel"
Click to expand...
Click to collapse
If You are on Beta 6 of PA, it doesn't have twrp or cwm. Flash the twrp v2.8.0.1 by terminal emulator method.
Mirhawk said:
If You are on Beta 6 of PA, it doesn't have twrp or cwm. Flash the twrp v2.8.0.1 by terminal emulator method.
Click to expand...
Click to collapse
i am on PA 4.6 BETA4
terminal emulator means the android app or PC's cmd?
PS: sorry giving you too much trouble by asking stupid questions. but i dont have much knowledge about this things deeply. so kindly bear me for some time.
mr.sky10295 said:
i am on PA 4.6 BETA4
terminal emulator means the android app or PC's cmd?
PS: sorry giving you too much trouble by asking stupid questions. but i dont have much knowledge about this things deeply. so kindly bear me for some time.
Click to expand...
Click to collapse
Ah yes, even that one doesn't have recovery.
Unlocked bootloader is must.
You need an Android app. You can find the app here. Also, here is the page of the twrp.
What You need to do is, download the twrp from here. Rename it to fotakernel.img .
Then copy it to Your sdcard.
Then run the following commands on the terminal emulator app:
Code:
su
dd if=/sdcard/fotakernel.img of=/dev/block/mmcblk0p11
TWRP installed!
I. Before You Begin Doing Anything
**As with all of these types of tutorials, this may void the warranty of your device. Do it at your own risk.
**Download and install the Asus USB Drivers on your PC, if you haven’t done so yet.
**This should only work on a Windows based PC only.
II. Downloading Required Files
** Necessary tools and Drivers - Mediafire Folder
**Latest OTA form ASUS website : WW_2.17.40.12
** Boot.img, Droidboot.img and Recovery.img from this MEGA Drive posted by Chinaphonearena user and belong to Shakalaca.
** System.img - if you want your phone ROOTed on latest ASUS ZF2 Firmware.
III. Yeah! Im ready to do it
**Plug in your device to your PC using a USB cable.
**Boot your device to fastboot mode Power + Vol Up to enter Bootloader Mode
**Hold down Shift and Right-Click anywhere in Fastboot Folder on your PC and select Open command here. It will launch a Command Prompt Window for you to issue commands to your device.
**When it launches, type in the following command and press Enter (.img files has to be in same folder as fastboot tools):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
fastboot flash system system.img - Only if you use Pre-ROOTed system image from MEGA Drive.
IV. Ready to go with OTA!
** Upload WW_2.17.40.12 or latest Firmware OTA ( Full firmware ) file to phone storage (Phone storage/File.zip)
** After uploading .zip OTA file to phone storage, unplug USB cable from phone. You will recieve notification that new OTA UPDATE is avaliable for installation.
When you bought CN version of ZF2 you may have to Rename OTA file from UL-Z00A-WW-2.17.40.12-user.zip to UL-Z00A-CN-2.17.40.12-user.zip to get notification about update avaliable.
** Wait till update will finish (approx 10 - 15 min) . Phone will restart when finished. First boot may take longer.
V. Dam! No Notification!? what now...
** Boot your device to fastboot mode Power + Vol Up to enter Bootloader Mode
** At Bootloader press Vol Up to choose Recovery Mode
** You will see an error message of updating ota. Wait 5 sec and then press Power + Vol Up simultaneously until you see recovery menu.
** Using Vol Down + Vol Up choose ADB mode and connect your phone to PC via USB cable
** You need Fastboot version 1.0.32 and up to make ADB Sideload working properly with Zenfone 2
** Extract Fastboot.zip somewhere at your PC and put OTA update file ( .zip) in same folder as Fastboot.
** Hold down Shift and Right-Click anywhere in Fastboot Folder on your PC and select Open command here. It will launch a Command Prompt Window for you to issue commands to your device.
** Use command : adb sideload filename.zip
** At 100% it will go back to Recovery Mode main menu. Restart your phone.
** Done !
** Hit THANKS button and RATE this thread for 5 STARS !
Credits to : Chinaphonearena for posting a link to latest pre-rooted system images.
Credits to : Shakalaca for making it all possible
Remember ! You should only do this at your own responsibility.
Please note !
If you posting somwhere else my guide. Please give me a Credit or just link to this thread. Thanks
Please read all pages if you have a issue with guide. I believe other people had it as well and its already solved.
vivix said:
1) Download image files http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash files by using fastboot commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
4) reboot phone
5) upload 2.15.40.10 OTA file to phone storage (http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.221138204.542811237.1430874705)
6) Update via notification about new update avaliable
7)Wait till update will finish (approx 10 min)
8)Enjoy
Say thanks if i helpedI lost 6 hours to achieve this.
Click to expand...
Click to collapse
Are you sure this works i mean there are thousands of threads regarding this issue but none of them work..Can someone with CN version confirm the working of this method....
I bought phone on Aliexpress website. Phone has WW OTA but update via Wi-Fi was impossible. Firmware was 13.40.13 so i think people with that firmware had CN version at start, then sellers updated it to 13.40.13 WW and sended to buyers. Following my method you can update to the latest WW.
Works fine. We've published a similar method. I recommend using the latest rooted ROM. Note, your LTE 4G bands won't be changed with this method.
Have written out the steps in detail for novice users. Includes setting up adb etc: http://www.chinaphonearena.com/forum/showthread.php?tid=10253
Chinaphonearena said:
Works fine. We've published a similar method. I recommend using the latest rooted ROM. Note, your LTE 4G bands won't be changed with this method.
Have written out the steps in detail for novice users. Includes setting up adb etc: http://www.chinaphonearena.com/forum/showthread.php?tid=10253
Click to expand...
Click to collapse
I agree.
But your method is only for pre-rooted system.img with 2.13.40.13 firmware.
I posted method for full OTA firmware upgrade.
Yes, it is similar )
vivix said:
I agree.
But your method is only for pre-rooted system.img with 2.13.40.13 firmware.
I posted method for full OTA firmware upgrade.
Yes, it is similar )
Click to expand...
Click to collapse
The method posted can be done with any system.img (don't have to use rooted ROM), there's no need to do the OTA update as its already the latest ROM (though it will be compatible with future OTA updates, thanks to the ROM creator), and you end up rooted.
They are essentially the same, except for flashing system.img at fastboot instead of doing OTA update. Take your pick. If not caring about root, your method is certainly quicker, as there's no need to DL the huge system.img file.
Thanks. Much appreciated
confirmed works fine on a rooted CN version
Hi,
I followed all the steps and apart from thinking I'd bricked it (the system update screen was sat with the blue bar unmoved for 15 minutes) . It's just completed perfectly.
Really great advice - thanks - I got 2 of these handsets yesterday via ebay both came rooted and it turns out they are CN models but had WW software on them - as per your model - prior to reading your post I was probably going to try and send them back.
I hope and presume for future updates I can continue to use this method?
will do 2nd one now.
Cheers
Ian
Thanksssssssssssssssssssss
Honestly, last time that I tried to have a custom ROM or in any other words, last time I installed and used ( I'm still using it) it was on my samsung galaxy tab(the first galaxy tab of all time) two years ago!
At first I was puzzled in all of these forum pages. I started to change my CN rom to WW Rom yesterday at 2 o'clock. Since I started this process, I just ate dinner and slept for 5 hours. The rest of the time I was trying to install 7 different roms which are available in this forum or asus zenfone forum by 3 different methods of loading a ROM! NONE OF THEM WORKED CORRECT AND COMPLETELY. so I had to start again and read. I can easily say that I've read more than a fat ass book for this process (most of them were duplicates, but I was looking for s.th new among them...)
Your method worked just nolw (@ 1 pm) and I'm really thankful. Honestly I was so bumped and I was thinking to send this device back, just an hour ago I saw your way for the second time and I just decided to try this time as the last way, before returning it!! thank u again for giving me a zenfone
keep up the good work
Confirmed ok on 2nd handset - red CN model 32gb 4gb ram.
It has removed the root access though... Supersu app has gone. and Root checker confirms not rooted.
Which is ok because I can now use Skygo app on the phone - really wasn't expecting that to work!
Thanks guys for good news that it work for you too. I hope that TUT will help others to get rid of 13.40.13 which drain battery as $%^&. Without root it's hard for efficient battery save but atm i use battery doctor from G market and I need to say after 4h it drained 3% battery with turned WiFi. I just wait for proper root tutorial.
vivix said:
Thanks guys for good news that it work for you too. I hope that TUT will help others to get rid of 13.40.13 which drain battery as $%^&. Without root it's hard for efficient battery save but atm i use battery doctor from G market and I need to say after 4h it drained 3% battery with turned WiFi. I just wait for proper root tutorial.
Click to expand...
Click to collapse
Several proper root tutorials already posted. Just follow your own tutorial but flash the pre-rooted system.img. Bam, done.
But latest system.img is not from newest bug fixed firmware mate. That's the problem.
vivix said:
But latest system.img is not from newest bug fixed firmware mate. That's the problem.
Click to expand...
Click to collapse
Latest pre-rooted system.img is the latest ROM available and OTA updateable.
https://www.mediafire.com/folder/k7z5qzh579oc4/Asus_Zenfone_2_ROOT_System_Image
Hello,
Im stuck at no.5, sorry to ask but I don't know what you mean by phone root storage and where it is found.
Can you help please
He means the base of your SD card. Don't copy the OTA into a folder on SD. Copy it to the base of the SD.
with my cable still connected and fastboot still open?
Because I have put it in the sd card nothing happen
Reboot the phone. You should get an OTA update notification. Or boot into recovery and apply the update from there.
Chinaphonearena said:
Latest pre-rooted system.img is the latest ROM available and OTA updateable.
https://www.mediafire.com/folder/k7z5qzh579oc4/Asus_Zenfone_2_ROOT_System_Image
Click to expand...
Click to collapse
Latest WW Firmware is : Version WW_2.15.40.10
Latest pre-rooted system.img you posted is : Version WW_2.13.40.13
I just rewrited whole GUIDE to make it more easier to understand.
vivix said:
1) Download 2.15.40.10 .img files from : http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
2) Boot to fastboot mode (Power + Vol Up) to enter Bootloader Manu and connect it to PC using USB cable provided.
3) Download ADB TOOLS : http://tools.asuszenfoneblog.com/2014/10/adb-fastboot-tool.html
TIP : At Flashtool/fastboot folder <b>press Shift+Right Click then Open Command Here
Using ADB command prompt flash files by using following fastboot commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
4) Reboot phone connected to PC
5) Upload 2.15.40.10 Firmware OTA file to phone storage (Phone storage/File.zip) :
http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.221138204.542811237.1430874705
6) After uploading .zip file to phone storage, unplug USB cable from phone.
You will recieve notification that new OTS UPDATE is avaliable for installation.
7)Wait till update will finish (approx 10 - 15 min) . Phone will restart when finished.
Dont touch phone because you can mess up something .
8)Enjoy latest V2.15.40.10 WW Firmware.
Say THANKS if i helped !
I Lost 6 hours to achieve this and only THIS method working for 100%.
You will lose your ROOT.
Be careful! Pre-rooted system.img widely avaliable have glitch where when you update superuser app you will soft/hard brick your phone, bootloops etc.
Above method work also as UNBRICK method.
Click to expand...
Click to collapse
You fail to give credit to those who made this possible, especially shakalaca.
This is my version of the steps:
ddfault said:
I recommend using the tools directly from google. (Links fixed 2015MAY08)
These include fastboot and adb
Windows SHA1:720214bd29d08eb82673cd81a8159b083eef19d7
Linux SHA1:b78be9cc31cf9f9fe0609e29a6a133beacf03b52
MacOS SHA1:ddc96385bccf8a15d4f8a11eb1cb9d2a08a531c8
Click to expand...
Click to collapse
As far as steps, I can only speak of the ZE551ML. Start with an unrooted OS.
1.) Download the ADB and Fastboot tools from google (see links above). Download the pre-rooted from from shakalaca in post #1 (If you download the 200MB split version, Windows File Explorer will allow you to open the .zip and copy the .img file out.)
2.) Download the stock full ROM WW_2.15.40.10 directly from support.asus.com
3.) Plug the phone into the PC via USB and copy the UL-Z00A-WW-2.15.40.10-user.zip onto the phone.
4.) The phone will notify you that there is an update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.) When you select the notification you will be prompted of which file to use in the update:
6.) Hit OK and the phone will reboot and update everything it needs to update per ASUS. (This will include the fastboot/droidboot image, boot, recovery, system, silentlake, and modem firmware.)
7.) Once the update has completed, unplug and power off the phone.
8.) While holding volume up, press the power button until the phone vibrates. At this point release the power button but keep holding the volume up button until the screen flickers to the fastboot menu. Release the volume button when the screen flickers.
9.) Plug the phone back into your computer, open a command prompt and navigate to where you extracted the google tools and the system.img.
10.) Run:
fastboot devices
11.) You should see a your device listed, if you do not, your device is not in fastboot mode.
12.) Assuming you see your device listed in Step 10, run:
fastboot flash system system.img
This will erase your current system partition and then start writting the new image to the partition. Fastboot will split the system.img file into ruffly 500MB chucks and send them to your device.
13.) Once its finished, you can select boot normally on your phone by pressing the power button or run:
fastboot reboot[/QUOTE]
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Help Required - Soft brick - Stuck in bootloader
Dear All, Would really appreciate if you can help me with this thread..
Thanks
Regards
Tarun
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
Try to switch the slot to B and then boot
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
amusing_ankesh said:
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
Click to expand...
Click to collapse
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
same
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that ?
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot customrecovery.img
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
kristoff07 said:
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
Click to expand...
Click to collapse
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
secure boot yes? you may have vertified boot, you can try flash patched magisk boot.img to disable that
jjgvv said:
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
Click to expand...
Click to collapse
I checked the info and it gave me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A how-to guide of restoring a completely bricked Redmi Note 9
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a useless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get thefastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (else you'll get error STATUS_EXT_RAM_EXCEPTION (0xC0050005) when using SP Flash Tool). ( I also tried it with a full battery and still worked so idk for sure how necessary this step is).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool.MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer,while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons AND power button!) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-downbox below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE. (If you get "Error : STATUS_STOR_LIFE_EXHAUST" go to options-> general and uncheck Storage life cycle check).
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power buttonto start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github
Very good guide, my friend.
Thank you very much for details and contribution
My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.
aries.1482 said:
My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.
Click to expand...
Click to collapse
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.
vagelis199 said:
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.
Click to expand...
Click to collapse
Your window is 32 or 64 bit, I use windows 10 64 bit and did all step, one by one but no effect.
Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.
aries.1482 said:
Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.
Click to expand...
Click to collapse
Cool ill update the guide!
Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!
lionfishes said:
Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!
Click to expand...
Click to collapse
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version
vagelis199 said:
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version
Click to expand...
Click to collapse
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!
lionfishes said:
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!
Click to expand...
Click to collapse
There's no qualcomm version of Redmi Note 9
i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3
nikosefs said:
i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3
Click to expand...
Click to collapse
Thanks i updated the guide including this
i'm having an ERROR notification : STATUS_EXT_RAM_EXCEPTION (0xC0050005) help me
Looking for some info/help if possible: apologies i'm not trying to derail your thread.
I had bricked my RN9 but managed to unbrick and have it working ok now however I am wanting to restore it/lock the bootloader to allow for using banking apps. But I am encountering an issue. I had tried using MiFlash Tool but during the flash, I get a mismatch error and it doesn't succeed in flashing the Fastboot rom.
If i was to follow your guide from step 13, would this work for me? Or which steps do I need to skip in your list?
Thank you for any advice/help
** I finally managed to get it sorted ** used the EDL flash guide and then flashed in SPFT.
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
vagelis199 said:
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a unless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (I'm not sure if this is completely necessary but that's how I did it).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool. MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer, while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-down box below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE.
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power button to start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github
Click to expand...
Click to collapse
Hi thanks a lot for your help. I accidentally flashed a redmi 10x miui 11, wanted to downgrade my Redmi 9 from 12.5, bad perfomance, resulting in your hard-bricked version. Flashing last fastboot version doesn't help, do i have a chance to fix it?
vagelis199 said:
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Click to expand...
Click to collapse
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.
Coroneln said:
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
View attachment 5476667
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.
Click to expand...
Click to collapse
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name
vagelis199 said:
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name
Click to expand...
Click to collapse
i promise i am choosing fastboot but it ends up in the recovery i have tried several different versions in case it was a file wrongly indexed.
TL|DR
Python errors, step 8 and 12 on Windows 10
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
=========================
Now read....
Just in case someone has trouble with step: 8
Escenario: the BAT file calls `python` and in some windows 10 this will result in a message about the windows store (Even if the path is added)
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings
but `py` works, so just edit the BAT file and replace the call for `python` with `py` it will install all the python modules with no errors.
EDIT:
This also affects step: 12
Found a solution here: https://stackoverflow.com/questions...arguments-to-install-from-the-microsoft-store
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
The error:
After editing the BAT file replacing `python` with `py`
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
It would be easier to build a custom rom than installing it.
VD171 said:
It would be easier to build a custom rom than installing it.
Click to expand...
Click to collapse
LMAO well, there's too much text to read. but it is totally worth it installing a custom ROM on redmi note 9
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
VD171 said:
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
Click to expand...
Click to collapse
I've been developing games for android, and the redmi note 9 is my primary phone for it, because it is the middle ground of performance based on the average user. so as long the game runs well most people would be fine.
The thing is, MIUI with its ram management really makes me struggle, minimizing, and multitasking re-launches the game and System UI a lot of time freezes, nothing of those things ever happens with pixelplusUI, that's why I prefer it making me focus mostly on the GPU performance without getting bottlenecked by the heavy and nonoptimized os.
Well, well.
I understand you.
I confess that I've never played nothing at any android I've ever had, since my first android in 2014.
Really interesting to know about that.
I like the ram management because I don't have to close everything by myself.
My brother and my mother keeps everything on memory and management keeps to the system.
My brother has an iphone (sadly) and my mother has a Redmi Note 10.
I agree that the management by MIUI is excessive and should be more customizable.
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Hello, i flashed miui 12.0.3 but it doesnt want to boot, stuck in bootloop, fortunately it boots into recovery, i wiped data and factory reset but it still doesnt want to boot, how do i fix it?
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
NewtonPL said:
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
Click to expand...
Click to collapse
Nothing faulty there you did not read the whole step. It says "downgrade using MI-Flash software", not using a custom recovery. Read the step properly and completely.
0xSteeW said:
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Click to expand...
Click to collapse
Yea it's safe I've downgraded from miui 12.5.5 to miui 12.0.1 and its totally safe. You can use miflash to downgrade
0xSteeW said:
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
Click to expand...
Click to collapse
Edl bypass is only needed of you brick your device or it doesn't boot into fastboot or for taking backup kinda stuff.
Otherwise miflash does the job
thanks.
All works, thanks for the very detailed guide!
Quick question: do I have to flash with sideload or can I flash with SHRP?
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Manjotbenipal said:
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Click to expand...
Click to collapse
Any ROM before 12.5 is ok
vagelis199 said:
View attachment 5566615How to install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
Click to expand...
Click to collapse
I'm on miui12.0.1 and want to install pixel experience android 10 with shrp.
Do I need to flash the vendor if I don't want to install pixel experience via sideload and is it necessary to disable avb 2.0 after flashing vendor and custom rom?
I cant boot into the recovery mentioned in this step, what do I do?
“6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do “fastboot flash vbmeta vbmeta.img”, reboot into recovery mode, by turning off your phone,“
how long it take to flash redmi note 9? already 1000 seconds passed and its still flashing