Think I bricked my Fire~~~~ - Fire Q&A, Help & Troubleshooting

:crying::crying::crying:I take my tablet one day,and I think want to root it,but I don't know its firmware versions which is 5.3.2.1 .Then I try to root it and I failured.
Rebooted, black screen, nothing - no logo, no splash, nada. When plugged into my computer I hear it connect& disconnect over and over, with no changes to the screen. Devices & Printers shows MediaTek Preloader USB VCOM (COM6) briefly as its connecting/disconnecting.
I've tried holding Power & Vol Down for 30sec-2min at a time, no change.
Any hope of recovering?:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

It sure sounds like it a brick . Did you attempt to roll back the device ? What method did you use to try to root ?

Mr McBoatface said:
It sure sounds like it a brick . Did you attempt to roll back the device ? What method did you use to try to root ?
Click to expand...
Click to collapse
How to roll back the device? I've tried holding Power & Vol Down for 30sec-2min at a time, no change. Now it's black screen, nothing - no logo, no splash.

As I said it sounds like its a brick... The best action for you is to return to amazon if its a new device and get a replacement.
Regarding the rollback, I should have been clearer. Your device can't be saved , I was trying to find out how you bricked it . Did you try to downgrade the software ? How did you try to root it ?

Mr McBoatface said:
As I said it sounds like its a brick... The best action for you is to return to amazon if its a new device and get a replacement.
Regarding the rollback, I should have been clearer. Your device can't be saved , I was trying to find out how you bricked it . Did you try to downgrade the software ? How did you try to root it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/show...php?p=63943805
I root it from this Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.

There are several video tutorials on that page, none there for OS 5.3.2.1
That OS is not rootable and it seems you followed a process that bricked it.
Best to return the tablet, get a replacement and post here for guidance when the new tablet arrives. There are many tutorials that are correct at the time of writing but as OS versions change are no longer relevant .

Related

Ruined My Phone?

My friend told me to do a software upgrade on my phone so I followed some of his instructions. First off, I managed to use ODIN to reset the phone and I have installed a version of Honeycomb onto the phone. Now, I could easily swap back to Gingerbread, but I have two issues. When I can get the phone to start, it looks like a tablet! Everything is small, and when I connect my USB to my computer to put something onto the internal SD it won't actually open up in my computer? Secondly, it's now not even starting up into the phone, it's stuck on a black screen with a light blue ANDROID logo just pulsating. It won't go further.
Any help?
I now know not to trust my mates. Heh.
Which phone do you have? Honeycomb is for tablets and you flashed it on a phone. Luck for you that you didn't brick your device.
trale26 said:
Secondly, it's now not even starting up into the phone, it's stuck on a black screen with a light blue ANDROID logo just pulsating. It won't go further. Any help? I now know not to trust my mates. Heh.
Click to expand...
Click to collapse
First visit My Android Solutions, link below...do the first step . Than visit My Android Collections ( link below) and use a i9000 rescue kit to recover
I'm having issues understanding your tutorial. I've tried powering it down and removing all of the components and restarting after 30 seconds but still no luck.
Yeah, I downloaded and installed HoneyComb which is a tablet software. It looks like a tablet. But right now, all I get on start up is a flashing "ANDROID" icon, it won't go any further.
I'm sure I've ruined it.
trale26 said:
I'm sure I've ruined it.
Click to expand...
Click to collapse
Nope, you had messed it up, but its still recoverable by going into download mode and flashing a stock ROM with PIT, use the i9000 rescue kit from My android collection link below , and use the WIKI to get better understanding of your phone

[Q] recover bricked Samsung ATIV Odyssey ? HELP !!!!

