YESSSSSS A NEW FP THREAT AGAIN YOUR FP IS NOT..... I REPEAT NOT DEAD. I KNEW IT... I'm almost sure it's the bootloader. Notice the attached picture s
Why. Mine died also after flashing about a month ago. Shortly after my new X2 arrived.
It does not die couse of heating issues because I heated my X2 to disassemble it. And that heating is way mutch hotter than charging does.
What I did.
Rooted. Flashed TRWP 3.0.2.0 (not higher) flashed pure nexus on it. And FP got bricked. On top of pure nexus I flashed 26s Rom. This bricks the X2 cause it hangs in bootloop of course. Now you're only able to use the unbrick method. When you do that. Flash the given QFill developers Rom. When you flashed that one and booted up first go to settings/storage and do a factory whipe tikking erase internal storage also. Perform the factory reset. Reboot and set-up fast again. Activate developers mode again. And again reflash by using fastboot mode TRWP so you get the TRWP recovery mode. After that flash Pure nexus again. All should be fine now. Recalibrate your fp several times And it works
As you can see under leeco extras. The font does not match up my system font. This type of font (Hindy I guess) is also seen under under security settings. FingerPrint callibration...
I'm almost positive that it's the bootloader. Not 100% sure.
Succes
That's exactly what I did last Wednesday. I flashed the developers ROM, then flashed TWRP without setting anything up, and flashed another ROM. My fp sensor remained dead, as it is right now. I'm glad to hear that you managed to recover it using this method, but it didn't work for many of us, me included.
Anyway, thanks for sharing. This may work for a lot of people, and everyone with a dead fingerprint sensor should try it. It's not risk free, but it's not so hard to do, either.
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Moon75 said:
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Click to expand...
Click to collapse
Well, if you don't care about getting a replacement or a refund, why not try to recover the sensor yourself, by every means possible? You're also free to leave as it is. I'm now using an app that unlocks the screen using the proximity sensor, along with face recognition unlock (thanks to Small EUI ROM) so I don't care too much about the dead fp sensor now, but I have not completely given up on it. If someone finds an easy and reliable way to fix it, I may try it.
Hi, for sure if there is easy fix I will fix it but there is none and many people have dead FP on this phone because they can't fix it. For Nougat rom you can wake it up with Volume button but stock rom you can't. There is some app you can install and wake up the phone by double tab or cover sensor as you mentioned. If FP working sure it's better but don't have it not big deal.
Moon75 said:
Mine was dead after one week, why so much hassle? it should work out of the box or stay dead as it is. It's the hardware problem on Le max 2.
I got LE Pro 3 too, it work 100% from day one until now, no issue.
Click to expand...
Click to collapse
Mine worked perfectly untill I flashed let max 2 day after arrival. It has something to do with the bootloader. Because I got the 26s version bootloader in it and now it works while using pure nexus droid
jman0 said:
That's exactly what I did last Wednesday. I flashed the developers ROM, then flashed TWRP without setting anything up, and flashed another ROM. My fp sensor remained dead, as it is right now. I'm glad to hear that you managed to recover it using this method, but it didn't work for many of us, me included.
Anyway, thanks for sharing. This may work for a lot of people, and everyone with a dead fingerprint sensor should try it. It's not risk free, but it's not so hard to do, either.
Click to expand...
Click to collapse
And you did use the 26s Rom ? Because that fixes it.
chetermaat said:
Mine worked perfectly untill I flashed let max 2 day after arrival. It has something to do with the bootloader. Because I got the 26s version bootloader in it and now it works while using pure nexus droid
Click to expand...
Click to collapse
You mean those never flash any firmware, never have their fingerprint dead?
So if I am still stock, I should not flash anything to preserve fingerprint functionally?
kkcheong said:
You mean those never flash any firmware, never have their fingerprint dead?
So if I am still stock, I should not flash anything to preserve fingerprint functionally?
Click to expand...
Click to collapse
Yes. Or flash the 26s version. It's official dev for our max 2. After flashing the 26s you may root. Install TRWP 3.0.2.0 not higher. And when you installed TRWP you may flash pure nexus on your le max 2. The fact losing fp functionality must have something to do with bootloader and or combined with TRWP.
chetermaat said:
Yes. Or flash the 26s version. It's official dev for our max 2. After flashing the 26s you may root. Install TRWP 3.0.2.0 not higher. And when you installed TRWP you may flash pure nexus on your le max 2. The fact losing fp functionality must have something to do with bootloader and or combined with TRWP.
Click to expand...
Click to collapse
Not true at all first you can flash anything and FP still work. Before I bough X820 and come back home, after 2 hours FP stop working while on stock rom that came with the phone. So I returned it the next day and get the Le Pro 3 in stead. It's hardware fault.
Why dont just update the modem for 23s chiinese version, wipe cache, dalvik, data (not internal storage) and system then flash a new rom and test if the FP back to work? its a simple test way.
On mine i have it for 3 months now, on first day i have updated the modem for 23s version, and the FP never stops working.
i bought mine from china , I got the same issue after 2 weeks , it happened as a result of using the FP while charging , I took it to the service center and there where many people with the same issue with FP and the same reason as I had , they had to replace the sensor with a new one.
they told it might be because of the heating effect of charging with a static overload on the sensor .
try cleaning with isopropanol or throw away
Gesendet von meinem LEX820 mit Tapatalk
Moon75 said:
Not true at all first you can flash anything and FP still work. Before I bough X820 and come back home, after 2 hours FP stop working while on stock rom that came with the phone. So I returned it the next day and get the Le Pro 3 in stead. It's hardware fault.
Click to expand...
Click to collapse
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
chetermaat said:
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
Click to expand...
Click to collapse
You mean like now if I flash any 26S stock rom it might be fix?
Is there a guide for what you mentioned here? thanks
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
chetermaat said:
Like I said. If you first flash the 26S version FP wil work
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Reflash TRWP 3.0.2.0
Reflash your taste of Droid
Reroot with superuser via TRWP
You should still have FP.
Most important is the 26S version at first
Click to expand...
Click to collapse
Can you point me to the 26s firmware file you used for this?
Or the thread where you found it?
Looks like I'm blind
Moon75 said:
You mean like now if I flash any 26S stock rom it might be fix?
Is there a guide for what you mentioned here? thanks
Then restock with QFill and do the proper fact reset incl erase internal storage to get correct partition table.
Click to expand...
Click to collapse
JamBax said:
Can you point me to the 26s firmware file you used for this?
Or the thread where you found it?
Looks like I'm blind
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BxPg20xeuX4JekZEcjNKWEpCcEk/view
chetermaat said:
https://drive.google.com/file/d/0BxPg20xeuX4JekZEcjNKWEpCcEk/view
Click to expand...
Click to collapse
I asked beacuse it did not work with aurel's version, so I wanted to make sure I use the right version.
Another question, is anything known about differnt versions of the fingerprint sensors, different manufacturer?
Is it the same fingerprint as in other devices X52x or X62x??
Is there a way to read out if the system recognizes FP sensor?
How long should it take to calibrate FP? It is written 2-3 minutes, but when the sensor is dead, it only takes about 20 seconds??
I did this and after months of trying to get my finger print reader to work trying all the "fixes" people have posted, and finally mine works again. I am and was using the RR Rom 7/13/17 & Open Gapps, I didn't follow your step exactly but my finger print reader works perfectly and quickly now.
What I did:
Flashed Modem 26s : https://yadi.sk/d/woKdrlRrv8yhr/Китай (modem_cn_26s_v00033.zip)
Flashed TWRP 3.0.2-1 : https://dl.twrp.me/x2/twrp-3.0.2-0-x2.img.html
( Fastboot flash recovery TWRP-3.0.2-x2.img )
Flashed RR 7/13/17 over my current flash no wipe (besides dalvik/cahce)
waited for it to boot, went into settings and boom it worked first try no issues... FINALLY A WORKING FP Sensor again, Thanks I owe you one. The flashing order seems to be critical as i have done similar to this with no success....
kintera said:
I did this and after months of trying to get my finger print reader to work trying all the "fixes" people have posted, and finally mine works again. I am using the RR Rom 7/13/17 & Open Gapps, I didn't follow your step exactly but my finger print reader works perfectly and quickly now.
What I did:
Flashed Modem 26s
Flashed TWRP 3.0.2-1 : https://dl.twrp.me/x2/twrp-3.0.2-0-x2.img.html
( Fastboot flash recovery TWRP-3.0.2-x2.img )
Flashed RR 7/13/17 over my current flash no wipe (besides dalvik/cahce)
waited for it to boot, went into settigns and boom it worked first try no issues... FINALLY A WORKING FP Sensor again, Thanks I owe you one. The flashing order seems to be critical as i have done similar to this with no success....
Click to expand...
Click to collapse
Which ROM were you using before flashing 26s modem?
Related
This is my first post on XDA and i am in desperate need of help. I own a Asus Zenfone 6. Recently i tried unlocking bootloader and installing TWRP recovery so that i can flash a custom ROM. It went horribly wrong and i bricked my device. I managed to unbrick it and revert to Stock ROM which i also upgraded to LOLIPOP using adb sideload. I also managed to root it and have super user access. The problem is that i cannot install a TWRP or any other recovery. When i try to install a custom recovery i get and error " cannot install unsigned image on secure device" which probably suggests that the boot loader is locked. I ran the commands to unlock the boot loader and they ran successfully but i am not sure if the bootloader is locked or unlocked.
I tried running fastboot oem devices but i get an error " Unknown Oem command".
It was after hours of troubleshooting that i decided that i am OK with stock LOLIPOP rom as long as i have a rooted device. It was after sometime that i noticed that the camera wasn't working. Also the flashlight wasn't working. I uninstalled the updates and flashlight was working. However the camera just gives me a black screen for some time after which it quits with an error message " Camera is used by another application. Please reboot your device and try again". I uninstalled the updates for Camera and reverted to a previous version by also removing the camera application using super user access. However for an older version i get an error " Camera not found". I have also tried installing other camera applications but none seem to work even after making them a part of system. Currently flashlight works but only under an older version , as soon as i update it stops working. I decided to lock the boot loader again as it was just not worth it. However after running the commands and locking the bootloader i still cannot get the camera to work. I tried in safe mode and the camera won't work there either.
When i go to recovery i just have four options, there is no install from internal storage or SD card which suggests i am on stock recovery.
Currently i just want my camera to work. I am OK with the stock ROM and recovery as long as i have a rooted device. I have spent hours researching and nothing seems to work. I am in desperate need of help. Some of the friends suggested to try my luck here. I would be indebted as i dont want to purchase another device just because i screwed my camera. Also when i was under kitkat i ran the SIMI test and was getting an error 1667 and 1668 for both cameras. The test is failing under LOLIPOP as well. I dont think its a hardware issue or maybe i am wrong. Any help would be appreciated.
Thanks.
Not even a single reply. DISAPPOINTED!
You need to Lock Bootloader then reflash the rom (wipe all) to fix it. Custom ROMs sometimes cause camera not working cuz there are some devices that have different camera.... Next time, just make sure you Lock Bootloader => Flash Stock recovery => Wipe => Flash Stock ROM
qureshiburhan92 said:
Not even a single reply. DISAPPOINTED!
Click to expand...
Click to collapse
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one (https://zenfones.gajetzki.com/) say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
LGenius3 said:
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
Click to expand...
Click to collapse
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
may zenfone 6 with stock rom 3.24.40.87 can't be unlock,pleas help me
qureshiburhan said:
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
Click to expand...
Click to collapse
Sorry for the late reply, but I'll try to help as much as I can. First things first, I know there are two different models of the Zenfone 6, the A600CG and the A601CG, but apparently this shouldn't make a difference, but it could have in this case, after all they must have different names for a reason. Also, the support for the Zenfone 6 is pretty terrible in terms of custom roms and the such, so you may even be better off with the stock experience, just root it and you'll have all the functionality you could ever dream of.
If you're still keen for the custom roms and stuff maybe check out this thread:
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Other than that, I guess Google is your friend, but so are we!
I haven't been able to hold onto my Zenfone 6, as it was a friends, so I no longer have it and never got the opportunity to have some fun with it, so I'm just going off my own experience with my HTC One M9, which is probably vastly different, but I suppose the process isn't too different. Nonetheless, I hope all goes well!
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.
crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!
rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since
jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference
Edited. We are all just trying to help others. Lets keep it that way.
so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips
jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob
Okay. This is an odd one for me. bought another axon 7 bc it was cheap. swapped in my old board and battery because it was charging and running really hot. (ive owned 4 axon 7 now, it was the hottest ever) so surgery went fine. upon booting, the touch screen, does not respond to touch. while within recovery (twrp by nfound) touchscreen works perfectly. i really dont know what to do to it. i have tried to restore all sorts of backups, but every one has the same issue. ive tried not including EFS and tried it included. if the screen wasnt working in TWRP, id question my hardware labor, but im kind of stumped. i keep trying to download B19 nougat edl, but the download keeps failing. (thanks tmobile and my in-laws wifi). my question is coming from a functional custom recovery is there a way to flash or restore stock recovery? i know i can EDL eventually, i was just wondering if there is an easier way?
EDL fails to complete using any of the EDL files i have tried so far using
Secondary question, is there any EDL thats works as a necessary starting point? i.e.- on moto devices, many firmwares were not backward flashable. ultimately, i just want to know if i can EDL Marshmallow or if that is even possible. i have attempted B15, B19, and B32 with no success.
kitcostantino said:
Okay. This is an odd one for me. bought another axon 7 bc it was cheap. swapped in my old board and battery because it was charging and running really hot. (ive owned 4 axon 7 now, it was the hottest ever) so surgery went fine. upon booting, the touch screen, does not respond to touch. while within recovery (twrp by nfound) touchscreen works perfectly. i really dont know what to do to it. i have tried to restore all sorts of backups, but every one has the same issue. ive tried not including EFS and tried it included. if the screen wasnt working in TWRP, id question my hardware labor, but im kind of stumped. i keep trying to download B19 nougat edl, but the download keeps failing. (thanks tmobile and my in-laws wifi). my question is coming from a functional custom recovery is there a way to flash or restore stock recovery? i know i can EDL eventually, i was just wondering if there is an easier way?
EDL fails to complete using any of the EDL files i have tried so far using
Secondary question, is there any EDL thats works as a necessary starting point? i.e.- on moto devices, many firmwares were not backward flashable. ultimately, i just want to know if i can EDL Marshmallow or if that is even possible. i have attempted B15, B19, and B32 with no success.
Click to expand...
Click to collapse
you should be able to EDL any update without problems. Use EDL Tool, that one works even better than miflash.
What a mess. ? Maybe an EDL flash on the newer board would have fixed the thermal problems...
Try an IDM for downloading stuff. If the download fails you can simply resume it no problem. IDMs on Windows are crap, but this one works perfectly (on Android, that is):
https://play.google.com/store/apps/details?id=idm.internet.download.manager
Choose an username... said:
you should be able to EDL any update without problems. Use EDL Tool, that one works even better than miflash.
What a mess. Maybe an EDL flash on the newer board would have fixed the thermal problems...
Try an IDM for downloading stuff. If the download fails you can simply resume it no problem. IDMs on Windows are crap, but this one works perfectly (on Android, that is):
https://play.google.com/store/apps/details?id=idm.internet.download.manager
Click to expand...
Click to collapse
Pretty much par for the course with me and Axon 7's. Simple op impossible. lol.
I just flashed b32 which Miflash says flashed successfully, yet as was the case after b15N and b2xN the splash screen pops up, the image of stock recovery flashes just for a sec, several red flashes, and power off.
It takes a try or two to get EDL mode after that. i guess tomorrow (left it at work on my desk) the phones original board is going back in. lol.
So i swapped back to the board that came in the phone and touch works perfectly. that board was missing the pink paste on the back of the SOC. after having it run 115-125° F, i decided to swap the battery with my good one and add the pink gummy stuff too. on stock it got so hot it would freeze and shut down, and now bl unlocked on O RR, i have to undervolt -25 global to keep it stable. i did finally manage to get full EDLs to work, but the SOC just seems faulty or tweaked. i imagine it is just one that runs hotter. also, in swapping the screen back, i have concluded that the other board i had must have a connector issue for the touch display. i may try to resinstall it later. kinda tired of screwing with it for now. any input is appreciated. thanks
EDit:
hot board made cool by flashing back as far as i could go, but now it has no IMEI. lol.
UPDATE: finally figured out the b15 full edl i was using was what was killing the screen. flashed back to b20 and screen worked fine. now both phones do not have IMEIs, though. win some, lose some. lol
Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!
I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.
Untouched? Is there anything on here like that?
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken
djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.
Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!
Hello
I decided to start from scratch and installed latest stock rom with mi flash. The tool reported successful but I ended up in a boot loop. Somehow it failed when the screen came up with 'data encryption....'. I flashed it again ad the phone only vibrated when power on. I hat to do the restore point method to gain EDL mode. I flashed an older firmware. Now the screen stays black. I'm able to boot into fastboot, unlock the bootloader and install TWRP. But the screen is just blank/black.
I have a feeling it haves something to do with emmc_appsboot.mbn or boot.emmc.win
When I flash boot.emmc.win with fastboot on Slot A (I tried both slots) at least the LED turns on when the device is plugged on a USB cable. But nothing more........
I still have my backups, created by TWRP. I don't know this is in some way helpful.
I find the tool TWRP Backup Tool. It seems I could restore a TWRP backup from there. But which file should I use? My backup is a folder. There isn't any .zip or .img file.
Some ideas?
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
laugeek57 said:
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
Click to expand...
Click to collapse
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
XtraWater said:
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
Click to expand...
Click to collapse
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
laugeek57 said:
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
Click to expand...
Click to collapse
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
XtraWater said:
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
Click to expand...
Click to collapse
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
laugeek57 said:
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
Click to expand...
Click to collapse
How did you flash the OS? Because My screen is dark, so I can't see anything.
XtraWater said:
How did you flash the OS? Because My screen is dark, so I can't see anything.
Click to expand...
Click to collapse
If dark screen flash december modem but becarrefull i lost imei after
laugeek57 said:
If dark screen flash december modem but becarrefull i lost imei after
Click to expand...
Click to collapse
Thank you. I installed december rom. But screen is still black. Probably hardware defect.
XtraWater said:
Yes, the bootloader is unlocked. I'm able to enter into fastboot. From there I can flash TWRP and boot into recovery. I installed even Magisk. It seems everything to work, but the screen. I was very careful when I did the testpoint method.
Here's the result of the fastboot oem device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.047s]
Finished. Total time: 0.047s
Do you think there is still a chance to fix the device? I thought about to send the device back where I bought it. The device isn't even 2 week old. But I doubt the dealer will grant me warranty since I opened the device.
Edit: THe cellphone starts normally me thinks. If I want to boot into bootloader I have to press power and vol -
I run the TOOL ALL IN ONE which shows me immediately when a Fastboot device is detected.
Click to expand...
Click to collapse
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
samuro625 said:
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
Click to expand...
Click to collapse
After I was in bootloop (with screen) I wasn't able to unlock bootloader. So I used the Mi Flash tool. I tried different (at least 6 or 8 )versions from this site: https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
After flashing the roms, the phone only vibrated when tried to boot. It repeatedly vibrated when connected to the USB cable and charger.
Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ )
That's the rom which is currently on my phone.
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Actually, in all those versions GAPPS or Magisk isn't included.
Just to mention; my Mi A1 is a MDG2. Not sure if that matters.
Without the screen, I'm kinda limited regarding to TWRP.
EDIT: I never did a backup by ADB. But I did several with TWRP. I wanted to recover one of them. But methinks, that's not possible with the TOOL ALL IN ONE.
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
XtraWater said:
(...)I wasn't able to unlock bootloader. (...) Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ ) That's the rom which is currently on my phone.
Click to expand...
Click to collapse
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
XtraWater said:
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Click to expand...
Click to collapse
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
XtraWater said:
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
Click to expand...
Click to collapse
For now these files are not useful, but do not erase them.
samuro625 said:
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
For now these files are not useful, but do not erase them.
Click to expand...
Click to collapse
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
XtraWater said:
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
Click to expand...
Click to collapse
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
XtraWater said:
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
Click to expand...
Click to collapse
Anyone who is allowed to install by TWRP, following the developer's instructions.
samuro625 said:
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
Click to expand...
Click to collapse
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
XtraWater said:
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
Click to expand...
Click to collapse
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
They will see it. I tried with a common screwdriver. Since this didn't work, I bought a kit.
Well, bad luck.
However, thank you very much for your effort. That was very kind.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
XtraWater said:
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
Click to expand...
Click to collapse
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
samuro625 said:
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
Click to expand...
Click to collapse
Hello
I didn't give up so far. Something interesting happened.
I did the follow command: fastboot flash boot.emmc.win
The flash boot.emmc.win I extracted from my TWRP backup. Now, the phone rebooted and I hear a android notification. The charging LED is working too and the backlights of the buttons. When I touch the screen, the backlight of the buttons goes on. It looks like the phone is running. But, the screen is still off.
When I press the power button short, I hear the sound which indicates the screen goes off.
Tell me if I'm wrong, but with that behavior I think it isn't a hardware damage. Since still is Nougat installed, I might need a boot.emmc.win for Nougat?
We could be very close to fix the software.
EDIT: I used: fastboot boot boot.emmc.win
If I understand this correct, that way it is only temporary. So I tried:
fastboot flash boot_a boot.emmc.win
and
fastboot flash boot_b boot.emmc.win
With that, nothing happens. So, now again fastboot boot boot.emmc.win
Phone has restarted. I hear a sound. When touch the screen backligh of buttons goes on. I'm in a menu I guess. The installation wizard. I also hear the sound when I press something on the installation wizzard.
At least, that's new. Before there was nothing.
Edit 2: Might it be related to efs1.emmc.win and efs2.emmc.win ?
Edit 3: That's crazy. I touched the screen randomly and activated a 'Screen Reader' for blind people