Develop Bugs

[10.2.2015][TUTORIAL][how to root yu yureka][noob friendly][Only for Kitkat 32bit]

Hello all Yu Yureka lovers!!! :highfive:
Explore the seemless possiblities by ROOTING your Yu Yureka!!!
This guide helps you to "Unlock Bootloader", "Flash Custom Recovery" and "Gain Root Access"
*Things you needed: Laptop or Desktop with windows OS (not tested in other OS), USB Data cable, ADB and Fastboot Drivers( you can find these here or here extract these file in c:\ of your laptop/desktop) and last ofcourse your Yu Yureka (atleast 75% charged).
Warning: This process will delete all data stored in internal storage so better backup all the files stored in internal storage.
So before getting started you need to enable USB Debugging/Android Debugging to enable you can just follow these steps:
Go to settings> About phone and keep taping on build number till it appears "You are a developer now", now you can exit.
Now again go to settings>developer option(only after the previous step it will be enabled)> check/select android debugging.
Before doing unlocking procedures win x64 users [all 7,8,8.1,10 OS] need to disable driver signature enforcement"
for windows 7 x64 :
When boot screen loads, press the F8 function key a few times until you see this boot menu boot menu:
{
"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"
}
now look for option in the bottom called Disable Driver Signature Enforcement
Use the arrow keys to highlight it and then press the ENTER key. Windows will load like normal and now u can unlock yureka like win x86 [dont restart windows without unlocking becoz restart makes again the driver signature enable]
for windows 8,8.1,10 x64
click this link and follow instructions there and follow yureka unlocking procedures..
So lets get started!!!
1) Unlocking Bootloader:
Power off your Yu Yureka device
Connect your device and laptop/desktop by USB data cable
You will see the notification light of your Yu Yureka will glow "RED"
Now keep pressed the volume up button of your Yu Yureka, till it boots to the fastboot screen
Now browse to your c:/ open the folder which you extracted earlier(ADB and fastboot)
Now open command window in that folder(press ctrl+shift and right click).
Type the following command and press enter.
Code:
fastboot -i 0x1ebf oem unlock
Your Bootloader in now unlocked
*If you are facing issue like "waiting for device" when you type the command then please install minimal adb and fastboot or ADB and Fastboot drivers from google drive and try to execute the command
2) Flashing a Custom Recovery:
Download the recovery-yu.img file (here is link for CWM v6.0.5.1)
place the downloaded recovery-yu.img file in folder where fastboot files are extracted
Open command window in the folder and type the following command and press enter.
Code:
fastboot -i 0x1ebf flash recovery recovery-yu.img
*note: if you download any other custom recovery which is named differently, while writing the command you need to put the name of the recovery which is in ".img" file.
Now you just flashed a custom recovery
3) Last part giving root access:
Download the superuser file
Place the file in the internal storage or external storage
Boot your Yu Yureka into recovery mode by pressing volume up + volume down + power button
In recovery select install zip from storage and browse to the folder where you have downloaded the superuser.zip
And select install
Please note:
These l are the issues faced after the new incremental update:
Issues:
*cannot root because custom recovery is not booting
*every time after flashing custom recovery it boots into stock CM recovery
Solution:
1. Download the superuser. zip and place it in external sd-card
2. Go to developer option and disable "update cm recovery".
3. now flash the custom recovery again through command prompt
4. Disconnect the cable and press these combination keys to boot into recovery "vol up+ vol down+ power
5. Now it should boot into custom recovery
6. Install the superuser. zip
Click to expand...
Click to collapse
Congratulation you have successfully rooted you Yu Yureka and now "PlayGod"
Credits:
@vishal_android freak for his original post, recovery and superuser.zip
@ansebovi for adding disable driver signature enforcement to the OP
If it helped hit thanks :good:

"waiting for devices" issue
*If you are facing issue like "waiting for device" when you type the command then please install minimal adb and fastboot and try to execute the command Don't forget to enable USB debugging:good:

Yu Yureka phone struck on fast boot mode
How to go to normal mode from fastboot mode , i tried most of option but didn't worked. If i press power button it shows fastboot mode, volmue up +down then power button also it shows fastboot mode screen nothing happens. This is happening after seletec advanced reboot then recovery . I tired to unlok the bootloader , it say's unlocked but i m somehow struck in FASTBOOT mode, pls help to get out of it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x1ebf oem device-in
fo
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s

