Database Users

I've bricked my device after flashing CM12.1 and need help urgently

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! ZTE Axon 7 won't boot after deleting Lineage and TRWP

Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways

If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition

Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.

tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it

Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks

tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum

jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/

That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.

https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.

wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc

Was finally able to get into recovery, so all is well. Thanks for the help yall

OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?

gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc

My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

Solved Moto g4 always turn on in recovery mode

Solved (update)
In the end I finally understand that it was possible reinstall a stock rom with Android Nougat, the hard part was find the correct stock rom, then with fastboot method, one command at the time I managed to get back my phone with stock Nougat and solve the reboot issue.
Now I will wait if the official Oreo update comes for this phone too and see if it can be updated.
High everybody's, I see there's few trend that talk to the same problem I'm experiencing with my moto g4, but none one get a solution to this, so I try too.
First, I'm using a resurrection remix rom (nougat), when I reboot or turn off and then on again the phone goes always in recovery (twrp). So I have to select reboot to bootloader and from there select start to properly boot the phone.
I already try using this command from my PC with the phone connected in fastboot mode:
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
But nothing happened.
I can change the ROM if it worth to solve the problem, also I see there's a resurrection remix with android Oreo or wait for official Oreo ota that could possibly be on line soon.
Second, in case I can't solve it with a custom rom, there's a way to come back to the original ROM (android 6), and wait for the official update or the downgrade it is impossible?
Thanks to anyone that can give me any advice or help.

Well, how did you fix the recovery boot issue?

shadymnms said:
Well, how did you fix the recovery boot issue?
Click to expand...
Click to collapse
Hi, thanks to the help of @echo92 in this forum, here the link of the topic: https://forum.xda-developers.com/mo...e-nougat-to-marshmallow-t3487201?goto=newpost
He share the proper and last official nougat stock ROM NPJS25-93-14.7-8, is specific to XT1625/XT1644 my device it's XT1625.
Then connecting my device to my PC and using fastboot command I reinstall each part of the stock firmware.
If you search the way to use fastboot command here one of the topic where explain it: https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Bye

Nokia 6.1 installed TWRP problems since

Hello,
I recently tried to degoogle my phone with Lineage and twrp. It's been a bit of a brick wall. Long story short i'm stuck in twrp. It boots into recovery fine from that. Everything else is DOA. When I plug it in the pc recognizes it and I can see my storage. I run adb devices and it comes up. When I reboot to bootloader I see download as I should on the phone screen and I hear it connect to the pc. Then that's it, it doesn't show up as storage or when I run adb of fastboot commands. I fairly certain TWRP F'd this all up. I have the recovery image for lineage but like I said nothing gets done.
So the question is, is it totally bricked or is there a soulotion I haven't found yet?
Thanks for the listen.

Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...

gouthamram said:
Some LineageOS build working with own recovery so you can try to flash with LineageOS recovery via sideload option...
Click to expand...
Click to collapse
That's the whole problem. I can't even do that.

mech1164 said:
That's the whole problem. I can't even do that.
Click to expand...
Click to collapse
First of all flash LineageOS recovery on fastboot mode then restart to LineageOS recovery & flash LineageOS rom via adb sideload...
Everything you will do even working fastboot mode...
A/B partition system is caused whole problem so this is only the method to flash custom rom...

As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?

The problem might be the recovery image you want to flash as it's for a Nokia 6.1 (PL2) not Nokia 6.1 Plus (DRG).
If your device is actually a Nokia 6.1, then you could try the `Install Recovery Ramdisk` option in TWRP, under `Advanced`.

mech1164 said:
As I said this has been the whole problem. I boot back to bootloader where It says Download Mode. When I try to flash the recovery image this is what I get.
C:\Users\rpwor\NexusTools>fastboot flash recovery lineage-18.1-20210831-recovery-PL2.img
< waiting for any device >
And there it sits never to move again. Now do you understand what i'm dealing with?
Click to expand...
Click to collapse
How is your brick? Did you find a way to revive it?