Related
Good evening,
That I had already come to you last summer because I had managed to bricking my LG.
Now I got new adventures ... If you have an idea, please ...
Let me explain, having broken my screen, I'm ordering one, when I received it I noticed that he was writing D800 on one party. I then contact the vendor who told me it was "fit", so I still do the replacement. After that the phone did not want to come out of standby (but the backlight is lit yet); and occasionally, white stripes with a focal effect.
I say that with a little luck it was a software concern. I reinstall an update CM days that the manager had automatically upload at a time. Then the phone remained bootloop on the LG logo.
So surely very intelligently I wanted to zero all over again, and so I reinstall the recovery to date (http: //forum.xda-dev...-tools-t2898705) and then install rom ..
So then the real trouble begins, I had more access to recovery and against it as going longer in the sequence of boot, until optimazation App and continually turned round: restart, optimization, restart. ..
So I told myself last solution KDZ flash tool, not quite knowing what version take KDZ file I got the following: UK EE D80230b.
And since I have nothing, no download mode, no recovery, and even no screen! just the backlight that lights up.
Help please
edit :
and when i'm plug it in, in the device manager its say : USB MTP and LGE phone ... but no bulkmode or something
Try reinstalling your broken screen or another screen matching the model of your device. If it works then you're set. But if it doesn't, replace the d800 screen with the correct screen and try flashing cyanogen or another rom for your model. Thats all I have goodluck I hope you manage to fix your phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
butinside said:
Try reinstalling your broken screen or another screen matching the model of your device. If it works then you're set. But if it doesn't, replace the d800 screen with the correct screen and try flashing cyanogen or another rom for your model. Thats all I have goodluck I hope you manage to fix your phone.
Click to expand...
Click to collapse
I meant flashing another rom which you are completely sure is compatible with your phone.
Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Optimusik said:
Hi, i dont know what happened before this state but now it is not booting and anything show on the screen. Device Manager shows Qualcomm HS-USB QDLoader 9008. Can this phone work normally or it is fully dead? Thanks in any case.
Click to expand...
Click to collapse
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
superviked said:
You can always get it up and running as long as it's only the software issue. Have you tried using the Wugfresh Toolkit/ any other toolkit and connecting your phone? Have you tried to reboot to bootloader or recovery?
If you haven't already, press and hold volume up + power button until you see the bootloader then connect your phone to your PC and install the toolkit of your preference and install the stock Rom, follow onscreen instructions on your PC. Hope this helps.
Click to expand...
Click to collapse
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
It is definitely hard bricked. QDloader mode = Hard Brick. But if Google has released the blankflash files for the N6P (Idk if they have or not), then you can recover.
Optimusik said:
I would try this with pleasure but its always black screen anytime. And phone recognized by computer only in that mode that i described
Click to expand...
Click to collapse
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
superviked said:
You can always get it up and running as long as it's only the software issue.
Click to expand...
Click to collapse
Not true.
superviked said:
This is the closest I found related to your issue, however this is the guide to resolve the same issue but for the Nexus 5 Hammerhead. Someone needs to confirm if the N6P images can be flashed with the same method.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
theesotericone said:
Not true.
The boarddiag tool is specific to LG devices. It will be of no use here.
This is the first post I've seen for Angler that has a Qualcomm HS-USB QDLoader 9008. If it starts to happen more people will start to look into a fix. Until then I'm afraid the OP is bricked.
Click to expand...
Click to collapse
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
superviked said:
Have you installed TWRP, have you been able to boot into recovery/bootloader via ADB?
---------- Post added at 12:02 PM ---------- Previous post was at 11:40 AM ----------
What I meant was the phone is not completely dead. It's in a state of coma but not dead. There's a way, it could take time but this can always come back to life, but the OP will have to wait for device and storage specific files and the boarddiag/ tool to reflash image files manually.
Click to expand...
Click to collapse
I dont know the history of this phone. It came to me in this state. Now i know that i have to wait blankflash from Google. Thanks everybody for the answers.
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
robertputt said:
Qualcomm HS-USB QDLoader 9008. Having the same issue. Hope there's a fix soon. Heart broken.
Click to expand...
Click to collapse
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
seco2004 said:
I would like to know what did you do to cause the phone to brick? I got the phone a week ago and I'm thinking if I should root or not. I became scared after I bricked my Moto X 2014 and there's still no blankflash files for it :crying:
Click to expand...
Click to collapse
I did it myself, was trying to patchrom miui for the phone and must have used a wrong boot file or bootloader file, corrupted emmc.
first time i've ever hard bricked a phone and been flashing stuff for years, once you follow guides and use tested files you should be fine. found someone here in ireland to repair it for me. Only one huawei repair centre here
Recently found myself in the same predicament.
mzahiri said:
I'm having similar issues. For some reason I can't get passed the white Google screen. I can see the phone when I plug it in, wugfresh toolkit can even flash it back to stock. Yet, it won't go past the Google,in white, loading screen.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same thing with my girlfriends phone, have u manage to fix it ? Thanx
letmarebrmbarove said:
Same thing with my girlfriend phone, have manage to fix it ? Thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Check in here. No solution (yet, hopefully), but you're not alone with this issue.
count me in!
I flashed LineageOS (for the Moto G4 Plus) onto my Moto G4 Plus (XT1644) using TeamWin (TWRP) and clicked reboot. It didn't boot, and instead went into a blank screen and the LED flashed. I can still enter back into FastBoot and Recovery. Please help me (am a noob)
Thanks!
I have the same problem
DragonHartX07 said:
I have the same problem
Click to expand...
Click to collapse
Hello. If you have this problem, follow the directions @ https://forum.xda-developers.com/showpost.php?p=67031808&postcount=4 and if you have XT1644, download firmware at http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip.
Hope this helps, wish you the best of luck with your soft-bricked device. Need any other help, I am happy to research for you.
~wz68XDA
Same problem man. It's been about 2 weeks with me. If you look closely its only the backlight which goes off after the boot and the LCD and touch is still on.
Please do look for a solution as i have found no solution to this problem. I've tried reflashing different roms and the stock firmware too, it comes on for a few mins after I flash stock firmware and the blacklight goes off after some time and the issue repeats after every boot. @wz68XDA
_Rushaan_ said:
Same problem man. It's been about 2 weeks with me. If you look closely its only the backlight which goes off after the boot and the LCD and touch is still on.
Please do look for a solution as i have found no solution to this problem. I've tried reflashing different roms and the stock firmware too, it comes on for a few mins after I flash stock firmware and the blacklight goes off after some time and the issue repeats after every boot. @wz68XDA
Click to expand...
Click to collapse
Have you tried flashing the complete stock ROM for your device? Did you follow the instructions in the link in my previous post, completely resetting the whole device, or did you flash it with TWRP/CWM? This will reset your bootloader, recovery, everything back to stock.
Also, do you have a picture of your device when this problem occurs?
Thanks,
wz68XDA
wz68XDA said:
Have you tried flashing the complete stock ROM for your device? Did you follow the instructions in the link in my previous post, completely resetting the whole device, or did you flash it with TWRP/CWM? This will reset your bootloader, recovery, everything back to stock.
Also, do you have a picture of your device when this problem occurs?
Thanks,
wz68XDA
Click to expand...
Click to collapse
I have tried flashing the complete stock rom for my XT1643 with "fastboot oem lock" but I noticed it never locked the bootloader no matter how many times I flashed the stock rom.
The phone won't even go into the bootloader now and the LED Flashes for a while when connected to a USB cable and then nothing, it won't come up or get recognized by the computer.
wz68XDA said:
I flashed LineageOS (for the Moto G4 Plus) onto my Moto G4 Plus (XT1644) using TeamWin (TWRP) and clicked reboot. It didn't boot, and instead went into a blank screen and the LED flashed. I can still enter back into FastBoot and Recovery. Please help me (am a noob)
Thanks!
Click to expand...
Click to collapse
After you flash a ROM, make sure you wipe the Cache/Dalvik before you reboot. And, in case something goes wrong, ALWAYS MAKE A BACKUP!!
And, LOS takes about 10 minutes after a flash for the first boot.
_Rushaan_ said:
I have tried flashing the complete stock rom for my XT1643 with "fastboot oem lock" but I noticed it never locked the bootloader no matter how many times I flashed the stock rom.
The phone won't even go into the bootloader now and the LED Flashes for a while when connected to a USB cable and then nothing, it won't come up or get recognized by the computer.
Click to expand...
Click to collapse
The instructions in my post do not indicate that you need to relock the bootloader. There are separate instructions for that. Flashing the stock ROM will not relock your devices bootloader.
wz68XDA said:
The instructions in my post do not indicate that you need to relock the bootloader. There are separate instructions for that. Flashing the stock ROM will not relock your devices bootloader.
Click to expand...
Click to collapse
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
_Rushaan_ said:
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
Click to expand...
Click to collapse
What OS were you on before, btw - was it Nougat? Try holding the power button down for 2-3 minutes, see if a reset will cause it to boot.
Does your computer still see your device as a Qualcomm HSB BULK or USB 9008 or something similar? Perhaps try https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
If the above doesn't work, you may have to take your device to a service centre.
Also, as I understand, you need the latest firmwares to lock your device, which would be flashing the latest Nougat build.
As for your original backlight issue, it does appear to be a hardware issue if it's persisting across ROMs.
_Rushaan_ said:
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
Click to expand...
Click to collapse
So you are unable to get into fastboot? Then, unfortunately, I believe yout device is hard bricked.
echo92 said:
What OS were you on before, btw - was it Nougat? Try holding the power button down for 2-3 minutes, see if a reset will cause it to boot.
Does your computer still see your device as a Qualcomm HSB BULK or USB 9008 or something similar? Perhaps try https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
If the above doesn't work, you may have to take your device to a service centre.
Also, as I understand, you need the latest firmwares to lock your device, which would be flashing the latest Nougat build.
As for your original backlight issue, it does appear to be a hardware issue if it's persisting across ROMs.
Click to expand...
Click to collapse
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
wz68XDA said:
So you are unable to get into fastboot? Then, unfortunately, I believe yout device is hard bricked.
Click to expand...
Click to collapse
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
_Rushaan_ said:
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91987/p/1449,8620
You can send a support ticket to Motorola
and locking bootloader will NOT restore warranty
Good Luck,
wz68XDA
_Rushaan_ said:
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
Click to expand...
Click to collapse
Hmm, now it's powering on (and hopefully now charged), would you be willing to try re-flashing the latest firmware (https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369), see if you can get your system back up and running. Also, in that guide, there'll be instructions on how to re-lock your bootloader (and possibly mask the bootloader warning). It's still however up to the service centre as to whether they'll check your warranty (as on record it's been voided by issuing the unlock code) or whether they just look at the receipts. Good luck either way though!
Hi.
My Leeco le s3 x626, helio x20 is bricked with red light.
I Just work with win7, Windows 10, but don't work.
It is recognised like
Mtk usb and with mtk preloaded.
Flashtool, with download give back error or doesn't start.
I see guide for mediateck x6...
b1gb1ng said:
Hi.
My Leeco le s3 x626, helio x20 is bricked with red light.
I Just work with win7, Windows 10, but don't work.
It is recognised like
Mtk usb and with mtk preloaded.
Flashtool, with download give back error or doesn't start.
I see guide for mediateck x6...
Click to expand...
Click to collapse
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
bricked my Leeco le s3 x626
AxtExpos said:
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
Click to expand...
Click to collapse
Hi, i am new to this and i just bricked my Le s3 x626. please help me. the phone is just showing a red blinking light when i connect the usb cable to charger or pc. tahnks
I have the same problem...
leeco le x626 red light brick
AxtExpos said:
Hello, if you're still looking for a way to restore, then write to me in private messages, I'll help you with this deal)
Click to expand...
Click to collapse
Please what is the solution i need help mine also bricked while trying to root
Hi,
i have the same problem - stuck on red light.
Its recommended to use SP Flashtool to flash Stock.
Before, installing correct VCOM drivers. I've done that successfully.
But now...
I need the Stock ROM for this LeEco Le S3 X626 WITH the scatter file (MT6797_Android_scatter) that is needed for SP Flashtool.
None of the downloadable Stock ROMs i could get contain this scatter file. These Stock ROMs are all for devices that can still access fastboot.
This brick, stuck on red light can't access fastboot anymore..........
Any help? i need this ROM with the scatter file... please!
majo334 said:
Hi,
i have the same problem - stuck on red light.
Its recommended to use SP Flashtool to flash Stock.
Before, installing correct VCOM drivers. I've done that successfully.
But now...
I need the Stock ROM for this LeEco Le S3 X626 WITH the scatter file (MT6797_Android_scatter) that is needed for SP Flashtool.
None of the downloadable Stock ROMs i could get contain this scatter file. These Stock ROMs are all for devices that can still access fastboot.
This brick, stuck on red light can't access fastboot anymore..........
Any help? i need this ROM with the scatter file... please!
Click to expand...
Click to collapse
I have the files you need.
blueasteroid said:
I have the files you need.
Click to expand...
Click to collapse
Hey, i also recently bricked my phone, it has the red light problem and i have the flash tool installed, i am looking for a rom with the scatter files or the files themselves since i can't access fastboot, could you send them over?
Here you have some.
https://www.leakite.com/2017/09/download-letv-le-s3-x622-stock-firmware-flash-file.html
https://bbs.le.com//zt/eui/le_2.html
https://mega.nz/#F!MI9w3T6L
password: !YMutE59mUDbdOs9BoYY59Q
https://www.youtube.com/watch?v=xOKFI_eFq9o
blueasteroid said:
Here you have some.
https://www.leakite.com/2017/09/download-letv-le-s3-x622-stock-firmware-flash-file.html
https://bbs.le.com//zt/eui/le_2.html
https://mega.nz/#F!MI9w3T6L
password: !YMutE59mUDbdOs9BoYY59Q
https://www.youtube.com/watch?v=xOKFI_eFq9o
Click to expand...
Click to collapse
i am panicked
so so so panicked
i tried everything i could already but it is giving me errors and the red led persists, i followed https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937 but it doesn't work at all, just gives me a lot of errors that when i google nothing turns up, when i try to flash only the preloader alone it gets me somewhat through the process but gets stuck and there pops up the same error as always, i will try your files (as i was using the ones provided in the tutorial) tomorrow and report back, thanks for posting them so quickly.
marksklava said:
i am panicked
so so so panicked
i tried everything i could already but it is giving me errors and the red led persists, i followed https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937 but it doesn't work at all, just gives me a lot of errors that when i google nothing turns up, when i try to flash only the preloader alone it gets me somewhat through the process but gets stuck and there pops up the same error as always, i will try your files (as i was using the ones provided in the tutorial) tomorrow and report back, thanks for posting them so quickly.
Click to expand...
Click to collapse
Read the last post in that thread. 2 days ago I was like you. Read carefully.
i don't know at all, but it actually sounds like u didn't have the correct files before... i hope at least! things should work out with tutorials and instructions, i mean we're not that dumb right? but if we don't have the exact matching files..........
i will also try the same procedure with the new files thanks ALOT to blueasteroid, and write my results here.......
marksklava, are u actually on a L3 x626 aswell? cause most seem to operate with a x622
majo334 said:
i don't know at all, but it actually sounds like u didn't have the correct files before... i hope at least! things should work out with tutorials and instructions, i mean we're not that dumb right? but if we don't have the exact matching files..........
i will also try the same procedure with the new files thanks ALOT to blueasteroid, and write my results here.......
marksklava, are u actually on a L3 x626 aswell? cause most seem to operate with a x622
Click to expand...
Click to collapse
i am on an x626, it has a 21 mp camera and i bought it from china, sorry for not replying for 4 days.
---------- Post added at 02:14 PM ---------- Previous post was at 01:50 PM ----------
I get errors still, i believe it is a drivers issue but i don't really know how to fix it, i have tried uninstalling the drivers and installing the ones needed but they do not work at all. What do i do now? Am i out of options? What are the drivers supposed to look and how do i install them? i installed the ones that were provided in the inf file, those give me error 10 and my phone keeps disconnecting and connecting on a different COM port, although the driver seems to be installed, can someone help? If anyone is kind enough to screenshare with me i can do that via skype, discord and teamviewer, i also found a 5 year old camera here so i can catch any errors on video with my phone in the frame now which could be useful. Thanks for reading this, please help me any way you can, every bit helps.
marksklava said:
i am on an x626, it has a 21 mp camera and i bought it from china, sorry for not replying for 4 days.
Click to expand...
Click to collapse
Don't panic, i figured out this thing yesterday with my x626, it was successful and was not too hard in the end! don't worry much about the drivers, its completely normal that u lose connection all the time, it happens to all of us with bricked LeEco. The drivers won't keep still for the procedure, its normal...... I worked with the drivers in the Unbrick LeEco folder from blueasteroid. I installed all the stuff there was, and Windows said: Preloader VCOM 10 - it still switched but this is normal!
It is necessary to have the correct files, the correct paths in SPFlashtool and it only worked (for me) with DA_PL_HIGH and the pressing of buttons on the phone (Pow and Vol- holding it all the time). There was no BROM Error anymore and it all worked out.
All i can say don't give up, i have been at this point since beginning of December and now i finally got it unbricked! as much BROM errors u get, don't lose patience, keep on doing... u will finally find the right timing by happenstanc and it will work. The part after it is not that problematic then.
Check this thread, its very active at the moment and imo very very helpful: https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937/page5
Read the last pages...
leeco s3 x626 bricked
i also have the same problem with 4gb-32gb from the first day . Bricked after "fastboot reboot" command.
I tried to repair with flash_tools.exe but without success. I also tried various drivers.
Hello.
If anyone can help me... LeEco X625, blocked on red led, not charging, not connecting on PC, just red led when connect.
NOT seen in device manager.
jonyx87 said:
Hello.
If anyone can help me... LeEco X625, blocked on red led, not charging, not connecting on PC, just red led when connect.
NOT seen in device manager.
Click to expand...
Click to collapse
Same problem with mine. I once hard bricked mine, but whenever i connect to PC it gives sound, i was able to restore the phone @Long run. Few weeks after, i went to charge the phone and the phone went off, ever since then, not charging, no signs nor sounds when connected to PC... Took it to Engineers and all they say is dat i need to change the board... I'm so sad because i used all the money in my account to get the phone. The phone is still enjoying inside my wardrobe
Hey guys,
My XZ Premium updated to 9.0. Since then I started to have many problems.
Yesterday a messagage appeared: Your phone is corrupt, it may not work properly. It can't be trusted.
Hours later it frozed and turned off. Now it's not responding to anything. The led isn't working and the device manager shows it as SOMC Flash Device.
The comands pressing volume buttons while I connect the USB cable are not working either.
Can I save it? I bought it three months ago :crying:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Styler911 said:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Click to expand...
Click to collapse
I alredy tried. It's not working. I bought in a different country that I live now. I can't use the local warranty.
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Probably water in usb port then charging caused it
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
mad0701 said:
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Click to expand...
Click to collapse
I don't have the TWRP installed. The device is not responing via PC.:crying:
stipi69 said:
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
Click to expand...
Click to collapse
The device is not responding to any command that I try...
amakuramio said:
Probably water in usb port then charging caused it
Click to expand...
Click to collapse
It never get wet, and when it does I make sure that no water remains....
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
mad0701 said:
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
Click to expand...
Click to collapse
It only appears as SOMC Flash Device. The ADB or Flash Tools can't get access to the internal memory. I know there's a way to access the internal memory. Just don't know which one yet.
It looks like a coincidence. Hardware not be working may be the real issue.
If you find a knowledgeable repair shop, they can clear your flash and install the original Sony shipped OS for a little money. Most of the time this is done from the USB after a factory reset explained by others here. However, if the USB port is not working then accessing the flash needs opening the unit which will cost you.
And then if the hardware has failed, none of this would help anyway.
What's happen, if you press for 6 Sec or longer Power and Volume up together?