Database Users

Help for bricked Device[Solved]

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.
Thanks

bijilidk 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.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z

Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?

bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html

sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.

bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader

bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434

Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.

bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration

neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/

So everything is solved here right ? you can close this thread now i think !

No Such Partition

I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
target reported max download size of 536870912 bytes
sending 'recovery' (45048 KB)...
OLAY [ 1.385s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.405s
Click to expand...
Click to collapse
So there is no recovery partition on my phone currently, but I can still boot to stock recovery

th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
Its likely a dodgy lead or try a different usb port!
I had it before and had to reboot my laptop that was all

We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.

th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.

tech_head said:
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.
Click to expand...
Click to collapse
My apologies, I thought I had it in that section. Thanks!

Also having trouble ..I can't flash return to stock .no boot partition also .. can flash twrp but from there I'm not sure what to do now .. any help would be great thanks

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
i did that and couldn't boot my phone

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
WOW!!! Really appreciate that!

@Somcom3X life savor, thank you

Djcall11 said:
i did that and couldn't boot my phone
Click to expand...
Click to collapse
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once you're in TWRP, you need to rewrite the boot image.

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanks...this fixed an issue I had as well rolling back to a Beta version.

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?

sruel3216 said:
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?
Click to expand...
Click to collapse
Thanks that worked. Rooted on elementalX now!

I did that, but nothing happens
kfhughes said:
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once your in TWRP, you need to rewrite the boot image.
Click to expand...
Click to collapse
I'm using a Pixel XL 2, so sorry for the post in the wrong forum, but I lucklily found the post so thought to send the query which was already ongoing here. Nothing still happens and Im stuck, it shows the logo of teamwin recovery porject 3.2.3.1 and it's stuck there. I've no clue how to proceed further.

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
alright, so I did this now I can't get back to twrp.. can you help?
Update: I opened a new thread here: https://forum.xda-developers.com/oneplus-6/help/screwed-flashing-twrp-t3846690

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Interesting, I did
Code:
fastboot flash [U][B]boot[/B][/U] stock.img
Sending 'boot__b' (20769 KB) OKAY [ 0.559s]
Writing 'boot__b' FAILED (remote: 'No such partition.')
then did
Code:
fastboot flash [B][U]boot_b[/U][/B] stock.img
Sending 'boot_b' (20769 KB) OKAY [ 0.557s]
Writing 'boot_b' OKAY [ 0.831s]
Any idea why it does the double underscore when not specifying
Code:
__b
....and the single underscore when specifying?
Code:
_b
Very odd behavior. Either way, thanks for the tip!

New Issue after this solution
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
So I did this and it worked to get twrp booted up, but now a new issue has come up. TWRP is stuck on the splash screen, and I can no longer boot up my phone since this overwrote my boot partition. So I ****ed up and tried to unplug and reboot, but when I did that I reset my USB debugging. So now I can't even get to my phone through adb or fastboot. I can boot into the bootloader, but other than that and starting at the TWRP screen I'm stuck. Any Ideas or solutions? I'm hoping I get lucky and TWRP boots up after a while, but so far it's not looking good.

Recovery Done But Not boot in Recovery
Recovery is successfully finished but device not boot in recovery
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot flash boot test-twrp-3.3.1-2-guacamole.img
target reported max download size of 805306368 bytes
sending 'boot' (55976 KB)...
OKAY [ 1.242s]
writing 'boot'...
OKAY [ 0.161s]
finished. total time: 1.412s
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot boot test-twrp-3.3.1-2-guacamole.img
downloading 'boot.img'...
OKAY [ 1.233s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.262s

Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanking you in 2019! :laugh::good:

there is a reason guides tell you to use
fastboot getvar current-slot
fastboot set_active other
because the device will flip flop between active slots depending on OTA
if you simply just specify a slot with fastboot flash boot boot_*
you could flash the wrong slot, which is bad
you do not want to overwrite your current active slot with twrp or you won't be-able to boot
once again the steps are
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot yourtwrpimagehere.img
reboot normally it will boot to twrp
then if your touch screen is not working
adb shell
twrp sideload
adb sideload twrp-installerzip

TWRP not replacing CyanogenMod recovery

Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help

badyards said:
Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help
Click to expand...
Click to collapse
You unlocked bootloader and checked oem unlock im sure.
But which command did you use to flash the twrp?
Output should be like this:
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY
Please post your output

Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly

after that command type fastboot boot twrp.img (twrp is the name of recovery img) and it will booted into recovery

badyards said:
Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly
Click to expand...
Click to collapse
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs

Sharma_Ji said:
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
Hi, this is the message received after flashing:
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.340s]
writing 'recovery'...
OKAY [ 0.138s]
finished. total time: 0.594s
then I digit this
PS C:\platform-tools> fastboot reboot recovery
< waiting for device >
if i switch off it is booting automaticaly into CM12. If I exit the shell and try power + volume down it opens a plain recovery, neither the CM revocery nor the twrp. Any idea of what I'm doing wrong?
edit: also tried this
PS C:\platform-tools> adb devices
List of devices attached
cb02ec72 device
PS C:\platform-tools> adb reboot bootloader
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.330s]
writing 'recovery'...
OKAY [ 0.134s]
finished. total time: 0.467s
PS C:\platform-tools> fastboot boot recovery.img
< waiting for device >
looks like the fastboot is gone after flashing

hi everyone, sorry for the newbie question above. Eventually I've managed to install TWRP, I just missed the right key combination to reboot.
Thanks

bought a oneplus 2 with 3.6.1 OOS and cant flash twrp to recovery part

newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.

TWRP 3.2.1 doesn't work properly yet on the OnePlus 2 for some reason. I can assume that you wanted root so I can give you 2 options:
1) If you want to stay on stock OxygenOS 3.6.1 or a custom rom Nougat or lower, then flash TWRP 3.1.1
2) If you want to have an Oreo rom, then you have to get your hands on the unofficial TWRP from anupritaisno1. The download link for that on his forum doesn't work so if you want, I can link my Google Drive.

This is my first time trying to root my android and I am having the same problem with my oneplus 2 3.6.1 OOS. I have successfully unlocked oem but can't seem to flash twrp.
I have downloaded twrp 3.2.1 on my desktop and renamed it to "recovery".
I used the same command "fastboot flash recovery recovery.img" but it just says "error: cannot open 'recovery.img' "
Can you please tell me how you managed to install twrp and root your android?

you need to downgrade the OOS to ver 3.002 or 3.1, then you re-unlock the bootloader then flash twrp recovery.
Finally flash your phone with root of your liking.

rp201 said:
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
Click to expand...
Click to collapse
dear,
do you mind sharing the twrp.img you used?
Thank you

fastboot flash boot failed

trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?

Did you solve the problem?

i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461

ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.

hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.

try fastboot flash bootimg instead.