Hi all,
Wondering if anyone could help me. On the Samsung ATIV Odyssey I have, when it boots, it will show, Windows Phone, Samsung screen then just shows the spinning gears..this will go on forever. I tried to reset and "tried" to hard reset it but could never get the "!" To show up.
Is there any way possible to recover this phone or am I stuck having to send it out to Samsung?
I have not been able to get anywhere with this phone and can't find recovery software like Nokia has for their phones for Samsung models....
Thanks in advance!!
Can anyone help with this issue ?
I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....
DavidinCT said:
I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....
Click to expand...
Click to collapse
If 'someplace in CT' means 'quacche patte a Catania vicinu a fera o luni' we live in a similar place
Anyway you can get informed better here:
http://forum.xda-developers.com/showthread.php?t=2692049
Take a Flash tool. more infos here(the procedure should be the same for the odissey)
http://forum.xda-developers.com/showthread.php?t=2391138
You can try to flash the fake wolfROM with the customwolfROM.csc(or mbn, I don't remember) for Odissey (You'll find it in the first thread i've linked you)
OF COURSE FOLLOW THE GUIDE NOT TO BRICK MORE YOU DEVICE.
If you have any problems you can ask.
Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...
DavidinCT said:
Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...
Click to expand...
Click to collapse
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing
gidannifico said:
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing
Click to expand...
Click to collapse
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?
DavidinCT said:
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?
Click to expand...
Click to collapse
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.
gidannifico said:
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.
Click to expand...
Click to collapse
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....
DavidinCT said:
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....
Click to expand...
Click to collapse
You're welcome
When the phone will be perfectly working you 'll be able to interop it with wolf's custom csc (the thread I've linked to you)
Cheers
BTW, I have the custom rom for the Odyssey, its definitely got some odd bugs.
Verizon stores can reflash it for you too for free, just need to hit up a Verizon CORPORATE store. Apparently they have the tools and the ROM, instead of waiting for it to be mailed and come back.
Well I used the wolf custom rom and follow the exactly instructions but my phone now say is corrupted, and instead of boat show me a message telling me that!
So, I got another one and now has the same problem, so, somebady knows if there is at day an original rom available?
Still no public Odyssey ROM yet.

[XT1068] - Hard Bricked while downgrading - HELP!!

Recently i installed the soak test of Marshmallow update. but after that i decided to go back to stock kitkat by using Easy KITKAT installer http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295
while i was downgrading my phone automatically TURNED OFF!!! :crying: . After that i tried to restart my phone. But it didn't restart. i plug the wall charger in, it didn't charge. i tried to connect it to pc. nothing happened. Only there is a plugging sound in pc. In device manager my phone is recognized as QHSUSB_BULK with yellow exclamatory sign. :crying: . i can't flash another rom because
Stock Recovery isn't working.
Yesterday i took my phone to service center, they told me they can't fix it. i am very frustrated right now.
I couldn't find any solution in the internet and in this forum. So this is my last try by posting in this forum.
IF ANY ONE CAN HELP ME, I WILL BE VERY MUCH APPRECIATED.
HELP! HELP! :crying:
There have been warnings everywhere to not downgrade the bootloader after going to Marshmallow, the Kitkat easy installer most likely did that. There's nothing you can do, other than get a new phone.
Transdimensionalotaku said:
There have been warnings everywhere to not downgrade the bootloader after going to Marshmallow, the Kitkat easy installer most likely did that. There's nothing you can do, other than get a new phone.
Click to expand...
Click to collapse
:crying:
ratedrzihad said:
:crying:
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
gvala said:
try this http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
hey man , I tried to link the procedure ... But my phone now connects as " Qualcomm ... " and now connects as unknown device. Already left the appliance by pressing to make sure that the problem is not in the battery but did not succeed. What I do?
GuilhermeEng said:
hey man , I tried to link the procedure ... But my phone now connects as " Qualcomm ... " and now connects as unknown device. Already left the appliance by pressing to make sure that the problem is not in the battery but did not succeed. What I do?
Click to expand...
Click to collapse
I had the same problem. Like the guy said... no other option BUY a NEW PHONE! At the moment that's the only option available. Everyone is waiting with eager anticipation for 6.0 update, if it's so good why are so many people going back to their previous OS version and bricking their phones? Motorola are not prepared to help at all claiming that downgrades are not supported and will never be supported. I go a new (2nd hand) XT1068 and I'm on 5.0.2. I WON'T be updating again that's for sure!
Guys a good news is the required mbm ci files have been released for moto g 1st gen and people have been successfully reviving their dead phones... Just keep hope and continue discussing in forums so that we get a solution as well... I am asking help from a couple of developers... hoping for the best. Cheers!! : )
LeoKarun said:
Guys a good news is the required mbm ci files have been released for moto g 1st gen and people have been successfully reviving their dead phones... Just keep hope and continue discussing in forums so that we get a solution as well... I am asking help from a couple of developers... hoping for the best. Cheers!! : )
Click to expand...
Click to collapse
. That's great for people with 1st gen phones. Lenovo / Motorola have said repeatedly on their forum that are aware of the problem but that they have no intention of releasing the required files for The Moto g2...
what is the proper way to downgrade from 6.0.1 to 4.4.4? or there is no way to downgrade. I also want to go back to kikat but there is no proper tutorial on forum so that i afraid.
my bootloader version is 48.86 !

Pretty sure My Kindle Fire 5th Gen is bricked.

