Develop Bugs

Format partitions in fastboot mode

Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's

You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply

Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.

It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.

soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium

LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?

Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.

Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)

LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.

Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?

soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?

I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?

soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot

LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.

soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help

I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.

soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium

soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..

LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?

Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem

amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?

Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse

Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here

Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.

Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk

tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.

Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools

jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.

Magisk and TWRP problems

Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!

TWRP I can't help you with as I haven't tried installing it.
Magisk is partially solved in the thread here.
Check the posts by myself and M47Z.
The short version is that the Moto boot image needs some, rather difficult, manual massaging before you can install Magisk to it.

Curmudge0n said:
Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!
Click to expand...
Click to collapse
when TWRP hangs like that after booting i've found in my own experiences that is usually caused from the version of TWRP you are using. Or you could have just downloaded a bad file of TWRP if you didn't use the official website. I currently use twrp-3.5.1 for my g7 play xt1952-t channel. hope this helps a little.

Question I bricked my phone, any advice?

So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?

Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.

Did you get solution?

As mentioned in the post right before you; yes.

Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help

You could try this: fastboot --set-active=b

[Redmi Note 8] Unable to boot to recovery or fastboot (System has been destroyed)

Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?

Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL

loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .

Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?

No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.

Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.

Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...

loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)

bro how did you booted into fastboot i also in same situation

how did you fixed i also in same situation

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;

Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.