[PLEASE READ BELOW]
Code:
*** Disclamer * Your warranty is now void. * *
We are not responsible for bricked devices, dead SD cards, * thermonuclear war,
or you getting fired because the alarm app failed. Please * do some research if you
have any concerns about features included in this ROM * before flashing it! YOU are
choosing to make these modifications, and if * you point the finger at us for messing
up your device, we will laugh at you.
[Sorry if this DevDB thread is ugly, I will organize is later]
Hi, this is Jiiro.
I have finally finished compiling and testing out this LineageOS custom ROM for the SM-T350.
You may have seen @andr0idfr3ak's post on LineageOS for the SM-T350 (mine is updated).
I am now going to announce that I am going to be the maintainer for the SM-T350 development of LineageOS for now.
More custom ROMs are coming through!
Specs:
Samsung Galaxy Tab A SM-T350 8-Inch Tablet (16 GB, Titanium)
SM-T350 XAR GT58WIFIXX/GT58WIFI
Known bugs:
External Audio not working
Camera
Things that work:
Internal Audio does work (For example, using headphones)
Bluetooth Audio does work
Download Links:
Latest as of August 1, 2018
Latest Updato Firmware
Latest Unofficial LineageOS
Latest TWRP from Ashyx
Latest ODIN
*Note: I don't know if ********** is trusted, I downloaded it and ran it and had no problems whatsoever
Steps:
1) Get ODIN
2) Go to Download mode on your Samsung device
3) Flash TWRP
4) In TWRP go to Wipe > Advanced Wipe and click on
a) Dalvik / ART Cache
b) System
c) Data
d) Internal Storage
e) Cache
5) Go to Download mode after that
6) Go back on your ODIN and flash the firmware from Updato
7) After that happens, go back to Download mode and flash TWRP again
8) Do Step 4 and after that move onto Step 9
9) Have ADB on your machine, be in TWRP while this happens
10) Go to Advanced > ADB Sideload
11) On your computer type
Code:
adb sideload [Destination of your LineageOS .zip]
12) You're done! It will take about 5 minutes to boot.
Sorry if the guide is confusing, I will try to rephrase them again later.
XDA:DevDB Information
[ROM][UNOFFICIAL][LINEAGEOS 15.1][ANDROID 8.1][SM-T350], ROM for the Samsung Galaxy Tab A series
Contributors
Jiiro, deadman96385, ashyx
Source Code: https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T350XXU1CQJ5 | T350XAR1CQJ5
Version Information
Status: Beta
Created 2018-08-08
Last Updated 2018-09-06
lets get this thread started I been on your Rom a day or 2 now and i like it. Its gives me a picture in picture , and it saves on storage big time from all the apps Samsung puts on these tablets. Thanks for the work.
Thanks for keeping the tab A 8" alive!!! And working on a speaker fix!!
Any luck with the audio?
Please fix this soon
RebuffedRacer13 said:
Any luck with the audio?
Click to expand...
Click to collapse
Please fix this soon
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
ELProfeMcK said:
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
Click to expand...
Click to collapse
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I can't find 3.2.1
Can you post a link?
lividhen said:
I can't find 3.2.1
Found it! But it says it's for oreo... Is it safe to install?
I'm on a rooted stock 7.1.1.
Never mind! ? I didn't see it!
Click to expand...
Click to collapse
Were you able to install twrp 3.2.1 it should work fine with stock nougat. Did you try flashing lineage again? Its really stable and boots right.
I recommend trying pico gapps first
---------- Post added at 10:55 PM ---------- Previous post was at 10:18 PM ----------
lividhen said:
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Click to expand...
Click to collapse
Bluetooth and headphones work no external speaker. I tried different audio mods viper and it works with Bluetooth or headphones wired but no external speaker. Camera I can't remember I don't ever use it.
---------- Post added at 11:31 PM ---------- Previous post was at 10:55 PM ----------
lividhen said:
I can't find 3.2.1
Can you post a link?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=962339331458992706
ELProfeMcK said:
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Click to expand...
Click to collapse
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
yep. that is also my situation.
blackness, evrywhere.
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Techguy777 said:
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Click to expand...
Click to collapse
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
ELProfeMcK said:
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
Click to expand...
Click to collapse
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Flash twrp with twrp or Odin?
And if it's twrp do you extract the .tar file?
Okay! I installed it! Now can someone please tell me how to turn on the backlight? I tried the brightness thing bit the backlight still stays off.
Would another kernal fix it?
Techguy777 said:
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Click to expand...
Click to collapse
I did this in both TWRP and lineage O.S, brightness won't change. My brother told it could be kernel related but i dont understand why it works for some and black screens for others
Related
Is there a complete and idiot proof way to make my X into a lollipop S on AT&T without losing 4g and still able to use the tablet docking?
Thanks in advance to the wizards!
If you are rooted and your bootloader is unlocked .
0. If not, Root it using kingroot or towelroot v2(not v4) and use flashily (from the playstore) to flash cwm or twrp to flash crowlock to unlock the boot loader. (careful to tap recovery and not boot)
1.Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
Optional: If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
-- While at that recovery back up System, Boot and the EFS partition and cache(This recovery has the Efs option, and since the efs partition contains the communication info its best to do that so you cannot lose the bands.)
Great now you have just backed up every thing so now I will say for the next set of steps install Cyanogenmod, preferably 12.1 since cm13 is a bit unstable.
2. --For this to work with the conversion I suggest now you will need to install the latest version of twrp. (That could be found under this link)
*Make sure You put cm12.1 some where you can find when you are going to flash it*
3. Using the newest version of twrp available, flash cm12.1 on to your phone (Great Almost done) (your choice if you want gapps or not)
4. When its booting up and everything is set up put the latest WW firmware in a place you will remember when you flash it. (Also put in crowlock too, since flashing this fw will relock your Bootloader)
5. Once thats done Boot into Twrp and select advanced wipe. Under there Choose to wipe System, Data, and Cache.
6. Now its time to flash that WW firmware, which does take some time.
7. After that, flash crowlock again since your bootloader has been locked again. (Reflash Twrp.img too after that, using the img flashing option and make sure you flash the recovery and not boot)
8. Great Now you can boot and everything should be alright
Optional con't: If you are bothered by the lack of LTE connection at times, flash that other version of twrp I gave you earlier (only if you bothered to back it up before flashing the ww firmware.)
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
For future updates refresh your recovery to quarx's twrp, but keep the Adam's n5 recovery to future updates when you lose band 17 and connectivity options.
---------- Post added--------- Previous post was at 10-30-2015 ----------
Credit goes to tjsooley for figuring out this process and the other people who were present during the thread at the time.
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
colla.paolo said:
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
Click to expand...
Click to collapse
Flash ww firmware after cm12.1 through twrp and the dock should work again.
The Dock isn't supported on cm12.1 yet. (Stay tuned though it could happen in a couple of months)
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
Click to expand...
Click to collapse
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
Justatechie said:
If you are rooted and your bootloader is unlocked .
Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
--
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
Click to expand...
Click to collapse
The link to the lte recovery is dead.
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
The link to the lte recovery is dead.
Click to expand...
Click to collapse
The link is updated for the twrp recovery that supports efs backups.
If you dont know how to flash cm12.1 check this out He recommends cwm recovery
Afterwards after you successfully flash and booted cm12.1 up just flash to the newer version of twrp then install ww firmware.
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
wattseb said:
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
Click to expand...
Click to collapse
Yes thats what it did with me but it ignored it anyway
to be exact it said "are you sure you want to leave recovery with an empty system partition" funny how I flashed it so I left and it booted it up pretty normally,
I always flash cyanogenmod with an empty system partition, too, eh
next time I booted recovery up after booting system (just to root it with supersu) recovery and left it, the message went away.
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Same here
Hi los1010, same here dude, sorry to say.
I have been in contact with two ROM creators, Sudamod & Cyanpop.
I'm using TWRP 2.8.7.0 Blu_Spark.r8 recovery, this might be the problem, from my experience
What we have come up with (sort of) is that it definitely is a kernel issue. i still think that if i changed my recovery it might work. otherwise the E1003 is the issue here, this model was meant to be only for Chinese huh? then they changed that policy to a European-allowed model. I really don't know. i recently went back to android after some years with ios. Please let me know if you find the resolution. I have to much to do to make it some time soon but i'll update this thread if i succeed.
i think you all should try the twrp recovery by master awesome
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
andlin97 said:
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
Click to expand...
Click to collapse
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
andlin97 said:
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
Click to expand...
Click to collapse
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
I have this issue as well with a black E1003, just bought it. Doesn't matter what recovery I use. anything based on 6.0 doesn't work, not even recoverys.
mohammedtabish said:
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
Click to expand...
Click to collapse
los1010 said:
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
Click to expand...
Click to collapse
sydeu said:
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Click to expand...
Click to collapse
dadaz007 said:
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Click to expand...
Click to collapse
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
dadaz007 said:
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
Click to expand...
Click to collapse
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Ok will try this
dadaz007 said:
Ok will try this
Click to expand...
Click to collapse
Regarding setup wizard crashed when you have phone up and running, Fixed that to. Mod the Gapps zip using a PC and remove setup wizard file from CORE, then flash the zip in recovery on phone. Problem nr.3, hardware buttons down on screen does not respond. only the right one which now is back. Huh.
andlin97 said:
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Click to expand...
Click to collapse
Good job! I would guess it's end stk with his latest Blu spark r88 that solved it
Everyone here interested, i suggest you use cyanpop instead, trid to flash it the same way, it works much much better with the onyx. No Gapps problem either.
Maybie it was the format of the partition that did it then. Sounds strange that you can't fastboot another recovery though?
Yes i know, i have tried but it says Remote:dtb not found. I don't know why but could it be the migration from blu_Sparks custom made recocery for onyx to TWRP v12 that screws it up? Do i have to format or wipe anything before? Have tried with rashr and fastboot.
I think what did the trick is "Blu_spark r88 CM13" , thanks
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Jogoe said:
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Click to expand...
Click to collapse
You could try this:
Download latest cm 11 nightly
In cm recovery got to apply update and flash cm11.
Reboot then in recovery (should be cwm) flash again latest cm 12.1 together with "isorec- twrp recovery 3.0.2-1.zip by the.gangster" in one go (important!)
Then you have latest twrp for flashing anything and also for incrasing partition (System/data) for flashing bigger packages of gapps or cm 13 with gapps (here incrasing System and data partition is a "must")
Sent from my STAIRWAY using XDA-Developers mobile app
---------- Post added at 01:46 PM ---------- Previous post was at 01:41 PM ----------
Just to add: i never tried to flash twrp.zip in cm recovery so i am not sure if it works (would save some Step from above
Sent from my STAIRWAY using XDA-Developers mobile app
Jogoe said:
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Click to expand...
Click to collapse
Hi Friend,
CM official roms come with default recovery mode just like the official google roms have there official recoveries cm have.
here is what you will do what you need to do (I use Odin)
NOTE:don't Restart your phone, you have to make the steps from 2 to 4 without restart
1-Install any recovery or kernel from Odin to your mobile (that is the only way to get rid of cm recovery) VERY IMPORTANT!!!
2- open the recovery you installed and flash the rom that you want
3- flash the gapps (optional)
4- flash this file https://dl.twrp.me/i9100/twrp-3.0.2-0-i9100.img (VERY IMPORTANT To Be In The Same Order)
now restart your phone your phone must open now with the new rom, open the recovery mode after the restart to check
VERY IMPORTANT reply to me, I want to know if it worked with you
Thanks,
M.FANDIES said:
Hi Friend,
CM official roms come with default recovery mode just like the official google roms have there official recoveries cm have.
here is what you will do what you need to do (I use Odin)
NOTE:don't Restart your phone, you have to make the steps from 2 to 4 without restart
1-Install any recovery or kernel from Odin to your mobile (that is the only way to get rid of cm recovery) VERY IMPORTANT!!!
2- open the recovery you installed and flash the rom that you want
3- flash the gapps (optional)
4- flash this file https://dl.twrp.me/i9100/twrp-3.0.2-0-i9100.img (VERY IMPORTANT To Be In The Same Order)
now restart your phone your phone must open now with the new rom, open the recovery mode after the restart to check
VERY IMPORTANT reply to me, I want to know if it worked with you
Thanks,
Click to expand...
Click to collapse
Hi
Just want to mention 2 things:
You cannot use any recovery to install cm12 of above. It must be at least a KK compatible recovery.
And not all recoveries can flash .img-files (and the latest version of twrp is 3.0.2-1 of which @the.gangster made a .zip-file for us to use).
Regards
Sent from my ME173X using XDA-Developers mobile app
TriboDoP said:
Hi
Just want to mention 2 things:
You cannot use any recovery to install cm12 of above. It must be at least a KK compatible recovery.
And not all recoveries can flash .img-files (and the latest version of twrp is 3.0.2-1 of which @the.gangster made a .zip-file for us to use).
Regards
Sent from my ME173X using XDA-Developers mobile app
Click to expand...
Click to collapse
sorry for mistakes i have Focused on the Isorec Bec It Have Been a long time from the last time i used it as i have no more i9100
and sure the hard point isnt the compatable recovery it is easy to find and as he have flashed an official cm12.1 rom then he have a working one
am i right or not
thanks,
M.FANDIES said:
sorry for mistakes i have Focused on the Isorec Bec It Have Been a long time from the last time i used it as i have no more i9100
and sure the hard point isnt the compatable recovery it is easy to find and as he have flashed an official cm12.1 rom then he have a working one
am i right or not
thanks,
Click to expand...
Click to collapse
Yes your instructions are correct when using kk recovery and isorec- rec .zip.
Of course there are more ways to do it like by the great @Lanchon in this thread (MOD) IsoRec: Isolated recovery for Galaxy S 2 on Page 53 Post # 529.
Regards
Sent from my STAIRWAY using XDA-Developers mobile app
Thank u guys, i will try and report back next week!
TriboDoP said:
Yes your instructions are correct when using kk recovery and isorec- rec .zip.
Of course there are more ways to do it like by the great @Lanchon in this thread (MOD) IsoRec: Isolated recovery for Galaxy S 2 on Page 53 Post # 529.
Regards
Sent from my STAIRWAY using XDA-Developers mobile app
Click to expand...
Click to collapse
lol thanks! you can actually link posts by right-clicking on the #NNN at the top right corner of each post and selecting "Copy link address"...
http://forum.xda-developers.com/showpost.php?p=69118100&postcount=529
Lanchon said:
lol thanks! you can actually link posts by right-clicking on the #NNN at the top right corner of each post and selecting "Copy link address"...
http://forum.xda-developers.com/showpost.php?p=69118100&postcount=529
Click to expand...
Click to collapse
Thanks!
I never bothered about it but it will save me some typing in the future.
TribodoP
Sent from my STAIRWAY using XDA-Developers mobile app
Anyone here care to share stock firmware? Looking for one and Sammobile's server is down..
---------- Post added at 11:56 AM ---------- Previous post was at 11:42 AM ----------
Disregard the above request.. I've got the download working..
HTML:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working :-
Dual SIM
WiFi
Ril
Bluetooth
Audio
Sensors
Data working
Camera (photo and video recording)
GPS
FM Radio
OTG
Screen Recording
Supports Youtube 720P Videos
Youtube live playback fixed
Gello browser added
USSD Fixed
Autorotation Fixed
ChangeLog :-
Upstreamed to r79
Updated Security Patch to May 1,2017
Fixed 2G/3G Switch (Thanx to Tribetmen)
Fixed Reboot to Turn On Data (Thanx to Tribetmen)
Fixed Consecutive Lags due to Selinux
Bugs :-
VPN Only
Instructions To Flash :-
Reboot Into Recovery.
Wipe Data
Wipe System
Wipe Cache, Dalvik Cache.
Flash "LineageOS 13" ROM .
Flash GAPPS 6.0.
Reboot
Download Links :-
LineageOS 6.0.1 Rom
Gapps (Goto Opengapps.org and Download ARM/6.0/pico)
Device Tree:- https://github.com/EndLess728/android_device_hm_note_1w
Vendor tree:- https://github.com/EndLess728/android_vendor_hm_note_1w
XDA:DevDB Information
LineageOS 6.0.1 For Redmi Note 3G, ROM for the Xiaomi Redmi Note
Contributors
EndLess, Tribetmen, SamarV-121, [email protected], Fire855, Ferhung
Source Code: https://github.com/lineageos
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-05-28
Created 2017-05-28
Last Updated 2017-05-28
EndLess said:
HTML:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working :-
Dual SIM
WiFi
Ril
Bluetooth
Audio
Sensors
Data working
Camera (photo and video recording)
GPS
FM Radio
OTG
Screen Recording
Supports Youtube 720P Videos
Youtube live playback fixed
Gello browser added
USSD Fixed
Autorotation Fixed
ChangeLog :-
Upstreamed to r79
Updated Security Patch to May 1,2017
Fixed 2G/3G Switch (Thanx to Tribetmen)
Fixed Reboot to Turn On Data (Thanx to Tribetmen)
Fixed Consecutive Lags due to Selinux
Bugs :-
VPN Only
Instructions To Flash :-
Reboot Into Recovery.
Wipe Data
Wipe System
Wipe Cache, Dalvik Cache.
Flash "LineageOS 13" ROM .
Flash GAPPS 6.0.
Reboot
Download Links :-
LineageOS 6.0.1 Rom
Gapps (Goto Opengapps.org and Download ARM/6.0/pico)
Device Tree:- https://github.com/EndLess728/android_device_hm_note_1w
Vendor tree:- https://github.com/EndLess728/android_vendor_hm_note_1w
XDA:DevDB Information
LineageOS 6.0.1 For Redmi Note 3G, ROM for the Xiaomi Redmi Note
Contributors
EndLess, Tribetmen, SamarV-121, [email protected], Fire855, Ferhung
Source Code: https://github.com/lineageos
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-05-28
Created 2017-05-28
Last Updated 2017-05-28
Click to expand...
Click to collapse
I can't expand notifications windows!!!
dargonswim said:
I can't expand notifications windows!!!
Click to expand...
Click to collapse
use this gapps https://drive.google.com/open?id=0B8u0DMYQ8pXqd3VzX1QtY2wzcVk
And please dont quote the whole thread
cant send any media on telegram or whasapp
When i try to send photo on telegram, theres no preview at all of my photos. When I send it, it cant be sent. Plz help. I love this ROM very much.
Edit:
I found that everything will normal again if after install several apps, we reboot our phone.
So far so good. I dont try VPN since I dont use it.
But the problem I get is:
1. I can't find screenshot icon in notification bar, so have to activate the option on power button, but I prefer not to use
power button so often since it is faster broken. So, I install apps from playstore, need root, and done.
2. I cant find option to use volume button to awake my phone from sleep.
Just that... I found this ROM is very nice in everyday usage.
Thank you so much.
this rom works great!
thanks!
but how can i get root?
o i found it
http://www.cyanogenmods.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
@EndLess the ROM looks great. However, the download link seems to be broken. Could you (or any other user) provide a new link?
Freewander10 said:
@EndLess the ROM looks great. However, the download link seems to be broken. Could you (or any other user) provide a new link?
Click to expand...
Click to collapse
DL link is fine. Anyhow here is the direct link. Open with a browser.
Link : Click me
sachin n said:
DL link is fine. Anyhow here is the direct link. Open with a browser.
Link : Click me
Click to expand...
Click to collapse
Clicking on the download button throws up this error. Did the download start for you?
Freewander10 said:
Clicking on the download button throws up this error. Did the download start for you?
Click to expand...
Click to collapse
Umm yep. I'm using adaway.
Try using a VPN.
sachin n said:
Umm yep. I'm using adaway.
Try using a VPN.
Click to expand...
Click to collapse
I don't know what's wrong then. Because I tried downloading on my phone and laptop. And its the same problem with both.
Freewander10 said:
I don't know what's wrong then. Because I tried downloading on my phone and laptop. And its the same problem with both.
Click to expand...
Click to collapse
Check pm
Sent from my mido using XDA Labs
Freewander10 said:
I don't know what's wrong then. Because I tried downloading on my phone and laptop. And its the same problem with both.
Click to expand...
Click to collapse
Try uc brwser to download
Download link is working fine here is the link
if it still not working than try 'https' instead of 'http' else try VPN.
EndLess said:
Try uc brwser to download
Download link is working fine here is the link
if it still not working than try 'https' instead of 'http' else try VPN.
Click to expand...
Click to collapse
Its working now. Thanks.
I can't seem to get root access though.
I've flashed the LOS root add on, and Super SU but neither of them seem to work. The "Manage root accesses" option remains greyed out. Any suggestions?
I'm also facing ghost touches every now and then which aren't present in stock ROM.
I'll do a full wipe and fastboot flash the stock ROM again later then give it another try.
The fastboot flash keeps on failing at 68% but the phone still booted. Though the sim cards aren't being recognized.
Do you think the fact that the fastboot flash of the stock ROM wasn't completed would cause the ghost touches or other issues on custom ROMs?
Sorry for the long post
Freewander10 said:
Its working now. Thanks.
I can't seem to get root access though.
I've flashed the LOS root add on, and Super SU but neither of them seem to work. The "Manage root accesses" option remains greyed out. Any suggestions?
I'm also facing ghost touches every now and then which aren't present in stock ROM.
I'll do a full wipe and fastboot flash the stock ROM again later then give it another try.
The fastboot flash keeps on failing at 68% but the phone still booted. Though the sim cards aren't being recognized.
Do you think the fact that the fastboot flash of the stock ROM wasn't completed would cause the ghost touches or other issues on custom ROMs?
Sorry for the long post
Click to expand...
Click to collapse
no issues with supersu and try flashing fastboot rom (format all+download mode) and then flash twrp recovery and then the rom and ghost touches is our device issue i even facing ghost touches in stock rom .. ervryone kwns that rn3g is buggy for ghost touches
EndLess said:
no issues with supersu and try flashing fastboot rom (format all+download mode) and then flash twrp recovery and then the rom and ghost touches is our device issue i even facing ghost touches in stock rom .. ervryone kwns that rn3g is buggy for ghost touches
Click to expand...
Click to collapse
I flashed MIUI 7.5 global fastboot ROM (still failed at 68%) then LOS 13.1 and now it's working perfectly. Sims still aren't being recognized but that's no fault of your ROM. I tried another one of your tutorials to get them working but nothing works. Guess I'll just have to use it as a browsing only device until I can figure it out.
And I realised that ghost touches are on every ROM.
Thanks.
---------- Post added at 01:35 PM ---------- Previous post was at 01:00 PM ----------
Did you get Xposed working?
Does anyone know maximum supported mirco SD card now? 64gb/ 128gb?
adapted/ extended storage working as well?
Thanks!
i try to install screenshot app cus i really dont like to use power button as SS.
but none is working.
EndLess said:
Instructions To Flash :-
Reboot Into Recovery.
Wipe Data
Wipe System
Wipe Cache, Dalvik Cache.
Flash "LineageOS 13" ROM .
Flash GAPPS 6.0.
Reboot
Click to expand...
Click to collapse
Could you please tell us how to wipe data, system, cache, davik cache and flash the ROM and GAPPS?
Thanks!
markfarnell said:
Could you please tell us how to wipe data, system, cache, davik cache and flash the ROM and GAPPS?
Thanks!
Click to expand...
Click to collapse
i think you are too new to these things i sugggest better u use google for more understanding .. ther is custom recoveries which is used to flash customs roms and gapps and other packages u can flash anything using those recovery .. i suggest to use twrp recovery , u can find any video on youtube which can give u better explanation how to flash roms
this rom can be utilizate on other phones like zopo 998 with mt6592 ???
Sent from my nypon using XDA Labs
I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
As I have reached the of Limit flashing ROMs over and over again, I came to the following occasion:
After casually flashing a new oreo based ROM, having installed also the Gapps, everything was fine for the time being. Suddenly when I tried to flash the magisk manager, from TWRP recovery it was saying that the installation had failed and that magisk failed to mount vendor(never before asked)!
I flashed one or two times stock ROM(miui 9), but I think that it might not be the proper one! For example, there used to be such a problem in the past, but when I slashed stoke MIUI 8 the problem was fixed! I don't know what's going on!
I also get sometimes unusual errors from TWRP and my device seems to be unstable! Do you think that I might have caused a serious problem to my device after flashing and flashing over and over again?
Here is a screenshot: https://drive.google.com/file/d/18xj7Xj3UWWG7NW7N_uOt7iECBMvkoyRP/view?usp=drivesdk
Device: mido
TWRP: any
ROM: any
Magisk: any
**Problem solved**
Steps to solution:
1. Flash latest MIUI from custom recovery or Mi Flash.
2. Boot up and finish the initial set up.
3. Reboot into recovery and flash latest magisk zip file.
4. Reboot and see that magisk manager is installed
5. Then reboot again into TWRP, wipe everything and format data!
6. Flash ROM, GAPPS and then latest magisk manager!
Done!
David_#27 said:
I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
Click to expand...
Click to collapse
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
DarthJabba9 said:
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
Click to expand...
Click to collapse
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
David_#27 said:
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Click to expand...
Click to collapse
Hmmm ... perhaps you should wipe everything (system, cache, and dalvik) and then format your data partition (which will also wipe your internal SD) and start afresh.
Go back to stock rom using fastboot method or MiFlash tool, that way you'll go back to complete stock and it maybe able to solve your problem
@DarthJabba9 and @rrgreatvijay5, thanks a lot for you're help, but I've already tried both of the methods you provide me! Maybe it is a hardware issue like @sk8223 says...
But, I won't quit till I find the solution to this problem!
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
sk8223 said:
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
Click to expand...
Click to collapse
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
chrismin13 said:
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
Click to expand...
Click to collapse
That's exactly what I meant! Thank you Chris!
So guys what firmware do you use in order to flash custom roms?
David_#27 said:
So guys what firmware do you use in order to flash custom roms?
Click to expand...
Click to collapse
You may try any of these, i usually flash latest one.
https://androidfilehost.com/?w=files&flid=236737
Edit: If you have already tried fastboot flashing method, my guess would be your firmware has already restored to stock, so it wont make any difference, but still give it a shot
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
No I didn't... The partitions is already ext4 formatted!
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
chrismin13 said:
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
Click to expand...
Click to collapse
Very good idea dude! I will give it a shot!
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Maximus909 said:
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Click to expand...
Click to collapse
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
I am about to try 16.4 treble built...found the link after a bit of digging... If it works (or it doesn't) I will update, also using the redwolf treble built recovery, checking if that helps....
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
All right so all done, and succeful this time. Now the problem was actually with the recovery and not magisk itself.... So what we need to do is flash redwolf recovery for tteble builds and download treble compatible 16.4 magisk version. I tried flashing through standard twrp but failed so we need this treble build :good:
Redwolf Recovery {treble build, for MIDO ONLY} : https://androidfilehost.com/?fid=746010030569954397 .
Magisk 16.4 modded : https://androidfilehost.com/?fid=962187416754478287 .