Database Users

URGENT HELP!! - Reflash Factory Image (Bootloader unlocked, not-rooted)

My phone is OEM unlocked but not rooted (secure boot - enable as so said in fastboot mode).
Basically my phone cannot get to bootup. It doesn't show "Google" on startup or "X" animation. it crashed yesterday and got stuck on the "X" screen animation. So tried to factory wipe and adb wipe stuff. and things gotten worse. And i need my phone urgently to work because i'm waiting for calls for job interviews. so this is an urgent request!
i tried the LG Google Nexus 4 toolkit to flash Google Stock image but i'm getting the error
"failed <remote: flash write failure>"
i can boot to Custom/Stock Recovery without Permenently Flashing it with Clockworkmod or TWRP.
i tried "update from ADB" option in Android system recovery with "adb sideload image-occam-jdq39.zip" and it's able to send it to the device, but i'm getting "Installation aborted"
I'm out of options and i'm really lost....please help!!

Can you flash a recovery using? :
Code:
fastboot flash recovery name-of-recovery.img
If you can, then download a rom and flash it through the recovery that you installed.

chromium96 said:
Can you flash a recovery using? :
Code:
fastboot flash recovery name-of-recovery.img
If you can, then download a rom and flash it through the recovery that you installed.
Click to expand...
Click to collapse
I'm getting the following error in CMD
sending 'recovery' <6398 KB>...
OKAY [ 0.405s ]
writing 'recovery' ....
FAILED <remote: flash write failure>
i'm trying to relock the device so i can replace it under warranty, but the device won't stay lock....wtf?

[HELP] Recovery Bricked and can't reflash

Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)

http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.

This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.

AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.

http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3

OPT bootloop, no recovery, cant boot into twrp.

So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!

Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.

SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863

Phone stuck on Essential Logo (Powered by Android) screen while trying Oreo B2 OTA

I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.

Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.

Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk

You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.

I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?

You could try: (you will lose all your data)
fastboot -w
fastboot reboot

ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..

update im still stuckk

Have you tried booting to bootloader and mounting /system?

This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.

I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything

Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay

Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???

Need help asap please. Keeps booting to twrp.

I am in a twrp boot loop except when I boot through fastboot>Start. It boots to OS. If I cold boot, it boots to twrp.
I followed this guide. here
I downloaded mfastboot
Entered the cmd to clear. Still boots to trwp.
C:\Users\Admin\AppData\Local\Android\sdk1\platform-tools>mfastboot oem fb_mode_c
lear
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse

Ok it's bricked.
I tried to restore an image backup "working one", it stops at restoring system, shutsdown and boots back into twrp.

I am going to try this. Restoring stock 7.0 through fastboot. This sux.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142

following this guide fixed it. I freaked out.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142

Was this your first time flashing TWRP? It sounds like you flashed the image to boot and not recovery...
fastboot flash twrp.img
Will result in the issues you stated, basically a "soft brick" condition.
fastboot flash recovery twrp.img
Is the correct format for the command. Without specifying the partition to flash, fastboot assumes it needs to go to boot... And if you don't have the original boot.img file it us unrecoverable.

acejavelin said:
Was this your first time flashing TWRP? It sounds like you flashed the image to boot and not recovery...
fastboot flash twrp.img
Will result in the issues you stated, basically a "soft brick" condition.
fastboot flash recovery twrp.img
Is the correct format for the command. Without specifying the partition to flash, fastboot assumes it needs to go to boot... And if you don't have the original boot.img file it us unrecoverable.
Click to expand...
Click to collapse
Nope, not first time flashing twrp, been doing it for a few years.
The rom is bad that I installed. It makes twrp freeze as well and shutdown.
But I followed this guide https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 and then reflashing latest twrp and restoring stock nougat rooted image backup I made worked.

Take a look here > https://forum.xda-developers.com/showpost.php?p=77204890&postcount=18