Related
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!
bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.
Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.