Related
Hi, I think this is my first post here. Anyway, here the question:
I have an Ideos X5 (not pro), it is bricked. So far, I have followed instruction for recoveries from several threads, but none of them worked because in my phone:
there is no boot screen
there is no pink screen
there is no logo
there are no images of any kind (screen wont even turn on)
it only vibrates when I plug it into my computer
Also *sometimes* the buttons light up and when this happens windows detect a new USB device, but after I while it dissapears again. Also, this happens only with the battery on.
The phone became bricked after I followed instructions to revert back to froyo from gingerbread (wifi wasn't working). All roms were originals from Huawei.
So, any suggestions??
Thanks in advanced.
I had a problem like you.I have deleted amss.mbn file because Huawei locked pink screen, it was bricked But i wasn't so patience enough, i sent my phone to technical care.But here are the answers, try it with caution:
shuiyunxingzuo said:
Hi
Space is not enough to flash any ROMs;
Bootloader is locked,you could not edit that sector.
So is there a special ROM that is very small and allows to edit the bootloader?
Here is the MINI ROM:
http://www.mediafire.com/?7c33h84a974va28
Flash it than edit the bootloader~
NOTICE: I format the whole sector ,and the file including IMEI was missing
'Cause I don't know how to edit recovery or other system files like .mbn,
so just delete the abnormal big file and you would be able to flash any ROM s
Click to expand...
Click to collapse
xmsnx said:
Yes!!!! My phone works"!!!!!!!
Ok here's what I did
Download mediafire.com/?1hbk6n46hgamyt6
Unzip it, and find UPDATE.APP
Put UPDATE.APP in a dload folder and upload to empty sdcard.
Put sdcard in phone, and hold vol+/- and power and flash it.
After phone has restarted pull battery.
Download http://www.mediafire.com/?6hrfz36b8e2vw87
Unzip and copy the dload folder to empty sdcard.
Hold vol+/- and power and flash it.
After it fails near the end or if it restarts then pull battery.
Download a rooted boot.img and a clockworkmod recovery.img (got both mine from links at modaco)
Attach phone to PC in pink screen mode and delete the boot.img and recover.img files.
Upload the downloaded root.img and recovery.img to image folder in phone.
Download any custom rom from XDA, I used http://forum.xda-developers.com/showthread.php?t=1475687 and upload it to sdcard
Pull battery.
Hold vol+ and power and go into clockworkmod, wipe everything and flash the custom rom!!
Good luck!
Click to expand...
Click to collapse
Tried taking off the battery for 10 seconds and after that inserted USB into computer (without battery)? Also try to take off battery and insert USB to wall-charger.
The buttons lighting up could be our way out, but if it only stays there for a couple of seconds it doesn't help. Can you see what Windows detects?
Hi again,
thanks for answering.
None of your suggestions worked anyway, because it won't even load anything from the sdcard, it just makes a short vibration and nothing more.
I managed to get the lights on again, but windows didn't show what kind of device it was, maybe because it's already installed but I'm not sure which usb device is it (windows did make a sound though, like "device is connected" sound). Also I noticed there's a red led blinking near the speaker, does that mean anything?
Anyway, tried to flash while the lights were up but it did nothing, and after two minutes the went off again.
Thanks again for your suggestions.
I connected the phone to my laptop with ubuntu, and despite I cannot do anything with the phone, there are two devices created in /dev: hiddev0 and hidraw0. Is there a way to flash the device using any of those files?
thanks again.
Worth a try on this post : Here
It is fried then
Try mounting those two devices, is there any file system recognized? It might not be bricked, but this is an issue probably nobody has had yet. Send it in for repair if it is still within warranty.
Important question: How did this even happen?
XphX
XphX said:
Important question: How did this even happen?
Click to expand...
Click to collapse
auxorro said:
The phone became bricked after I followed instructions to revert back to froyo from gingerbread (wifi wasn't working). All roms were originals from Huawei.
Click to expand...
Click to collapse
Sent from my U8800 using Tapatalk 2
Hi,
thanks for all the help.
Sadly nothing works with this phone, I tried mounting and dd from the devices but nothing happens.
I guess I'll send it for repair (hope it's still within warranty)
Anyway, thanks again for all the suggestions.
Bye!!
auxorro said:
Hi,
thanks for all the help.
Sadly nothing works with this phone, I tried mounting and dd from the devices but nothing happens.
I guess I'll send it for repair (hope it's still within warranty)
Anyway, thanks again for all the suggestions.
Bye!!
Click to expand...
Click to collapse
If the phone wasn't rooted, then it is still within warranty
Hello, recently I've tried to install clockwork recovery in my Galaxy S (I9000B), so I've downloaded ODIN and all the other tools and drivers. But the USB on my phone wasn't working, and it was the phone, I've tried different drivers on different computers and the same result, "The USB device was not recognized". So I've downloaded on play market the Busybox, in hope of getting something done. After installing it, busybox asked to reboot phone, so I did it, and the problem started, the phone is stuck on the booting animation, that one showing the phone model. I can still acess the download mode and the stock recovery, but can't connect to PC to flash via ODIN, and external SD is not possible aswell. I've already tried to wipe dalvik cache and data, but nothing. What do I do?
Zkaar said:
What do I do?
Click to expand...
Click to collapse
try a a solution from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Most of all i9000B is not compatible with i9000 ROMS so make sure you only use i9000B ROMS
xsenman said:
try a a solution from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Most of all i9000B is not compatible with i9000 ROMS so make sure you only use i9000B ROMS
Click to expand...
Click to collapse
Yeah, I've already tried that, but stays the same. I never got the chance to flash a custom rom because of the malfunctioning phone USB. There's nothing I can do, or there is something that I don't know
Zkaar said:
Yeah, I've already tried that, but stays the same. I never got the chance to flash a custom rom because of the malfunctioning phone USB. There's nothing I can do, or there is something that I don't know
Click to expand...
Click to collapse
all solutions to solve USB connection problems are mentioned in the above link
Zkaar said:
Hello, recently I've tried to install clockwork recovery in my Galaxy S (I9000B), so I've downloaded ODIN and all the other tools and drivers. But the USB on my phone wasn't working, and it was the phone, I've tried different drivers on different computers and the same result, "The USB device was not recognized". So I've downloaded on play market the Busybox, in hope of getting something done. After installing it, busybox asked to reboot phone, so I did it, and the problem started, the phone is stuck on the booting animation, that one showing the phone model. I can still acess the download mode and the stock recovery, but can't connect to PC to flash via ODIN, and external SD is not possible aswell. I've already tried to wipe dalvik cache and data, but nothing. What do I do?
Click to expand...
Click to collapse
Maybe You should try this:
http://forum.xda-developers.com/showthread.php?t=1602877
I simply took off the back cover and heated the motherboard.
It worked for me!
If you still have access to your recovery then just install a new kernel and ROM.
Sent from my GT-I9000 using xda premium
Hi, I'm new in this forum so don't be harsh on me I've bricked my u8800 pro.
I've downloaded firmware from: huaweidevice[dot]com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDY1NTY=
I've installed first UPDATE.APP file in my formated sd card and went to settings and chose to update from sd card. After some time installation failed and phone freezed so i removed battery, but when i tried to turn on the phone nothing happened, it doesn't turn in recovery mode either. Usb isn't working.
Is there any chance i can unbrick my phone? How?
Thanks for help.
Hi, download official 2.2/2.3 for U8800Pro and copy it on the MicroSD card via usb card reader.
Turn off the phone , insert MicroSD card and hold vol up, vol down and power buttons at the same time.
Phone will turn on and start installing official 2.2/2.3
When install was comlete, you are done.
Thanks for reply. I have done as you said ( used: U8800P_Android_2.3_V100R001C00B521_Oversea_Normal_05010TXB ) but nothing happened - installation haven't started, no pink screen. As I stated before phone does not turn on to recovery and it doesn't turn on with or without an sd card, it doesn't show any kind of life. Maybe you have another piece of advice.
Pull the battery out and connect phone to the charger/PC via USB and hold vol +, vol - and power at the same time. Maybe it helps.
Thanks for reply, but as i stated before usb isn't working, because there's a crack in mainboard near the usb socket. I'll try to solder the mainboard as soon as i'll find necessary screwdriver for unscrewing plastic parts. Maybe you have other suggestion that doesn't involve usb.
Try to install other official roms. Maybe one of all will work.
U8800h
hi all,
i have the exact same problem on my U8800h and i've tried all of that..
were u able to reach a solution or is there any further steps i can do?
thanks in advance
Maybe someone knows how to unbrick using jtag?
Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards
undulus said:
Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards
Click to expand...
Click to collapse
Hi, open ur phone again and check the display connector, try fully disconnecting it and reconnecting it and check if all other connectors in range are also properly connected. Then reassemble ur phone.
Next time, do not open your phone unless you really have to. I don't see why you have opened to reset it. You can press power for very long then after maybe 30 seconds or so, your phone will fully turn off. No need to open it for that.
Next time if you have a question, use the Q&A section, not this one. You'll get answers quicker there too.
Bricked or screen is broken
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..
undulus said:
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..
Click to expand...
Click to collapse
if that worked, i'd be curious to know
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.
i have the same issue.
one day stop working
AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&_ct=1551037935701&referrer=https://www.google.com&_tf=From %1$s&share=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down