Develop Bugs

[Q&A] [RECOVERY]ClockworkMod Recovery v6.0.4.7

Q&A for [RECOVERY]ClockworkMod Recovery v6.0.4.7
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

same here
mbwambo said:
heloo ,,,,,, i have a problem with my htc desire816 dual sim, after installng custom recovery fail to work and my phone wrote tampered above unlocked line and fail to show custom recovery help plz.............
Click to expand...
Click to collapse
Hello Bro,
Here i 've the same issue and awaiting for solution. Do you have any update ?
I'll share if i found anything.
you can have some idea on below link and ": ADVANCED BOOT PROBLEMS"
http://forum.xda-developers.com/showthread.php?t=1275632
But, i haven't tried...it's quiet fear about to have try (becuase they mentioned it's a worst situation and the link is not exactly for Desire 816 model).
Thanks in Advance, SR

Sivasr said:
Hello Bro,
Here i 've the same issue and awaiting for solution. Do you have any update ?
I'll share if i found anything.
you can have some idea on below link and ": ADVANCED BOOT PROBLEMS"
http://forum.xda-developers.com/showthread.php?t=1275632
But, i haven't tried...it's quiet fear about to have try (becuase they mentioned it's a worst situation and the link is not exactly for Desire 816 model).
Thanks in Advance, SR
Click to expand...
Click to collapse
hey bro
now i solve the problem to my own ........................what about you you still have the same issue

how ?
how did u solve this problem ?

mbwambo said:
hey bro
now i solve the problem to my own ........................what about you you still have the same issue
Click to expand...
Click to collapse
Really!!!!!!!!.....It's nice to know you geeting out from hectic. Would you plz explain step by step process...it would help many guys to get relieve from the issue...
Eagerly waiting for your response.. plz help us
---------- Post added at 02:41 AM ---------- Previous post was at 02:02 AM ----------
mbwambo said:
hey bro
now i solve the problem to my own ........................what about you you still have the same issue
Click to expand...
Click to collapse
Yes brother, i have still same issue

Did you all try to use the .exe or did you use the fastboot command to flash this? If this does not work for you go to the CM thread, download that recovery file and use the same fastboot command in this thread. When you download the CM clockworkmod rename it to what the command says so it should be recovery_en.img
Sent from my 710C using XDA Free mobile app

I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????

mbwambo said:
I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????
Click to expand...
Click to collapse
Everyone experiencing the no recovery or the exclamation mark on the recovery screen its because you tried to run the .exe or flash the recovery with a fastboot command WHILE IN HBOOT MODE. You need to be in fastboot to do this and your device bootloader has to be unlocked before you try anything root wise.
Mine does the same thing. When it enters recovery just hit reboot device and let it start up. It charges in 2-3 hours on or off as long as the screen isn't active.
Also, ANY device that you unlock the bootloader for will say Tampered. Its HTC's way of knowing if you unlocked the device, but that doesn't mean you can't return it. It is done through HTC though and you are allowed to relock it to return it.
If your device power button stops working HTC will take it back regardless of bootloader status as that's a hardware problem. If your phone is not charging properly that isn't a bootloader problem that is the software of Android and is valid for a claim.
If you try to flash an entirely different bootloader then they'll reject your device because you went further then to just "Tamper".
If it voided warranty to unlock the bootloader there would be no root apps on the Playstore allowed.
Sent from my 710C using XDA Free mobile app

@jaysoblitzed
Does yours shows those words in read colour that you dont have permission and so on...????

mbwambo said:
@jaysoblitzed
Does yours shows those words in read colour that you dont have permission and so on...????
Click to expand...
Click to collapse
Yes it does say the exact same thing but the message actually states:
This build is for development purposes only.
Do not distribute outside of HTC without HTC's permission.
Failure to comply may lead to legal action.
No worries though, this message is automatically put there by HTC after unlocking the bootloader. :laugh:

@jaysobitzed
Yes.....that is the message i was talking about.......but to my side its coming even in charging mode while my phone iz off.......then directly goes into CWM mode...How about yours ??

mbwambo said:
@jaysobitzed
Yes.....that is the message i was talking about.......but to my side its coming even in charging mode while my phone iz off.......then directly goes into CWM mode...How about yours ??
Click to expand...
Click to collapse
@mbwambo Yep, mine does the same thing :good: :good:
---------- Post added at 08:41 AM ---------- Previous post was at 08:36 AM ----------
[NEW UPDATE]:
IF YOU RECEIVE AN EXCLAMATION MARK ON THE RECOVERY SCREEN AFTER RUNNING THE .EXE THEN IT IS BECAUSE YOU NEED TO FLASH AN OLDER CLOCKWORKMOD FIRST!
POWER OFF YOUR DEVICE BY HOLDING VOLUME UP + POWER BUTTON FOR 15 SECONDS IF YOUR STUCK AND THEN POWER ON BY HOLDING VOLUME DOWN+POWER BUTTON AND YOU'LL GO BACK INTO THE BOOTLOADER.
ONCE YOUR DEVICE IS SET IN FASTBOOT USB MODE DOWNLOAD THIS FILE BELOW:
https://s.basketbuild.com/dl/devs?dl=Grarak/recovery.img
NOW SAVE THAT FILE WHERE THE ADB FOLDER / PLATFORM-TOOLS IS THAT YOU INSTALLED AT THE BEGINNING OF THE VIDEO IN (Local Disk C:/adb)
ONCE THAT'S COMPLETE GO INTO THAT FOLDER AND RIGHT-CLICK IN ANY WHITE AREA OF THE FOLDER AND PRESS "RUN COMMAND LINE HERE" & RUN THE FOLLOWING COMMAND:
fastboot flash recovery recovery.img
REBOOT TO RECOVERY AND CONFIRM!
NOW YOU CAN RUN THE .EXE IN FASTBOOT USB MODE AGAIN OR FLASH THE RECOVERY HERE FOR THE LATEST VERSION!
Done!

mbwambo said:
I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????
Click to expand...
Click to collapse
Hi mbwambo, I'm not sre aboput problem you face that "Bettery sign missing and power of ur phone "..but as you told, (it's n going to Recovery mode Or Hboot) You can able the fast boot option under settings > Power . then sytem will go automaticall into normal start up instead of going into recovery or Hboot mode. i had the same problem what you have. after checked in the fast boot it's simply restarts as usual in charging or not charging status. hope this would help ur restarting issue.
I've the same tampered, but still not enter into recovery mode....u r lucky at this case...now you root ur mobile
Thnx, SR

Sivasr said:
Hi mbwambo, I'm not sre aboput problem you face that "Bettery sign missing and power of ur phone "..but as you told, (it's n going to Recovery mode Or Hboot) You can disable the fast boot option under settings > Power . then sytem will go automaticall into normal start up instead of going into recovery or Hboot mode. i had the same problem what you have. after checked in the fast boot it's simply restarts as usual in charging or not charging status. hope this would help ur restarting issue.
I've the same tampered, but still not enter into recovery mode....u r lucky at this case...now you root ur mobile
Thnx, SR
Click to expand...
Click to collapse
Thanks Sivasr!
@mbwambo:
By going into your settings and checking fastboot it will stop the device from booting into recovery if put to charge when powered off. This will show the battery icon and no red text will appear.
@Sivasr:
Try the method I just posted it will work to get into the recovery. I have had some people ask me about that same issue and that solution has worked for them. Also, make sure to uncheck fastboot in Power - Settings!