mice3138 said:
How to go to normal mode from fastboot mode , i tried most of option but didn't worked. If i press power button it shows fastboot mode, volmue up +down then power button also it shows fastboot mode screen nothing happens. This is happening after seletec advanced reboot then recovery . I tired to unlok the bootloader , it say's unlocked but i m somehow struck in FASTBOOT mode, pls help to get out of it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x1ebf oem device-in
fo
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you flash recovery???

Still the same after installing it also

bro struck at waiting for device

Successfully unlocked bootloader, installed twrp & rooted (SuperSU). Thanks OP for tips.
USB Debugging should be enabled.
At PC (Linux OS): do use "sudo fastboot ....." otherwise you will not get response for fastboot cmd.
If using windows OS, open command prompt for administrator.

darshankedige01 said:
bro struck at waiting for device
Click to expand...
Click to collapse
Same here. Adb and fastboot drivers are installed. But its the device drivers are not installed. But my samsung galaxy s3 works fine with Adb.
dumtara said:
Successfully unlocked bootloader, installed twrp & rooted (SuperSU). Thanks OP for tips.
USB Debugging should be enabled.
At PC (Linux OS): do use "sudo fastboot ....." otherwise you will not get response for fastboot cmd.
If using windows OS, open command prompt for administrator.
Click to expand...
Click to collapse
Can you guide me how to do it with Linux. I have windows 8.1 and its stuck at waiting for device. So i want to try it with Linux now.

Note : try all this at your own risk.
Enable Developper mode & USB Debugging in YU Yureka.
Adb & fastboot should be installed on your linux m/c.
Now connect YU via usb .
At prompt type this.
Code:
$adb reboot-bootloader
YU will now be in fastboot mode.
Now give command as
Code:
$sudo fastboot -i 0x1ebf oem unlock
Code:
$sudo fastboot -i 0x1ebf flash recovery recovery-yu.img
Code:
$sudo fastboot -i 0x1ebf reboot
boot into newly installed recovery.
Code:
$adb reboot recovery
select "install from zip" option & flash SuperSU.zip

dumtara said:
Note : try all this at your own risk.
Enable Developper mode & USB Debugging in YU Yureka.
Adb & fastboot should be installed on your linux m/c.
Now connect YU via usb .
At prompt type this.
Code:
$adb reboot-bootloader
YU will now be in fastboot mode.
Now give command as
Code:
$sudo fastboot -i 0x1ebf oem unlock
Code:
$sudo fastboot -i 0x1ebf flash recovery recovery-yu.img
Code:
$sudo fastboot -i 0x1ebf reboot
boot into newly installed recovery.
Code:
$adb reboot recovery
select "install from zip" option & flash SuperSU.zip
Click to expand...
Click to collapse
I tried it. Got fastboot and adb installed on kali but some other error showing up now. I think its because of kali. Should work on ubuntu or other version.
---------- Post added at 08:30 PM ---------- Previous post was at 08:17 PM ----------
Its driving me crazy. Not able to root this phone. Never had any problem with samsung phones

Kapiljhajhria said:
I tried it. Got fastboot and adb installed on kali but some other error showing up now. I think its because of kali. Should work on ubuntu or other version.
---------- Post added at 08:30 PM ---------- Previous post was at 08:17 PM ----------
Its driving me crazy. Not able to root this phone. Never had any problem with samsung phones
Click to expand...
Click to collapse
Sir which windows os you are using???

is rooting yu void warranty or cynogen giving us freedom same as one+1?

vikas44493 said:
is rooting yu void warranty or cynogen giving us freedom same as one+1?
Click to expand...
Click to collapse
As per YU promise unlocking BOOTLOADER doesn't void your warranty

aashking said:
Sir which windows os you are using???
Click to expand...
Click to collapse
Windows 8.1 64bit
Never mind i finally rooted my phone. I tried so many adb and fastbooot drivers from different websites that one of them worked.

Kapiljhajhria said:
Windows 8.1 64bit
Never mind i finally rooted my phone. I tried so many adb and fastbooot drivers from different websites that one of them worked.
Click to expand...
Click to collapse
Can you post the link so that i can add to OP???

aashking said:
Can you post the link so that i can add to OP???
Click to expand...
Click to collapse
I have no idea which one worked. I downloaded same stuff plenty of times too from different websites. Kept trying all of them and then trying to root. I thought of posting here link to which one worked for me. But i couldn't figure out which one did.

