Hi all, this is my first post on the XDA. I am sorry if this is a duplicate post, but it seems that no one have posted this yet. Please beware that this method will completely erase the device, since it involves reflashing via original UPDATE.APP.
First of all, you need the bootloader unlock code. You can get it from huawei's website or DC-unlocker. Personally, I use android app DC-unlocker here on play store (it is cheaper, only 1 EUR).
Then, you need the stock ROM UPDATE.APP. If you have unlocked bootloader, chances that you also have TWRP installed. Boot to TWRP, and transfer the UPDATE.APP to the dload folder of internal storage via TWRP's built-in MTP support. Alternatively, if you don't have TWRP, you may flash the TWRP first, or copy the UPDATE.APP to an external SD card (also the same dload folder). Make sure the SD card is formatted as FAT32 (I've not tried exFAT/ext4 yet). Note that HW folder is not strictly required (optional).
After you've copied the UPDATE.APP, you must flash the stock EMUI recovery (also via fastboot). You can get it from the UPDATE.APP mentioned above using this windows software here. If you use the Huawei Update Extractor, use profile "Unknown (worstenbrood)". Then right-click, extract the RECOVERY.img (not RECOVERY2.img). You may flash the extracted RECOVERY.img via fastboot, e.g.:
Code:
fastboot flash recovery RECOVERY.img
Make sure the bootloader is in "unlocked" state.
Do a reboot via fastboot. Immediately after the "your device cannot be trusted" screen appears, hold the volume up button to enter the e-recovery. Then press shut down on the e-recovery screen.
Last step, press and hold volume up and down, along with power button. The device will start flashing the UPDATE.APP. After it's done, the device will be reverted to brand new factory state, and the bootloader state will become "locked", not relocked.
Tested and working on my VIE-L29 C636 using the B170 UPDATE.APP.
Ho, how can i check if bootloader status is locked or relocked ?
Thank you
Fil76 said:
Ho, how can i check if bootloader status is locked or relocked ?
Thank you
Click to expand...
Click to collapse
Start your phone in fastboot mode.
Sent from my HUAWEI VIE-L29 using XDA Labs
Mostar088 said:
Start your phone in fastboot mode.
Sent from my HUAWEI VIE-L29 using XDA Labs
Click to expand...
Click to collapse
thank you
Phone lock
frp unlock
Great post
Thank you
my phone enable oem unlock but FRPlock still lock ..ican't unlock bootloaderor flash everything what happen on my P9+
ccgchhun said:
my phone enable oem unlock but FRPlock still lock ..ican't unlock bootloaderor flash everything what happen on my P9+
Click to expand...
Click to collapse
First, to enable bootloader unlock, you must unlock FRP first. This can be done from developer options -> enable OEM unlock. Now, if you can't boot to the OS and have the default recovery (not TWRP) installed, you can try to factory reset the device.
If you still unable to boot, try to flash a default firmware, complete with it's HW folder, by using a TF/MicroSD card. Format your SD card as FAT32, and copy those firmware files to a folder called 'dload' on the root of the SD card. Then, insert the SD card to the device, and press these 3 buttons simultaneously : Power + Vol Up + Vol Down. Your device should begin to flash itself.
Worked.
My P9+ having issue always restart. How to 'relock' back my phone?
I check using fastboot my phone:
Phone unlocked
frp lock
mbursi said:
My P9+ having issue always restart. How to 'relock' back my phone?
I check using fastboot my phone:
Phone unlocked
frp lock
Click to expand...
Click to collapse
Flash full stock firmware and it will lock.
Sent from my VIE-L29 using XDA Labs
Mostar088 said:
Flash full stock firmware and it will lock.
Click to expand...
Click to collapse
If you have TWRP, don't forget to flash the stock recovery first (guide can be found at the top of this thread)
Mostar088 said:
Flash full stock firmware and it will lock.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
After flash full stock it's work. My Phone lock.
But, after restart it's unlocked again.
Do you encounter this before?
HI I have relocked my device but when I do a factory reset it I get stuck in the encrytion loop (i put in my password to decrypt it says it still needs to reset) but when phone reboots after reset it says the same thing (data encryption...) any idea? thanks J
P9+
Mostar088 said:
Flash full stock firmware and it will lock.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
After Flash stock firmware, the bootloader is lock..but, after restart it's unlock again.
Any idea?
Use three button recovery metod from shut down, and see to it that you keep all three buttons pushed until it's actually installing. But that may not be enough to get the phone 100% restored, mine didn't get totally restored until I made an update for the same rom from inside the service menu when the phone is turned on. Finally I got the "success" message and all warnings went away.
Phone locked frp lock
jnakoda said:
If you have TWRP, don't forget to flash the stock recovery first (guide can be found at the top of this thread)
Click to expand...
Click to collapse
pls i want fix my phone
PHONE LOCKED
FRP LOCK
problem: no unlock bootloader
give me this error FAILED (remote: Command not allowed)
{
"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"
}
jnakoda said:
Hi all, this is my first post on the XDA. I am sorry if this is a duplicate post, but it seems that no one have posted this yet. Please beware that this method will completely erase the device, since it involves reflashing via original UPDATE.APP.
First of all, you need the bootloader unlock code. You can get it from huawei's website or DC-unlocker. Personally, I use android app DC-unlocker here on play store (it is cheaper, only 1 EUR).
Then, you need the stock ROM UPDATE.APP. If you have unlocked bootloader, chances that you also have TWRP installed. Boot to TWRP, and transfer the UPDATE.APP to the dload folder of internal storage via TWRP's built-in MTP support. Alternatively, if you don't have TWRP, you may flash the TWRP first, or copy the UPDATE.APP to an external SD card (also the same dload folder). Make sure the SD card is formatted as FAT32 (I've not tried exFAT/ext4 yet). Note that HW folder is not strictly required (optional).
After you've copied the UPDATE.APP, you must flash the stock EMUI recovery (also via fastboot). You can get it from the UPDATE.APP mentioned above using this windows software here. If you use the Huawei Update Extractor, use profile "Unknown (worstenbrood)". Then right-click, extract the RECOVERY.img (not RECOVERY2.img). You may flash the extracted RECOVERY.img via fastboot, e.g.:
Code:
fastboot flash recovery RECOVERY.img
Make sure the bootloader is in "unlocked" state.
Do a reboot via fastboot. Immediately after the "your device cannot be trusted" screen appears, hold the volume up button to enter the e-recovery. Then press shut down on the e-recovery screen.
Last step, press and hold volume up and down, along with power button. The device will start flashing the UPDATE.APP. After it's done, the device will be reverted to brand new factory state, and the bootloader state will become "locked", not relocked.
Tested and working on my VIE-L29 C636 using the B170 UPDATE.APP.
Click to expand...
Click to collapse
May i know how do you RECOVERY.img via fastboot?
Is it placing the RECOVERY.img file in the dload folder and then press the up+down+power button?
moony2017 said:
pls i want fix my phone
PHONE LOCKED
FRP LOCK
problem: no unlock bootloader
give me this error FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
You have to do FRP unlock first. If you somehow cannot boot to the OS, try to reset user data first.
prismfire said:
Make sure the bootloader is in "unlocked" state.
Do a reboot via fastboot. Immediately after the "your device cannot be trusted" screen appears, hold the volume up button to enter the e-recovery. Then press shut down on the e-recovery screen.
Last step, press and hold volume up and down, along with power button. The device will start flashing the UPDATE.APP. After it's done, the device will be reverted to brand new factory state, and the bootloader state will become "locked", not relocked.
Tested and working on my VIE-L29 C636 using the B170 UPDATE.APP.
May i know how do you RECOVERY.img via fastboot?
Is it placing the RECOVERY.img file in the dload folder and then press the up+down+power button?
Click to expand...
Click to collapse
Just use "fastboot flash recovery recovery.img".
Hi jnakoda, thank you for this useful guide. I followed your steps and my phone is locked now, but it says FRP unlocked.
How can I lock a FRP? I need to do this because of warranty.
Thank you in advance.
Related
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
{
"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"
}
What can I do?
try to reboot on bootloader mode with volumes button combination
Doesn't work. I keep getting to this screen.
It looks like the bootloader but I guess it can not load the recovery.
Also fastboot does not work there.
I think i found the way
Hi-Suite installed on the PC. Phone off, connected to PC, press and hold Vol + and Power until the appearance of recovery.
Options available:
Reboot
Download the package
Switch off
Bootloader Mode (aka Fastboot):
Phone off, connected to the PC, press and hold Vol - Power up and appearance of the screen with the droid.
Or
Phone off, disconnected from the PC, press and hold Vol - and while holding down, connect to the PC.
Thanks for the help.
I can't get into recovery that way. When i press vol up + power I get into this screen again because recovery could not be loaded.
Unfortunately i don't think if there is a another way,,, contact with huawei
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
What can I do?
Click to expand...
Click to collapse
Assuming that you have bootloader unlocked and adb debugging enabled. Otherwise, I guess, you're out of luck.
Extract RECOVERY.img of respective ROM you have installed using this method: http://forum.xda-developers.com/showthread.php?t=2433454. Copy dload of the same ROM to the root of sd card and insert it. Now turn off the phone and boot into fastbboot (bootloader): conect it turned off with usb to the pc, where you have drivers and platform tools installed. Then press and hold volume down and power on simultaneously as long as needed to boot to fastboot.
After that install previously extracted RECOVERY.img ([Guide]How to root Honor 7). Boot the system, enable adb debugging, go to settings-Updater-Local update and flash the ROM from dload.
Then you may flash custom recovery, replace the ROM, but never again without making nandroid first.
ǀcey said:
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
Click to expand...
Click to collapse
Isn't rumrunner just for HTC?
Yea it probably is just for the resound. Idk.
I'm noob at all this.
What I do know is although my PC could see the phone perfectly before I tried to s-off. That once phone entered into never-ending boots the PC couldn't see the phone anymore. Hence I couldn't use abd or fastboot on the PC nor would the phone enter hboot, fastboot, + recovery on its own.
Somehow re-running rumrunner it was able to force the PC to see it enough to allow the phone to be forced into fastboot mode and that saved my poor phone.
At this point I think u [email protected] nuthin more to lose with trying it out. I hate to say that i'm sry.
In the least go read my post there maybe it's enough to help u to figure out how to undo what happened to yours.
If you do try to use rumrunner
Have phone powered on while hooked to PC
Say Yes twice in rumrunner
Rumrunner will try to selfupdate
Then it will try to force the phone to reboot
Watch phone screen..if it goes black
Immediately close rumrunner window on PC at that point.
We don't want rumrunner trying to s-off ur honor lol no and it will try soon as phone goes in fastbootmode. Keep phone plugged in PC.
If successful now load adb or whatever u need on pc
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
http://forum.xda-developers.com/showpost.php?p=63595063&postcount=193
ooooo
فرستاده شده از HUAWEI Y330-U11ِ من با Tapatalk
hello.
i have a plk-l01 with stock 5.0.2 and stock recovery.
with multi-tool twrp and root flashed, than i would like to flash modaco rom v4.1 (MM)
now i have by booting "honor" logo and under powered by android.
i have flashed another custom rom (yoda 7.0) but is the same.
with stock recovery can´t flash any rom, while by 5% come error.
what methode will work to flash any rom or stock rom back to phone?
thanks
helpppp
Lefteris Fragiadakis (Frago) said:
try to reboot on bootloader mode with volumes button combination
Click to expand...
Click to collapse
i have same problem but i can access fastboot . i have downloaded stock rom in my pc is there anyway to flash stock rom from adb?
kosmoo said:
hello.
i have a plk-l01 with stock 5.0.2 and stock recovery.
with multi-tool twrp and root flashed, than i would like to flash modaco rom v4.1 (MM)
now i have by booting "honor" logo and under powered by android.
i have flashed another custom rom (yoda 7.0) but is the same.
with stock recovery can´t flash any rom, while by 5% come error.
what methode will work to flash any rom or stock rom back to phone?
thanks
Click to expand...
Click to collapse
You must flash the rom with twrp after wipe system, cache, data.
To install MM the basic version was to be the B330.
Now you have to reinstall the stock recovery and flash the rom complete B330 through the three button.
Inviato dal mio PLK-L01 utilizzando Tapatalk
AleAndroid96 said:
You must flash the rom with twrp after wipe system, cache, data.
To install MM the basic version was to be the B330.
Now you have to reinstall the stock recovery and flash the rom complete B330 through the three button.
Inviato dal mio PLK-L01 utilizzando Tapatalk
Click to expand...
Click to collapse
this method was good, thanks!
now have a stock recovery with stock b330 rom.
thanks
You can root it with twrp-3.0.2-0-plank.img and SuperSU 2.62
YOUTUBE /watch?v=eDyxj6C8eW8
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
I decided to flash the stock recovery again. After I did that I got into rescue mode. I can not do anything anymore in there. No fastboot, no adb.
It just points to zh.ui.vmall.com/emotiondownload.php?mod=restore but in this list there is no download for the Honor 7.
Error messages are:
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
What can I do?
Click to expand...
Click to collapse
dude, i hope you fixed you issue... i had the same problem just now... all normal until i installed a new version of supersu (2.7.4 i think) and i wiped the cache and dalvic cache (caused problems everytime) after that i couldnt boot the system, error 10 and 2 i think (boot and system).
Then, after the whole day was over and i didnt find a fix for my problem (my twrp worked) i backed up everything and then installed the original recovery i got some time ago from huawaiextractor, but it got worser. did the same like you, every damned step xD now i understood what you were talking about, before i didnt understand what you said...
so when i boot, it says error 10 ans 2 and when i want to start recovery it says 11 and 2 (recovery and boot).
i dont know why usb debugging didnt worked and why i coulnt use fastboot and adb like everytime. i once fixed a similar issue with the honor multitool and adb and fastboot.
Only thing i can do is connect it to my pc and hisuite, then a new menu shows where u can download a package or update, but it says failed everytime when i use it.
So what did you do with your bricked phone?
I had the same problems (errors) I managed to find a solution. Just extract boot.img cust.img repair.img system.img with huawei extractor. Than just make a full cache wipe. Flash this four .img and love your fully working, totally wiped, almost brand new phone!
PS you should find a way to use fastboot!! There is no other way!
ǀcey said:
Try rumrunner on pc to get into fast boot mode.
Immediately close rum runner screen when it starts rebooting
sent with Huggzzz from my modded, non-OC'ed, very fast running S-Off ADR6425LVM on CyanogenMod 11 20150805 Rom with Tapatalk
Click to expand...
Click to collapse
How did you do please ? i can't enter to fastboot mode too
can you help me please ?
etticat said:
I just installed TWRP and after flashing SuperSU I couldn't get out of recovery anymore. On every restart the phone booted in recovery.
What can I do?
Click to expand...
Click to collapse
With a stock boot.img sometimes you'll end up in bootloop like yourself. If you are still having issues follow below steps.
Boot into bootloader mode, if its looping very fast, then press and hold Vol DOWN button once the screen gets blank after a loop and simultaneously connect to PC, you'll land in bootloader mode.
Once in bootloader mode, flash system.img of your respective previous firmware, in your case just flashing system.img will do.
After doing that you can enter into system again. If you want you also can flash the whole UPDATE.APP package by three button combo
I hope this helps someone.
Hello, the question is very simple: does anyone who has installed the rom 26S in x722 have been able to then unlock the bootloader or install another rom?
We know that in the rom 20S with the one that comes from the factory you can unlock the bootloader and install twrp, we know you can upgrade to the 26S, we know that there are people who have upgraded to 26S, but no one who has upgraded to 26S has Commented that it was able to install another rom then, only comment that the bootloader is blocked with the 26S.
All those who have updated to 26S you have to stay with her because you can not change?
Well if someone has succeeded, it would be nice to say how he did it.
Greetings.
*** TODAY, THE ONLY WAY TO LEAVE OFFICIAL 26S IS TO INSTALL THE ROM 01D, THAT UNLOCK THE BOOTLOADER AND ALLOWS US TO INSTALL ANY OTHER ROM. ***
My phone came with 20s shoprom and the bootloader is unlocked. I checked. So I will wait for a twrp before I update to 26s. Is the x720 twrp compatible with our phone to flash?
I have not tried it, but according to the comments of this and other forums, with the 20S factory version it is easy to unlock by ADB, and it allows you to install twrp from x720 which by comment works fine.
The problem is that if you upgrade to version 26S, the bootloader can no longer be unlocked and as the recovery is changed to the stock, you can not reinstall Twrp or any other ROM (I suppose you can install another official ROM, but The only one that exists is the 26S, there is not even the 20S with which it comes from the factory)
In short, if you upgrade to version 26S, the bootloader is blocked, and you can not reinstall twrp or anything that is not official, and for the moment there is nothing more.
Greetings.
It's not like there are so many ROMs
The bootloader changes in 26s and it makes device bootloader locked.
I would suggest to stay on 20s until a workaround is available for unlocking bootloader also on 26s.
I guess anyone who already has the 26S version will have to wait. But for the one who has a hard-brick with the blocked bootloader should try to get a copy of bootloader of 20S and with some flash tool try to change it.
Also it could be that with a flash tool install the rom 26S and before restarting change the bootloader by the 20S version. In some terminals, this has worked.
Greetings.
I have a nandroid copy of 20S Shop ROM boot. I made nandroid copies of all major partitions (the same ones that have stock ROM) before installing 26S Stock. I used the TWRP of the X722 version to install the ROM. Everything worked. Then I installed the GApps and gave it some error and rebooted. Now I have the bootloader locked, it does not go into recovery mode and it does not start the system. Totally brick.
And the worst: QFIL does not work here. I have tested on different versions, different computers, different drivers and nothing. He always gives this error:
Code:
15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
And Windows emits the disconnected device sound.
Here is a detailed log using the command to send the FireHose through the CMD:
Log.txt
Does anyone have any idea what this error is? And how to solve it?
Hello DK Boneco, I can not tell you how to solve it, but I can give you an idea.
The fault is because the bootloader is locked.
Look for another tool that does not use qfil and that allows you to flash with locked bootloader. Surely there must be some.
And by the way, if you have a copy of the complete 20S version, I would try to flash this one.
Greetings.
DK Boneco said:
I used the TWRP of the X722 version to install the ROM.
Click to expand...
Click to collapse
Can you please post a link
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Hi, this thread talks about "unlock bootloader with rom 26S" not from twrp.
Anyway there is no twrp for x722 but it works for x720.
Query in twrp threads or create one in section x722 for more information.
Greetings.
F.J.V said:
The fault is because the bootloader is locked.
Click to expand...
Click to collapse
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
F.J.V said:
Look for another tool that does not use qfil and that allows you to flash with locked bootloader.
Click to expand...
Click to collapse
Do you know another method? All that I looked for, ending up using the background QFIL to get the job done.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Here's the link: https://twrp.me/devices/leecolepro3.html
DK Boneco said:
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
Click to expand...
Click to collapse
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Try this sequence, in fastboot mode:
fastboot devices
fastboot device info
- when in fastboot device info, check CRITICAL partition unlock status. if FALSE, then try
fastboot flashing unlock_critical
fastboot device info
- now CRITICAL partition unlock status should be TRUE, try unlocking
fastboot oem unlock-go
- if you succeded unlocking, check status with
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
- if you still cannot unlock, you could try flashing a different emmc_appsboot.mbn file. You can extract emmc_appsboot.mbn from x722 20s firmware or from x720 firmware.
In fastboot mode
fastboot flash aboot emmc_appsboot.mbn
- if flashing is successful
fastboot reboot
adb devices
adb reboot bootloader
fastboot oem unlock-go
- if unlock is succesful
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
Flounderist said:
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Click to expand...
Click to collapse
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
{
"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"
}
DK Boneco said:
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
Click to expand...
Click to collapse
Would you try
fastboot format userdata
fastboot format data
fastboot reboot bootloader
fastboot device info
Check if (bootloader) is_allow_unlock: changed from 0 to 1. If it is still on 0 try
fastboot erase userdata
fastboot erase data
fastboot reboot bootloader
fastboot device info
If still on 0....try also formatting or erasing cache.
It seems that kernel does not allow any tampering attempt if value is =0, hence critical partitions are locked.
Hello DK Boneco, the error is reading the COM port.
Is the phone charged?
It appears that the phone is disconnected or exits EDL mode.
It may be a driver problem, or some phones exit EDL mode within a few seconds if the flash has not started.
Try not to take more than 4 or 5 seconds from the time the phone enters EDL until the flash starts.
You can also try the flash with MiFlash Xiaomi, say that can flash any modern phone and is quite effective, look for a manual and test.
Greetings.
DK Boneco said:
And Windows emits the disconnected device sound.
Click to expand...
Click to collapse
You may need to install drivers to your pc to recognize your, thats why it emits the disconnected device sound.
Hello DK Boneco, try these steps:
1. Method published with flashone2.0 and zip qfil.
2. When the fault appears, disconnect the USB phone.
3. Reconnect the phone in EDL mode (vol + and vol- and connect to USB)
4. Without losing time, in flashone2.0 press the "Refresh" button, select the COM port, press the "Flash" button and then "NO" (do not unzip it again).
From connecting the phone to USB until you press the "NO" button as fast as possible, without wasting time.
I hope it serves as something, what I see is that the phone goes out of EDL mode and that's why it fails.
Greetings.
To be sure to stay in EDL mode, you can type
fastboot reboot edl or fastboot reboot-edl
Be sure to install Qualcomm driver properly on PC.
Anyway it seems that QFIL is missing for X722 device. I assume that this device lacked a lot of development due to company failure, or it was developed exclusively for CN market (no google play support and locked bootloader from kernel to avoid any hacking activity).
Qfil is a Qualcomm tool for any Qualcomm smartphone, no matter brand or development.
Qfil should work for any phone with chip qualcomm, another thing is that the phone requires some specific configuration, or that the zip that is intended to flash is not correct.
Greetings.
Obs: these were the steps that i did to get it, try it by your own risk
----------------------update------------------------
Some people are saying that can't get the 11.1.021 via ota from zui10, but I got the information that this version of qfil 11.1.021 is getting ota to the 11.5, so you should try it just changing the files in the tutorial of step 1 and if don't get the ota, jump to the step 3
-------------------------------------------------------
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem unlock-go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
when I try to install just I got error 7 for everstep :S how can I solve it ?
brujaboy said:
when I try to install just I got error 7 for everstep :S how can I solve it ?
Click to expand...
Click to collapse
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Astronomico said:
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Click to expand...
Click to collapse
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
brujaboy said:
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
Click to expand...
Click to collapse
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Astronomico said:
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Click to expand...
Click to collapse
we need wait thank u bro
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot> adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Fixed
this is whilest in fastboot.. ^^
{
"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"
}
View attachment 4951729
it pushes a command when phone was on but when in fastboot / bootloader nothing ? any ideas?
Fixed
every time i push recovery img twrp via ADB it gets bootloader loop
leerh said:
every time i push recovery img twrp via ADB it gets bootloader loop
Click to expand...
Click to collapse
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Astronomico said:
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Click to expand...
Click to collapse
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Astronomico said:
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Click to expand...
Click to collapse
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
leerh said:
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
Click to expand...
Click to collapse
Oh, i thought you could access the twrp after install it, sorry
The tutorial on step 1 provides the official cn rom zui10, if you use it, your phone will probably boot normally.
I think you should lock your bootloader and use the official, you will have the updates via OTA, since you can't use TWRP, I think it will be the best for you, I don't know how help you more :/
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
brujaboy said:
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
Click to expand...
Click to collapse
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Astronomico said:
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Click to expand...
Click to collapse
doesn't matter, thank u so much for replying yesterday I installed all of driver versions but I saw still again and I find another method like pushing very fast download click button and I did successfully 11.1.021 thank u so much again for supporting
Astronomico said:
Obs: these were the steps that i did to get it, try it by your own risk
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem-unlock go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
Click to expand...
Click to collapse
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
leerh said:
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
Click to expand...
Click to collapse
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
lipeneiva said:
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
Click to expand...
Click to collapse
best thing is to try again an follow every letter and step this only way to install 11.5 (beta) did u set a pin it is needed ive not seen another guide to install android 10
Lombachita said:
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
Click to expand...
Click to collapse
Ops, fixed
I was trying to use twrp in my device to install a custom ROM, but when after flashing it i cant boot into it, i used sp flash tool and it does not recognise my device.
when booting through cmd i get this error:
{
"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"
}
this is the error that i get, i have unlocked bootloader
this might be useful to you guys i guess:
so please help me guys.
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
aIecxs said:
keep holding Volume Up while rebooting. do not release until you successfully entered TWRP recovery
Code:
fastboot flash recovery TWRP_lenovotb_7304f-030818.img
fastboot reboot
https://forum.xda-developers.com/t/...l-tb-7304f-hard-bricked.3934944/post-81607437
Click to expand...
Click to collapse
it doesnt works, held volume up just after i typed the command and brought me back to boot modes. there are 3 modes there: recovery mode, fastboot mode and normal mode.
selecting recovery mode would just show a android robot saying no command.
recovery mode is the right option. the no command screen is half way to stock recovery, flash twrp again. on the no command screen, press Power + Volume Up again to continue into recovery
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
so i keep flashing until it happens?
aIecxs said:
the no command screen is stock recovery, flash twrp again
Click to expand...
Click to collapse
but it doesnt even boot into recovery now just boots into normal mode when selecting recovery mode. (only when connected to pc) but when removed from pc it boots into recovery mode and doesnt connect back to pc so fastboot command shows waiting for device.
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
aIecxs said:
What does the "no command" screen mean? (Trying to execute hard reset Recovery)
"The No Command screen means recovery checked the normal area (/cache) for an update file, like an OTA, and it didn't find one, so it had 'No Command' to execute. Androids stock recovery is intended for the normal, everyday user, giving them a menu they could easily access could cause lots of potentially angry people who are just playing around and reset their device by accident. Stock recovery, and its menu, are specifically engineered so that you have to take special steps to do anything. The No Command screen, meaning no automated script, is part of that safe guard."
source @acejavelin
Click to expand...
Click to collapse
ok, now i understood about the recovery menu, so to access the twrp recovery i would need to delete stock recovery i guess, but it would in turn brick my device so that just means i cant root my device, still going into root checker it says root availability is yes but it is hard to do it. so now im stuck on a roadblock...
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
aIecxs said:
(if you accidentially boot into android, twrp is gone, reflash and try again)
Click to expand...
Click to collapse
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
aIecxs said:
no need to delete stock recovery, it's opposite. you're just not booting straight into recovery right after flashing, so twrp recovery got deleted:
actually there are three different methods to root that device (I have linked) it's even possible on locked bootloader
your bootloader is unlocked already, so using fastboot is safest and most straightforward method
Click to expand...
Click to collapse
THERE ARE 3 METHODS!!!?? so ill just do the thing and see what happens.
VoxPlays08 said:
so ill just do the thing and see what happens.
Click to expand...
Click to collapse
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
aIecxs said:
This is exactly how people brick their devices. You must not do anything without understanding what you're doing...
why not just repeat post #2
Click to expand...
Click to collapse
Ok I'll reply if anything happens
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
aIecxs said:
maybe repeat download and make sure checksum matches?
Code:
certutil.exe -hashfile TWRP_lenovotb_7304f-030818.img MD5
bcb6aa10333edd89054f3bddca7abbdc
Click to expand...
Click to collapse
checksum matches exactly
so flash it from fastboot and keep holding Volume Up while rebooting, select recovery mode
Im at the exact same spot, I can do the "fastboot flash recovery" but when rebooting, no matter what I press (when reboot) it always go to fastboot or normal boot..
the fastboot says its flashed ok in recovery, but I guess its overwritten when booting..
Stuck here..
If I choose recovery in fastboot using the Lenovo recovery and from there trying to flash with adb and 18.1 it erros out after 40% isch
I can use it but.. old.. and work wifi blocks me cuzzits old.
Hi, here I bring you a procedure for rooting your device using Magisk and Adb. I guess there is no need to say the risks involved in doing this.
First you'll need:
1. Having installed ADB on your pc, you can use this link: https://www.xda-developers.com/install-adb-windows-macos-linux/
2. Your device must have bootlader unlocked, here the process to do so: https://c.realme.com/in/post-details/1526491339024314368
3. The corresponding boot.img (In this thread you can find attached the file for RMX3301_11 global variant) or you can extracted by yourself from the ofp file using htis script https://github.com/bkerler/oppo_decrypt
Note: During the process I encountered that fastboot commands didn't seem to work, getting the message <<waiting for device>> when unloocking bootloader on windows 11.
This problem was caused due to the lack of proper drivers, if you face this problem there is a file with the needed drivers attached in this post as well.
Now rooting process:
1. You need to install the latest stable release of Magisk on your device, which you can find here: https://github.com/topjohnwu/Magisk
2. Copy the boot image to your device
3. Press the Install button in the Magisk card
4. Choose “Select and Patch a File” in method, and select the boot image, then connect your device via usb to your PC
5. Copy the patched image to your PC, move the file inside your platform-tools folder and rename it to patchedboot.img
6. Make sure usb debugging is turned on under developer options and give permission to your PC on your cellphone after typing the command adb devices on your ADB terminal
7. Type the command adb reboot bootloader
8. Once your device is on bootloader type de command fastboot devices to make sure your device is "attached".
9. Now type fastboot flash boot patchedboot.img
10. Reboot and open the Magisk app on your phone to check everything is ok.
Aditional stuff you might find useful:
Here you can find the Universal Safetynetfix module, which is working properly: https://github.com/blog2i2j/kdrag0n.._..safetynet-fix
You just need to flash it via magisk, reboot, turn on Zygysk and reboot again.
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
{
"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"
}
arzuakay said:
it is not work unlock app my phone
GT2 Pro RMX3301_11_A.16
View attachment 5651113
Click to expand...
Click to collapse
[EU model] Unlock bootloader of European model
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post. First of all, this is only for the European RMX3301...
forum.xda-developers.com
Where is the guide?
Please stop saying there is root or even bootloader unlock for the global variant. India is not "GLOBAL" aka the world, although you might like it to be.
Lol, I UBL EU Global phone with guide here on xda
Device doesn't boot anymore after flashing patchedboot.img
Ty
where is the boot.img for glabal RMX3301_11_C.13 android 13
Extract from Full OTA package.
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Magisk should work, drivers ok?
Stano36 said:
Magisk should work, drivers ok?
Click to expand...
Click to collapse
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
morphius88 said:
Flashes just fine as far as I can tell according to CMD (admin) but right after flashing, on reboot, it goes directly back to the bootloader (or switches to the other working slot). I just flashed the EUEX C.19 update using the OnePlus updater app and same thing.
Its weird because when I type "fastboot boot patchedboot.img" just to check if the patched boot image works, it boots fine with root working. But flashing using "fastboot flash boot patchedboot.com" goes into that "bricked" or "bootloop" status, whatever its called.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Stano36 said:
adb reboot bootloader
fastboot devices (identified)
fastboot flash boot patchedboot.img
fastboot reboot
Click to expand...
Click to collapse
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
morphius88 said:
Thats pretty much exactly what I do. See screenshot attached from my last attempt using stable Magisk 26.1 patched boot image. The reboot goes back to bootloader.
Click to expand...
Click to collapse
Use this command before flashing the patched boot.img and try again
fastboot set_active a
Click to expand...
Click to collapse
NumberOneDz said:
Use this command before flashing the patched boot.img and try again
Click to expand...
Click to collapse
I've tried that too, it does the same result in either slot.
The funny thing is, using "flash boot patchedboot.img" works fine but that is obviously temporary so I dont understand why it doesnt want to stick if the temporary rooted boot works fine.
Edit: see screenshot, I ran fastboot getvar all after flashing patched boot to both slots. I will flash stock boot to get back to a workable phone for now.
morphius88 said:
It appears that Magisk 26.1 isnt able to root the GT2 Pro. I have flashed the patched boot image twice. First time it stuck around til I installed a module and restarted. Second time didnt even get root. I will try a third time with a canary version of Magisk.
Edit: Canary doesnt work either. Device keeps rebooting to bootloader. Flashed stock boot for now. Will try older version of magisk.
Edit2: Magisk 25.2 doesnt work either. All 3 versions flashed it just fine but device keeps reboot back to bootloader. Both slots too. Flashed back to stock boot.
I am on Indian version of Color Os 13.1 (C.19) so I assume India is not considered global. I will go flash a global rom I guess.
Click to expand...
Click to collapse
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rapper_skull said:
You need to flash vbmeta with disabled verification:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thank you for this. I think this did it. First time I had to disable verity on any phone to get root as far as I know.
I now have root and pass Safety Net.
@vanya.ag you might need to put that in your original post in case there are others that run into the same situation.