Zte Axon 7 (A2017G) System ui stopped and continuously self reset - ZTE Axon 7 Questions & Answers

Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS

CrazySE said:
Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS
Click to expand...
Click to collapse
Boot into recovery and delete dalvik cache, cache and data

CrazySE said:
Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS
Click to expand...
Click to collapse
My phone resetted itself about 10 -15 times a day a while ago. Especially when connected to the charger. Some apps stopped working and needed reinstalled. That all happened after I took the pone out skiing with me. I assume it was caused by the phone getting moist in my pocket. After a while the reboots stopped and now its working fine again.
Did your phone get moist or wet? Check the USB port for ingress of dust or moisture.
Clearing Cache is a good idea. Also check how much free memory space you got. If your memory is full to the brim you might experience problems with dead memory cells. Have at least 10GB free.
UPDATE:
When replacing the battery which served for 3 years, I whitnessed corrosion on the USB circuit board. Moisture must have got in thru the unsealed USB port. That corrosion attacked the components around the board aswell as the ribbon cable and connector. After cleaning up with isoprop alcohol (and putting in the new battery) the phone behaves like new! It definately runs smoother and snappier, has no more hickups and itle discharge is back way down. Im sure the reboots on my phone were caused by moisture ingress that confused the bottom PCB.

Related

[CLOSED] Help! Nexus 10 stuck on Google logo after Rooting attempt

Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance
Have you tried using a different usb port on the PC, and rebooting the PC?
bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.
When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!
Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.
bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out

Stuck SM-N900A - No free space

Ok this phone was running out of space, so my friend attempted to delete one of her exchange email accounts from work to free some space and then the phone went crazy crashing every second. After pulling the battery out, it boots and gets stuck in the ATT logo.
I have searched this forum and google endlessly and the most reasonable solution i found was trying to access the storage using ADB.
so this is what happens:
1. Windows does not detect any hardware being plugged in the computer if the phone is in recovery mode like in the attached pictures.
2. Windows DOES detect an MTP device when the phone is stuck in the ATT logo, and plugged to the computer, but the driver fails to install and i get the yellow exclamation mark on the device manager under portable devices.
3. I waited and clicked on scan for hardware changes but still get the "Device cannot start (code 10)" in windows.
4. I wiped the cache partition to no effect.
5. Everything is stored on the internal memory, she never had a micro SD card installed.
All i know this is a stock phone. My friend got it with ATT and no one ever played with it (rooting and stuff). I have no clue about what software version was installed other than the numbers you see in the attached pictures.
I know "wipe data/factory reset" will get rid of the problems, but she needs to recover pictures, and work related SMSs that she never backed up. Losing this data will set her back very badly with customers and more than a year of work.
Any tips are much appreciated and i hope there is light at the end of the tunnel.
Thanks a lot.

LG L5 E610 - Strange issue

Hello guys.
I have an LG L5 (E610) that is having a very strange behavior.
It started by throwing a lot of ANR with different applications (Google Play Store, Play Services, Facebook, and others).
So, seeing this, I decided to do a factory reset. After reboot, what is my surprise that I see everything as I had before. All the applications, all the data, everything.
With this, I tried almost everything at the moment. And by saying that, I mean:
- Tried to follow the key combination for the recovery, it goes to recovery, I see the Android and some progress bar moving, but after the reboot, the system remains with no change;
- When on the system, I uninstall applications, they seem to be uninstalled, but after a reboot all the applications are back.
- Tried to root the phone with more than one process, no success. I cannot install any application. Not via play store, not via adb install, there is no way;
- Tried to flash a recovery img, to try to clean cache partition from there, no luck. From Fastboot it says everything went well, but when I reboot, everything is the same;
- In fastboot, I tried to erase cache and userdate partitions, no luck. When I try, i have a message saying "FAILED (status read failed (Too many links))". This happens with all the partitions. I even tried to erase the system partition, and I have the same response. Strange thing is that after this error, the phone reboots and goes directly to the system;
- Tried with KDZ images and tools to install different versions, I receive errors during the deployment and at the end the phone reboots. Again, the same system is installed as before. No changes.
As of now, I was trying to understand if there is any problem with the internal flash system. Maybe it is corrupted and is causing all these issues.
The thing is, as the phone is not rooted, I cannot launch a e2fsck to the maybe faulty mmcblk0pXX
The phone has a stock ROM based on Android 4.0.3 (build IML74K / LG-E610-V10e-JUN-30-2012)
I am out of ideas, I've looked around here at XDA, Google and I have no other ideas to try.
Does anyone have another suggestion?
Is there something else I can do to try to make the phone live again?
Any help someone can provide will be very much appreciated..
Now this is what I call a coincidence.
About 2 years ago, a friend of mine asked me for help with her E610. Almost all actions were giving us ANRs. Whatever you do, i.e. unsinstall, install, change, delete... after reboot/reset were all there, even notifications! Tried KDZ updater, and, while the update was OK without signs of errors or so, after reboot - nothing, everything was like before. After trying to find a solutions by hundreds of ways, with adb and fastboot commands (all partitions&folders were locked, no read, no write, and you can't see any file, tried root to no avail), L5 got bricked. She already got a new phone and this LG was laying there without any use.
Three days ago I decided to try again, with no hope tbh No screen, no vibration, nothing, apparently dead. But, I could install Qualcomm drivers and my Windows can see it in download mode. I think that the only way is to flash the phone with LGFlashTool and using COM port. I already extracted *.dz from *.kdz but I need the dll for FlashTool. Found 2 or 3 webs with this dll, but you need a 100 bucks subscription :crying: If anyone can upload that dll I'd be very happy to try to flash this phone I'm really big n00b in this, just a plain phone user, nothing more, so don't blame me if I said something wrong
Many thanks in advance.
same problem
Hello! Same problem...
My L5 is making me crazy... It has CyanogenMod 10 nighlty. A friend of mine was using it and he tried to install the GAPPS after he did a factory reset. I have no idea what guide he used but it got soft bricked... It's constantly showing a "stopped working" message and after a while reboots by itself.
I tried to do a factory reset but it always returns to the same point, same apps installed, everything like the reset never happened. I even used CWM to reset it and it allways goes back to the same recovery point.
After a while I decided to flash a stock room but here's the problem: I can't get into emergency mode.
After reading ALL post about it I found that there's at least three ways of entering EM, (1) down VOL and plug in usb cable without battery; (2) down+up VOL and plug in usb; (3) down+up VOL + power botton.
Conclusions:
(1) - gives me a screen full of code like a command line
(2) - White screen
(3) - White screen
I've read ALL the unbrinking post on the internet, including xda, and none of them helped.
The KDZ Updater never recognizes the phone. I installed all the drivers but everytime I plug in the phone it installes the same LGE MTP drive...
Can anyone help, please?!
How to enter Emergency mode? How to flash another rom?

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Mi A1 stuck at MI logo page

Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
What error show miflash when you try to flash in edl mode?
balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way
ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply
kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!
Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience
Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.

Categories

Resources