Database Develop

Stuck on HTC logo

Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is all I'm seeing atm.

ruckus92 said:
Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
This is all I'm seeing atm.
Click to expand...
Click to collapse
Extract boot.img from custom Rom zip file, place in PC's fastboot directory. Enter fastboot mode on phone. Type
Code:
fastboot flash boot boot.img
and restart.

THAAAAAAAAAAAAAAAAAAAAAAAAAANK YOOOOOOOOOUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! that just made my day bro:good:

I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium

Fshtiwi said:
I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Make sure you are typing the command correctly and not just fastboot boot boot.img

[Q] Atrix HD Corrupted Data partition

I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks

Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.

OnePlus 3t hard bricked?

So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?

NotAbdShahid said:
So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?
Click to expand...
Click to collapse

Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.

thes3usa said:
Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.
Click to expand...
Click to collapse
Except that I have and I've not found a solution to the sahara communication failed problem. I've tried different computers, usb ports etc. Still gets stuck at Sahara Communication failed.

ashokmor007 said:
Click to expand...
Click to collapse
Thanks but I've tried this and it still gets stuck at the same flippin error.

Download the current adb ... use the original cable ... there was a process done with cmd as well as signing the certificate in win10, have you done these?

[Oneplu 3t] md5 checksum failed:system and recovery failed
My Oneplus 3T(with android 8.0.0) suddenly turn off and it wouldn't boot or other option, i didn't ever rooted, it was new and updated. I tried to go to recovery, tried a hard boot hold the power button for 30s, connected to pc, and giving a charge... it just stayed dead... so i did a find the OnePlus3 Unbrick Tool, did find the phone on the tool and i run... after that it boot in a cycle where appear the 1+ logo and them the md5 checksum with the system and recovery failed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it does that loop, and now i can enter fastboot but can do nothing than going to that cycle and power off
phone apear in the device manager as "Qualcomm HS-USB QDLoader 9008(COM3)"
and using the tool again, goes to a error saying "Sahara Communication Failed£ Please try again after power off phone" and already tried what it said..
please help me, what can i do to boot my device?
PS: I dont know how to put images on the thread...

Stuck in the "ALL-FAILED" screen, when re-booting

Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:

Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!

Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!

[HARD Hard Brick] Literally nothing's working... Please help.

I need help. ​
The problem?​My phone is bricked AF.
Where it started:​So, a few days ago I was flashing custom ROMS on my Redmi 9C, at this point everything was good, although I did brick the phone twice, I was able to get it back up and running again using MTK Bypass and SP Flash tool.
You see, 2 days ago I stupidly it was a good idea to flash a custom ROM (Arrow OS) on top of another one (DotOS) ~I'm not a noob, I KNEW this probably wasn't going to work~. I thought it would work since it's still using the same base but shortly after flashing when I restarted my phone there was nothing, no boot logo, no sound, no vibration, nothing.
I couldn't boot to fastboot or anything, it wouldn't respond to ANY input.
At this point I already knew well how to fix the issue but this time it didn't work at all.
The first attempt kinda worked, I was able to bypass auth and flash but after like 2 seconds the flash tool stopped, and I got a STATUS_EXT_RAM_EXCEPTION error and after that I tried to reflash. It did get detected by the bypass tool a few times but after that every time I plug my phone into my pc, I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and I see this in device manager:
Libusb won't even detect it.
I tried driver after driver, I switched the cable, I tried a different computer, I waited a day, I read thread after thread, installed python, tried tool after tool, but to no avail.
I tried all sorts of button combinations but the only one that does anything is vol+ and pwr but that just makes it disconnect and reconnect to my pc with the same results.
I watched a bunch of videos about it and tried every method but still, no luck. I am confused where they say remove the battery because some do and some don't, but I can't really do that in my current position anyway...
I know there are MANY similar threads on this, but I haven't been able to find anything to help me in this situation.
I've tried all sorts of solutions but now I just don't know any more.
Please. Help. Would really appreciate it.

I had a similar brick yesterday, when I tried to use mtkclient but it only got halfway. As far as I understand, the system was actually on, but it got stuck in a state where it wouldn't respond to anything.
What fixed it was power cycling the device by disassembling it, and disconnecting and reconnecting the battery (search for battery replacement videos). The idea is from this comment by bkerler, the author of mtkclient. I guess my warranty really is void now.
(Another thing I considered was power cycling it by waiting for the battery to run out, and then recharging it. But I've no idea if this might have got it into a state where it wouldn't even charge, so I didn't do it.) I'll avoid mtkclient from now on when possible, and prefer to use fastboot or a recovery for flashing.
I am a noob; no guarantee that I'm right about anything (other than that my phone works now), nor that your situation is identical to mine.

Here is solution if you are not noob,
Post in thread 'HARDBRICKED REDMI 9C ANGELICA NO BOOT NO RECOVERY NO FASTBOOT ONLY VIBRATES' https://forum.xda-developers.com/t/...-fastboot-only-vibrates.4494095/post-88308869