Currently, I have a Honor 7A device which have a lot of problem. Currently, the phone stuck in a charging state with 100% battery although in idle condition. I've downloaded the exact same firmware and try flashing it using dload method only to get software install failed. I currently unable to use fastboot or adb for some reason, the PC don't detect the phone. Even HiSuite would not recognize the phone. I also tried using Vol+ and power combination to download the firmware but it shuts down on 1% progress. I don't usually post new thread but I have no choice. I hope someone can help me.
Did you try factory reset once to see if it fixes
I've tried thrice and the problem is still there
Did you try dload the next or higher version
shashank1320 said:
Did you try dload the next or higher version
Click to expand...
Click to collapse
Unfortunately,there is no higher version beside I'm currently on.
My current build is AUM-L29C636 8.0.0.165 while both internet and Firmware Finder only give build 8.0.0.164. I can't get the exact build or higher.
Sorry for double posting
I currently confirmed that the software caused this problem since I have changed the charging port but the problem persists. Is there anyway to :
1) Somehow do a successful dload firmware flashing?
2) Make phone don't turn off during wifi recovery?
3) Make phone detectable on fastboot so I can use unlocked bootloader method?
Related
Hello all.
My Xperia X10 Mini Pro is stuck on bootloop as you can see on this video
http://youtu.be/EhaBn0uuSvE
It just got like that from one moment to the other..I was using stock ROM
I tried to flash with Flashtool with these ROMs
U20a_2.1udpt1_Generic
ST17i-Active_4.1.B.0.431-1254-6360_SONY
On the first ROM it gets 100% successfull but still cant boot !
This phone was bought on Portugal, so I dont know if the ROM makes any difference..
Need some advice please !
I've read somewhere that Gordon's Gate (part of Flashtool) can still access a phone even when it bootloops.
Could you document what steps you already took? Perhaps link to the article you followed? (Below is a list of certain steps one usually takes when installing custom ROMS, but they are by no means always necessary, could you perhaps indicate what you already did?)
Rooted Yes/No/Not Sure
ClockWorkMod installed Yes/No/Not Sure
Unlocked bootloader Yes/No/Not Sure
Custom kernel Yes/No/Not Sure
The location of where the phone was bought will not make a lot of difference for the ROM. It might affect things like hardware keyboard layouts, but there are fixes available for those. But things like specific baseband and firmware are still important. By carefully reading the description, you can usually check if your phone can be used.
To be honest, I only have used Flashtool to flash new kernels to my X10 Mini Pro, for just installing another ROM I use ClockWorkMod.
What you can try:
Unbrick through SEUS: here (video)
I've read about people unbricking their devices with PC Companion, here.
If you should be able to regain access to the phone and still want to tinker:
This ROM works nice with the stock kernel
Later, you could unlock the bootloader, flash custom kernels (nAa ICS 04) and install ROMS needing such custom kernels (the U20 ICS ROMS, like MiniCM9)
Should you feel the need to ever unlock the bootloader, use this tool
Cheers and thanks for your post !
I used SEUS and updated to latest firmware but still no success on booting. It stills the same...
Rooted No
ClockWorkMod installed No
Unlocked bootloader No
Custom kernel Not Sure
Any chance that you can point me a stock rom and stock kernel to see if it boots that way?
JotaM07 said:
Cheers and thanks for your post !
I used SEUS and updated to latest firmware but still no success on booting. It stills the same...
Rooted No
ClockWorkMod installed No
Unlocked bootloader No
Custom kernel Not Sure
Any chance that you can point me a stock rom and stock kernel to see if it boots that way?
Click to expand...
Click to collapse
Don't update, repair... leave your phone unplugged when SEUS searches for updates, it can't recognise your phone when it's not connected and will give you a repair option. choose that, and make sure you select your phone from the list presented. it will then flash original kernel and firmware to your phone.
Don't know which kernel you flashed before you got this bootloop, but the second rom you mentioned in your opening post isn't even for your phone, so i guess you got confused with what goes for your phone. You don't even get a kernel logo, so i guess you flashed a kernel for a different model altogether, or your stock kernel got corrupted. a repair should fix it.
I'm now updating on PC Companion like belgianguy said
If unsuccessfull I'll follow your instructions, thanks a lot in advance !
Same on PC Companion..no boot !
SmG67, I dont see any repair option on SEUS. It detects the phone and says thar it's updated. If I remove the battery while is searching my phone it keeps saying that it's updated. What am I doing wrong ?
On PC Companion I got the Repair option, it repaired, but...surprise...still can't boot !
JotaM07 said:
Same on PC Companion..no boot !
SmG67, I dont see any repair option on SEUS. It detects the phone and says thar it's updated. If I remove the battery while is searching my phone it keeps saying that it's updated. What am I doing wrong ?
On PC Companion I got the Repair option, it repaired, but...surprise...still can't boot !
Click to expand...
Click to collapse
That's a shame... because you now have all official sony ericsson firmware on your phone, kernel and rom... If it's still not booting the kernel, there's nothing you can do about it, maybe a repair-shop might be able to fix it.
Well, a repair-shop isnt able to fix it because the mini-usb port has bad contact and they consider this phone out of warranty because of that ! It almost never happens that bad contact..
JotaM07 said:
Well, a repair-shop isnt able to fix it because the mini-usb port has bad contact and they consider this phone out of warranty because of that ! It almost never happens that bad contact..
Click to expand...
Click to collapse
Well if it's that far gone it might very well be a hardware issue. But just to be sure, could you start Flashtool and see if it still recognizes the device (see screenshot of what I see).
If it isn't able to, an older version of s1tool had an IDENTIFY option that required you plug the USB cable into the computer (but not in the phone), to shut down the phone, then push the BACK button and then plug the usb cable into the phone.
The bad contact you mentioned might be causing troubke as well, are you sure it isn't the cable that is at fault? Perhaps try to attach the USB cable in such a way that its not stressed and so that the phone cannot move (to prevent it from disconnecting due to a bad contact). Your flashes very well might have gone faulty because of that. But then again, the SEUS/PC Companion flashes seem to have succeeded, so hopefully Flashtool can shed some light here.
Hi All. I'm afraid my Honor 10 is permanently dead but I'm looking for a solution to "exhume" it.
I had latest firmware installed, 9.0.0.219 (C636), but after I installed it, I observed some ghost touches and application lags so I wanted to install the Pixel Experience custom rom. To install this rom it needs not to be on Emui 9, so I used beta-downy_04 to rollback to latest oreo 8.1 fimware (COL-L29C636B153 8.1.0.153). All good until an error appears while flashing the firmware, "Software fimware failed"..Then a message appeared that suggested me to reboot or select eRecovery. I chose eRecovery but nothing. It won't to turn on. I tried to force reboot with Vol-Up and powe for more than 30 seconds, no responses. I tried to use Multi-tool because if I connect Honor 10 to pc it is recognised as fastboot device, so I tried to unbrick it flashing system, cust, kernel and recovery_ramdisk images, but nothing. So Am I finished? Can someone help me? Thanks :crying:
Sorry to hear that man. I noticed that after .219 update HiSuite doesn't get rollback firmwares from HiCloud anymore. Is that the reason why you tried the method above?
I tested rollback request with .212 in HiSuite and it successfully sent me the rollback data which is 219870 ID (not 206629 or 186881). Since Huawei device names change it's kinda tricky to force stuff into the phone.
{"status":"0","versionPackageCheckResults":[{"status":"0","autoPollingCycle":"1","components":[{"componentID":1,"createTime":"2019-04-25T07:08:45+0000","description":"219 - 153 fullback","name":"COL-L29 8.1.0.153(C636)","pointVersion":"1","reserveUrl":"updatessl.dbankcdn.com","ruleAttr":"","url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G3015/g1642/v219870/f1/","version":"COL-L29 8.1.0.153(C636)","versionID":"219870"}],"versionPackageType":1,"checkEnd":"1"}]}
If you didn't try the id 219870, can you try to flash it?
MagnoT said:
Sorry to hear that man. I noticed that after .219 update HiSuite doesn't get rollback firmwares from HiCloud anymore. Is that the reason why you tried the method above?
I tested rollback request with .212 in HiSuite and it successfully sent me the rollback data which is 219870 ID (not 206629 or 186881). Since Huawei device names change it's kinda tricky to force stuff into the phone.
{"status":"0","versionPackageCheckResults":[{"status":"0","autoPollingCycle":"1","components":[{"componentID":1,"createTime":"2019-04-25T07:08:45+0000","description":"219 - 153 fullback","name":"COL-L29 8.1.0.153(C636)","pointVersion":"1","reserveUrl":"updatessl.dbankcdn.com","ruleAttr":"","url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G3015/g1642/v219870/f1/","version":"COL-L29 8.1.0.153(C636)","versionID":"219870"}],"versionPackageType":1,"checkEnd":"1"}]}
If you didn't try the id 219870, can you try to flash it?
Click to expand...
Click to collapse
Hi. Thanks for your answer. Yes, I tried to rollback with beta-downy program because I wanted to flash a custom rom and I needed android 8.1 to do that.
Unfortunately I flashed a firmware COL-L29 8.1.0.153(C636) with ID 186881 because it has three files and beta-downy program works only if update.zip, update_all_hw.zip and update_data_public.zip files are present in ZIP-HERE folder and firmware with ID 219870 has only two files...
At this moment Honor 10 is fully dead. I can't access to bootloader mode but if I connect it to pc and I use adb, I seem to be able to use fastboot but I don't know if It really flashed something. So I can only use fastboot ( and I flashed all needed files of latest firmware installed, version .219) but it is useless at this time because Honor 10 appears dead, it won't charge. Sometimes seven red blinding appear when I try to force reboot pressing and holding power on and Vol-up buttons.... I tried to remove battery also, then to plugin the charge and holding power button for 30 seconds and then to insert the battery again but nothing. No charge and no power on... I have no idea what I must to do...
Someone alive???
Why you can't access bootloader?
Did you try to plug in charger while pressing vol down button?
empedocle86 said:
Hi All. I'm afraid my Honor 10 is permanently dead but I'm looking for a solution to "exhume" it.
I had latest firmware installed, 9.0.0.219 (C636), but after I installed it, I observed some ghost touches and application lags so I wanted to install the Pixel Experience custom rom. To install this rom it needs not to be on Emui 9, so I used beta-downy_04 to rollback to latest oreo 8.1 fimware (COL-L29C636B153 8.1.0.153). All good until an error appears while flashing the firmware, "Software fimware failed"..Then a message appeared that suggested me to reboot or select eRecovery. I chose eRecovery but nothing. It won't to turn on. I tried to force reboot with Vol-Up and powe for more than 30 seconds, no responses. I tried to use Multi-tool because if I connect Honor 10 to pc it is recognised as fastboot device, so I tried to unbrick it flashing system, cust, kernel and recovery_ramdisk images, but nothing. So Am I finished? Can someone help me? Thanks :crying:
Click to expand...
Click to collapse
Same happened to me so i bought new phone, luuckly i bought phone that broke with "found" money. Go to nearest repair center and say you left phone plugged overnight to update, tomorrow you came and it was dead. They will repair it for free if it had guarantee.
bestenderowner said:
Same happened to me so i bought new phone, luuckly i bought phone that broke with "found" money. Go to nearest repair center and say you left phone plugged overnight to update, tomorrow you came and it was dead. They will repair it for free if it had guarantee.
Click to expand...
Click to collapse
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
For all of you if you are willing to open back panel of your phone I can help you.
miststudent2011 said:
For all of you if you are willing to open back panel of your phone I can help you.
Click to expand...
Click to collapse
Panel back open....and now??
darks0ldier said:
Panel back open....and now??
Click to expand...
Click to collapse
There is a method known as test point method where you short two ports and flash service firmware. And later you flash full firmware.
Search Huawei p20 forums for details. Try to find them and share the links you got then I will guide you what next.
darks0ldier said:
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
Click to expand...
Click to collapse
I bought Chinese ****, i tried everything, i paid 30 bucks for code from one asshole, than i thought i hardbricked my device, i went to service, they said the motherboard was burnt, i lied that i left device update overnight xD, because bricking voids warranty. They said they dont support chineese guarante because we are Eu, so i sent my **** back to bang**** banggood. Com scammers. Than year i waited and they sent me refund 100 dolars, i paid 450 bucks, luckly i bought it with my grampa credit card so lol i got 100 bucks free xD ans i bought iFix it kit. So i recommend you to buy unlock code, and if you know what you are doing, you can successfully rebrand it, il send you one link, that helped me a lot. But it was t9o late, and i was stupid. I was curious and i flashed my phone with upgrade file, i didnt flash it with full ota., so basically idfk what did i do xD. So i probably wiped end to end and it removed power supply unit settings and full power from battery destroyed my cpu. Sooooo good luck and find something cheap or just try to get free code from funky huawei, they can help you rebrand, better pay 50bucks than loose 400 bucks
---------- Post added at 07:52 PM ---------- Previous post was at 07:49 PM ----------
darks0ldier said:
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-10/how-to/successfully-rebranding-chinese-col-t3823782
And i just noticed your device is dead. Okay idk are u familiar with those processes.
Extract boot.img file from firmware, (firmware extractor) by huawei. Than open adb, and do flash boot boot. Img, flash recovery recovery.img and thst
So my phone just got stuck while normal usage. Tried restarting and the phone began boot looping.
Did plenty of research and finally decided to flash. Tried to flash using mi flash in fastboot mode but failed then google search made me realise my bootloader was locked. Did more research and decided to flash using test point EDL method.
Things went pretty well and the flash (miui v8) and the process became successful and when I powered my device the phone went back to boot loop again.
Tried flashing again and the result was the same.
It would be really helpful if somebody could actually help clear the issue. Did pretty much everything I could do as a newbie to flashing.
thank you!
There are 2 varients of rn4 one is mediatek(note 4x) and the other is Snapdragon so check if u flashed right firmware
thisbearisdrunk said:
There are 2 varients of rn4 one is mediatek(note 4x) and the other is Snapdragon so check if u flashed right firmware
Click to expand...
Click to collapse
No, I have flashed the correct file(Mido) and the flashing process went quite well but the problem still exists.
M i L i N said:
No, I have flashed the correct file(Mido) and the flashing process went quite well but the problem still exists.
Click to expand...
Click to collapse
How is ur phone being recognised in mi flash tool?
A serial number appears or something else like "com_port" appears?
thisbearisdrunk said:
How is ur phone being recognised in mi flash tool?
A serial number appears or something else like "com_port" appears?
Click to expand...
Click to collapse
It's recognised as COM4 the first time I tried then sometimes when I connect it shows COM3.
M i L i N said:
It's recognised as COM4 the first time I tried then sometimes when I connect it shows COM3.
Click to expand...
Click to collapse
If it recognises ur phone like that then flashing does nothing to ur phone so the only way is to go into edl mode and then flashing
https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Use this tool to go into edl mode and then flash
This thread can help ,because i bricked my phone once without unlocking the bootloader and the miflashtool recognised my phone like how it recognised urs and this thread saved my phone
Good luck
Hello everyone.
I have just got this phone brought to me by my little brother. It seems that phone is made for Japanese network (Softbank)
according to him, he downloaded few apps and was using it for few week until recently there was a problem and the phone had some issues. So he took it to repairer and the phone was flashed back to the company default
But now the issue is that the phone doesn't recognize any SIM and also WIFI searching forever without finding any network. I am not able to pass through this initial phone setup configuration to find out what exactly is wrong with the phone
Although phone restart with inserting SIM but soon as it boots to setup it acts like no SIM is inserted and prompt to connect to either network.
I have used Xperia companion with no luck cause the file size taking very long and my internet connection is not stable and failed on many attempts
Downloaded the exact Japanese firmware from Xperifirm and flashed using newflasher but still could not pass the setup due to no connection
I am not able to even skip that network and initial setup like all other android phone because the phone has to be connected to network and there is not step to skip
What could have gone wrong with the phone. Is this a software issue because the phone bricked by that guy accidently did something to software stuff or is it hardware issue? any urgent assistance would be highly appreciated.
I haven't touched the bootloader yet and as far I know it cant be unlocked?
Please help me resolving this issue
usually it happens when flashing the wrong baseband or modem firmware from another japanese firmware e.g. au kddi/docomo firmware,clean flash via newflasher should fix the problem,make sure to download the right firmware for your model (701SO),not au kddi or docomo...
if problem still exist after flash it,try to flash the global firmware (try CE1 firmware),it will convert your device to global variant(but nfc will not work and deep sleep not working)
good luck :good:
filandry said:
usually it happens when flashing the wrong baseband or modem firmware from another japanese firmware e.g. au kddi/docomo firmware,clean flash via newflasher should fix the problem,make sure to download the right firmware for your model (701SO),not au kddi or docomo...
if problem still exist after flash it,try to flash the global firmware (try CE1 firmware),it will convert your device to global variant(but nfc will not work and deep sleep not working)
good luck :good:
Click to expand...
Click to collapse
Hi and thanks @filandry
I have downloaded the exact copy of firmware as per my model (701so) and I even downloaded the UK customised version today and flashed it. The phone boots to setup but same issue no SIM detection and no wifi activity. I can't even see SIM or WIFI icons on the status bar
I am now thinking of whether if it's possible to somehow find this setup file and delete it in the firmware folder and then flash the firmware to see if it works when it gets to phone.
It will also help me checking the IMEI and other stuff but just wondering if its possible?
I know there maybe still few options to get the phone somehow into desktop but I am kinda newbie into sony phones and i wouldn't mind doing it
Edit; Just forgot the CE1 firmware part. How different is it from UK customised version? You really sure this will make a difference? Cause downloading a big file is a very daunting task for me as I am living in a place where we barely get 512 KB (shared 1:3) download time take a whole day for me.
waheedxda said:
Hi and thanks @filandry
I have downloaded the exact copy of firmware as per my model (701so) and I even downloaded the UK customised version today and flashed it. The phone boots to setup but same issue no SIM detection and no wifi activity. I can't even see SIM or WIFI icons on the status bar
I am now thinking of whether if it's possible to somehow find this setup file and delete it in the firmware folder and then flash the firmware to see if it works when it gets to phone.
It will also help me checking the IMEI and other stuff but just wondering if its possible?
I know there maybe still few options to get the phone somehow into desktop but I am kinda newbie into sony phones and i wouldn't mind doing it
Edit; Just forgot the CE1 firmware part. How different is it from UK customised version? You really sure this will make a difference? Cause downloading a big file is a very daunting task for me as I am living in a place where we barely get 512 KB (shared 1:3) download time take a whole day for me.
Click to expand...
Click to collapse
you can try this via adb (i'm not sure if you can connect via adb since usb debugging not turning on)
https://forum.xda-developers.com/mi-4i/trick-skip-wifi-setup-setup-wizard-t3524419
or...try to boot up in safe mode
you can google it how to enter safe mode
filandry said:
you can try this via adb (i'm not sure if you can connect via adb since usb debugging not turning on)
https://forum.xda-developers.com/mi-4i/trick-skip-wifi-setup-setup-wizard-t3524419
or...try to boot up in safe mode
you can google it how to enter safe mode
Click to expand...
Click to collapse
Thanks for replying.
Adb can't be done since it needs usb debugging turned on and for that I need to get to the phone settings.
Safe mode already tried in the past and done it again for this new firmware but same issue
I wish i could flash custom rom so that its start-up settings might be different and no need to be connected
I really need help here if I still have an option
waheedxda said:
Thanks for replying.
Adb can't be done since it needs usb debugging turned on and for that I need to get to the phone settings.
Safe mode already tried in the past and done it again for this new firmware but same issue
I wish i could flash custom rom so that its start-up settings might be different and no need to be connected
I really need help here if I still have an option
Click to expand...
Click to collapse
is it already fixed?
Hi guys
I followed this guide for unlock bootloader and install magisk: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4344371/
I don't blame the author of the guide, it is my device, my responsibility, my decision to attempt this. My fault.
Everything was going great, I unlocked the bootloader successfully and my device wiped and rebooted. It boot back into android, I turn off, go to fastboot mode, and try to flash magisk img file I made earlier in the guide. It says success, then last step of the guide is to wipe with fastboot -w. This fails, says cannot wipe metadata. Reboot, now my phone says "your device is corrupted and cannot be trusted and will not boot"
No idea what to do here, so i try to use Xperia Companion to restore. But it refuses because it detect bootloader is unlocked. Now I try to use NewFlasher to flash firmware from XperiFirm, this starts off fine but then NewFlasher reaches this point
"Extracting sparse chunk super.040"
"Uploading sparse chunk C:\temp\xperiafirmware\flash_sesson_super.0.40"
"download:03b4c9c"
"ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
I have tried to do this with another computer, I have tried 2 other USB cables, I have tried another firmware (originally tried the latest version with open carrier but also tried with carrier specific one) I am now running out of ideas to try.
I can get to fastboot mode or flash mode, but if I try to boot OS it says "your device is corrupted and cannot be trusted and will not boot"
Any help or a point in the right direction would be much appreciated
Thank you so much in advance
Last week that happened to me. As long as you can go to fastboot you're good. First is relock the bootlaloader via fastboot then repair it using xperia companion. Or if you can download the firmware via xperifirm then flash it via flasher.
Also make sure that the PC your using has both an Intel CPU or AMD CPU and a full windows install not that cheap windows store only crap..but one you can actually install windows .exe files and make sure you have installed the Xperia drivers by turning off driver verification...o tried without and my 2 in 1 couldn't find my phone for Xperia companion nor the other flashing tool...
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
marshedpotato said:
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
Click to expand...
Click to collapse
No problem fam, glad it got sorted out