Hi everyone,
First of all, I have some basic knowledge but treat me as an absolute noob please
I have a issue with my Huawei Ascend G700-U10. I tried flashing twrp recovery from the phone itself. It was either a wrong one or (I read that that could happen) something with the partition. The result is a boot loop. My PC does recognise the decive, but only for a few seconds. The flash tool does "try" flashing, but as the phone is disconnected too fast, I get an error message. Without much experience, I'd say that the only way I could flash something is making the phone stay connected longer or make the program flash faster. I have no idea how to make the phone stay connected and tried to only flash the stock recovery because I thought it would have to flash less and get it done in those two seconds that the phone stays connected. That didn't work though.
I thought about buying a new phone anyway, so if I can't solve it, it's not dramatic, but a working phone is always better than one that doesn't.
Thanks for your help in advance
Hi, thank you for issued XDA Assist. I think you're right that you need to flash the stock firmware. I'm not sure why usb would keep disconnecting but try different usb ports, the ones in the back of your pc, and cables.
Thread closed.
Related
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'
Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't
Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working