Hi everyone, I'm new here. I have a problem with my LG L3 E405. Last night, I dropped my phone from the second floor of my house. When I reinserted the battery and restarted the phone, a error screen came up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
....Then I could not use my phone anymore. I searched on forum for my problem. Luckily, I found a post about "UNBRICK YOUR LG OPTIMUS L3 E405". I followed the instructions and my phone worked after that. However, when I restart the phone, the error screen
comes up again. Please help............:crying::crying::crying:
Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?
need4steer said:
Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?
Click to expand...
Click to collapse
Yes, my phone worked normally until I restarted it. Only when I restart the phone, the srceen message that I mentioned above will appear. . I look forward to your help.
I'll be glad if I'll manage to help you out.
Please explain in detail the procedure of the unbricking, and elaborate in detail what happened to your phone in the appropriate steps of it.
Here is hoanganspk comment:
hoanganspk said:
Sorry for border you. Because I'm a new member in this forum, I cannot post threat with outside link.
I carefully followed this instruction to unbrick my phone.
http://krazeefly.blogspot.com/2012/09/how-to-unbrick-your-android-phone.html
a
Then, my phone worked well until I restarted. Hope to hear your rely
Click to expand...
Click to collapse
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.
need4steer said:
Here is hoanganspk comment:
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.
Click to expand...
Click to collapse
Hey guy. T tried to unbrick my phone with your instruction again and again then my phone have worked. Million thanks for your help :good::good::good:
Thanks a lot for your confirmation.
BTW, you did it the exact same way again and again, and after a few times of it, it just worked?
If you changed something, please explain so others, including me, will know for the sake of solving this kind of a problem.
Related
Hey Guys,
I am trying to return a Galaxy S4 Duos GT-I9502 back to stock, for someone who attempted to root the device, which failed. I am however experiencing some difficulty doing so, and would appreciate some help, if anyone has any suggestions.
This is the screen on the device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I am pretty confident that I have the correct Samsung drivers installed, and I have tried completely closing all of the Samsung Kies processes on the computer. I have even tried using a different computer, and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUBMG2_I9502CHUBMG2_CHU
I9502ZNUAME3_I9502CHUAME3_CHU
I have also tried the 'Firmware upgrade and initialization' option in Samsung Kies, though I keep on getting this error message, before it closes (I do not know what it says, Google translate doesn't give a good translation).
"Binary files are not registered U.S. Congress gyeongmu mouth mid-sprocket
Bow can proceed
Please check the binary file registration myeobu"
Does anyone have any suggestion / idea of what is going wrong? Any help would be highly appreciated!
Never mind, I was able to resolve the issue by re-flashing CWM recovery!
same problem
i have exactly same problem with I9502ZNUBMH4 version , does anyone know how to flash this device because i tried 100 time with different versions of odin , and every time i failed repaird it with cwm .
oh and the device won`t do a full wipe , every time i full wiped it my files didn`t deleted ?!
Samsung S4 GT-I9502 root / flash failed - HELP
Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (see more Information below) and I had the following error message and no wifi.
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna
Philz 6.00.2
I have a similar problem.
I tried to install philz _touch_6.00.2-i9505.tar, by uisng Odin 3.09
Everything went OK. I got PASS! and my Samsung S4 i9505 rebooted into the stock ROM
However I cannot enter Philz. I tried to keep pressed volume Up + Home + Power but the phone goes immediately into the main Samsung screen. I have tried many combinations...the only working combination is:
volume Down + Home + Power > which leads to download mode (for Odin)
Thank you for your suggestions!
SA
Same problem, how did you fix it?
I have the same issue, how did you fix it? It's been a day that I've been trying to fix it. I've got the Exynos version I9500
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!
Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app
I like wugfresh's Nexus Root Toolkit.
I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).
I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.
So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.
Jack_Bauer_AUS said:
So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.
Click to expand...
Click to collapse
I haven't viewed the images, but try this
-Goto download mode.
-Open KDZ updater
-Select the kdz, select 3QCT (something like that) and DIAG (forgot the options, its been long since I flashed a stock ROM)
-Flash the kdz
-KDZ updater will crash, it is quite normal
-Do a hard reset (remove battery, put it back, vol - + power + home, when it vibrates remove power and hold on vol - and home for another 5 sec)
-Hopefully, it should boot..
Sent from my Moto G XT1033 using Tapatalk
Make sure you have drivers installed BEFORE conecting the phone.
Also the only flasher that worked for me is this: http://forum.xda-developers.com/showthread.php?t=2409308
Hey guys, Ive just successfully rooted my oppo f1s with the latest kingroot last night :laugh: but early on today i cant open my phone :crying: It keeps on rebooting, it only shows the logo then reboots again and again and again, i cant even go to recovery mode, it only stops when battery is drained completely or if its rebooting for too long, i cant remove the battery because it has a non removable battery and i cant shut it down cause it wont :crying::crying::crying::crying: please guys help me, i love that phone so much. I DONT KNOW WHAT IS THE PROBLEM, PLEASE REPLY AND PLS PLS. IF ONe OF YOU KNOWS THE SOLUTION PLS REPLY IMMEDIATELY I WILL APPRECIATE IT SO MUCH (sorry for bad english) PLEASE HELP ME! i just bought it last monday:crying: is it the root the problem or the battery is just wrecked up, this is the only thing that could turn my frown upside down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also same problem with oppo f1f. ?
sandiprao said:
I have also same problem with oppo f1f.
Click to expand...
Click to collapse
When did it started? did you root your phone too?
Yes..I did via kingroot and then try to flash twrp via flashfy apk..
sandiprao said:
Yes..I did via kingroot and then try to flash twrp via flashfy apk..
Click to expand...
Click to collapse
does your phone rebootswhenyou are charging? . hope well get a solution in this problem
Are you tried fastboot.. because my device is not detect on pc
I had the same problem after I installed xposed and it's framework the phone rebooted and kept rebooting. I turned it off by pressing power button with volume up. Then booted into recovery by pressing power and volume down then I deleted all the data from one option not as usual recoverise when you delete dalvic and cache then rebooted but the problem was still existed so I deleted data again and the device booted successfully
sandiprao said:
Are you tried fastboot.. because my device is not detect on pc
Click to expand...
Click to collapse
i dont know what is fastboot and i definitely didnt tried it
It is another way to flash ROMs...
yaserch1 said:
I had the same problem after I installed xposed and it's framework the phone rebooted and kept rebooting. I turned it off by pressing power button with volume up. Then booted into recovery by pressing power and volume down then I deleted all the data from one option not as usual recoverise when you delete dalvic and cache then rebooted but the problem was still existed so I deleted data again and the device booted successfully
Click to expand...
Click to collapse
IT WONT LET ME go to recovery mode,. when i tried going to recovery mode, it only shows the oppo logo with a "recovery mode" name located beyond the oppo logo, then reboots again and again. i remember flashing a oppo f1 twrp rom to my phone using the "Official TWRP App" from google play,
link: https://play.google.com/store/apps/details?id=me.twrp.twrpapp
but i dont know if it is successfully flashed, because i does not show any signs such as "TWRP IS SUCCESSFULLY FLASHED, BLAH BLAH BLAH", im so confused now if the flashed were neither successful or not, it only shows nothing when i pressed flash to recovery, then i uninstalled it quickly. That is my conclusion, what do you think
here is the link of the twrp rom: https://twrp.me/devices/oppof1.html
IF YOU KNOW WHAT TO DO, OR OU KNOW YHOW TO REPAIR THIS, PLS EMAIL ME, [email protected] .:fingers-crossed::fingers-crossed:
I WILL APPRECIATE IT SO MUCH, HAPPY HOLIDAYS
sandiprao said:
It is another way to flash ROMs...
Click to expand...
Click to collapse
HOW TO ACCESS IT?
Search on Google...if you don't know then don't mess with ur phone
YES
sandiprao said:
Search on Google...if you don't know then don't mess with ur phone
Click to expand...
Click to collapse
YA'RIGHT MAN, i shouldnt mess up with my phone. i was just being curious, bcoz i know that you know that there are many **** apps in google play, ,hope i'll find a solution:highfive:
Gud luck
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?