Related
Hey guys. I decided to have some fun and mod the Existing MIUI port for the desire 816t for a few other devices. I will link the full rom and you can download the edited build.prop for your device. Then just unzip the original rom and switch out the build.prop file. Happy flashing Note: Underlined section in previous paragraph applies only for MIUI v5
I AM NOT RESPONSIBLE FOR DAMAGES TO YOUR PHONE, YOU, OR YOUR SOCIAL LIFE AFTER FLASHING. BE CAREFUL
MIUI v5
MAIN ROM:
Normal
http://en.miui.com/download-256.html
This is built by the developer hasz. I am in no way taking credit for his work. He is very generous to make this base ROM for us!
Main Rom In French:
https://mega.co.nz/#!H85z0JYT!V77Fpj...pNAxt5tOU9FbDg
Translated by generous user tifalyz . Give Him Some Love!
build.props:
a5_chl: https://www.dropbox.com/s/abe0jtv6bvdf8qo/build.prop?dl=0
^Some users report a5_ul working with this too.^
a5_dug:Coming soon(?)
others coming soon. a5_chl is the one I own so others may be delayed a bit.
MIUI v6
Standard Download
http://miuirom.xiaomi.com/rom/u6213272/5.5.8/miui_d816t_hasz_5.5.8_d8c9a27e8b_4.4.zip
This is built by the developer hasz. I am in no way taking credit for his work. He is very generous to make this base ROM for us!
Virgin Mobile port:
https://drive.google.com/file/d/0B6AGYlsMVUD0aDVhMlAwR05ncDA/view?usp=sharing
NOTE: MIUI v6 for this device has a known google play issue. Flash the google play fix that is found in this
MIUI V7 [Beta]
Standard Download
http://www.miui.com/download-264.html
does not boot, change boot.img out with this one:
https://drive.google.com/file/d/0B6AGYlsMVUD0OEx3aWloTFlncmc/view?usp=sharing
This is built by the developer hasz. I am in no way taking credit for his work. He is very generous to make this base ROM for us!
Virgin Mobile Port
https://drive.google.com/file/d/0B6AGYlsMVUD0X3JkOGdOeF9ETGM/view?usp=sharing
XDA:DevDB Information
MIUI ported for other Versions of the Desire 816, ROM for the HTC Desire 816
Contributors
the_Victorian, hasz
Source Code: http://en.miui.com/download-256.html
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: CWM 6.0.5.1
Based On: MIUI, Cyanogenmod
Version Information
Status: Beta
Created 2014-12-22
Last Updated 2015-01-13
Great! Waiting for a5_dwg
Great! Thank you for your work!
Waiting….. For a5dug… dual sim
Good one....plz make it for a5ul.......
I can be a beta testa on this.....
can't wait for MIUI on my 816w (a5dug) ^^
It would be helpful if people would comment info about each model, like dual sim or not, what region, stuff like that. I may be a bit delayed because of the Christmas holiday but I have the whole week after off so I should have time then. Thanks for the support?
Also if a5_ul is single sim try the a5_chl prop I think they might be similar
kinghunki said:
Great! Thank you for your work!
Click to expand...
Click to collapse
Happy to help the community!
stable
is the rom stable enough for daily on a a5_chl
[email protected] said:
is the rom stable enough for daily on a a5_chl
Click to expand...
Click to collapse
I ran it on my own a5_chl for 3 hours with no issues. The notification bar is glitched to always display 1x even when connected to 4g, but 4g works perfectly. Remember to flash gapps if you want them. Good luck
the_Victorian said:
I ran it on my own a5_chl for 3 hours with no issues. The notification bar is glitched to always display 1x even when connected to 4g, but 4g works perfectly. Remember to flash gapps if you want them. Good luck
Click to expand...
Click to collapse
I am having trouble with the dual sim Variant's build.prop because MIUI was never ported to the dual sim htc One m7 which is what I used for reference one the a5_chl because of similarities.
happy Holidays,
the_Victorian
a5ul
the_Victorian said:
Also if a5_ul is single sim try the a5_chl prop I think they might be similar
Click to expand...
Click to collapse
I tried it on a5ul....it works a bit more good than the original one!the 3G is a bit more wirking even if when the screen goes off...the speed seduces till u turn it again......!sometimes i have to use the *#4636#*#* to select the wanted network manually! Thx for this nice work.....keep it up......!
I also experienced some apps crash like the MXPlayer, Google + requesting reinstallation,.....
I will work on a build specifically for a5_ul tonight, but I need some info. Is a5_ul specifically single sim or is it single Sim and wcdma/other internal radio something inside like the a5_chl?
Thanks,
The_Victorian
Sent from my Nexus 7 using XDA Free mobile app
a5_ul
the_Victorian said:
I will work on a build specifically for a5_ul tonight, but I need some info. Is a5_ul specifically single sim or is it single Sim and wcdma/other internal radio something inside like the a5_chl?
Thanks,
The_Victorian
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
a5_ul is single sim for Europe.....!!!! check this link for full specs: http://www.gsmarena.com/htc_desire_816-6073.php
I think it z like the a5_chl which is for sprint I think......!!!!!
Thx
Addymore said:
a5_ul is single sim for Europe.....!!!! check this link for full specs: http://www.gsmarena.com/htc_desire_816-6073.php
I think it z like the a5_chl which is for sprint I think......!!!!!
Thx
Click to expand...
Click to collapse
Yeah a5_chl is single sim sprint for the US yeah. I own that model. I will look into it, it shouldn't be too hard to fix
Hello ! I tested in HTC 816n single sim 4G and fully work ! Data 3g\4g OK wifi bluetooth OK APN ok no bug found just one question. It's possible to translate this ROM in french language ? Sorry to my bad english .( i not modify a build prop just flash the ROM ) and perfect work ! thanks you very much i love miui ROM
So do you flash the prop file? or?
No i just flash ROM / reboot / flash gapps and work perfectly i would just like to translate her completely into French but 100% thank's !
aerialdrone said:
So do you flash the prop file? or?
Click to expand...
Click to collapse
No you just change out the build.prop in the zip before flashing. Look in the OP for more info
I recently bought myself a Redmi Note 3 Pro Special Edition (Kate) for its ability to run an official build of CM13 and, importantly, because Kate offers Band 20 support - a major advantage for UK usage.
As you may realise, getting CM13 onto Kate is somewhat more complex than getting it running on Kenzo. This is due to both the bootloader not being able to be unlocked officially and also because the Radios in Kate are different to those in Kenzo.
After figuring everything out over the weekend, I managed to flash the Official Nightly CM13 onto my Kate device & everything ran perfectly!
I wrote up the process in my Blog in quite a bit of detail, so feel free to have a read if you wish to install CM13 on your Kate edition of the Redmi Note 3.
@mwarner mmm online you can find an version of CM13 for kate
http://blog.yam.com/amjads/article/171744431
Inviato dal mio Z2plus utilizzando Tapatalk
Naphtha said:
@mwarner mmm online you can find an version of CM13 for kate
Click to expand...
Click to collapse
My tutorial is very thorough - every step is taken into account, taking a phone as it would be out of the box running MIUI to having a fully working CM13 installed. If it wasn't complicated, I wouldn't have written a tutorial .
Thanks for the info though - the text and the ROM is all in Chinese but may be of use to someone.
Thank you for work. I will trying it till my kate comes. Doesn't band 20 and 8 work?
Gesendet von meinem Redmi Note 3 mit Tapatalk
mwarner said:
My tutorial is very thorough - every step is taken into account, taking a phone as it would be out of the box running MIUI to having a fully working CM13 installed. If it wasn't complicated, I wouldn't have written a tutorial .
Thanks for the info though - the text and the ROM is all in Chinese but may be of use to someone.
Click to expand...
Click to collapse
I don't believe is only in Chinese. Usually CM is multilanguage.
Inviato dal mio Z2plus utilizzando Tapatalk
A very well written and comprehensive guide, thanks! I've been seeing so many support requests all over the place that i'm still a bit hesitant to flash CM13. Have you noticed /ANY/ issues with hardware support? Dual sim, cameras, FP-reader? Is there anything that works worse on CM than MIUI7 stable?
Thanks again for a good guide, subscribed to your blog too
Sujejsjejej said:
Thank you for work. I will trying it till my kate comes. Doesn't band 20 and 8 work?
Click to expand...
Click to collapse
The Special Edition (Kate) phone supports the following bands:
LTE B1/2/3/4/5/7/8/20/28 ( 2100/1900/ 1800/ 1700/ 850/ 2600/ 900/ 800/ 700MHz)
Kenzo does not support Bands 2, 20 and 28.
kissamopo said:
A very well written and comprehensive guide, thanks! I've been seeing so many support requests all over the place that i'm still a bit hesitant to flash CM13. Have you noticed /ANY/ issues with hardware support? Dual sim, cameras, FP-reader? Is there anything that works worse on CM than MIUI7 stable?
Thanks again for a good guide, subscribed to your blog too
Click to expand...
Click to collapse
I must admit that the Note 3 is not my main phone - a Xiaomi Mi Max contains my primary SIM at the moment - so I have not tested it as much as I would like.
At this point (only having had the phone on CM13 for a few days) I have experienced one bug where I used the fingerprint sensor to unlock & the device unlocked, but to a black screen. Turning the screen off with the power button and then unlocking again with the fingerprint resolved this. I have only seen this once, but I did see it.
Generally, everything seems to work well - performance is great (smoother than MIUI) and both cameras and the fingerprint sensor work as expected. I haven't tried Dual SIM, or indeed a MicroSD card in the device, so I can't comment on this.
The bottom line is that it is a little too early for me to say whether I would use CM13 on the Note 3 if it was my primary phone. A safer bet is to use MIUI and set the phone up to turn off some of the oddities of MIUI. I posted about how I set up my phone here:
http://mikestechlife.blogspot.com/2016/10/guide-to-setting-up-xiaomi-miui-phone.html
On my main Mi Max I use Xiaomi.eu weekly on MIUI 8 with it set up as outlined above. CM13 only has partial supported on the Mi Max, so I don't want to go down this route with my Max.
That's quite the tutorial! Lots of good information there.
1. Xiaomi only support bootloader unlocking on Chinese Developer firmwares. There is NO Chinese firmware available for Kate - only Global ROMs. It is therefore impossible to officially unlock a Kate phone.
Click to expand...
Click to collapse
Not true, at least in my experience. I've officially unlocked my Kate using global dev MIUI8 v6.10.13. Followed these steps.. This particular MIUI release comes with a setting in the dev menu to check for unlocked bootloader and other things.
Now, I'm hoping I wasn't an exception, and officially unlocking Kate has now become just as easy for everyone.
Also, there's a ROM that's quite CM13-like and officially supports Kate and its radio. I come from a 2013 Moto G running CM13 nightlies and I don't miss CM13 after using this for a few days in my Kate. The experience is almost the same, and at least on my Kate, everything's running fine.
Too bad that Xiaomi is playing part lottery when making the phone, seems they can't be bothered to update their sources for all the part providers they're using. I guess we can't complain much when a phone of this caliber is so affordable.
I noticed that Xiaomi.eu have produced a build for Kate this week:
https://xiaomi.eu/community/threads/6-10-27.35843/
Cheers bud great tutorial.
I was using the latest Global Dev Rom and after the first boot loading TWRP it gave me a prompt for password. I could not access storage. Just fully wiped the device with TWRP/Advanced/Wipe Data and did the install. CM13 just booted on my device with a locked bootloader.
Biggie ups!
Does this work with cm 14 too?
Gesendet von meinem Redmi Note 3 mit Tapatalk
There is a developer ROM for kate? Would this not work for official unlock?
http://en.miui.com/download-301.html#449
Kate bootloader can be unlocked officially, I did it with mine on official global dev rom.
adamdabadboy said:
Kate bootloader can be unlocked officially, I did it with mine on official global dev rom.
Click to expand...
Click to collapse
how?
iakoboss7 said:
how?
Click to expand...
Click to collapse
go to en.miui.com/unlock/ and apply to unlock
Use updater to flash global dev rom
Settings -> additional settings -> developer options
enable OEM unlocking
mi unlock status -> register phone
enable usb debugging (not sure if necessary)
reboot into fastboot mode
use mi unlock tool to unlock bootloader
last time i tried the "mi unlock status -> register phone" it faild (and i tried many times and did allot of restarts). i tried it on 6.10.13, what version did you use?
Thanks for the Tutorial. When i flashed the rom with Alka Recovery, i had the error message Encryption was interrupted and can't be completed. With the ZCX Recovery it starts normally.
Has anyone tried this with CM14 or a 7.0 rom?
iakoboss7 said:
last time i tried the "mi unlock status -> register phone" it faild (and i tried many times and did allot of restarts). i tried it on 6.10.13, what version did you use?
Click to expand...
Click to collapse
I used 6.10.13, I'm not sure why you had that problem
I am a user of a OnePlus two and recently I was using Raj gopi's resurrection remix as my daily driver but after the update to Nougat version I experienced various issues in network compatibility( I have two sim cards idea and Jio and in my phone only the sim preferred for mobile data works and the other one does not connect) this is a major problem as I can't use both sims, to solve this I downgraded to resurrection marshmallow version, it didn't solve it so I again installed Nougat and as on today I am using oxygen 3.5.6 (fresh and clean)
Kindly provide a workaround for my problem. Any response would be much appreciated...
PSI kind of think I messed up with the EFS partition and now I am using 1+ recovery and my phone does not seem to be recognised in fastboot devices although it is detected in adb devices)
GandharvSachdeva said:
I am a user of a OnePlus two and recently I was using Raj gopi's resurrection remix as my daily driver but after the update to Nougat version I experienced various issues in network compatibility( I have two sim cards idea and Jio and in my phone only the sim preferred for mobile data works and the other one does not connect) this is a major problem as I can't use both sims, to solve this I downgraded to resurrection marshmallow version, it didn't solve it so I again installed Nougat and as on today I am using oxygen 3.5.6 (fresh and clean)
Kindly provide a workaround for my problem. Any response would be much appreciated...
PSI kind of think I messed up with the EFS partition and now I am using 1+ recovery and my phone does not seem to be recognised in fastboot devices although it is detected in adb devices)
Click to expand...
Click to collapse
Oh hell it starts again.
Please can you learn how to use search function on this forum and not create your own thread ?
Thanks.
casual_kikoo said:
Oh hell it starts again.
Please can you learn how to use search function on this forum and not create your own thread ?
Thanks.
Click to expand...
Click to collapse
Sorry, but I am new on XDA I will search to resolve my issue and will close this thread.
Thank you for your reply
I haven't found found any relevant posts on this topic so my quest for answers is still on...
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 guy!
As you know, J7 2017 was rooted, and you could install rom on it. I really love lineage rom special android 8.0 is coming.
Thus, someone can build lineage rom for j7 2017?
I think that bring more and more benefit to user.
Thanks!:fingers-crossed:
I would also like to see Lineage ROM for J730F
Thank you.
By the way, very little roms is available for our phone.
What is this... :laugh:
Lineage ROM for J730F
I flash it yesterday, but the phone is not want to boot.
Then I restored my backup with TWRP.
..
@sun75
Thank you dude :good: This is cool.
We are waiting for Lineage ROM for J730F
https://androidfilehost.com/?fid=673791459329062574
check this build phone boot up successfully but no camera and sim cards works
majinawaz said:
https://androidfilehost.com/?fid=673791459329062574
check this build phone boot up successfully but no camera and sim cards works
Click to expand...
Click to collapse
majinawaz said:
https://androidfilehost.com/?fid=673791459329062574
check this build phone boot up successfully but no camera and sim cards works
Click to expand...
Click to collapse
What you do with phone, where sim card does not work?
Maybe in next release @Yukick fix sim support.
Thank you for your hard work @Yukick.
We all waiting Lineage for J730F.
Any progress here?
No, we're still waiting.
Hey what about lineage os?
I think they forgot us.
Cheers ?
Hi, I want to know how to solve a buggy card not working and sound:crying:
Toey62 said:
Hi, I want to know how to solve a buggy card not working and sound:crying:
Click to expand...
Click to collapse
Please give me download link for this rom
Are you experienced very nasty lag in this Lineage? I'm waiting for the official release, but LineageOS makes official builds for only S series of Samsung...
forid said:
Please give me download link for this rom
Click to expand...
Click to collapse
This is a download link.
What's bugs are there in this rom?
forid said:
What's bugs are there in this rom?
Click to expand...
Click to collapse
I tried it
None off the sims detected
No wifi
No Bluetooth
Fingerprint not working
boots quick and seems snappy
Ive got a j730f ds
I hope that developer will fix it