So I was scrolling through some Magisk Modules and I think I installed the wrong one by not paying attention, as I installed it I couldn't stop the process and either way I was screwed, afterwards it showed up in the "Modules" section and I hit the trash can and rebooted. Afterwards the phone does not boot and cannot get to the recovery.
Can one of you good people give me steps to when I get to my computer. please and thank you!!
InfinityXDA said:
So I was scrolling through some Magisk Modules and I think I installed the wrong one by not paying attention, as I installed it I couldn't stop the process and either way I was screwed, afterwards it showed up in the "Modules" section and I hit the trash can and rebooted. Afterwards the phone does not boot and cannot get to the recovery.
Can one of you good people give me steps to when I get to my computer. please and thank you!!
Click to expand...
Click to collapse
If your bootloader is unlocked, while phone is booting press power button for 7-8 seconds or more this will restart your phone, when you see the black screen press vol down button to enter fastboot mode.
After fastboot mode you can flash stock rom with mi flash
Kineceleran said:
If your bootloader is unlocked, while phone is booting press power button for 7-8 seconds or more this will restart your phone, when you see the black screen press vol down button to enter fastboot mode.
After fastboot mode you can flash stock rom with mi flash
Click to expand...
Click to collapse
Thanks man I appreciate it! So after I do this do I have to re-unlock my bootloader?
InfinityXDA said:
Thanks man I appreciate it! So after I do this do I have to re-unlock my bootloader?
Click to expand...
Click to collapse
No you don't have to relock. You can use it as like that.
You should keep bootloader unlocked always in my opinion. It's not a bad or dangereous thing.
Kineceleran said:
No you don't have to relock. You can use it as like that.
You should keep bootloader unlocked always in my opinion. It's not a bad or dangereous thing.
Click to expand...
Click to collapse
When I go to the boot loader it reboots after like 1 minute then it stays on the android one screen until I reboot it to recovery. So I think my device is done and over with?
InfinityXDA said:
When I go to the boot loader it reboots after like 1 minute then it stays on the android one screen until I reboot it to recovery. So I think my device is done and over with?
Click to expand...
Click to collapse
Could you take a photo or video of that
This is a full video of what happens when I go to the bootloader
InfinityXDA said:
This is a full video of what happens when I go to the bootloader
Click to expand...
Click to collapse
prepare mi flash with rom and everything so you just have to enter fastboot and quickly plug in usb then start flashing.
Fastboot maybe just quits automatic if there is no input?
merlin.berlin said:
prepare mi flash with rom and everything so you just have to enter fastboot and quickly plug in usb then start flashing.
Fastboot maybe just quits automatic if there is no input?
Click to expand...
Click to collapse
Yes you right at that point but fastboot hasnt a timer
He should flash quickly.
Or using sideload method will be a good way to flash pixel experience and after that, turn to stock
Indeed thank you for so much help I'm indeed new to Xiaomi Devices, weird setup from my first rooted device which was much more complex. Thanks for both of your assistance
In less than 45 minutes I'll fill you in upon what I will do
InfinityXDA said:
Indeed thank you for so much help I'm indeed new to Xiaomi Devices, weird setup from my first rooted device which was much more complex. Thanks for both of your assistance
In less than 45 minutes I'll fill you in upon what I will do
Click to expand...
Click to collapse
Do you have MIFlash installed?
I had the same automatic reebots while in fastboot
regardless of the input but that was because i had the wrong drivers
When I installed MIFlash the right drivers were also installed
Hope this helps.
Related
I was trying to update my phone and something most likely went wrong. Then the update installed and screwed up my phone. When I turned it on it stayed on the startup for so long. I tried to clear cache through the bootloader, but now it shows the android screen of death except it flashes. This occurs even outside the bootloader.
I am rooted with stock os.
Thanks in advance to whoever helps
Flash it with the original firmware
anfalanl said:
Flash it with the original firmware
Click to expand...
Click to collapse
Yup, same thing happened to me, I had to reflash it to stock firmware.
How would i flash
Magister54 said:
Yup, same thing happened to me, I had to reflash it to stock firmware.
Click to expand...
Click to collapse
Hey, thanks for the response.
Could you please elaborate on how I would do this. Because I do not understand how to do this if the bootloader doesn't work.
Thanks, your response and input means alot
Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"
Magister54 said:
Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"
Click to expand...
Click to collapse
When i try to do this, i see the error sign but it is flashing
hudasameer450 said:
When i try to do this, i see the error sign but it is flashing
Click to expand...
Click to collapse
That's normal. When you get the error sign when booting into stock recovery, hold power down and press volume up and quickly release both buttons at the same time. If done correctly recovery menu will pop up and then you can start actually flashing.
Flashing
does this still work if the screen is flashing, because I tried before and it did not work, maybe I pressed it wrong or there is some other issue.
Thanks
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
try sideloading the full OTA.
https://developers.google.com/android/ota
robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you
v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable
robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes
robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,
Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.
I have a unlocked bootloader EVR-AL00 that has been bricked for awhile now. TWRP is stuck on load screen on erecovery and recovery. I have tried everything to get it to work. I can get to the bootloader screen and flash from Hstool, Funkyhuawei, ADB and Hisuite but it always goes back to the TWRP load screen and stays there. TWRP crashed on me back then and now it seems EMUI is gone forever. Any new tricks out there that might work? Please help if you can! Thank you!
can flash stock recovery via adb?
Which Firmware version is on it?
letschky said:
can flash stock recovery via adb?
Which Firmware version is on it?
Click to expand...
Click to collapse
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Steamer2499 said:
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Click to expand...
Click to collapse
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
letschky said:
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
Click to expand...
Click to collapse
That doesn't work either
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Rudolpht said:
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Click to expand...
Click to collapse
I can't get into TWRP. It is frozen on load screen
Steamer2499 said:
I can't get into TWRP. It is frozen on load screen
Click to expand...
Click to collapse
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Rudolpht said:
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Click to expand...
Click to collapse
To bad there's not a patch for TWRP...
I know there are some smart people out there that could tell me how to un-brick my phone
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
CCJ22 said:
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
Click to expand...
Click to collapse
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
ajsmsg78 said:
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
Click to expand...
Click to collapse
Sh*t if you can't help him it's not looking good.
Hi Friend,
I have tried to flash a stock firmware to Oneplus 9 pro (model LE2125) and I have followed this thread https://forum.xda-developers.com/t/restore-oneplus-9-to-stock-via-fastboot-commands.4265153/
but when I did a command "fastboot reboot fastboot" for flashing a file in userspace. the phone is going to black screen and cannot do anything untill now and I found that COMPort in device manager always up but I cannot do anything.
btw, I have tried to press all button Vol- Vol+, power but it does not work.
So, Could you guys please advise me how can I go back to fastboot mode again ? or I need to wait untill battery has died and try to turn on a phone again ?
Thank you
If the problem is occur on only camera app then check you use the latest version or old, if you use old version then update it. If you sing latest version that clean your mobile from cleaner.
iqranawaz said:
If the problem is occur on only camera app then check you use the latest version or old, if you use old version then update it. If you sing latest version that clean your mobile from cleaner.
Click to expand...
Click to collapse
Thank you for you answer, but the problem is I cannot turn on the phone for now. the phone still black screen and I can see a COMPort of this phone in device manager. I dont know why
NattDew said:
Thank you for you answer, but the problem is I cannot turn on the phone for now. the phone still black screen and I can see a COMPort of this phone in device manager. I dont know why
Click to expand...
Click to collapse
Ohh sorry i don't know why it happens but if complete black screen and when pressing the power button the phone won't vibrate. If this happen firstly charge the phone for 15 minutes at least and then try to turn on the phone again, if the phone has the black screen after power on, suggest you to apply for the after-sale services.
I am stuck in fastboot and can only boot into fastboot please help??
I can only accsess fastboot and cannot reboot into anything except fastboot.... I tried extracting the payload bin but can only flash a few lines then I am told to reboot into fastbootd but cannot access that either... I cannot access recoveries...
forum.xda-developers.com
Same issue. Trying to use msm tool but it stops after 18s.
fungisimp said:
Same issue. Trying to use msm tool but it stops after 18s.
Click to expand...
Click to collapse
Hi. did you get any fix. i am facing exact same issue. Black Screen, no EDL, after manually flashing from CMD.
it happed after when I did a command "fastboot reboot fastboot" for flashing a file in userspace. same as you.
BrokenOp9 said:
it happed after when I did a command "fastboot reboot fastboot" for flashing a file in userspace. same as you.
Click to expand...
Click to collapse
it shows up in device manager. But I took a break from it for now. I’ll get back to you if I get it.
fungisimp said:
it shows up in device manager. But I took a break from it for now. I’ll get back to you if I get it.
Click to expand...
Click to collapse
i hope we will get some fix.