Database Develop

Huawei P9 - Failed TWRP attempt

Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!

beratkazal said:
Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!
Click to expand...
Click to collapse
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code

zgfg said:
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code
Click to expand...
Click to collapse
Thank you for answer to me. But i have another problem... Visit here please: https://forum.xda-developers.com/p9/help/help-huawei-p9-device-unlocked-booting-t3932699
Thanks...

RMM state: prenormal after OEM unlock on Android 9.0

Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?

+1 waitting

Narkozzz said:
Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?
Click to expand...
Click to collapse
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?

Narkozzz said:
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?
Click to expand...
Click to collapse
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
bober10113 said:
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.
Click to expand...
Click to collapse
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.

Narkozzz said:
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.
Click to expand...
Click to collapse
flash stock. boot to home screen make it check for updates in the software menu once. check dev tool if OEM unlock is there. if it is a unlocked flash twrp. and boot directly to recovery after odin finishes. in recovery format data in wipe menu and type yes. go to reboot menu and choose reboot to recovery. flash ketans oem root fix v5 in aroma setup choose to flash kernel and magisk.
ive had your issue before. its not complicated. just do what i said if your oem unlock is there and unlocked. if its vanished and want it to appear then there are guides to make it appear instead of waiting.
also do you want oreo or pie? ketan has both. just read..

You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
well if you dont try as i said of course youll never know.
again, i had your issue and alot of people as well. please use xda search feature and read. if not then dont post for help if you dont want help.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
I also have the problem, but with the S10.
OEM activation active, even reactivated in download mode, so OEM activation is gray. Even the trick with the 8 days did not help - it remains prenormal.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
you should be using method 1 in the guide.
Click to expand...
Click to collapse
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away

bininga59 said:
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143

I am in the same situation, the rmm state prenormal still continues
even when I have the OEM unlocked, in fact I tried to do it through the chimera
program, but for having the June android security patch (CSF2)
the chimera friends commented to me that for that reason I could not do the
unlocking of rmm through their program, they told me that they worked on a
solution for it, but they did not give me an estimate of time, I guess we will
have to wait for a solution from them, since searching and reading most of the post,
none worked for me, I'm stuck in not being able to flash TRWP, so I can't really do anything.
I hope someone finds a solution or that through the chimera program, we can correct that problem.

I'm facing same problem on sm-a730f, the rmm state prenormal still active
even when I have the OEM unlocked

Same problem here, i'm using a brazilian Samsung galaxy Note 9 N9600 retail version

Same situation here i have galaxy s9 exynos

RMM state prenormal fix for non-US phones
@bober10113 et al, specially non-US folks
I guess these guys are suffering the same as me, it is exactly like what @Narkozzz said. RMM state prenormal (even with OEM already unlocked!!!) won't allow for flashing one single thing other than official binaries e.g. TWRP without which we can do nothing (the fixes are only prevention, not remedying).
Skimming through Samsung international forums abroad and other websites I saw the solution consists in installing the SIM card, flashing stock with Odin again, and then keeping the cellphone, the simcard and the mobile data turned on constantly. Eventually after 7 days, on in some cases more than a month, that state will reset back and we will then be able to flash TWRP and the RMM bypass, plus noverity etc. etc.
Ketan also mentioned that in the comments in his topic, although he did not mention specifically about keeping the simcard together with mobile data enabled during all the time
I'm about to flash mine now and wait with everything enabled, following that solution.
Will report back in here after a while
Cheers!

active usb debugging and active oem, the same happens in note 9, waiting for your experience

For what it's worth, I'm going to share what I've done; since it seems like I've somehow just stumbled through the same issue on my note 9, without having to wait any substantial amount of time. Hopefully it's of some use to someone.
I originally had N960FXXU3CSF9 (rooted with TWRP installed) on my Exynos Note 9; flashed stock N960FXXS3CSG5 using Odin, got about half way through the new device setting up process then black screen with "Only official released binaries are allowed to be flashed" message.
Me rambling about my fails
After the initial 30 minutes of panic and swearing, got the phone to download mode (Volume Down + Bixby, plug in USB from PC), then various combinations of trying to flash the same stock N960FXXS3CSG5 rom, TWRP, trying to install no-verity-opt-encrypt and Magisk-v18.0. The only change I noticed was RMM state sometimes seems to be stuck on "checking" instead of "Prenormal" while in download mode sometimes; either way, all ends with the same "Only official released binaries are allowed to be flashed" brick.
Last ditch attempt that worked for me:
(from RMM msg brick)
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed the old N960FXXU3CSF9 stock rom with Odin;
- Turned phone off after 1st reboot after ^;
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5
- Held down Volume Up + Bixby + Power before reboot from ^, to boot straight to TWRP recovery
- Transferred N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip & Magisk-v18.0.zip from PC to external SD card
- From TWRP, Wipe - Format Data - "yes"; after format is done, press back to first TWRP page
- Install N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip
- Install Magisk-v18.0.zip
- Wipe Dalvik Cache
- Reboot to System
More rambling
it then took a few minutes with boot img before "optimizing apps" (I assume this is code for Samsung black magic and murdering imaginary orphans?) then eventually I got to enter my details through the new device set up process... for the 10th time today. So far it's been about 6hrs since I've put all my apps back, in developer options OEM unlocking is off, but
I have root access back, and everything seems to be fine.
Sorry that I kept jumping between tenses and waffled on a bit there; it's been a long 20 hrs of reading forums, articles, hand cramps death gripping phone buttons and bashing head against desks. Hope this is useful to someone, I'm off to find 2 tin cans and some string.

Need help for n9... Prenormal

ASUS ROG2 SOFT BRICK

Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.

KnowThyPro said:
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
Click to expand...
Click to collapse
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.

reg66 said:
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
Click to expand...
Click to collapse
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.

KnowThyPro said:
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
Click to expand...
Click to collapse
Any news?

reg66 said:
Any news?
Click to expand...
Click to collapse
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.

KnowThyPro said:
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
Click to expand...
Click to collapse
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?

reg66 said:
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
Click to expand...
Click to collapse
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?

KnowThyPro said:
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
Click to expand...
Click to collapse
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest

reg66 said:
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
Click to expand...
Click to collapse
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.

KnowThyPro said:
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
Click to expand...
Click to collapse
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?

reg66 said:
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
Click to expand...
Click to collapse
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...

KnowThyPro said:
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
Click to expand...
Click to collapse
I've been googling for you dude but no joy yet.... will have another look tomorrow

reg66 said:
I've been googling for you dude but no joy yet.... will have another look tomorrow
Click to expand...
Click to collapse
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/

was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?

Sorry bud, really not sure what's going on with your phone or know much more. Good luck with it tho

KnowThyPro said:
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Click to expand...
Click to collapse
Actually, if you now have recovery, what about booting into twrp and flashing lastest 2012.65 zip from asus website, twice - both slots. see if that fixes your wifi issue
As you said using the QFIL approach worked to boot into system and recovery is back - boot to twrp from that state

KnowThyPro said:
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
Click to expand...
Click to collapse
I think my i messed my phone like yours. Can you provide me step by step? I have tried those step one by one but still stuck at rog logo

URGENT HELP!!! PLEASE HELP RIGHT AWAY!!! I WANNA CRY!!!

My phone is stuck on bootloop ENDLESSLY with NO FASTBOOT, RECOVERY OR WHATSOEVER, ONLY LOGO WITH UNLOCKED BOOTLOADER after bugged failed safetynet fix module. judging by this, it must be some soft brick with some of the sys files. I have everything, but can't install back to stock and then reinstall SHRP and restore from last known good config just before the cursed module
I DELETED AND DISABLED THE MODULE AND REBOOTED, BUT NO RECOVERY NO FASTBOOT.... NOTHING
PS: IMPORTANT - I noticed that the very small message low left BLOW: SUCCESS has dissapeared
How to reflash, please help me!!!!
I can buy u a coffee with paypal, please help me reflash back to stock with ANY METHOD

PSS: HycoonOS which works usually like a charm

Try to boot your phone to fastboot mode by pressing the buttons. It may not show the fastboot logo but it could still have gone to that mode. Happened with my old note 5 pro. It wasn't showing the fastboot logo on pressing volume up and power but it was booted to fastboot mode and I could flash a custom recovery.
So try booting to fastboot mode and flashing a custom recovery. You can also check using "fastboot devices" command.

Thanks. man, will try it. If nothing happens, can I do it with spflash

the fast edl etc areALL DEAD. will try spflash through linux now, and hopefully works

It worked!!!
1. Reflashed with SP tool in meta/download mode
2. Reflashed with fastboot
3. ReUNlocked bootloader
4. Reflashed SHRP
5. Restored FULL HyconOS backup to the latest as I left it

LordPain89 said:
It worked!!!
1. Reflashed with SP tool in meta/download mode
2. Reflashed with fastboot
3. ReUNlocked bootloader
4. Reflashed SHRP
5. Restored FULL HyconOS backup to the latest as I left it
Click to expand...
Click to collapse
Bro I have the same problem. Can you tell me the exact steps how to flash using sp flash & what files you flashed through it?

Question Redmi Note 11 Stuck/boot loop in Recovery mode

I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)

Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse

mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.

Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.

mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.

Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files

mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.