Database Info

[Q] Phone in not responding - led is on.

Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.

adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.

Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...

adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?

enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.

adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.

Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??

Can you still boot to recovery?

adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.

enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.

adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.

Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man

adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!

[S3] Bricked phone - only ADB is working

Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.

Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.

Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.

[Q] HTC one m8 hardbricked can't access any thing

I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.

Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know

DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go

piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.

M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset

piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.

Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please

rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.

It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.

rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?

Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..

Help - my honor 8 was block - No access Fastboot Mode or Debugging Mode

Hello,
I downgraded my Honor 8 via Rollback and installed the Rom FRD-L09C432B131.
But my phone is stuck on the blue Android startup screen.
I can not use the Volume +, Volume - or Power buttons.
All I can do is let it turn off by itself when the battery is at 0%.
When I put it on, it turns on by itself. Arrives on a blue screen. Reboot once and then stays eternally on the blue screen while heating up enormously.
I have no access to the Recovery, erecovery or via the computer (by plugging it into a USB port).
Thanks

gregase said:
Hello,
I downgraded my Honor 8 via Rollback and installed the Rom FRD-L09C432B131.
But my phone is stuck on the blue Android startup screen.
I can not use the Volume +, Volume - or Power buttons.
All I can do is let it turn off by itself when the battery is at 0%.
When I put it on, it turns on by itself. Arrives on a blue screen. Reboot once and then stays eternally on the blue screen while heating up enormously.
I have no access to the Recovery, erecovery or via the computer (by plugging it into a USB port).
Thanks
Click to expand...
Click to collapse
Once your phone turns off, press power button amd volume up button together. This should take you to recovery. Or you can't access this at all?
Sent from my Honor 8 using XDA Labs

I can not turn off my phone. It goes off when the battery is at 0%.
If I put on USB or mains, it recharges and restarts automatically. And I can not stop it ...
When I plug it into a USB port, the Power, Volume + or Volume buttons are ineffective.
And when it's plugged into the PC, it does not show up!
So I do not have access ... except perhaps by a software that would force the connection ... or a manipulation other than Power / Volume ..

When I say reboots, it is a program to display the Android blue screen and hangs on it!

does it say android or honor?
going to dload is kinda tricky sometimes and should be done when connected to wall adapter, not pc
can you keep vol- and power pressed while your phone is connected to pc. keep them pressed even after the phone restarts. dont let go. it might take some time. does it go to fastboot?

gregase said:
I can not turn off my phone. It goes off when the battery is at 0%.
If I put on USB or mains, it recharges and restarts automatically. And I can not stop it ...
When I plug it into a USB port, the Power, Volume + or Volume buttons are ineffective.
And when it's plugged into the PC, it does not show up!
So I do not have access ... except perhaps by a software that would force the connection ... or a manipulation other than Power / Volume ..
Click to expand...
Click to collapse
Is your phone still covered by the warranty?
Sent from my Honor 8 using XDA Labs

Do a factory reset I believe

PalakMi said:
Do a factory reset I believe
Click to expand...
Click to collapse
He can't even boot to recovery.
Sent from my Honor 8 using XDA Labs

Ohhh, sorry my bad

dats prolly because he has mismatched files for the os he's running. he should deffo check if he can go to fastboot. the fact that he cant go to dload doesnt really mean anything because i cant do it either 40% of the time. its a bit iffy. the fact remains, if it boots to honor logo, means some type of os is up there. if he can go to fastboot he can flash stock recovery/recovery2 and try dload again. without proper recovery combo he wont be able to flash anything anyways and warranty prolly wont cover it since its users fault, esp if he has unlocked warning.

Delete

Rommco05 said:
Check first post
Click to expand...
Click to collapse
My bad

Rommco05 said:
No way, Im just want to show you is here too much threads witch similar problems and much information and experiences... I think about one guide/thread where will be all info about rollbacks and nougat firmwares. But is a lot of work about finding info, all is ok
Click to expand...
Click to collapse
Thank you :laugh:

Similar to me, only way is go into bootloader mode, then charge the phone for awhile, you cant do nothing cuz of 0% battery, flash stock recovery, update via dload or direct wifi recovery.

qvnsq said:
Similar to me, only way is go into bootloader mode, then charge the phone for awhile, you cant do nothing cuz of 0% battery, flash stock recovery, update via dload or direct wifi recovery.
Click to expand...
Click to collapse
He can't go to fastboot

if he completely bricked it, he'd be stuck at black screen/android logo, not honor logo. either he's not telling us everything (ran out of juice while upgrading / error while flashing / flashing wrong rom), there is no chance all key partitions got wiped if the process finished successfully. meaning at least he should be able to fastboot cause thats the first thing flashing alongside bootloader. no way any type of system partition is up there, and bl/fb is not, even if they are from a different OS. h8 can be stubborn at times, but keeping the cable in pc and holding vol_down+power for good 20s deffo will force it to at least reboot. thats the only way. if this doesnt work, you should take it to a service center.

I guess it's better if he takes it to the service center

Nothing works. So I have to send it to the service center

Thank you all !

gregase said:
Nothing works. So I have to send it to the service center
Click to expand...
Click to collapse
It's sad but, I hope it gets fixed