Related
Hello community.
I'am having too many issues with muy OnePlus 2 (A2005).
On oxygenos doesn't work sensors (gyro,accel,proximity) and after a time lf use touch became unusable
On hydrogen OS doesn't work fingerprint unlock (lets me add fingerprint but cant unlock) anyway this os doesn't like me.
Actually i install cm13 and im having same issues than oxygen , touch sometimes became unusable (for some seconds) , sensors doesn't works , camera open but i cant see anything , gyroscope doesn't works.
If its possible, i want to stay con cm13
Sorry for my english and thank you so much.
Regards from Argentina
Flash latest OOS 3.1 using the Qualcomm tool, that should restore the persistent partition needed to get the sensors running again and maybe fix the fingerprint reader unless yours is broken hardware wise like many others.
Regards from Sweden
pitrus- said:
Flash latest OOS 3.1 using the Qualcomm tool, that should restore the persistent partition needed to get the sensors running again and maybe fix the fingerprint reader unless yours is broken hardware wise like many others.
Regards from Sweden
Click to expand...
Click to collapse
Which tool? QFIL?
Use the search function young Skywalker.
Pride, thank you so much for the answer. I install SkyDragon and all works perfectly except touch, firsts moments it works fine, but after a few minutes it comes to have issues half (and more) of the taps cannot be readed. I think your answer gonna be usefull for that too. Im going to try, maybe it's because my device was hardbricked and i restore it. Gonna try your method, any specific name of the tool? there's a few of tools by qualcomm. Anyway, im going to keep searching. Thanks again
PD: Curiously, touch works good in Hydrogen.
Okey , if i do the process for hardbrick and install Oxygen 2.x the touch works great. The problem is when im doing upgrade to android 6, because i need to install a patch https://www.androidfilehost.com/?fid=24421527759880815 . otherway , it doesn't let me upgrade. After that patch comes the issue. For the moment, im going to keep on 2.x and install OTA.
EDIT: Upgrade OTA and keep having the same issue.
Edit2: after updating ota i installed google now launcher and works okey. I think the problema is with OnePlus Launcher
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
ezrawk said:
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
Click to expand...
Click to collapse
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
TecnoTailsPlays said:
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
Click to expand...
Click to collapse
sarath67 said:
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
Click to expand...
Click to collapse
raymond_bqg said:
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
Click to expand...
Click to collapse
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
raymond_bqg said:
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
Click to expand...
Click to collapse
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
ezrawk said:
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
Click to expand...
Click to collapse
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
shyampandey said:
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
Click to expand...
Click to collapse
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
ezrawk said:
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
Click to expand...
Click to collapse
yeah, after problem bring fixed completely, you can come back to custom roms.
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Try flashing miui fastboot rom....it will fix the broken drivers...
Paleskin said:
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Click to expand...
Click to collapse
Yeah, the replaced touchscreen must be a replica. So bad drivers should be the case. If there's an official xiaomi agent near you, you should ask them to replace it or try finding an original touchscreen for RM2.
I'm guessing you've been facing frequent SoD's (Screen of Death that makes you have to force reboot the device) and unresponsive touchscreen when the device is trying to wake from sleep (ex: pressing power button). SoD's occurs because of the proximity sensor that is attached to the replica screen is buggy.
I used to have the same problems, but it got fixed. I bought a dead original Redmi 2 and right away I started switching parts from the dead redmi 2 to my redmi 2. Salvaging parts that I've tested and arent using right now, and replacing bad parts. Extra info: RM 2's Touchscreen isn't sold by piece. You gotta buy the whole package, from LCD to TS and Proximity.
Try reading an old ROM thread by @ketut.kumajaya (CM 12.1-13), there you'll find tons of information about buggy parts of your redmi 2. Starting from eMMC to Proximity sensors, because RM 2 are sometimes shipped with different parts inside it.
and one more thing, your thread should be posted in Q&A section, just reminding you mate!
Good luck!
So my best option right now is to go back to miui based custom rom and twrp 2.8.7, since I encountered no errors with them, thankz very much mate
Paleskin said:
So my best option right now is to go back to miui based custom rom and twrp 2.8.7, since I encountered no errors with them, thankz very much mate
Click to expand...
Click to collapse
By all means yes if you don't have the leisure to do what I just posted (Changing your replica screen to an original RM2 screen). If you do plan on using MIUI based ROM, I suggest you to sneak a peek at xiaomi.eu and download the latest rom for Redmi 2 (running MIUI 8.2 with LP-bootloader). Best performance for MIUI.
Or if you are the 1 GB RAM variant of RM2, Try going for Kitkat MIUI 8 (with KK bootloader). I'll be praying that SoD's and other bugs won't occur while you're on KK and using that replica screen of yours.
I've been on this phone for a year, and at last when I fixed it (with the methods in my last post), I fully unlocked all customization for RM2, please do consider my methods if you are going to settle with RM 2 for a while or you're facing the same bugs that I used to.
Good luck!
ezrawk said:
By all means yes if you don't have the leisure to do what I just posted (Changing your replica screen to an original RM2 screen). If you do plan on using MIUI based ROM, I suggest you to sneak a peek at xiaomi.eu and download the latest rom for Redmi 2 (running MIUI 8.2 with LP-bootloader). Best performance for MIUI.
Or if you are the 1 GB RAM variant of RM2, Try going for Kitkat MIUI 8 (with KK bootloader). I'll be praying that SoD's and other bugs won't occur while you're on KK and using that replica screen of yours.
I've been on this phone for a year, and at last when I fixed it (with the methods in my last post), I fully unlocked all customization for RM2, please do consider my methods if you are going to settle with RM 2 for a while or you're facing the same bugs that I used to.
Good luck!
Click to expand...
Click to collapse
Nah, I done wasting money on r2, I was in minovo cusrom kitkat before, and no problem encountered, so I'll just go back to minovo then, thanks
Paleskin said:
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Click to expand...
Click to collapse
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
nadifzidane said:
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
Click to expand...
Click to collapse
Works perfectly, thanks
You got any fix for sod issue on lineage 14.1 too ?
nadifzidane said:
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
Click to expand...
Click to collapse
Hi, where have you seen this link? I would like to learn more about the source of this TWRP before flashing it.
I was for a while on the Global Rom (a few months) after receiving the phone with EEA software.
I think one or two weeks ago I wanted to give it a try and update to MIUI 12 and took and installed the suitable ROM from xiaomi.eu, followed by a couple of updates (I think both were made bt TWRP).
I bounced a bit between ROMs, now I am on stable beta 12 that was released a few days ago, I tried before to wipe davlik and data options I think to see if in some way something got messed up on the way. A few Roms I tried were installed with MIFlash utility as well, trying to see all options/find a solution.
I looked a bit here on xda to see similar issues from other posts/people but there were some suggestions to go into the Android files - yet, I did not want to mess if further without asking beforehand - maybe someone knows a little better.
Thanks in advance for any info
Have a nice day
Hi, did you already solve this bug? I having the same problem on my Redmi Note 9 pro... I see this solution (but I can't do it on my phone, I don't know how to disable the permission)... https://forum.xda-developers.com/t/...dphones-max-volume-mod.4150907/#post-87377199
Tx
I have a Huawei DRA-AL00 (either called the Y5 2018 or Enjoy 8e Youth depending on which source you believe) currently running Android 8.1 (device details from Droid Info attached).
I am seeking an English language ROM with gApps (or the option to add it). I have already searched the forums and found this thread, however, the ROMs listed seem to just be copies of the stock ROM (or, at least, I can't find any details about them except that they're Android 8.1) I'm worried they'll have the same issues as the factory reset OS that I've already tried. I also searched google generally and found a lot of ROMs for other Huawei phones but none that looked promising for this one... Neither LineageOS nor ArrowOS seem to have an option for this phone. I also don't see a TWRP version that's been specifically tested for this phone, but I'm thinking of trying the one that's recommended for the Y5 2017 or the Enjoy 8 Plus. Of course, that's only relevant if I can find a custom ROM worth using. I'm willing to risk bricking this phone by using a TWRP and ROM that are intended for a different but similar phone, but I'd rather do so with input from someone who's more knowledgeable about phone OSs than me . I'll post the results of any ROMs I try here so others with this phone can have clearer info on what works with it.
Thanks for your help!!
***
Additional info below, not necessary to answer the original question .
For context, I'm a complete newb to flashing custom ROMs on phones. That said, I follow directions just fine and have spent most of today watching and reading tutorials for other Huawei phones (can't find one for this phone specifically...). I've also already tried several different fixes to get this phone functional without replacing the OS, but each new fix keeps raising a new issue or only partially resolving the original one. Hence reverting to the solution that's always served me well on laptops and desktops, replacing the OS.
I have already:
- Factory reset the phone.
- Set the system language to English (this succeeded in getting most of the day-to-day interface to show up in English, but about half of the pop-up messages and the contents of the in-built app store/browser/etc are all still in Chinese...).
- Replaced the keyboard app as it was also still an odd mix of English and Chinese which made typing pretty difficult...
- Tried four different methods to install gPlay on a Huawei phone all of which appeared to be working during install but result in a gPlay app that won't open.
- Tried installing the apps that I need without going through the Play store, however, anything affiliated with google (eg gmail, gmaps) refuses to work. I updated Google Play Services and Google Services Framework APKs to the most recent versions I could find that are Android 8.1 compatible but that didn't fix the issue.
- Disabled as much of the bloatware as I can.
If I can't find a decent ROM for this phone, I'll keep trying to work around its issues using third party apps. However, I'm starting to lose hope in reaching a truly functional solution with the current OS. It'd be sad to give up on this project since it's a quite nice little phone for the very basic functions I need - decent speed and truly epic battery life (nearly a week if I'm not using it much!). At the end of the day though, it only cost me $88 in the first place, so I'd rather risk bricking it by flashing an incompatible ROM than leave it to gather dust in the back of a drawer somewhere .
Hey I have a Huawei DRA-AL00 with English ROM . It comes with Gapps and stuffs but my problem is getting Twrp for it. Can I ask how you got yours?