Good afternoon, I have been trying for Two weeks now to try to unbrick my OP2
I have flashed, reflashed and god knows what else and the furthest I can get is into Fastboot mode.
The bootloader is locked so i cant flash using Fastboot and cant even get ADB to recognise the device.
I have tried all of Namans methods and no4 is what allows me to use fastboot.
I have no recovery or OS installed, just fastboot. USB debugging is off also.
Is there anything i can do, because im banging my head against the wall here.
Many thanks.
Did you try unlocking the bootloader?
Sorry for not replying sooner, I have been busy with work.
The bootloader is locked and Fastboot oem unlock fails.
Im beginning to feel that i own a brick.
Related
Edit: I forgot to write that the device is an MX4 normal 32gb(not pro)
So my situation is like this :
In accordance with this guide:
http://forum.xda-developers.com/meizu-mx/general/news-cm12-1-normal-mx4-t3210491
I installed Flyme OS 4.2.8.2A installed the custom recovery and succesfuly flashed CM 12.1.
But than I had a problem with my messages app that couldn't be fixed simply
so I decided to reflash Stock and than CM 12.1.
After doing so the phone is now bricked and the situation is such:
*its stuck in an infinite bootloop
*Recovery doesn't work
*Fastboot does work and recognizes my device when I type in "fastboot devices"
*ADB does not recognize my device
*When plugging in the device turned off it just charges and doesn't pop up
Only when I plug it in fastboot it recognizes it as an ADB HTC Dream device.
Things I've tried:
I tried to erase previous recovery and flash a new recovery
but I keep getting security error 0x2017
so I figure my bootloader is locked.
I tried unlocking using commands I found on the internet but they all seem to be wrong.
I get "remote: unknown command" for all the following commands:
*"fastboot flashing unlock_critical",
*"fastboot flashing get_unlock_ability"
*and "fastboot oem unlock don't work".
I've also tried this guide : http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
but the program doesn't even seem to recognize my device after I push "start" it doesn't do anything.
I despratley need your guys help and I'm even willing to pay a nice sum on paypal to anyone
that has any ideas on how to solve this.
I'm specificaly looking for some way to unlock bootloader or get my device properly recognized so I can reflash a rom..
Thanks in advance for any of your help.
Anybody? Willing to pay..
If anybody has any solution I'm willing to pay on Paypal.
Any advice will be of help..
Thanks.
From what I've gathered all Meizu devices have a locked/stripped fastboot. But have you tried through SP Flash Tool? worth a shot.
Try using CM instead of ubuntu in this thread:
http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
If you can connect your phone with those drivers and have a PID=2000(preloader), you should be able to write to anything, or you'll have PID=0003 and can't write a thing.
Not much but maybe? I'm waiting for a new motherboard to get mine up and running
The thing is I tried installing the drivers
but it doesn't seem to do anything with the drivers at all
unless its in fastboot.
How did you order a motherboard?
I'm starting to think maybe I should send it to Meizu to fix since i'm still under warranty
and make up a story about flashing stock..
Reflashed with uboot patched??????
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!
Ok I'll just rewrite this post instead of starting a new one
Drivers are installed working fine.
Phone is unlocked.
So if I trwp phone at this stage it works and I can root it.
The issue seems to be once I fastboot the 4 files to the phone phone will not boot and hence can not root it.
I've redownloaded the fastbootl29 files still no luck
Am I missing a step is the fastboot stage just sending those 4 files to the phone no unpacking/setup or anything?
Anyone in Aus want to earn some $$$
Got past that stage it's now unlocked and sitting in fastboot mode.
Now when I send the command
Fastboot flash cache c:/1/cache.img
It just says waiting for device any ideas guys
gros31 said:
Got past that stage it's now unlocked and sitting in fastboot mode.
Now when I send the command
Fastboot flash cache c:/1/cache.img
It just says waiting for device any ideas guys
Click to expand...
Click to collapse
Did you tried rebooting ur pc and ur phonte?
Got past that stage. Had to change the boot loader driver.
Load up the l29firmware in 4 parts use twrp then it won't let me root the device like it can't find it.
When trying to boot up the system it just won't boot. Now it's doing its erestore but notice it's looking for the cn firmware.
Hello and thanks in advance for taking out time to help me out here. I did something stupid. I had successfully rooted my new 6t and all was good until i turned off oem unlocking and usb debugging in developer mode. Wheni restarted my phone things went bad. Cant access bootloader or fastboot by pressing the power and volume up buttons. My pc wont recognize the phone so cant reflash or reboot into stock.
What shall i do.
Did you try fastboot devices
and fastboot oem unlock ?
Then I'd flash Oxygen from OnePlus website.
I used BluSpark on my 3T. Apparently, they have TWRP for 6T through BluSpark: https://oneplus.gadgethacks.com/how-to/install-twrp-recovery-your-oneplus-6t-0190296/
If that doesn't help go for the MSMtool.
Bonecloner said:
Hello and thanks in advance for taking out time to help me out here. I did something stupid. I had successfully rooted my new 6t and all was good until i turned off oem unlocking and usb debugging in developer mode. Wheni restarted my phone things went bad. Cant access bootloader or fastboot by pressing the power and volume up buttons. My pc wont recognize the phone so cant reflash or reboot into stock.
What shall i do.
Click to expand...
Click to collapse
If you get it booted again.
Try adb devices..... if recognized. Type..... adb reboot bootloader...
Then.... fastboot devices.
Also use TWRP fajita 3.2.3-8
I've had great luck with that one.. I rooted my 6T with blue spark but then switched to Fajita 3.2.3-8.
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry