Database Users

my divece is being hard brick. what do i do now?

Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.

throw it out of the window.You're welcome. Sorry.coudn't help it.You should provide a bit more details

sonhg said:
thanks!
Click to expand...
Click to collapse
Follow this tutorial and first try the third method. If that doesn't work then try the second one :silly:

thanks
MASK10101012 said:
throw it out of the window.You're welcome. Sorry.coudn't help it.You should provide a bit more details
Click to expand...
Click to collapse
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.

sonhg said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Click to expand...
Click to collapse
My friend,this is no hard brick.sometimes this error happens because because your recovery.img file is corrupted.Check that your recovery.img is found in the cmd folder...And use command 'fastboot boot recovery.img' << this one surely will work.Otherwise,please follow my own thread where I faced an identical problem..>>http://forum.xda-developers.com/lenovo-a6000/help/problem-flashing-rom-soft-brick-t3353665 Oh,and calm down, not that serious of a problem,you wont have to go to the dreaded service center.

sonhg said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Click to expand...
Click to collapse
When you can't even enter to bootloader (or fastboot), that situation is called hard brick. The problem you are facing is due to the wrong recovery version. Try this latest twrp 3.0.2 by sevenmax.
And yah, if "fastboot flash recovery recovery.img" doesn't work, then try "fastboot boot recovery.img"

sasukay said:
Follow this tutorial and first try the third method. If that doesn't work then try the second one :silly:
Click to expand...
Click to collapse
This method alsi not gud. Try this method.
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
I did it & saved from hardbrick. Just do whatever files u have. But dont forget ti erase boot. Erase boot then flash boot* this is main step. Then flash twrp and instll any backup or new rom.

Follow these instruction.... main files are in stock firmware file. Recovery alone flash ur own custom recovery of ur choice

rule breaker sarath said:
This method alsi not gud. Try this method.
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
I did it & saved from hardbrick. Just do whatever files u have. But dont forget ti erase boot. Erase boot then flash boot* this is main step. Then flash twrp and instll any backup or new rom.
Click to expand...
Click to collapse
Bhai, This method is for soft- bricked device, when you can enter bootloader.
In case of hard brick you can' t even enter in bootloader, and can't run these commands. The link I posted is for hard bricked devices.
And, you don't actually need to go through these complicated steps in case of soft brick.
Just flash any recovery through bootloader and then flash any ROM. You don't need to extract and flash each file separately.

Asus ZenFone 2 Laser 551KL Z00TD soft-bricked in bootloop

Hi XDA Community,
I'm in a bit of a pickle. Yesterday my Zenfone started to bootloop and I tried to reset to fabric settings in bootmode but it didn't do anything. Afterwards I put the stockrom (Lollipop) and the latest rom (Marshmallow) and installed them. No errors, but it is stuck in bootloop and I can only enter fastboot mode now and it gets stuck there.
Tried Intel SoC solution, no results and also QFil but it isn't shown under ports.
How can I unbrick it?
Thank you very much.

The way I did it
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.

utahja1 said:
If you install the latest version of twrp it should automatically boot correctly as if nothing happened. it's strange, but every brick I have had has been fixed that way.
Click to expand...
Click to collapse
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s