Pretty sure My Kindle Fire 5th Gen is bricked.
In the process rolling back the firmware from 5.1.4 to 5.1.1 using the ADB tool and the 5.1.1: "update-kindle-full_ford-37.5.4.1_user_541112720.bin" file, the Kindle died. I have done this before a few days ago with no problem. I was having difficulty rooting the device using KingRoot so I decided to re-flash the image. After the ADB tool finished flashing the firmware I pressed the power button to reset the tablet. Now it won't turn on. The screen is completely black. No response when trying to power up the system. Tried every combination of holding the buttons. I've even pulled the battery.
The Kindle Unbrick tool also doesn't work. All the options say they can't find the device. When it is plugged into the computer the "MT 65xx Preloader" appears in Device Manager. It will appear and disappear every 10 sec or so. All the while the screen is completely powered off.
Has anyone dealt with this issue successfully or have i created a paper weight
BTW... I am pretty new to the Android hacking world, so I'm sorry if the terminology is incorrect.
bazarte said:
Pretty sure My Kindle Fire 5th Gen is bricked.
In the process rolling back the firmware from 5.1.4 to 5.1.1 using the ADB tool and the 5.1.1: "update-kindle-full_ford-37.5.4.1_user_541112720.bin" file, the Kindle died. I have done this before a few days ago with no problem. I was having difficulty rooting the device using KingRoot so I decided to re-flash the image. After the ADB tool finished flashing the firmware I pressed the power button to reset the tablet. Now it won't turn on. The screen is completely black. No response when trying to power up the system. Tried every combination of holding the buttons. I've even pulled the battery.
The Kindle Unbrick tool also doesn't work. All the options say they can't find the device. When it is plugged into the computer the "MT 65xx Preloader" appears in Device Manager. It will appear and disappear every 10 sec or so. All the while the screen is completely powered off.
Has anyone dealt with this issue successfully or have i created a paper weight
BTW... I am pretty new to the Android hacking world, so I'm sorry if the terminology is incorrect.
Click to expand...
Click to collapse
Rolling back to to 5.1.1 or below from 5.1.2 or above is a guaranteed brick. Numerous cautions posted in multiple Fire threads. What ever you did before did not start with 5.1.2+ and terminate with a working device running 5.1.1. No known recovery at present.
Davey126 said:
Rolling back to to 5.1.1 or below from 5.1.2 or above is a guaranteed brick. Numerous cautions posted in multiple Fire threads. What ever you did before did not start with 5.1.2+ and terminate with a working device running 5.1.1. No known recovery at present.
Click to expand...
Click to collapse
Well... Crap.
I attempted to downgrade 5.1.2 -> 5.1.1 with pretty much the same result......paper weight. Used aftv2 tools to establish COM port comm with the MT chipset in the tablet, even writing the correct lk.bin file to it but no difference. Either someone comes up with the unbrick method, or I just acquired a very expensive paperweight.
kasimhansia said:
I attempted to downgrade 5.1.2 -> 5.1.1 with pretty much the same result......paper weight. Used aftv2 tools to establish COM port comm with the MT chipset in the tablet, even writing the correct lk.bin file to it but no difference. Either someone comes up with the unbrick method, or I just acquired a very expensive paperweight.
Click to expand...
Click to collapse
I just bought a Fastboot Cable online. Going to see if it can be used to restore the Kindle. Will update after it arrives.
bazarte said:
I just bought a Fastboot Cable online. Going to see if it can be used to restore the Kindle. Will update after it arrives.
Click to expand...
Click to collapse
Fingers crossed! I am not sure factory/fastboot cable will work without the tablet being able to boot up or go into fastboot mode (power + vol up keys). Anyway, if it works, it'll be worth the $10 spend. Lemme know how it goes.
bazarte said:
I just bought a Fastboot Cable online. Going to see if it can be used to restore the Kindle. Will update after it arrives.
Click to expand...
Click to collapse
Fastboot/factory cables are ineffective on this device.
Did the Fastboot cable work?
---------- Post added at 02:01 AM ---------- Previous post was at 01:59 AM ----------
bazarte said:
I just bought a Fastboot Cable online. Going to see if it can be used to restore the Kindle. Will update after it arrives.
Click to expand...
Click to collapse
Did the Fastboot cable work?
kasimhansia said:
Did the Fastboot cable work?
---------- Post added at 02:01 AM ---------- Previous post was at 01:59 AM ----------
Did the Fastboot cable work?
Click to expand...
Click to collapse
I should have the cord by Thursday the 16th
I bricked my tablet as well over the weekend. I downgraded from 5.1.3 to 5.1.2 with no issue. I then tried downgrading from 5.1.2 to 5.1.1 I’ve tried several ways to unbrick and been unsuccessful. I also have the issue with the MTK device showing for about 2 seconds and then dropping offline in Windows. However in that split second the device comes up, I tried looking at what was coming across a TERMINAL. The Terminal just says READYREADYREADY. So no go!
bazarte said:
I should have the cord by Thursday the 16th
Click to expand...
Click to collapse
Not Luck. I have tried all the tricks i know. I hope i got the correct cord.
This is the cord i bought
bazarte said:
Not Luck. I have tried all the tricks i know. I hope i got the correct cord.
This is the cord i bought
Click to expand...
Click to collapse
As previously noted factory/fastboot cables are ineffective on this and several other Amazon devices. A different cable won't help.
I downgraded 5.1.3 to 5.1.2 everything worked like it should. Then for some odd ball reason I downgraded to 5.1.1 soft bricking the device. You can get the device to talk to the MediaTek Preloader Usb drivers by using the "./handshake.py" python script. However everything I have tried doesn't do anything. I also have tried a fastboot cable, and results are null! So now I either ask Amazon to replace the device. Or we keep trying different methods to find a working unlock. I would say the device isn't 100% bricked as it does respond to the handshake. =P
dem0nk1d said:
I downgraded 5.1.3 to 5.1.2 everything worked like it should. Then for some odd ball reason I downgraded to 5.1.1 soft bricking the device. You can get the device to talk to the MediaTek Preloader Usb drivers by using the "./handshake.py" python script. However everything I have tried doesn't do anything. I also have tried a fastboot cable, and results are null! So now I either ask Amazon to replace the device. Or we keep trying different methods to find a working unlock. I would say the device isn't 100% bricked as it does respond to the handshake. =P
Click to expand...
Click to collapse
Ask for an exchange. Time and talents have been expended on unbrick attempts without success. There is no indication a breakthrough is near.

