Dear Sir,
My device Meizu M2 Note can't boot to Normal, Bootloader and Fastboot. well seems to be bricked.
[Device manager (Windows) detect as MediaTek Preloader USB VCOM . . . and randomly restarts with beep.[/B]
I had rooted it with Kingo root successfully.
[While unblocking the bootloade,r instead of going for “fastboot oem unlock” in the command window I accidentally switched off the mobile while" Fastboot Mode" was being displayed.[/B]
I will be highly obliged, if a solution to the above mentioned problem could be sent to me.
Regards,
Dadimaa
Related
Please help, I need proffessional help.
Android Phone: ASUS Zenfone 2 Laser 5.0 (ROOTED)
Android Firmware: 5.0.2 Lollipop
Aim: To enter into Fastboot mode and Recovery Mode without problems
Situation: Recently installed TWRP Recovery in-app and through software, but when I try to enter in Fastboot Mode (HOLD POWER & VOLUMEUP) or even Recovery Mode (HOLD POWER & VOLUMEDOWN), I just end up in a hanged out ASUS Logo. I can't do anything except pulling out the battery myself and putting it back then booting the device through power button to boot it normally. I don't know if it's the problem with the model, or the phone's system itself, or it's just a bug, or a problem when I rooted my device through ADB.
(Note: When I rooted the device, I wasn't even able to see the blue "FASTBOOT MODE" when I tried it, I only saw the ASUS logo as well.)
For anyone who has any idea on what's going on with my device, please reply and help me. I really want to have the benefits of a rooted phone completly and I'm a new root user so I need assistance.
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
CrimsonShade09 said:
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
Click to expand...
Click to collapse
Do you can acesse to twrp recovery on your device
Same problem.....waiting for helping, please
mohamedelkholy said:
Do you can acesse to twrp recovery on your device
Click to expand...
Click to collapse
I think I have "access" to TWRP recovery. However, I can only access it through booting it up from ADB. I used the command "adb reboot bootloader" to boot it to fastboot mode, however only the ASUS screen appears but I treated it as the fastboot mode itself. Then I checked if it was really on fastboot mode through "fastboot devices" and it showed my serial number. I can only enter into TWRP using "fastboot boot twrp.img" . I don't know if I already installed it because although I opened it, I can't do it from the phone (POWER+VOLUMEDOWN)
Ok now boot twrp and then flashamodified zip or cm13 and your phone should eork you dhould to have unlockrd bootloader
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
...anybody?
Up.....
sh4d3_ said:
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
Click to expand...
Click to collapse
Up...
QFIL or AFT can be the solution.
I have a similar problem, a hard bricked Z00ED (ZE500KL) not able to get into fastboot or recovery.
after reading some thread here an there. that are Processor / Chipset specific flash tools that help flash bootloaders and repartition hard bricked device.
For mobiles with MediaTec devices, there is a tool called SP Flash Tool. I wasted a whole day with it. then understood that Z00ED (ZE500KL) has a Qualcomm Processor MSM8916
Therefore we need a Qualcomm Flasher here (QFIL )
But nos I am stuck with getting firmware for ZE500KL that can be used by QFIL tool, It should have a firehouse*.mbr file that is the programmer (dependent on CPU of the phone) and a rawprogram*.hex file that I don't know where to get from.
Thanks... It seems a bit less wild, but in any case no solving, yet
Up! ...anyone?
Up!
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Download the latest stable fastboot ROM from here http://en.miui.com/a-234.html then flash it.
Sent from my Redmi 3S using Tapatalk
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Because I had this exact same thing happened before. What I did was while it kept bootlooping at the Mi boot splash I held down Vol - + power until fastboot mode pops up. Then you'd be able to flash.
Sent from my Redmi 3S using Tapatalk
Trovies said:
If only it was that easy. I've tried 3 methods above but still no luck. Use Adb reboot edl, fastboot oem.
How to flash if its only stuck at mi logo
Click to expand...
Click to collapse
First off you cannot just unlock the bootloader easily, like in fastboot or anyhow, you need to follow the guides. And this is possible by the way only with a working Dev rom.
Well so now, you've to get miflash tool and flash either stock rom, or dev rom.
You simply hold power and volume down as long (can take some time) as it will show "fastboot" and some android art.
Then you follow the guides to flash either stock rom or dev rom using fastboot, and you're good to go.
I don't see why this wouldn't be working for you, try to stick exactly to what i said. If you don't know how to use Miflash then search at en.miui.com
Trovies said:
Hai all , I am new here.
I need some help to unbrick my device. i tried almost all method and still no luck. the only method i havent tried is DFC, but i dont prefer to do it since its pretty complicated.
My device run rom Global Stable Miui 7 and i flashed Developer rom Global using EDL download mode.
there was an error and now my device stuck in Mi logo. I can still access Mi bunny fastboot ( vol down + power)
So far I have tried 3 methods
Method 1: reboot to fastboot mode, plug to pc, open ADB cmd prompt and type fastboot oem EDL. But no success because device is still locked bootloader.
Method 2: reboot to fastboot mode, plug in to pc, download fastboot EDL cmd from xda forum, unzip then run edll.cmd, device reboot to mi logo again.
Method 3: in Mi logo, plug in to pc, open cmd prompt, type Adb reboot edl, press enter but device cannot reboot to edl mode because it says I need to tap on confirmation dialog on device. But its not possible since device only load up to mi logo
Click to expand...
Click to collapse
Did you unlock developer mode as in my case I am also stuck in bootloop and fastboot oem edl is not working as developer mode is disabled thus oem is also disabled.
Hey!
I had the same Problem.
Flashing with Miflash was unsuccessfull and then EDL was locked. You can check this when the device is in fastboot and send "fastboot oem edl". Then there may be the message that EDL is locked. In that case you have to build a "deep flash cable". It is pretty easy. You can check this tutorial:
http://en.miui.com/thread-310325-1-1.html
But I would build it another way: Just cut a USB cable and reconnect all wirepairs with the open copper. Now you can just put "ground" and "data+" togehther and follow steps 7 to 9. At point 10 you can just disconnect the wires "ground" and "data+" again, so that all wires are connected normally again. Now you are in EDL and can flash with MiFlash.
Hi All,
Trying to do what should be simple - install TWRP , then omnirom.
Have a new le pro 3, running stock firmware.
have enabled usb debugging, enabled oem unlock.
I can see the le pro 3 in adb devices. I then reboot (adb reboot bootlader).
Phone goes into fastboot. But fastboot devices, or any other command cant see the phone in fastboot mode..
Appreciate any help.. I'm at a loss. Thanks!
Even if ADB show your empty list, when you're at bootloader you can flash TWRP... Look my thread about brick.
Do it with flashing guide... You should also unlock in bootloader mode. And check the status.
For anyone that cares - on a Macbook pro retaina (with windows 10 as VM) - I could only see phone in adb, not fastboot.
installed fastboot for OSX, and ditched the virtual machine, and voila.
3 months back i hv flashed fastboot rom successfully. but now i stuck with different problems with no solution
1) mobile is dead, when i hold power button mobile screen blink for a second and off again
2)when mob is dead i cant go in developer option and do all that stuff
3)in fastboot mode when i type command "fastboot oem unlock" it shows error
4)when bootloader is locked i cant flash fastboot rom through mi flashtool
this all happen because of choosing wrong patched_boot file at the time of installing magisk manager.
cmd cammand only recognize my device but cant unlock. i find only one solution that is test point method. before i proceed to that need suggestion from u gye's should i go for testpoint or to service center coz mobile is still under warranty.
You can flash stock ROM in edl mode with locked bootloader.
Put phone in fastboot mode and type "fastboot oem edl".
You should be able to flash stock ROM with Miflash. If your device is not recognised update your drivers. Google for qualcomm qloader drivers.
Next time before flashing a modified boot.img try to only boot it and see if it works.
Long story short,
I tried unofficial unlocking method to try to unlock my bootloader, which resulted in boot loop.
Oem unlock-go gave me remote unlock not allowed error.
Yes, before flashing i did all the steps correctly,
Allow oem unlock : CHECKED
usb Debugging : CHECKED
sign out mi account : CHECKED
DRIVERS correctly installed
After flashing original appsboot file, my device is working good.
Note: Also when my device was in boot loop, miflash could not detect my device, and the device manager was showing Qualcom diagnostic port 9008 or something
So please someone point me to the direction i must take, Do i need to wait for patched appsboot file for this version or something ??
If you install the rom with fastboot (MiFlash)? (Without lock option, only clean)...
I install miui10 and i have unlock bootloader (but i unlock it before official)... Equally i need to reinstall recovery in each reboot haha.
Qualcomm diagnostic? Mmm i use this to use QPST to use MiFlash need other driver...to use MiFlash i use it: Qualcomm HD-USB Qdloader 9008 (or is the same?)