13330
jaysoblitzed said:
Thanks Sivasr!
@mbwambo:
By going into your settings and checking fastboot it will stop the device from booting into recovery if put to charge when powered off. This will show the battery icon and no red text will appear.
@Sivasr:
Try the method I just posted it will work to get into the recovery. I have had some people ask me about that same issue and that solution has worked for them. Also, make sure to uncheck fastboot in Power - Settings!
Click to expand...
Click to collapse
thanks again.....but too sad, i had relocked my phone after all tries are done. this evening i tried again to unlock it's not unlocking my phone only sticks with "Unlock Bootloader? " screen and it's says entering Rocovery... very long time. I don't think i can do unlock my phone again. i know iwe could not flash the recovery.img without unlock booloader....:crying::crying::crying::crying::crying::crying:

Sivasr said:
thanks again.....but too sad, i had relocked my phone after all tries are done. this evening i tried again to unlock it's not unlocking my phone only sticks with "Unlock Bootloader? " screen and it's says entering Rocovery... very long time. I don't think i can do unlock my phone again. i know iwe could not flash the recovery.img without unlock booloader....:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
@Sivasr
To unlock it again just use the same unlock.bin file you got in the email. Then use the recovery.img file I listed or go to the CM11 thread and download the recovery from there and use that one.
After you flash that old version you can go into it from the bootloader. Just go to advanced in the recovery, reboot to bootloader, and flash the new recovery with the .exe or with the recovery file from the CWM thread.
Done
You can't flash the recovery if it's still locked you are correct. If it seems frozen use the volume keys to navigate and power button to select.
Sent from my 710C using XDA Free mobile app