DEAD P10

Hey Guys,
so i was made the bootloader unlock based on this . Everything was ok, got the TWRP on it.
After that i was install this rom. Aaaand it's gone. Black screen. If i plug it to my PC, the HiSuite starts. If i try to put it to recovery, nothing. Turning on neither.
So how can i unbrick it? Found this but the link is dead.
Or if i bring it back to my provider, will they change it, or they will see the opened bootloader?
Thanks guys!
forregand said:
Hey Guys,
so i was made the bootloader unlock based on this . Everything was ok, got the TWRP on it.
After that i was install this rom. Aaaand it's gone. Black screen. If i plug it to my PC, the HiSuite starts. If i try to put it to recovery, nothing. Turning on neither.
So how can i unbrick it? Found this but the link is dead.
Or if i bring it back to my provider, will they change it, or they will see the opened bootloader?
Thanks guys!
Click to expand...
Click to collapse
One more thing?
How do i know my exact model number if my phone dead?
On the box there is just VTR-L09
Thanks again
forregand said:
One more thing?
How do i know my exact model number if my phone dead?
On the box there is just VTR-L09
Thanks again
Click to expand...
Click to collapse
In your shoes, I would not bring it to any provider like you have it.
I would perform something like the following: https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
There are tons of guides on how to unbrick P10 phones too. I could not recommend any specific one, but your phone seems to be far from dead, you just need to perform a full reflash/rebrand procedure. Best phone to rebrand to IMHO is VTR-L29, you gain an additional SIM with no counter effect.
Regards
Floodland said:
In your shoes, I would not bring it to any provider like you have it.
I would perform something like the following: https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
There are tons of guides on how to unbrick P10 phones too. I could not recommend any specific one, but your phone seems to be far from dead, you just need to perform a full reflash/rebrand procedure. Best phone to rebrand to IMHO is VTR-L29, you gain an additional SIM with no counter effect.
Regards
Click to expand...
Click to collapse
Thanks a lot Floodlan, i will try it and come back!
Floodland said:
In your shoes, I would not bring it to any provider like you have it.
I would perform something like the following: https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
There are tons of guides on how to unbrick P10 phones too. I could not recommend any specific one, but your phone seems to be far from dead, you just need to perform a full reflash/rebrand procedure. Best phone to rebrand to IMHO is VTR-L29, you gain an additional SIM with no counter effect.
Regards
Click to expand...
Click to collapse
Re. It does not helped me.
If i push the power button long, the Windows playing the unconnect sound. If i push the Vol down and connect it again, the Windows play the connect sound. But the phone's display is black. Whatever i do with it, the display is black.
forregand said:
Re. It does not helped me.
If i push the power button long, the Windows playing the unconnect sound. If i push the Vol down and connect it again, the Windows play the connect sound. But the phone's display is black. Whatever i do with it, the display is black.
Click to expand...
Click to collapse
Did you try with fastboot mode? You will need fastboot drivers installed in your computer, but if you can see the device, you should be able to flash a new recovery or whatever needed to start from scratch...
Floodland said:
Did you try with fastboot mode? You will need fastboot drivers installed in your computer, but if you can see the device, you should be able to flash a new recovery or whatever needed to start from scratch...
Click to expand...
Click to collapse
sure, i tried. black screen. it was on charger for a night. nothing. if i push the power button for minutes, nothing. if i try the fastboot vol down + cable, the windows makes sound, the HiCare turns on, but nothing. moreover i don't know the product id.
finally i was paid to funkyhuawei, and they made it working. it was 2 hours...
bigup for the guys, they are magicians.

Categories

Resources