Database Users

Needing some help to fix my recovery

I'm having a problem getting into my recovery. I have the D800. It started out I sideloaded cwr thru twrp. And it said it flashed fine. I selected to reboot back into recovery and got a fastboot error. So i tried just rebooting and couldnt get passed the splash image. So I did the whole flash stock firmware. And after i got done with that, I think I did the ota update, And I got my phone rerooted. But still no recovery, it loads to a black screen and my pc says I have to format drives from like u-z but one has a folder titled image with these files. I've tried adb pusing and flashy and nothin,.Please help

never mind I got it fixed I think. Please delete post

[Q] 5.0 Won't Work

Firstly the flash-all.bat wouldn't work, it kept failing at the boot.img, saying it wasn't in the file. I extracted all the parts of the zip and flashed them manually, and I got a bootloop. I flashed TWRP and did a factory reset from the recovery, it then booted into Android 5.0, but with no home keys at the bottom of the screen. I did a factory reset from inside 5.0, but it didn't fix it.
I then flashed a factory image of 4.4.4, got the same boot.img and had to manually flash all the parts. the flashed 5.0 over the top of the factory image, again with the boot.img is missing error, and again the home keys were missing.
I did another factory reset t see if it would fix it, but I still had no home buttons, so I ended up reverting back to 4.4.4, but when flashing that, I got the same boot.img error message, again. I had to manually flashed it and it booted into 4.4.4, and all is working.
Question is how do I get to 5.0 with home keys and not get the boot.img error message?

I had the same problem
unzipping the zip inside the tar.gz and following http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1"]efrant's guide (flashing all img's individually and in the proper order) worked for me.

Boot loop after flashing latest Android 7 image

While on a developer preview of Android N with my unlocked rooted phone and TWRP 3.0.2-1, I accidentally ran the September OTA. The OTA failed, but left a mess behind with the phone rebooting 4-5 times a day.
Today, I decided to fix the problem, so I flashed the latest official image (NRD90U). Complete wipe, but since I have backups, I considered it to be no big deal. Turns out it was
The phone is now a boot loop (corrupt warning -> google logo -> corrupt warning -> google logo...). Reflashing changes nothing. Trying to boot (fastboot boot) TWRP (any version) does not work (it just goes into the boot loop). Tried to downgrade back to 6, same problem. Nothing seems to work.
Somehow, something is still ****ed up on the phone, but I have no idea what. This seems to be very similar to this thread (http://forum.xda-developers.com/nexus-6p/help/help-help-help-hard-bricked-6p-t3428225/page3), but there does not seem to be a solution.
Is it definitely bricked or is there anything I can do from fastboot to try and fix this? I am unlocked. I just need a stupid TWRP so I can restore my backup and hopefully get back to a working state from there.
PS: I'm sure I downloaded the right image and flashed it properly.

Phone only boots with factory mode. I did something wrong.

I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.

ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this

Phone stuck in bootloop. Recovery says directories not found.

I performed a factory reset from within the OS and when it restarted it was stuck on the Samsung splash page. After this I performed a reset from the recovery menu. Now the phone was stuck in a boot loop. At this point I re-flashed the factory ROM from ODIN and it is again in a boot loop. Sometimes it makes it to setting up the apps but just resets again.
For some reason the phone attempts to install an update whenever I enter the recovery and once there it states that it cannot locate files. The location of these files is "E:". I have no idea why it cannot locate anything it looks for and why " E: " is not there if it needs that location as the phone is completely stock.

Did you flash the HOME-CSC or the normal CSC file? I too got into a bootloop after a factory reset from the recovery, so flashing with the CSC file could be useful I guess. Recovery checking for an update always happens for me and it goes to recovery normally after checking.