Related
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
MyNameIsRage said:
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
Click to expand...
Click to collapse
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only ? All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too ?
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
MyNameIsRage said:
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
Click to expand...
Click to collapse
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!! ?????
addymishra said:
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!!
Click to expand...
Click to collapse
lol, god bless our redmi note 4.
MyNameIsRage said:
lol, god bless our redmi note 4.
Click to expand...
Click to collapse
Yes!
addymishra said:
Yes!
Click to expand...
Click to collapse
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Jimmy_979 said:
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Click to expand...
Click to collapse
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
addymishra said:
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
Click to expand...
Click to collapse
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
Haha thats great congrats! Tip for custom rom installation is to follow install guide carefully and don't ever touch root partition lol! I've stopped flashing roms now... I'm on miui now permanently with bootloader locked lol
MyNameIsRage said:
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Click to expand...
Click to collapse
Haha @MyNameIsRage I'm thinking so ???
I m stuck in this same problem
But i never tried qflash
Wellll
I buy new op5t but i still wnt back to rn4
Will tell ya guys tonight nd please help me with proper procrdure
I downloaded everything but wich file have to flash
Or any video out there?
Saved my rn4
Thank u all
Thnx alot
my phone keeps rebooting
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
Pls bro am going Tru this same problem flashed through recovery flashed through fastboot but it keeps rebooting pls help me out with the exact steps u used to fix urs
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
I am in same problem on mido. Can you help me how to get in edl mode because QFIL Not detecting PORT.
Also my adb not detecting the device so i cant use adb commands.
But i can flash Stock ROM using MI Flash Tools.
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
hey guyz i have the same problem , please help me i tried all written in the replies but faces the same problem in the QFIL.
please reply, i'm dead :"(
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.
So, I've been at this for the better part of three hours now, and I'm having a hell of a go at it. Every time I download one, I get an error from ADB "Cannot read <filename>" which doesn't seem to happen with any of the regular stuff like AOSPEx or LoS.... However, as both time and bandwidth are worth something, I figure asking for assistance at this point is warranted.
All I am looking for is either a STOCK rom or something with the EUI base that can be loaded on a Le Max 2 x829. Would someone very kindly link me if they know of one that has a WORKING download? I've had no luck with Gdrive hosted downloads, so I'd really like to avoid those if possible. Hell, the rom doesn't even have to be that good, just stable. I don't intend to keep it.
Unfortunately, my FP scanner is kill, and I fear I may have done this with some bad electronics, but I'm trying the software methods that have enjoyed some success to bring it back to life, as I'd like to sell the phone. Nothing against it, just time for something better is all. I'd like to avoid having to give a sharp discount on account of the dead FP however :\
Thank you for any assistance.
Heyyo, here is the long lost stock EUI ROM 5.8.020s for x829
https://www.needrom.com/download/5-8-020s-x829-le_x2_na/
It's right when LeEco dropped their video service so it comes with Netflix instead of levideo
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Also, that ADB error could just be an old TWRP bug if you're trying to sideload. I'd recommend using latest official TWRP.
ThE_MarD said:
Heyyo, here is the long lost stock EUI ROM 5.9.020s for x829
https://www.needrom.com/download/5-8-020s-x829-le_x2_na/
It's right when LeEco dropped their video service so it comes with Netflix instead of levideo
Click to expand...
Click to collapse
@ThE_MarD - Is it mandatory to use TWRP to flash this rom? I am on India 5.8.0.19s at the moment but stock recovery when trying to update to this one says:
Failed to update!
Cause: corrupted
Failed to update: APK not found
Heyyo, hmm you might need to at least use bootloader with fastboot boot TWRP-3.2.1-2-x2.img
If you use fastboot boot instead of fastboot flash? It will only temporarily boot to TWRP instead of flashing over your recovery which is nice in cases like this where you wish to retain your stock recovery... Albeit, I think stock EUI ROM zips always overwrite recovery.
Otherwise? Sorry I can't remember where I saw it but ChrisBalGreece did have a stock recovery.img and misc.img which works good... Maybe check out his thread or ask him on his Telegram channel or maybe it was on his AndroidFileHost account? Sorry I can only give advice at this point...
I do remember his stock EUI recovery that Microsoft Security Essentials picks up this flash script as a virus but I wouldn't worry about it. Just reboot your device to bootloader and use...
fastboot flash recovery recovery.img
Fastboot flash misc misc.img
Damnit... looks like I fried the scanner. Oh well, I'm sure someone would still buy it.
TheLastCanadian said:
Damnit... looks like I fried the scanner. Oh well, I'm sure someone would still buy it.
Click to expand...
Click to collapse
Sorry bud for that I'm not sure what you can do. I saw some threads talk about flashing a really old version of EUI ROM stock... Maybe searching XDA threads might turn up a solution?
Otherwise, you can try and contact the vendor who sold you the phone and see if they have and QFIL files or whatever they are called to try and restore the fingerprint reader.
There is some messed up QFIL files out there on the internet that cause a bad display split screen issue so I wouldn't try those
ThE_MarD said:
Sorry bud for that I'm not sure what you can do. I saw some threads talk about flashing a really old version of EUI ROM stock... Maybe searching XDA threads might turn up a solution?
Otherwise, you can try and contact the vendor who sold you the phone and see if they have and QFIL files or whatever they are called to try and restore the fingerprint reader.
There is some messed up QFIL files out there on the internet that cause a bad display split screen issue so I wouldn't try those
Click to expand...
Click to collapse
I have suspicion it may be legitimate HW damage. In my adventure to find a working Qi tag, I tried a Chinese one that was perhaps... not adequate to the task. I plugged it in, tried it, and the scanner hasn't (despite working wonderfully to that point) worked since. Too coincidental, in all probability. Thanks for the suggestions though.
ThE_MarD said:
Heyyo, hmm you might need to at least use bootloader with fastboot boot TWRP-3.2.1-2-x2.img
Click to expand...
Click to collapse
Weird but this TWRP also says zip file corrupted. Checked .zip file with integrity check and downloaded one more time and tried again but still.
Nevermind , downloaded .zip file once more and flashed succesfully by TWRP. Thank You, ThE_MarD!
lot's of confusion with Leeco rom is this 5.8 or 5.9 description says 5.9 but the file says 5.8? thanks
MikeViller said:
lot's of confusion with Leeco rom is this 5.8 or 5.9 description says 5.9 but the file says 5.8? thanks
Click to expand...
Click to collapse
It is 5.8.0.20S
Burgeruking said:
Weird but this TWRP also says zip file corrupted. Checked .zip file with integrity check and downloaded one more time and tried again but still.
Nevermind , downloaded .zip file once more and flashed succesfully by TWRP. Thank You, ThE_MarD!
Click to expand...
Click to collapse
Heyyo, that's unlucky that it was corrupted a few times but glad you got it going meow!
MikeViller said:
lot's of confusion with Leeco rom is this 5.8 or 5.9 description says 5.9 but the file says 5.8? thanks
Click to expand...
Click to collapse
Burgeruking said:
It is 5.8.0.20S
Click to expand...
Click to collapse
Yeah my bad hahaha Burgerking is right it is 5.8.020s for x829. Either way, it is 20s EUI Marshmallow for x829. :silly:
Hmmmm. I did a QFIL flash with the x820 files.... didn't seem to do anything. Anyhow, I have since flashed the newest TWRP and AOSPEx(8.1, Apr 29/18) and while it's not working... well.... I did get a vibrate and at least 1 bar of progress on committing the fp, so.... there's hope!
Edit: There was not hope. It's phantom pressing. At least now I know it's HW definitively.
TheLastCanadian said:
Hmmmm. I did a QFIL flash with the x820 files.... didn't seem to do anything. Anyhow, I have since flashed the newest TWRP and AOSPEx(8.1, Apr 29/18) and while it's not working... well.... I did get a vibrate and at least 1 bar of progress on committing the fp, so.... there's hope!
Edit: There was not hope. It's phantom pressing. At least now I know it's HW definitively.
Click to expand...
Click to collapse
Ah that is unfortunate but at least you gave it a go
Have fun on your future device! Upgrading is always nice. I don't see myself upgrading for a while though as I don't have the spare finances to get a proper upgrade. :silly:
Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.
@Walden0 brother could you help may be?
Naagraj said:
@Walden0 brother could you help may be?
Click to expand...
Click to collapse
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Walden0 said:
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Click to expand...
Click to collapse
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Naagraj said:
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Click to expand...
Click to collapse
First take a backup of EFS Am& modem partitions from recovery.
Wipe data, cache, dalvik & system. Flash miui rom, format data and flash orange fox recovery again. Boot into system.
That's it.
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Naagraj said:
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Click to expand...
Click to collapse
Should work, orangefox has aggressive stock recovery deactivation which isn't available in twrp I guess.
btw quote or mention me as I can't get any notification if you don't.
Naagraj said:
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Click to expand...
Click to collapse
Have already told you pal, try flashing miui and see if it works.
Modem partition should be in orangefox. I can't confirm as I don't have the device anymore.
Brother I am having same problem right now in 2020. did you find any solution to it? Any response will be greatly appreciated
I'm having this same problem in 2021. Any fix guys?