@aashking
hi nice tut...
but this works only on win x86 users...
so can you please add this to OP for x64 users
before doing unlocking procedures win x64 users [all 7,8,8.1,10 OS] need to disable driver signature enforcement"
for windows 7 x64 :
When boot screen loads, press the F8 function key a few times until you see this boot menu
:
now look for option in the bottom called Disable Driver Signature Enforcement
Use the arrow keys to highlight it and then press the ENTER key. Windows will load like normal and now u can unlock yureka like win x86 [dont restart windows without unlocking becoz restart makes again the driver signature enable]
for windows 8,8.1,10 x64
click this link and follow instructions there and follow yureka unlocking procedures..

OP updated [31.1.2015]
Guide updated with some useful steps which i missed.
Enjoy Rooting :good::highfive:

So, i'm planning to root my yureka... Does the OT's steps to root yureka work completely fine now (after the steps updation & all) ?
i use a win 7 x64 PC. Do i need to take any other extra precaution?

ujilraj said:
So, i'm planning to root my yureka... Does the OT's steps to root yureka work completely fine now (after the steps updation & all) ?
i use a win 7 x64 PC. Do i need to take any other extra precaution?
Click to expand...
Click to collapse
Don't worry there in only one in a million chance that you can damage your device by rooting.
I tried above steps (before thread got updated) atleast 20 times.
There is nothing in these steps that can harm your device.

Error while flashing twrp from PC

I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )

vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
Try official recovery it worked

kash2freedom said:
Try official recovery it worked
Click to expand...
Click to collapse
it is the official one

vib$$$ said:
it is the official one
Click to expand...
Click to collapse
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like 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"
}
​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second picture​

Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 4494056​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060​
Click to expand...
Click to collapse
Yes. My bootloader is unlocked. So oem is also ticked. I'll try using this software. Do you have the proper steps for it?

type fastboot devices and see if it shows a device
maybe try using anothar usb port on laptop
if fastboot devices is not showing anything, its coz adb and fastboot drivers are not installed properly, are u using a windows 10 laptop??? they tend to give some problems while installing drivers.. google up and u will find ways

I had the same issue. Its coz windows 10 driver issues. I tried the same method in a windows 7 pc and it worked.

Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 4494056​2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060​
Click to expand...
Click to collapse
is it for redmi note 5 pro

vib$$$ said:
is it for redmi note 5 pro
Click to expand...
Click to collapse
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing

vib$$$ said:
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing
Click to expand...
Click to collapse
It's OK not to show device name in the toolkit if the toolkit only shows fastboot as green color that means you device has been recognized and you don't have to install adb driver again so now you just need to click on the button Recovery Flash and a new box will appear and then check my second Pic file and find the twrp file and flash it, it's very simple
And I have done this method for my Redmi Note 5 AI(China)

Same thing happened with me. I can't even flash anything via fastboot. I updated from 8.4.25 to 8.5.2 global beta on my Redmi Note 5 Pro and this happened.
Also, I noticed that if I try to flash anything from MiFlash, the phone would disconnect itself even if I would flash from CMD.
After disconnecting from itself, the screen stays on fastboot and immediately a text appears "Press any key to shut down" on the top left corner.
Now I'm on Miui 9.2.4.0 Global Stable flashed through EDL mode still the fastboot is broken
confused what the heck happened! Tried reinstalling all drivers but no luck.
p.s In the image I was just testing the flashing state using userdata.img and twrp files

vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%

Easiest solution is to go with linux!
You can make this even form freshly created ubuntu live USB drive. Just go in terminal, install adb and fastboot and voila, no need for "drivers", here You work in "native" environment!
Then, agin in terminal go with:
sudo fastboot flash recovery recovery.img
or for ROM flashing, when You are in recovery, activate sideload option an again in terminal go with:
sudo adb sideload rom.zip
That's it!
Works every time!

nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT

nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk

vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
U can try but in My case the 9.2.7 boot image worked

gavi7566 said:
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk
Click to expand...
Click to collapse
This is the boot image of which Rom?

vib$$$ said:
This is the boot image of which Rom?
Click to expand...
Click to collapse
9.2.7.0

I had same problem , Yesterday i fixed it somehow .

S_Arya said:
I had same problem , Yesterday i fixed it somehow .
Click to expand...
Click to collapse
How??

Please help me there is a problem MI A2 lite‏