bricked phone
hi all
My htc desire 816 dual sim got hard bricked after flashing rom
Please help
:crying:

abdealli dalal said:
hi all
My htc desire 816 dual sim got hard bricked after flashing rom
Please help
:crying:
Click to expand...
Click to collapse
Hard bricked? There is no help for you.

CWM auto boot
Hi there.
Can anybody explain me, why my 816w (CWM v6.04.7) when I put it on charger after total battery discharge, turns on automatically and boots in recovery
Thank you in advance!

FoxyDrew said:
Hard bricked? There is no help for you.
Click to expand...
Click to collapse
What ROM did you flash? Does your device still turn on? Can you access the bootloader and/or recovery?
Sent from my 710C using XDA Free mobile app
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
bunkker said:
Hi there.
Can anybody explain me, why my 816w (CWM v6.04.7) when I put it on charger after total battery discharge, turns on automatically and boots in recovery
Thank you in advance!
Click to expand...
Click to collapse
This is a glitch with the old CWM recovery. If you use the one from the CM12 thread; 6.0.5.1 CWM then you will be able to avoid this issue. Only thing is instead of it booting into recovery it won't boot unless you remove it from the power source. Lol so you win some you lose some.
Sent from my 710C using XDA Free mobile app

[Q] [LG G3 F400S] Can't boot anything

Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?

Its bricked, there is a version mismatch between your android bootloader and your phone's bootloader meaning that it prevents you from going into download or recovery mode

KuHaKu said:
Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?
Click to expand...
Click to collapse
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129

Quote100 said:
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Click to expand...
Click to collapse
If you bothered to read properly he cant boot anything

itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try

Quote100 said:
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try
Click to expand...
Click to collapse
itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?

KuHaKu said:
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?
Click to expand...
Click to collapse
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)

Quote100 said:
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)
Click to expand...
Click to collapse
That would be what i would of noted as TWRP or Recovery - No

KuHaKu said:
That would be what i would of noted as TWRP or Recovery - No
Click to expand...
Click to collapse
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?

FIXED
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965

brick
it bricks bro

Quote100 said:
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?
Click to expand...
Click to collapse
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))

Celly624 said:
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Click to expand...
Click to collapse
Fastboot doesnt work for any variant with a locked bootloader
OP can try the old LG Flash Tool guide but i doubt that will work

KuHaKu said:
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))
Click to expand...
Click to collapse
Alright! that's great, glad i could help

Bricked Phone [No Display] after Marshmallow Berta Update...

