Related
(BLU Studio Selfie S070Q bugless R Remix Rom)
Finally bugless CM 12.1 based remix rom is here for BLU Studio Selfie S070Q
This rom is not official .... but its bugless so you can try ... It was really time consuming for developing and bug fixing hope you ll appreciate my work
Rom Details:
Name: Resurrection Remix
Android Version: lollipop 5.1
Android kernel: 3.10.x
Rom porter and moderator : Prajwal Dhungana, NEPAL (myself)
Whats working:
1. Sim Cards
2. Mobile data (if it don't work then look for a video on you tube about DNS changing in Cm roms)
3. Camera
4. Audio
5. Google play services
6. Wifi
7. Bluetooth
8. Hotspot
9. Location
10. Nav Bars
11. Flashlight
12. SD card
Features:
1. Clock customization
2. Battery customization
3. Kernel auditor
4. Pre rooted
5. High quality sound tweaks
6. Speed tweaks
7. Other Build.prop tweaks
8. Fully bugless
9. System UI is amazing and amazing looks and graphics
10. Can change the screen resolution (default will be 240 but change font size to tiny and resolution to 220 to get best appearance)
Not working:
1.FM Radio only (as you know this is the universal problem for cm based roms) :laugh::laugh:
(Follow my insructions or I wont be responsible for your bricked device)
How to install rom :
1.Unlock bootloader (You can find guides for unlocking bootloader for mtk devices on google Use skyneel adb drivers )
2. Install twrp/cwm/philz recovery on your device
3. Go to twrp mode .... at first fully backup your phone to sd card
4. Now put your downloaded R Remix .zip into SD card
5. Advance wipe your device (system + cache + dalvix cache + internal + data but dont wipe ext sd card )
6. Now install the zip
7. As soon as the rom is installed .... then go go http://opengapps.org then download (ARM - 5.1 - Stock gapps ) then connect your device in twrp mode to computer and send downloaded gapps to sd card
8.Now go to install in twrp and install the gapps as well
9.Now wipe the dalvix cache again
10. Reboot your phone and you will be running CM 12.1 based resurrection remix rom on your BLU studio selfie
Here's the link :
https://drive.google.com/file/d/0B_8NzSmywh8TcERXMHdoV3NpcHM/view?usp=sharing
If you are looking for the TWRP recovery that I made, here's the link
https://drive.google.com/file/d/0B_8NzSmywh8TZjF2M3IwVDg4bW8/view?usp=sharing
I suggest you guys to use Dark Pitchblack Red , Android N theme , Britzer , Dark Matter themes from Play Store
enjoy......
If you wanna port it to other MT 6580 devices then you are free to port :good::good:
Dont forget to say thanks for my hard work
Please do comment , shares , you are free to port as well ........ dont forget to say thanks
bootloader
Good job! can you provide us with the bootloader unlock tutorial please? I want to try this rom, looks great!!!
okay ..... I ll post the tutorial as well
andusxx said:
Good job! can you provide us with the bootloader unlock tutorial please? I want to try this rom, looks great!!!
Click to expand...
Click to collapse
Easy method : Root your phone using kingroot ..... install twrp using rashr ...... then flash the rom .... gapps ..... cm based rom will unlock bootloader themselves . . ...
and I suggest you to use my ATOS rom .......... its better than this rom
andusxx said:
Good job! can you provide us with the bootloader unlock tutorial please? I want to try this rom, looks great!!!
Click to expand...
Click to collapse
Link for ATOS : link https://drive.google.com/file/d/0B_8NzSmywh8TVWxlMjNYQ19UV0U/view?usp=drive_web
Gapps : opengapps.org (arm-5.1-stock)
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
Hi, so basically I am satisfied with my S7 edge but it's become a bit sluggish so I thought of doing a factory reset. Then I thought maybe I can root as well, device is 15 months old, not much warranty left anyway. I am satisfied with stock Rom and use Samsung widgets, Samsung gear fit, I like it the way it is but surely I could debloat it. Is there any stock debloated Rom that I could install? Also pre rooted? And how does rooting in general work, I only have experience with HTC and they had their devportal to do that. What's the Way to go with S7 edge? Thanks!
I will help you and guide you.
So i also have S7 Edge and im rooted since i buy the phone.
I love stock look with debloat and root. So im using stock roms, no fancy modification and that things..
So..
This is how to flash superstock rom with superstock kernel and supersu!
First download:
SuperStock ROM | Download LINK | Information about ROM |
SuperStock KERNEL | Download LINK | Information about KERNEL |
TWRP for S7 Edge | Download LINK |
Odin Software | Download LINK |
No-verity-opt-encrypt-2.2.zip | Download LINK |
1 ) Activate developer mode on the current system and enable OEM Unlocking!
2) Reboot phone mode to DOWNLOAD MODE and FLASH TWRP using ODIN! (TWRP File place in position AP)
!!! You must turn off AUTOREBOOT option in ODIN and after FLASH manually reboot the phone into TWRP !!!
3) Go to WIPE and select FORMAT DATA - write YES , then go back till you see main screen, then go to Reboot and select RECOVERY!
4) Confirm "Allow modifications" !
5) Go to FLASH and select No-verity-opt-encrypt-2.2.zip
6) Again go back till you see MAIN screen and go REBOOT and select RECOVERY!
7) Confirm "Allow modifications" ! (If TWRP ask)
8) Go to FLASH and select ROM File! (SuperSTOCK ROM File)
8.1) In aroma choose next: (FULL WIPE, UPDATE BOOTLOADER&MODEM, SUPERSTOCK-Kernel, SUPERSU , DONT CHOOSE ANY MODIFICATION (example. LTE Icon..), REMOVE ALL EXCEPT SAMSUNG BROWSER AND SAMSUNG S-PRINT)
Setup your phone after that boot into TWRP, go to Wipe and select Cache and Dalvik!
After that reboot to TWRP and go to flash and flash SuperStock Kernel
Dont press reboot to system, before you need to flash Magisk or SuperSU same like kernel
IF YOU NEED INSTANT HELP JOIN MY TELEGRAM GROUP OR VISIT GODSETUP THREAD!
Telegram GROUP --> TELEGRAM GROUP JOIN NOW <--
Thanks and this superstock rom is basically a debloated and optimized stock rom?
fBx said:
Thanks and this superstock rom is basically a debloated and optimized stock rom?
Click to expand...
Click to collapse
Yup ?
Alright thanks. Looks like it's quite easy to get twrp on there, from there I'll got the rest. No experience with Samsung but I have flashed tons of custom Roms back in my HTC days, I think I'll figure it out. Maybe I'll get to it today, or maybe tomorrow. Odin I had already set up and flashed the nougat Rom manually back in January, so I got that working already and from there it should be easy to handle.
I must say the superman Rom is also looking nice, seems to allow a bit more customization. I'll have a look at both and decide later.
Why don't you just use package disabler
k****ij84 said:
Why don't you just use package disabler
Click to expand...
Click to collapse
Yeah, cause that's absolutely the same as rooting and removing.
Alright, thanks Talentooman! SuperStock Rom is currently installing. I chose clean install instead of Full wipe tho, cause I also wanted to wipe internal storage.
Why do I need to flash Kernel and SuperSU again later? It was already chosen during Aroma installer. But I can as well just do it. Waiting for the first boot now.
[Edit] everything works fine, I just need to sort out SafetyNet now.
fBx said:
Alright, thanks Talentooman! SuperStock Rom is currently installing. I chose clean install instead of Full wipe tho, cause I also wanted to wipe internal storage.
Why do I need to flash Kernel and SuperSU again later? It was already chosen during Aroma installer. But I can as well just do it. Waiting for the first boot now.
[Edit] everything works fine, I just need to sort out SafetyNet now.
Click to expand...
Click to collapse
In aroma isnt newest kernel included ?
hehe no safetynet.. im using supersu
I switched to MagiskSU and now I pass Safetynet.
Talentooman said:
I will help you and guide you.
So i also have S7 Edge and im rooted since i buy the phone.
I love stock look with debloat and root. So im using stock roms, no fancy modification and that things..
So..
This is how to flash superstock rom with superstock kernel and supersu!
First download:
SuperStock ROM | Download LINK | Information about ROM |
SuperStock KERNEL | Download LINK | Information about KERNEL |
TWRP for S7 Edge | Download LINK |
Odin Software | Download LINK |
No-verity-opt-encrypt-2.2.zip | Download LINK |
1 ) Activate developer mode on the current system and enable OEM Unlocking!
2) Reboot phone mode to DOWNLOAD MODE and FLASH TWRP using ODIN! (TWRP File place in position AP)
!!! You must turn off AUTOREBOOT option in ODIN and after FLASH manually reboot the phone into TWRP !!!
3) Go to WIPE and select FORMAT DATA - write YES , then go back till you see main screen, then go to Reboot and select RECOVERY!
4) Confirm "Allow modifications" !
5) Go to FLASH and select No-verity-opt-encrypt-2.2.zip
6) Again go back till you see MAIN screen and go REBOOT and select RECOVERY!
7) Confirm "Allow modifications" ! (If TWRP ask)
8) Go to FLASH and select ROM File! (SuperSTOCK ROM File)
8.1) In aroma choose next: (FULL WIPE, UPDATE BOOTLOADER&MODEM, SUPERSTOCK-Kernel, SUPERSU , DONT CHOOSE ANY MODIFICATION (example. LTE Icon..), REMOVE ALL EXCEPT SAMSUNG BROWSER AND SAMSUNG S-PRINT)
Setup your phone after that boot into TWRP, go to Wipe and select Cache and Dalvik!
After that reboot to TWRP and go to flash and flash SuperStock Kernel
Dont press reboot to system, before you need to flash Magisk or SuperSU same like kernel
IF YOU NEED INSTANT HELP JOIN MY TELEGRAM GROUP OR VISIT GODSETUP THREAD!
Telegram GROUP --> TELEGRAM GROUP JOIN NOW <--
Click to expand...
Click to collapse
quick question:
if im coming back to this rom after flashing a different rom do i still need to flash the "No-verity-opt-encrypt-2.2.zip" ?
All credit goes to @mijing
grab universal-safetynet-fix-v2-beta-5-magisk-v14.zip from
https://androidfilehost.com/?fid=673368273298984533
Clean flash your ROM as normal (I used Alberto's AOSP 8.1 13-3-18 to test):
Advanced Wipe the usual 4: Dalvik/ART, system, data, cache .
Flash ROM
Flash appropriate gapps (for this it was opengapps 8.1 arm64 nano)
Boot to install to desktop.
->>> wait a minute or 2 for google to update
Reboot to recovery
Flash latest Magisk (1620) (this was tested with 1600).
Boot to desktop (I have to boot to desktop twice before the Magisk manager icon appears - go figure!!!)
Boot back to Recovery.
Flash the old Magisk from above (v2 beta5).
Boot back to desktop and check Magisk Manager /settings /modules and you should see the old one now sitting in modules!
You are now rooted and fully safteynet'ed.
EDIT - for soaks and folks testing 8.x stock and or signed ROMs see this for magisk-izing an 8.x stock ROM
Thanks! @rafikowy
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
All credit goes to @mijing - I just copied @mijing 's work.
I won't expected like this from you . thank you for create this Guide
mijing said:
I won't expected like this from you . thank you for create this Guide
Click to expand...
Click to collapse
Totally thanks to you and your patience explaining it to me. I knew nothing of Magisk Modules. Now thanks to you I know a bit!!! Thanks!!!
fixed for 8.x bootloaders - see OP above.
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootloopedcredits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing
I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootloopedcredits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.
Thnx. I will try & let u know.
thank u sirThis kernel help me from bootloop .how did u make this kernel
Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
This kernel really working in bootloop.thnx
doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.
Kernel properties added.
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)
The link to download the kernel won't work anymore, is there a mirror?