I recently tried converting my phone to the global version, but it was stuck on the flash-all.bat. Before, I was able to reboot into the bootloader and now the furthest it gets to is the oneplus screen then goes black. I cannot get EDL mode working to run the msm tool. Any advice?
See other post
Related
I first unlocked the bootloader and then flashed the TWRP image, later I flashed AEX 4.6 ROM and then I thought or reclocking the bootloader but when I did it's not booting up. The ZUK Logo appears for a second and screen goes black, the led remains lit and holding the power button for 10 seconds doesn't turn of the device , it restarts again and same thing happens.
Im not able to even access EDL(Emergency Download Mode) to use QPST or MiFlash tool.
Help me guys...
You should really learn to use "FORUM SEARCH". This kind of issue has been resolved and there are few guides available too.
Not my phone, but a friend that rooted their friend's phone.
Goal: Unlock the bootloader and root the Redmi Note 8 Pro (Global)
Steps:
- Unlocked bootloader.
- Flashed TWRP. (it worked & booted)
- Installed Magisk (worked, phone booted with Magisk)
- Update Magisk through the Magisk Manager
This is where the problem occured:
The moment they clicked on Update in Magisk Manager, before the update process could even begin, before the update file would be downloaded, the phone rebooted (vibrated as if it was force rebooted) and the display never came back on.
This makes me believe it was a coincidence and the phone just rebooted on its own anyway.
The phone seemingly appeared to not work, as the display was off and would not turn on, but the phone does actually boot into MIUI and vibrations can be made using the screen.
The phone is detected in ADB according to my friend.
I am unsure whether fastboot or recovery works, but I would assume that if the system boots, fastboot would also work.
We tried looking this up online and we get all sorts of stuff about bricks and whatnot, but nothing about a display not working but the phone booted.
This isn't a brick, as the phone boots, but there is no visual output, not even the Mi logo on startup.
Anyone have a clue?
The user isn't comfortable with messing more with their phone to fix it, but they would like to charge my friend even if the repair ends up free. This is stupid.
Should try fastboot mode and flash the stock boot of the current rom
I need help, i have a Redmi Note 8 from Telcel Carrier on Mexico, trying to change the MIUI version to global form 10.3 to 11 the phone just restart everytime that i turn it on, no redmi logo, just a black screen for 1 sec and then it turns off, when i connect it to any power source the screen goes on and off all the time, and also when i try to set the phone on fastboot, the logo appears and then it turns off again
I used Orange fox recovery, when i tried to set the rom the first time i got the 7 error code, telling me that my device was willow instead of gingko, then, i downloaded the willow global rom and when it was flashed, it just began whith the problem
Sorry for my bad english*
What about recovery mode, can you still enter orangefox? If you can't even get fastboot mode, the odds don't look so good. Will fastboot mode stay on if connected to pc with mi flash ready to flash stock ROM?.
SkullAder said:
I need help, i have a Redmi Note 8 from Telcel Carrier on Mexico, trying to change the MIUI version to global form 10.3 to 11 the phone just restart everytime that i turn it on, no redmi logo, just a black screen for 1 sec and then it turns off, when i connect it to any power source the screen goes on and off all the time, and also when i try to set the phone on fastboot, the logo appears and then it turns off again
I used Orange fox recovery, when i tried to set the rom the first time i got the 7 error code, telling me that my device was willow instead of gingko, then, i downloaded the willow global rom and when it was flashed, it just began whith the problem
Sorry for my bad english*
Click to expand...
Click to collapse
I think you bricked your phone because cross flashing, you need bring your device to xiaomi service center(if is there any in your country) or you need authorized account for flashing through edl mode
So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.
While using the phone it suddenly gone freezing and started showing 'Qualcomm CrashDump Mode'. Then flashed the stock 11 ROM following this method but showed the 'Qualcomm CrashDump Mode' after showing the OnePlus logo. The phone is showing a complete black screen after showing the OOS (I tried both 10 and 11). I'm also able to boot into Fastboot and also stock recovery. But unable to go past the OnePlus logo.
I did this same method MSM Download Tool method last day and the phone worked without any issues till a few hours ago.
Hardware prob