Dear All,
I've found that my bootloader is automatically Locked after flashing Marshmallow Beta. So, I've tried to unlock it again to bring back my TWRP, but both official and unoffiacial methods failed to unlock and even temporary CWM also didn't work. Then I've flashed .139 droidboot image though fastboot and tried unofficial unlock method and got unlocked. Then I've flashed TWRP and got it worked.
Now I've flashed Supersu 2.65 through TWRP and rebooted my phone..... OMG, I've bricked my phone.... There is no display at all (Black Screen), but getting vibration at the Power On.
I've tried all the unbrick methods including xFSTK Tool method! But no use... I've used these methods previously to unbrick from USB Logo Issue. But now, it's refusing to help me...
It shows in xFSTK as like this...
Firmware download completed. Continuing to OS...
Click to expand...
Click to collapse
But it fails download OS after many attempts to reconnect my device. Then my device reboots (gives vibration) but nothing is displayed in the screen and it is still blank. It's not even booting to bootloader...
Kindly suggest me some tips to unbrick my phone (Z00AD-ZE551ML)....
Thanks in advance...
Edit: Sorry for the title mistake, it's Beta Update....

argggghhh ! now i understand where you went wrong relating to this
http://forum.xda-developers.com/showpost.php?p=67378070&postcount=88
too late now but your first paragraph ....
(........Dear All,
I've found that my bootloader is automatically Locked after flashing Marshmallow Beta. So, I've tried to unlock it again to bring back my TWRP, but both official and unoffiacial methods failed to unlock and even temporary CWM also didn't work. Then I've flashed .139 droidboot image though fastboot and tried unofficial unlock method and got unlocked.>>>>> Then I've flashed TWRP and got it worked......)
You should`ve flashed stock recovery for 139 -- then rebooted recovery -- select side load -- then adb sideloaded WW - stock 139 firmware.
i dont know where you go from here , if you do manage it, remember this ^^^ and anyone else --- i put this process numerous times but people just ignore !
possibly start again and try flash raw for 139 and correct the steps ^^^?

timbernot said:
possibly start again and try flash raw for 139 and correct the steps ^^^?
Click to expand...
Click to collapse
But from where I can start? There is no fastboot and no display at all... I'm struggling where to start...

ponnuvelpandian said:
But from where I can start? There is no fastboot and no display at all... I'm struggling where to start...
Click to expand...
Click to collapse
You are bricked my friend
Until , dnx and ifwi and os image for 6 comes about...
Find out how to extract them from the 61 firmware from marshmallow ?
Oh and the raw too .
Maybe , put here for others to use .
Come back and let us know how you go ?

timbernot said:
You are bricked my friend
Until , dnx and ifwi and os image for 6 comes about...
Find out how to extract them from the 61 firmware from marshmallow ?
Oh and the raw too .
Maybe , put here for others to use .
Come back and let us know how you go ?
Click to expand...
Click to collapse
I've already extracted dnx and ifwi from 61 firmware. But don't know how to convert droidboot.img to .bin...
But, I've tried to download dnx and ifwi extracted from 61 firmware, but it doesn't go well...
Edit 2: -but the same extracted from .184 firmware goes well..... But still no display at all...
Edit 1: Attachment....

Edit 2: -but the same extracted from .184 firmware goes well.....
goes well ?
what do you mean here ?

timbernot said:
Edit 2: -but the same extracted from .184 firmware goes well.....
goes well ?
what do you mean here ?
Click to expand...
Click to collapse
I mean it's getting flashed (only ifwi & dnx) but still no boot at all as like said at the OP... But the ifwi & dnx taken from .61 firmware is not at all flasing...

ponnuvelpandian said:
I mean it's getting flashed (only ifwi & dnx) but still no boot at all as like said at the OP... But the ifwi & dnx taken from .61 firmware is not at all flasing...
Click to expand...
Click to collapse
ok , have you just tried naming the droidboot.img to droidboot.img.bin ---longshot i know but trying to research this a little myself -- this is for another phone with an older downloader but maybe some clues here ...
http://onehallyu.com/topic/294288-a-fluke-that-save-my-phone-fonepad-7fe171cg-from-hard-brick/

timbernot said:
ok , have you just tried naming the droidboot.img to droidboot.img.bin ---longshot i know but trying to research this a little myself -- this is for another phone with an older downloader but maybe some clues here ...
http://onehallyu.com/topic/294288-a-fluke-that-save-my-phone-fonepad-7fe171cg-from-hard-brick/
Click to expand...
Click to collapse
Ya, I tried that too by renaming droidboot.img to droidboot.img.bin and tried it. But still as like before it's not even going to OS section after finishing the firmware section... So, I cant come to a conclusion that whether renaming like this is correct or not...

OK, all you can do is wait for people with more understanding than me on this topic ...apols ..

timbernot said:
OK, all you can do is wait for people with more understanding than me on this topic ...apols ..
Click to expand...
Click to collapse
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......

ponnuvelpandian said:
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......
Click to expand...
Click to collapse
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me .
good luck and put what you find here :good:
---------- Post added at 11:01 AM ---------- Previous post was at 10:28 AM ----------
ponnuvelpandian said:
OK my friend, I' waiting.... and I really thank you very much for your kind interest in solving my issue......
Click to expand...
Click to collapse
Out of curiosity can you post a screenshot of the extracted ifwi that you have ?

Have you tried pressing (and holding) the "vol-up" button immediately after the "fw download completed continuing to os.."?
That's how I managed so the phone didn't reboot

pecholino said:
Have you tried pressing (and holding) the "vol-up" button immediately after the "fw download completed continuing to os.."?
That's how I managed so the phone didn't reboot
Click to expand...
Click to collapse
Yes, I also did it some times to try to go to bootloader, but didn't work...

timbernot said:
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me .
good luck and put what you find here :good:
---------- Post added at 11:01 AM ---------- Previous post was at 10:28 AM ----------
Out of curiosity can you post a screenshot of the extracted ifwi that you have ?
Click to expand...
Click to collapse
These are the files I've taken from the ifwi.zip inside the Stock ROM Beta.....

timbernot said:
I did read somewhere that letting the battery discharge itself completely --then try. Then try a fullcharge after , if not -- infact i`d try battery disconnect too lol but thats just me . good luck and put what you find here :good:
Click to expand...
Click to collapse
But I've already opened my phone and tried disconnecting and reconnecting the battery to test. But it didn't helped me...
================================================================================================================
And this is the exact mistake I've did I think which they asked no to do....
What we know so far:
* DO NOT flash droidboot.img in Android 6.0 update when ifwi version is 94.17x
* The bootloader will be ' locked ' after flashing Android 6.0 update.
* The splashscreen of Android 5.0 and Android 6.0 are in different format and if you don't update after changing the ifwi version, your phone might not boot.
Click to expand...
Click to collapse
Which is stated clearly at ZenTalk forum here http://www.asus.com/zentalk/thread-79657-1-1.html
But I've flashed droidboot.img from .139 firmware over Android M Beta... This made the splashscreen not to work and my phone became unbootable...
But the sad thing is, I was really not aware of this before doing this to my phone...
​Edit: Now the clue is splashscreen, is there any way to flash splashscreen using a downloader like xFSTK...?
​Where to use it What is OS Dnx in xFSTK Downloader? Can I use splashscreen there?

ponnuvelpandian said:
But I've already opened my phone and tried disconnecting and reconnecting the battery to test. But it didn't helped me...
================================================================================================================
And this is the exact mistake I've did I think which they asked no to do....
Which is stated clearly at ZenTalk forum here http://www.asus.com/zentalk/thread-79657-1-1.html
But I've flashed droidboot.img from .139 firmware over Android M Beta... This made the splashscreen not to work and my phone became unbootable...
But the sad thing is, I was really not aware of this before doing this to my phone...
​Edit: Now the clue is splashscreen, is there any way to flash splashscreen using a downloader like xFSTK...?
​Where to use it What is OS Dnx in xFSTK Downloader? Can I use splashscreen there?
Click to expand...
Click to collapse
Well theres hope for you yet , i did just that what you did and bricked my fone a couple of hrs ago - i managed to get working bootloader using ifwi dnx fwr and droidbootPOSsignedbin for version 2.15.40.13 and the raw for it -it flashed like fastboot messages on fone and rebooted into system all by itself
just upgating now , leaving 5.0 stock till mm comes ota
ps , tried 3 times and 3 bricks - cycling between 4 colours - usb cable - bootloader - and blank screens -each time i tried the raw -- soon as i ticked the wipe data in raw flasher it took.
remember i was coming from mm beta

timbernot said:
Well theres hope for you yet , i did just that what you did and bricked my fone a couple of hrs ago - i managed to get working bootloader using ifwi dnx fwr and droidbootPOSsignedbin for version 2.15.40.13 and the raw for it -it flashed like fastboot messages on fone and rebooted into system all by itself
just upgating now , leaving 5.0 stock till mm comes ota
ps , tried 3 times and 3 bricks - cycling between 4 colours - usb cable - bootloader - and blank screens -each time i tried the raw -- soon as i ticked the wipe data in raw flasher it took.
remember i was coming from mm beta
Click to expand...
Click to collapse
Have you ever went up with the blank screen issue? (like me..)...
Edit 1: I forgot to mention one thing in the OP. After unlocking my phone with .139 droidboot.img, I got white splashscreen, then I've flashed black splashscreen (older one that I already had for LP).... I think this may be the issue...
Edit 2: Which RAW Flasher you are using to recover from blank screen?

I used 2.15.40.13 raw with the only flasher available I think 1.7
Downloader,1.14 cos it worked for me before, I have 1.34 but never used and didn't want to alter my successful flash stuff

Dear @timbernot
Thank you very much for giving me hope to unbrick my phone. Now I've unbricked it successfully by trying with xFSTK again and again repeatedly.... First I got the USB Logo, then four colours, and then fastboot.... Then I've flashed the raw firmware.... Feeling happy now....

Hard Brick with black screen and bootloops. Help will be appreciated

How my phone got bricked - Yesterday when i was listening to music my phone restarted, i turned it back on and it restarted again with a black screen (or blue screen because i can see it lighting up a bit).
I tried restarting it multiple times, turning it off and also punching it but nothing helped. Later i installed miflash and went back to stock rom. But the problem still persisted , black screen .
My PC recognizes the phone as a device , but i cant get into recovery or edl mode because the phone just reboots.
I have tried holding the power + volume up and every possible combination to get into some kind of recovery.
Now when i press the volume button on my phone i can hear the sound it makes when it can't go any louder , so im guessing my phone works .
Has anyone managed to fix this?
Edit: My phone got recognized by pc as QD9008 , and i was able to flash it with qfil , but my phone still has a black screen. I also flashed it with miflash and still black. Should i try doing the deep flash cable ? Will it even do anything ? Thanks.

Really don't know.

New info in post.

Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?

sotosgolf said:
Did you unlock it and flash recovery?
Can you boot into recovery or it's just a black screen from the beginning?
Have you tried any other versions of zui?
Indian/Chinese marshmallow/nougat?
Click to expand...
Click to collapse
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.

daxtera said:
Before i flashed my phone with mi flash , adb was able to recognize it , but now it can't so i cant flash recovery.
Everything is black with no image at all. I have tried other versions of zui 1.9 and 2.3. But i haven't tried an Indian version.
Click to expand...
Click to collapse
Since the screen has light and the phone is recognized by pc my money would go on firmware issue. I would try more versions of zui. I have read that qfil is better for flashing zuk than miflash. (I'm not an expert on this, just suggesting)

Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629

Flashed 3 different versions of zui and nothing . Let my battery drain but that didn't help either. So now i think my only option is to flash the unlock bootloader file , because i have read that could fix my issue but i cant get adb to recognize my device even in qd9008 mode or 900e . Any way i can get adb to work? Im really getting desperate here.

Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.

@daxtera, did you solve the problem? I had the same situation and still no luck

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
open the phone and remove battery plug, then connect again

I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.
---------- Post added at 12:55 PM ---------- Previous post was at 12:54 PM ----------
I have same problem. I disconnected battery, but nothing changed. I'm in stock ROM as it came from Bangood. Android 6.0.1 and ZUI versión 2.0.093 ST.
Problem came using phone normally without any flashing process. When connected to computer it is recognized as Qualcomm HS-USB QDLoader 9008. I tried to flash 2.0.093 ST ROM using QFIL but process always ended in Download file: Fire Hose Fail FHLoader Fail: Process fail. Can anybody help me to recover my phone usability? Pls give me any suggestion.

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
packpunk said:
@daxtera, did you solve the problem? I had the same situation and still no luck
Click to expand...
Click to collapse
Hello, would like to know, if you guys tried any further & were able to resolve this issue. Please advise.

daxtera said:
Edit 2: Tried with deep flash cable , flashed countless stock roms and my phone still has a black screen. If anyone has any idea what else i can do i will try it.
Click to expand...
Click to collapse
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:

Dhananjay_Yadav said:
try this it might help ....
look at every post, many people have posted many different solutions, one might work for you
zukfans.eu/community/threads/deep-flash-revive-your-zuk-z2-from-hard-brick-state-9008-mode-easily.3504/
:good:
Click to expand...
Click to collapse
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.

kubersharma said:
Hi, i hope you don't have the similar issues as i had?
Have a read!
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-plus-stuck-edl-9008-port-help-t3713629
Click to expand...
Click to collapse
rocky459 said:
Thanks, the xda'ian who was facing this issue i.e. 'Black screen irrespective of QFIL success' reported that he was able to revive by opening the back cover & resetting the battery
Hope this helps everyone, who were facing similar issue.
Click to expand...
Click to collapse
This didn't helped bro

xyro8651 said:
This didn't helped bro
Click to expand...
Click to collapse
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2

adhieputra1 said:
My zuk z2 was like that. Press the power button. Then press and release the volume up for 10-15 seconds, then press and release the volume down 10-15 seconds. You press the power button anyway. Do it for about 5-10 minutes or more. Until the device reboots. When the device boots, choose download mode or EDL mode. Do a qfill or mi flash to flash your zuk z2
Click to expand...
Click to collapse
It is not working bro |
My phone is still with that condition
screen with blank dark color with backlight

Can't enter fastboot or recovery

Hi friends. i've got stuck on power on in my redmi note 8:
I've flashed twrp and then flash Potato AOSP. then i decided go back to MIUI and flash the official rom. there the phone don't boot recovery or fastboot (Screen stay black). if i hold the vol- button appears the logo of fastboot but inmediatly reboots
Any idea??
Tks

madvader1 said:
Hi friends. i've got stuck on power on in my redmi note 8:
I've flashed twrp and then flash Potato AOSP. then i decided go back to MIUI and flash the official rom. there the phone don't boot recovery or fastboot (Screen stay black). if i hold the vol- button appears the logo of fastboot but inmediatly reboots
Any idea??
Tks
Click to expand...
Click to collapse
try booting to fastboot using power button and vol down and then flash recovery or flash stock rom using mi flash. When fastboot logo appears don't touch anything on the phone.

the_weird_aquarian said:
try booting to fastboot using power button and vol down and then flash recovery or flash stock rom using mi flash. When fastboot logo appears don't touch anything on the phone.
Click to expand...
Click to collapse
Tks for the replay...
I've tried to enter fastboot but when the logo appears the phone reboots again.

the_weird_aquarian said:
try booting to fastboot using power button and vol down and then flash recovery or flash stock rom using mi flash. When fastboot logo appears don't touch anything on the phone.
Click to expand...
Click to collapse
Re-Reply:
Tks for the reply...
I've tried to enter fastboot but when the logo appears the phone reboots again.
I make a little video of how the phone keeps rebooting...
i'm new at the forum so i can't put attached URL's (https ://vimeo. com/385283136 ---please delete spaces after https and after dot)
Again tks

madvader1 said:
Re-Reply:
Tks for the reply...
I've tried to enter fastboot but when the logo appears the phone reboots again.
I make a little video of how the phone keeps rebooting...
i'm new at the forum so i can't put attached URL's (https ://vimeo. com/385283136 ---please delete spaces after https and after dot)
Again tks
Click to expand...
Click to collapse
maybe try connecting the charger then boot into fastboot mode.

Same here
madvader1 said:
Re-Reply:
Tks for the reply...
I've tried to enter fastboot but when the logo appears the phone reboots again.
I make a little video of how the phone keeps rebooting...
i'm new at the forum so i can't put attached URL's (https ://vimeo. com/385283136 ---please delete spaces after https and after dot)
Again tks
Click to expand...
Click to collapse
Hi, same trouble here, did you manage to figure it out?

After flashing rom you may have used the option "Clean all and Lock" therefore you people are experiencing bootloop on Redmi logo​remember do NOT use "Clean all and Lock" then bootloop is for sure​

maybe its xiaomi making it difficult to flash custom roms, why phones are so easily geting hard brick, why can not enter fastboot errors and "System has been destroyed" error, why they locked EDL mode, in my previous devices i was able to reinstate my phone in EDL mode when anything goes wrong but now we have to go to service center.
? I think I hate xiaomi for their flashing policies ???
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------

Redmi 4A abdal said:
maybe its xiaomi making it difficult to flash custom roms, why phones are so easily geting hard brick, why can not enter fastboot errors and "System has been destroyed" error, why they locked EDL mode, in my previous devices i was able to reinstate my phone in EDL mode when anything goes wrong but now we have to go to service center.
I think I hate xiaomi for their flashing policies
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
Click to expand...
Click to collapse
Redmi Note 9 PRO users are also experiencing bootloop

Any solution?

madvader1 said:
Re-Reply:
Tks for the reply...
I've tried to enter fastboot but when the logo appears the phone reboots again.
I make a little video of how the phone keeps rebooting...
i'm new at the forum so i can't put attached URL's (https ://vimeo. com/385283136 ---please delete spaces after https and after dot)
Again tks
Click to expand...
Click to collapse
did you lock your bootloader again

madvader1 said:
Hi friends. i've got stuck on power on in my redmi note 8:
I've flashed twrp and then flash Potato AOSP. then i decided go back to MIUI and flash the official rom. there the phone don't boot recovery or fastboot (Screen stay black). if i hold the vol- button appears the logo of fastboot but inmediatly reboots
Any idea??
Tks
Click to expand...
Click to collapse
I am having very similar effects. My story is that I executed fastboot return to stock ROM procedure using official firmware package (script), but for some reason it failed (bad cable or bad USB3 controller, this phone does not really like a lot of USB3 hosts).
My phone is returned to service to have the software loaded back, to my understanding it is hardbrick because no fastboot and no recovery is working in any ways. I am expecting it to be ready in a few days, will update this thread.

Hi I have exactly same problem with blinking screen and not booting. has anybody solved it yet?

mara91 said:
Hi I have exactly same problem with blinking screen and not booting. has anybody solved it yet?
Click to expand...
Click to collapse
I waited 40+ days for the Hungarian Xiaomi service partner to do anything with the phone. For some reason which I am not aware of, they did nothing.
Now I am expecting to receive back my faulty phone.
I heard that we can enable EDL mode with shorting two pins on the motherboard. If I am correct, this is a last chance method for a bricked Note 8 to be flashed again with factory software.
I will update if I have any news.

hi I was able to fix the phone - and made a tutorial. hope it helps https://forum.xda-developers.com/t/...ight-turns-on-for-a-second-using-edl.4228641/