So, I finally managed to install the latest version of TWRP and SuperSU (don't know which version, tried two of them and thee TWRP install and finally one of the stuck).
I tried back2stock with 1.14 and 1.17 firmware, but the same problem happened. Bootloop and bootloop, on and on and on. The curious thing is that I didn't encounter any error message during installations so what could be the problem. Is there a log I can see to disover what could be the solution.
Thank you.
adriantamas said:
Tried it.
This is the error that it gives me.
g:\adb and recovery>fastboot boot twrp-3.1.1-0-Z00T.img
downloading 'boot.img'...
OKAY [ 0.944s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.953s
Click to expand...
Click to collapse

TWRP for Lenovo Tab 4 10 Plus TB-X704A

Hi!
I've been looking around and found the TWRP for L/F but not the A model. TB-X704A has been out for a while now and I'm trying to root it.
If someone can help me achieve root on it or has the TWRP for this model, I would really appreciate your help.
Kind Regards, Joaquin

Any luck?

alekdavis said:
Any luck?
Click to expand...
Click to collapse
No. If it's not for personal use, I'd highly recommend the classic SAMSUNG Galaxy Tab E T560. Very high community support.

Also looking to root my x704a if help can be found

Someone linked the Chinese version that works for the x704a. I just flashed it on mine and I can confirm it works:
https://forum.xda-developers.com/showpost.php?p=79635441&postcount=213

scorcher64 said:
Someone linked the Chinese version that works for the x704a. I just flashed it on mine and I can confirm it works:
https://forum.xda-developers.com/showpost.php?p=79635441&postcount=213
Click to expand...
Click to collapse
were you able to get any custom roms on you device or did you have any further issues?

I am unable to boot lenovo tab 4 10 plus to twrp recovery after successfully flashing
I am unable to boot lenovo tab 4 10 plus to twrp recovery after successfully flashing. Need your help.
Please see the below ADB screen results:
PS C: Users bhask Downloads Lenovo Tab 4 10 Plus ADB & Drivers platform-tools_r30.0.4-windows platform-tools> fastboot devices
1824dcea fastboot
PS C: Users bhask Downloads Lenovo Tab 4 10 Plus ADB & Drivers platform-tools_r30.0.4-windows platform-tools> fastboot flash recovery D: twrp-3.4.0-0-X704F.img
Sending 'recovery' (27726 KB) OKAY [ 1.221s]
Writing 'recovery' OKAY [ 0.374s]
Finished. Total time: 1.658s
PS C: Users bhask Downloads Lenovo Tab 4 10 Plus ADB & Drivers platform-tools_r30.0.4-windows platform-tools> fastboot boot D: twrp-3.4.0-0-X704F.img
Sending 'boot.img' (27726 KB) OKAY [ 1.187s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
PS C: Users bhask Downloads Lenovo Tab 4 10 Plus ADB & Drivers platform-tools_r30.0.4-windows platform-tools>
Please anyone help me.

Does anyone have Information regarding Zenfone Max Pro m1 X00TDB?

It is very hard to find any Information on the ASUS Zenfone Max Pro M1 X00TDB Modell, is there someone who knows more?
I cannot find a modell specific twrp recovery.img or any kind of Custom OS support
Maybe someone can show me how to compile them myself?
My Bootloader is already unlocked
When I try to install the unofficial X00TD recovery.img, I just get this error code:
PS C:\adb\unlock> fastboot flash recovery twrp-3.2.2-1-20180727-X00TD.img
Sending 'recovery' (58328 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
For some reason my stock android recovery it says:
asus/WW_X00TD/ASUS_X00T_1
Is that normal?
Any advice is helpful, thanks in advance
*UPDATE: I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.

OT4KUBoi said:
It is very hard to find any Information on the ASUS Zenfone Max Pro M1 X00TDB Modell, is there someone who knows more?
I cannot find a modell specific twrp recovery.img or any kind of Custom OS support
Maybe someone can show me how to compile them myself?
My Bootloader is already unlocked
When I try to install the unofficial X00TD recovery.img, I just get this error code:
PS C:\adb\unlock> fastboot flash recovery twrp-3.2.2-1-20180727-X00TD.img
Sending 'recovery' (58328 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
For some reason my stock android recovery it says:
asus/WW_X00TD/ASUS_X00T_1
Is that normal?
Any advice is helpful, thanks in advance
*UPDATE: I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.
Click to expand...
Click to collapse
I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.
Now I have a new problem, when I try to Install the official LineageOS X00TD https://download.lineageos.org/X00TD on my X00TDB Device I get an error 7 message on TWRP, do you guys know a solution?

Installed Android 12 firmware onto Android 11 (LineageOS 18.1)

See solution here: https://forum.xda-developers.com/t/...roid-11-lineageos-18-1.4488535/#post-87389567
--------------------------
Original post:
--------------------------
Hi guys,
I don't even want to take much of your time. Maybe someone knows a solution off the top of their head.
Does anyone have any idea what I could do to either
flash the OxygenOS 11.0.11.11 firmwares again?
or save my user data through fastboot?
all while avoiding using the MSMTool?
My last hope is trying to lock the bootloader and then unlock again. Seems to have helped some dude... but it's kind of a last resort before MSMTooling the sh*t out of this phone... However... doesn't fastboot oem unlock wipe everything anyway...? ughhh
Phone: OnePlus 8 Pro (IN2023 - EU Model).
If I could save my user data at least, that would be great! (Latest backup is a couple weeks old.)
I was using LineageOS 18.1 (Android 11) and decided it would be a great idea to update the phone's firmware partitions to the official OxygenOS 12 / Android 12 versions, using https://wiki.lineageos.org/devices/instantnoodlep/fw_update (and yes, I used the DDR5 files)
After receiving a not-at-all concerning "boot/recovery partitions are destroyed" message... I am now stuck in the Bootloader.
I managed to actually access the stock recovery by flashing stock boot.img and recovery.img from the OxygenOS 12 zip. But that is all. What can I do here, besides "Format data"? It seems nothing...
I was rooted before, now I'm wondering if I should patch the A12 boot.img and try that... but why would that make a difference...
These are my example results after trying so many things and Google just wasn't helpful:
Code:
fastboot flash abl abl.img
Sending 'abl' (2112 KB) OKAY [ 0.058s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
(same for abl_a and abl_b and all other partitions, except modem)
Code:
fastboot boot twrp-3.6.2_11-0-instantnoodle.img
Sending 'boot.img' (67268 KB) OKAY [ 1.482s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
(WHY??? If only this worked! Either it is this, or it actually does boot, but into a screen that only says "FastBoot Mode", without the serial numbers and so on that you can usually see in the bootloader.)
Code:
fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Code:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
Thank you to everyone who just read this!
Cheers!

Once you update firmware MSM is you're only hope to go back

Oh my God!
I was somehow able to revive my phone with all my data intact!
Flashed LineageOS 19.1 recovery through fastboot
Booted into said recovery
Activated ADB sideload
Sideloaded the latest LineageOS 19.1 zip
Rebootet into recovery again
Sideloaded MindTheGapps
Rebooted to system but got stuck in a bootloop with the LineageOS logo
Reflashed firmware from the OxygenOS 12 C.33 zip as per https://wiki.lineageos.org/devices/instantnoodlep/fw_update
And that just did the trick! All my settings, all my data, everything was there!
I was even able to patch the boot.img with Magisk, now having root again and the fingerprint sensor working as well, thanks to the Android 12 / ColorOS 12 Fingerprint fix for Magisk by wuxianlin and MlgmXyysd (from https://github.com/wuxianlin/ColorOSMagisk)
I will leave this here, in case anyone comes across a similar issue.
Maybe it can save someone's life!
I would probably have preferred to somehow go back to Lineage 18.1 or OxygenOS 11, but LineageOS 19.1 doesn't seem to be nearly as bad as OxygenOS 12 is. So I guess I'll be OK with Android 12 for now... let's see.