Hi, I have a problem in my phone. Please help me install a system that has been modified by developers
You have started a new system that is not working, please watch the video
https://drive.google.com/file/d/1sQz-FjEPEKduXM6zE9JT8kEcrqKgxlHG/view?usp=sharing
https://drive.google.com/file/d/1W1m12WVzDWT7Vk2N6vcvGNglKmHT1i_8/view?usp=sharing

Try edl
" fastboot oem edl"
with mi flash 2016.4 is working fine,

ht0 said:
Try edl
" fastboot oem edl"
with mi flash 2016.4 is working fine,
Click to expand...
Click to collapse
{
"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"
}

if you didn't unlocked bootloader you can't go on try "fastboot oem unlock"
"fastboot oem unlock go"
or firstly try normal flash using "flash_all.bat"
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
essam_alasmi said:
Click to expand...
Click to collapse
must do it on edl
if you don't know please Google it

ht0 said:
if you didn't unlocked bootloader you can't go on try "fastboot oem unlock"
"fastboot oem unlock go"
or firstly try normal flash using "flash_all.bat"
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
must do it on edl
if you don't know please Google it
Click to expand...
Click to collapse
not work

not work
Click to expand...
Click to collapse
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type:
Code:
adb devices
and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
Code:
adb reboot bootloader
- Now repeat the operation to see if device is detected again but now in fastboot with
Code:
fastboot devices
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type
Code:
fastboot getvar all
you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
Code:
fastboot oem unlock
if your device is not Daisy you won´t to unlock it this way.
- If all continues well just now you can send device to EDL mode with fastboot oem edl
- Now flash what you want through MiFlash tool.

bro
did you trying on fastboot or edl?;
if edl should work/not sure..?
but on fastboot if you try flash_all_except_torage.bat" should work

SubwayChamp said:
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type:
Code:
adb devices
and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
Code:
adb reboot bootloader
- Now repeat the operation to see if device is detected again but now in fastboot with
Code:
fastboot devices
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type
Code:
fastboot getvar all
you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
Code:
fastboot oem unlock
if your device is not Daisy you won´t to unlock it this way.
- If all continues well just now you can send device to EDL mode with fastboot oem edl
- Now flash what you want through MiFlash tool.
Click to expand...
Click to collapse
is not done.. Will continue with Xiaomi Thank you

ht0 said:
bro
did you trying on fastboot or edl?;
if edl should work/not sure..?
but on fastboot if you try flash_all_except_torage.bat" should work
Click to expand...
Click to collapse
Thank you my friend did not work but I will communicate with Xiaomi

essam_alasmi said:
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type: and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
- Now repeat the operation to see if device is detected again but now in fastboot with
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
is not done.. Thank you bro we Eamil xiaomi
Click to expand...
Click to collapse
It looks like you didn't enable OEM unlock in developer options

SubwayChamp said:
It looks like you didn't enable OEM unlock in developer options
Click to expand...
Click to collapse
Problem I can not enter the system Also the phone was working without problems when installed the system again can not work appears on the screen of Android One I am to communicate with Xiaomi The solution will be sent to an update right For Fastboot V10.0.16.0.PDLMIXM Because my phone was on protection mod Thank you for help

Hi, I tried the solution is not resolved yet The phone hung a logo Android one

hi plz help the phone no work

Unfortunately, I tried to solve the problem, but unfortunately it did not work, and I am waiting for the release of the new update, maybe the problem will be solved with the phone

essam_alasmi said:
Unfortunately, I tried to solve the problem, but unfortunately it did not work, and I am waiting for the release of the new update, maybe the problem will be solved with the phone
Click to expand...
Click to collapse
Reboot into fastboot and type fastboot oem edl and try flash from PC again

czeckpage_FUZE said:
Reboot into fastboot and type fastboot oem edl and try flash from PC again
Click to expand...
Click to collapse
did not work it seems Error
I am waiting for an update From Xiaomi

MI 9 SE Brick After Locking the Bootloader (Global rom installed on Chinese phone)

Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.

Did you try the original chinese ROM, the first release? The same with global?

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:

If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.

Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"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"
}
It didn't work, says 'Flashing is not allowed in Lock State'

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI

savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?

savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily

Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box

Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?

Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:

That's so incredibly strange. Guess I'll have to check that phone out.

Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...

pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?

savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.

https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).

Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then

Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.

savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!

You can flash him only with testpoint and auth account

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"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"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
hello sir is it compatible with rmx3363 ?

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs