Hello. When trying to run TWRP on OnePlus Nord N100, in fastboot with the command: fastboot boot twrp.img, the computer indicates that everything went well, but instead of loading into TWRP, the smartphone froze 1+, Powered By Android and hangs. What can be done to get TWRP running?
Oh god, the same thing happend to me, just don't use that command with TWRP on OnePlus Nord N100, your phone is pretty much soft-bricked, could get worse.
Trust me, i've Hard bricked my phone 3 times using this method, you need to recover it, if you want root, just get the boot.img and patch it with magisk, rename it back to boot.img and flash the boot with the new boot.img.
(MSM will help you recover your phone to factory settings, i can help you further once i get back home.)
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
After getting phone hard bricked for the first time, on my second attempt to load a custom rom, the phone hard bricked again.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
Click to expand...
Click to collapse
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
I don't know a lot about bricks in general but i think you are supposed to format data after you flash the recovery because that's what i did after installing arrow os but i don't know how would that cause a hard brick.
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
regedit12345 said:
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
Click to expand...
Click to collapse
The problem is I have another exact device which is running the latest version of PE fine.
jylee1997123 said:
The problem is I have another exact device which is running the latest version of PE fine.
Click to expand...
Click to collapse
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
regedit12345 said:
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
Click to expand...
Click to collapse
I think there is some confusion here.
Are you referring to the first hard brick? No OTA update is performed because it is running PEX which does not support OTA updates.
If you are referring to the second hard brick, the phone is never in PE firmware at all. The moment I tried to flash PE rom, the phone got hard bricked with these steps. ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
2 Devices
1) My personal device (POCO F3 Alioth) - Working fine with current latest stable PE
2) Her device (POCO F3 Alioth) - HardBricked, EDL when flashing with these steps ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
jylee1997123 said:
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
Click to expand...
Click to collapse
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Zainullahk1234 said:
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Click to expand...
Click to collapse
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Try flashing aospa.
jylee1997123 said:
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Click to expand...
Click to collapse
hmm i dunno then pe works perfectly on my x3 pro
are you sure your using the correct firmware?
try flashing miui firmware over it and booting (cause mabye the oss vendor is the issue)
or just sell your f3 and get the f4 once it comes out (looks to have snapdragon 8 gen 1!)
Try installing CrDroid, follow their installation steps, they work very well
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
usmanjavid said:
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
Click to expand...
Click to collapse
You definitely haven't tried PPUI
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
LOL
dont mention that buggy mess
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
i tried installing this instead of arrow os and i couldn't even boot into it it would just go back to miui
Zainullahk1234 said:
LOL
dont mention that buggy mess
Click to expand...
Click to collapse
I have tried all the A12 roms including syberia and arrow and by far this is the best rom. The maintainer of the rom is dev himself and very active and responsive on the telegram grp.
[Discontined][12.0][alioth/aliothin] Pixel Plus UI Poco F3 / Xiaomi Mi 11X / Redmi K40
This tread was discontined as far as I dropped support of PixelPlusUI Project. Thanks to all users and supporters who was Interested to project. Future Development for Poco F3 will be according to own new project - VoidUI Project Github...
forum.xda-developers.com
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
i have seen pixel extended that got his thread closed because at shutdown the phone bricked so it really is the roms fault
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
Pixel extended= bad
pixel experience= amazing
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
That's why I suggest using CrDroid, mostly because I haven't failed any installation following their installations steps, the ROM being stable and having good customizations is a perk that comes with it
I switched from dotOS to Pixel Experience because I wanted to get a taste of A12. After the change my phone started behaving strangely. It doesn't turn up on Windows File Explorer anymore and ADB doesn't detect my phone unless I set it to USB charge only. Plus the biggest problem of them all- TWRP doesn't work anymore. Whenever I reboot my phone it boots into TWRP, and the screen keeps flashing at the TWRP logo. The only way to boot to A12 is to enter fastboot and hit fastboot continue in the CMD. I'm at my wits end here and honestly a bit desperate. I have attached the logs from when the TWRP screen kept flashing. I wiped my device completely before installing Pixel Experience and I think that may be the problem. I fear that I may have sort of permanently damaged my phone or something. Any help would be appreciated. Thank you.
Pixel Experience A12 has it's own recovery u need to use that twrp or orangefox won't work on that rom same as los has it's own recovery
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
TWRP doesn't work with A12.
ffejy462 said:
TWRP doesn't work with A12.
Click to expand...
Click to collapse
This, decryption isn't supported AT ALL by any recovery running on A12. I've seen modified recoveries for A12 for other devices and it seems they try to disable forced encryption which is a BAD idea!
If you want to decrypt, would recommend either staying with OOS 11 or a custom ROM on A11. Bear in mind there have been numerous reported issues with TWRP hence why most custom ROMs for the OP9P choose to stick to LineageOS recovery.
cat139lyleb said:
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
Click to expand...
Click to collapse
It's because you flashed an incompatible TWRP (not compatible with Android 12 ROMS)
Okay, maybe TWRP is already aware of this problem with 12 ROMS, plus I already did tried a few times with OEM unlock in 11, but no luck. So that's why OEM unlocked in 12... very weird...
The bootloader won't unlock until OEM unlocks in any android versions. So first, that's why.
I have a question about that. Do you think it's why -> SECURE BOOT - YES?
Then how do we make it say NO?
Because we are aware that it is FULLY unlocked as DEVICE STATE - UNLOCKED, correct?
Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.
Mjammjam said:
Hi,
my LE2123 OnePlus 9 Pro is successfully resisting a boot into the recovery. This is not the first phone I flashed, but this time I am a little out of luck and ideas what to do next. Maybe someone would have an idea on what's going wrong - already many thanks in advance.
It's a Model LE2123 with OOS 11.2.2.2.LE15BA7.
As I got it, I did the following:
OEM Unlock
Reboot into Bootloader
fastboot boot twrp-installer-3.6.2_11-0-lemonadep.zip
TWRP puts the device into the "Fastboot Mode" Screen (the on with the icon in the middle) and that's it. Trying other recoveries, like from e.OS (recovery-e-1.1-r-20220629200015-dev-lemonadep.img), this make the phone boot OOS right away.
With that being unsuccessful, I reverted back to stock OOS 11.2.2.2 going through EDL and MsmDownloadTool V4.0.exe, pushing "rev_OverSeas_210324_2236_release_OTA-BLOCK_Signed_fp2103242236_cve2021-03-01_ufs_Oxygen-OS-11.2.2.2.LE15BA" from the forum here on it (Kudos!).
That I updated to OOS 11.2.10.10 through a local system update (using OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_a28e911b11ec5.zip from here as well. Kudos again!).
After that I tried the various recoveries available (twrp-installer-3.6.2 (no other version), e.os recovery (all available), lineageOS recovery (both 18.1 available)). But all of the fail to boot, same as before: TWRP does not start, e.OS and lineageOS recovery hang shortly, then boot the OS (which then takes like 3 minutes to boot, but does so successfully).
So I am right out of clues. If anyone would have an advice what else I could try - greatly appreciated!
Many thanks for your help.
Click to expand...
Click to collapse
Alright, so this is what you're going to want to do (please tell me if you attempted this)
1. MSM back to stock, then unlock bootloader
2. Update to 11.2.10.10, then flash recovery (make sure you do fastboot flash boot lineage.img from bootloader, not fastbootd)
3. Then, make sure you type "fastboot reboot recovery"
It should work after that.
Thanks for your reply razor.
I did it similarly, but not identical:
- Instead of flashing the recovery, I just booted into it. (fastboot boot .\lineage-18.1-20220524-recovery-lemonadep.img). In the past this had always worked out as a good way to try it out first.
- I did not not to fastboot reboot recovery, as that happened automatically when fastboot boot was done.
The phone is right now still on 11.2.10.10. It was flashed back to stock 11.2.2.2 using MSM and then from android settings locally updated to 11.2.10.10.
So right now I could go ahead and do as you said:
- fastboot flash boot lineage.img: Which recovery should I use? LineageOS proposes to match it with the Android version, so that should be LOS 18.1: lineage-18.1-20220524-recovery-lemonadep.img ?
- fastboot reboot recovery (I guess that will happen automatically again)
Thanks!
One thing that I checked is that slot B seems to be all empty right now. Setting this as active goes into bootloader right away. Maybe that confuses the recovery.
I managed to get into recovery now, fastboot using twrp.img word.
fastboot boot twrp-3.6.2_11-0-lemonadep.img
With both of these I had no luck getting into recovery, instead they start into OOS right away:
fastboot boot recovery-e-1.1-r-20220629200015-dev-lemonadep.img
fastboot boot lineage-18.1-20220524-recovery-lemonadep.img
LE2123 with OOS 11.2.10.10.LE15BA