Related
14 November 2014
There are several great lollipop builds out there currently with a lot of work being done to give us all a great product. So far multirom is working perfectly in Primary slot as well as secondary slots in multirom with @scrosler AOSP builds 5-7, Build 7 here as well as @scrosler Factory Stock Rooted ROM LRX21P which can be found here
If your favorite dev is making a Lollipop build for the Nexus 7 and you have successfully used it with multirom, please let us know so we can tag it and place a link for future users to this thread.
06 November 2014 (ORIGINAL POST)
Ever since I mentioned this in an email, I have received a few requests on how I got @scrosler Pure AOSP 5.0 Build to work with MultiROM on my Nexus 7 flo.
First off, I have only done this with the build by @scrosler which can be found HERE, but I would guess that it can work with similar builds.
Secondly, this worked perfectly on my device. If you mess up your device, I am not responsible.
Thirdly, and most importantly thank you to:
@scrosler for the lollipop build and all the extras
@Chainfire for SuperSU
@sykopompos for the permissive boot image
@flar2 for the ElementalX Kernel
@Tasssadar for MultiROM
if I forgot to mention someone, please holler at me
Okay, on to the easy stuff...
This has been tested and is successful on Nexus 7 flo (2013). For information on Deb procedures, please refer to this post by @drewski_1 but at the request of @scrosler, please bring all multirom questions back to this thread. Also for Nexus 7 deb, @darkobas has given us a modified boot image to use which can be found here
This ROM (this particular build I've been working with) cannot go into a secondary slot of MultiROM, I have tried everything. If you found a way, please share it.
1. go HERE and read the OP, download necessary files, (latest build, latest gapps, busybox flashable, etc), update bootloader if needed, and goto step 2.
2. go HERE to get ElementalX Kernel for Lollipop
3. go HERE to get a very permissive boot image that works perfectly with this setup.
4. go HERE to get the latest SuperSU
After you have everything in order, reboot into recovery...
1. Move your primary ROM into a secondary slot in TWRP recovery.
2. Go back out to the main TWRP page (outside of Advanced/MultiROM)
3. Install Scotts Pure AOSP build 5.0
4. Install Recovery Saver
5. Reboot Recovery (just to make sure your recovery is still intact)
6. Install GAPPs
7. Install Permissive boot image
8. Install SuperSU
9. Install ElementalX Kernel
10. Reboot and Enjoy
When you get into your ROM, check to verify that your SuperSU is functioning properly and set your ROM up to your likings. :good:
appreciated clarification
OP said:
I've gotten a few requests about multirom with this build since I posted something earlier. If you need to know how to do it (you should already if you're using multiROM), you can check it out HERE.
I didn't want to post the info in here and muddy up the dev thread.
http://forum.xda-developers.com/showpost.php?p=56558107&postcount=802
Click to expand...
Click to collapse
I know but tend to forget details over time - THANKS. I like to verify procedures before committing anyway - saves me from bricks soft or hard. With the file structure changes, etc I like to know what I'm getting into and how best to do it safely.
I'm in the process of moving roms and should have this latest L in slot #1 before dusk, heh.
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
hhairplane said:
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
Click to expand...
Click to collapse
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Megaflop666 said:
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Click to expand...
Click to collapse
It might just be with Deb, then...
hhairplane said:
It might just be with Deb, then...
Click to expand...
Click to collapse
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Megaflop666 said:
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Click to expand...
Click to collapse
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
hhairplane said:
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
Click to expand...
Click to collapse
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Megaflop666 said:
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Click to expand...
Click to collapse
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
hhairplane said:
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
Click to expand...
Click to collapse
Its all good. There's been conversation scattered everywhere, that's one of the biggest reasons I wanted to start this thread.
Edit: Link has been updated to the correct post.
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
dadeo1111 said:
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
Click to expand...
Click to collapse
Try going into twrp into one of the secondary ROMs and fixing it's boot? Something must've gotten missed in the setup or something happened because this issue is new.
Megaflop666 said:
Try going into twrp into one of the secondary ROMs and fixing it's boot sector?
Click to expand...
Click to collapse
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
edit to add:
I am able to install/add roms, btw. I successfully re-added a jellybean rom from nandroid backup just fine. I'll probably throw them out except one anyway. I'm not sure what happened or when but I followed your steps verbatim. thanks again.
dadeo1111 said:
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
All the multiform specifics can be found in that thread here.
I would try restoring your backup first and see if that fixes the secondary ROMs. Especially since you don't have much time in the lollipop ROM yet. If you restore and it works, let me know.
@scrosler has build 4 up, please see his thread which can easily be found in the OP, second paragraph.
OP will be updated shortly if necessary.
Okay, I've gone through this a few times now. @scrosler work is perfect unless we want to use it on multirom. Continue the same steps listed in the OP or you will lose root, as well as the ability to boot multiple Roms.
Build 6 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Megaflop666 said:
Build 5 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Click to expand...
Click to collapse
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work too - as usual. If not I'll post so here.
This is going to be my daily driver now. :good:
I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
dadeo1111 said:
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work - as usual. If not I'll post so here.
This is going to be my daily driver now. :good: I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
Click to expand...
Click to collapse
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Megaflop666 said:
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Click to expand...
Click to collapse
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
dadeo1111 said:
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
Click to expand...
Click to collapse
Are you using the permissive boot image from the OP and elementalX kernel 3.01? Just curious why I have full function with ES and other people don't.
Hi guys,
I've downloaded with XperiFirm the latest available firmware for T-Mobile Poland - D5503_14.5.A.0.283 and created a prerooted .zip with PRFCreator. This does not have any branding at boot, themes etc., only a few apps that you can remove or disable as per your choice, I didn't remove anything so you can choose yourself.
What's included:
D5503_14.5.A.0.283_T-Mobile_PL
UPDATE-SuperSU-v2.46.zip
Z1C-lockeddualrecovery2.8.20-RELEASE.flashable.zip
You need to have custom recovery to flash it, and please remember to backup your device, you use the file at your own risk.
Download link: https://mega.nz/#!bF0lBbxI!8YfxjyDl7kDrPasOsx8g29UJuF3DZ9S4suYkDl3-fJo
Enjoy!
thank you very much! seems to work very well!!!!
Nice. One question xposed is working with this rom?
At first I was satisfied with this rom, but after few hours I've come across few problems with it.
1. TOO many unnecessary apps mostly due to t-mobile origin
2. NDR Utils did not work for me
3. Recovery option does not work any more - had to flash it again
4. SU did not work since the beginning.
I start to think that KitKat is the best choice for me right now.
As it was already rooted, I removed the unnecessary apps.
NDR Utils, Recovery, SU all worked for me.
I had problems with the wifi connection: it always dropped the connection even with good reception.
I couldn't charge the phone with a USB2.0 port, only with a USB3.0 port.
Now back to KitKat and no problem at all.....waiting for 5.1 ...
@denishome Additional apps are there, but can be disabled, I wrote about it in the first post. NDR Utils, Recovery, SU all should be working. Looks like something went wrong while you were flashing this ROM. Re-flashing should help.
@bodrovics I didn't notice any problems with WiFi, as for charging issue - I've had some problems while charging via docking station, but that's not specific to this ROM, also earlier when using .270 it was the same. It charges but slower than straight via USB and not always to full 100%. Have to look a bit more into it, possible that it's a fault of my docking station.
The only real problem for me is battery drain in Lollipop 5.0 in general. After I updated to this ROM battery life improved over .270, possible that it was due to the fact that I have made full wipe. I didn't do full wipe while upgrading from 4.4.4 to 5.0 for the first time, firmware .270 and battery life was tragic. Now I can reach 24 hours, but it's more or less 60%-70% of what I was getting with 4.4.4 (I do use Stamina Mode).
@oiseau Xposed works, I'm using it. Seems Amplify helps with battery life while we're at Xposed modules
@doenen thank you for your kind words. What are your observations after few days, still no issues?
denishome said:
At first I was satisfied with this rom, but after few hours I've come across few problems with it.
1. TOO many unnecessary apps mostly due to t-mobile origin
2. NDR Utils did not work for me
3. Recovery option does not work any more - had to flash it again
4. SU did not work since the beginning.
I start to think that KitKat is the best choice for me right now.
Click to expand...
Click to collapse
1. Unistall them
2. They work ok
3. It works as always
4. SU working fine.
Ok, now sh*t got really messy
I'm unable to run any sort of recovery. No matter what I do, I can't go into recovery mode. I've tried flashing via fastboot TWRP recovery and still no result.
I've also tried to "install" recovery from the instructions from this link -> http://forum.xda-developers.com/showthread.php?t=2647480 with no luck doe.
any suggestions?
@denishome off the top of my head, what I would do
1. Read the sticky Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More...
2. Proceed with flashing stock ROM (FTF file)
3 root the device
4. install Recovery.
5. (optional) flash other pre-rooted ROM if needed.
Maybe you wanted shorter method but this one will surely work.
Just read the sticky before you start, download all needed files to your hard drive, it shouldn't be a problem for you it's not a hard process to follow.
Hey! The ROM was working well for me however I think KitKat is a lot more efficient concerning battery life. Since I find this to be one of the most important aspects of a ROM I switched back to modified stock KitKat.
Xposed, CWM, root, everything was working fine...
ok just to give a little heads up for the future users. If you encounter by any chance same problems as I did, simply update your kernel to be able to go into recovery - for me this worked flawlessly -> [5.0][Kernel Z1C][.283 source][V 3.1] RockZ1L Kernel [29/06/2015]
Hi, just a quick question I don't have any custom recovery installed at the moment since I lost my root when I upgraded to the .270 FW, but would I still be able to flash my phone with the .283 FW via FlashTool?
Can I flash it via Flashtool? (sorry, I'm a beginner to this )
kornelkahh said:
Can I flash it via Flashtool? (sorry, I'm a beginner to this )
Click to expand...
Click to collapse
No, You require a recovery(TWRP) to flash it.
Hi guys,
I've downloaded with XperiFirm the latest available firmware customized for Central Europe and created a prerooted .zip with PRFCreator.
Some details about the used FTF file:
Code:
Device: Xperia Z1 Compact (D5503)
CDA: 1280-7870
Market: Central Europe 5
Operator: Customized CE5
Network: EURO-LTE
Release: 14.6.A.1.216 / R1D
What is included in the package:
Code:
D5503_14.6.A.1.216_Customized CE5
UPDATE-SuperSU-v2.46.zip
Z1C-lockeddualrecovery2.8.21-RELEASE.flashable.zip
XZDR-2.8.21_Patch.zip
You need to have custom recovery to flash it, and please remember to backup your device.
You use the file at your own risk!
Get it while it's still hot! Download link: http://bit.ly/Xperia_Z1C
WARNING for Xposed users: Your phone WILL BOOTLOOP if you upgrade from a ROM with installed Xposed v74 or older.
You need Xposed v75, this works OK, I have it installed on my phone and works flawlessly.
If you have v74 or older installed now, first you need to uninstall it from within Xposed Installer -> Framework, and only then you should perform update. Don't forget to make a backup before you start
Newest version of Xposed can be found here
No changelog available but this is what we have observed so far:
+ Not vulnerable to Stagefright (including CVE-2015-6602)
+ MX Player + Hardware decoder bug - fixed
+ possible better battery life (subjective opinions of few users)
- some users experienced problems with root / recovery after update, trying to pinpoint the cause of this with a poll...
Enjoy!
Any new features with this version? Is stagefright 2.0 fixed?
I believe it's mostly bugfixes and optimizations - I am just using this for a few hours but initial impressions are positive - system is very responsive and I did not have any issues so far.
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Changelog is nowhere to be found I'm afraid, didn't notice anything in particular in terms of new features or apps between this version and 14.6.A.0.368.
szturchen_pl said:
I believe it's mostly bugfixes and optimizations - I am just using this for a few hours but initial impressions are positive - system is very responsive and I did not have any issues so far.
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Changelog is nowhere to be found I'm afraid, didn't notice anything in particular in terms of new features or apps between this version and 14.6.A.0.368.
Click to expand...
Click to collapse
Thank you very much for your work.
You can record at 60fps in this update??
Is hw+ freeze bug on MX Player fixed?
I got a bootloop when installing xposed v74 on this rom. everything else was working fine!
Can confirm bootloop after flashing xposed v74. So it is no option for me. Pity that.
Gesendet von meinem D5503 mit Tapatalk
@suprememaster, @kislack you are right, IT WILL BOOTLOOP i forgot to mention that, I will update first post right away - you need Xposed v75 if you want to use it. It works OK, I have it installed on my phone and works flawlessly.
If you have v74 or older installed now, first you need to uninstall it from within Xposed Installer -> Framework, and only then you should perform update. Don't forget to make a backup before you start
Newest version of Xposed can be found here
@oviseven666 i haven't used this feature before, but I couldn't find it in camera app so I think you can't record 60 fps - at least not with the default camera app installed.
@bumjrah I do not use MX Player so can't help you there, you will have to try it yourself or maybe someone else who is using the app will.
bumjrah said:
Is hw+ freeze bug on MX Player fixed?
Click to expand...
Click to collapse
I got no freezes yet with mx player and HW+ decoder. scrolling through the video is working fine.
Xposed is also working fine with v75 sdk22
Thinking of upgrading from 14.5.A.0.270, but i read i another thread that someone had problems when upgrading with an unlocked bootloader. That seemed very strange. Should i be concerned or just flash it like a man?
szturchen_pl said:
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Click to expand...
Click to collapse
This could be the changelog for this update.
14.6.A.0.368 is vulnerable to CVE-2015-6602.
I think this update also fixes the charging bug with the magnetic cable. My phone finally charges to 100%. But the led started flashing when it was at 75% till it was fully charged. It has been a long time since kitkat
No Root
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?
suprememaster said:
I think this update also fixes the charging bug with the magnetic cable. My phone finally charges to 100%. But the led started flashing when it was at 75% till it was fully charged. It has been a long time since kitkat
Click to expand...
Click to collapse
Unfortunately not, my phone was charged to 93% with magnetic charger.
skochxxl said:
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?
Click to expand...
Click to collapse
Hi, i had the exact same problem and know the solution.
The reason it did not work is, you need to install lockeddualrecovery (Z1C-lockeddualrecovery2.8.21-RELEASE.installer.zip at http://nut.xperia-files.com/ unzip it and run the .bat on your pc)
And THEN you reboot with the volume keys pressing pulsing. and load the zip file. After it is finished, i also selected wipe cache+darvin or whatever it is called. It installs without problems and with SuperSU.
So now that you know how to do it, you need to find a way to get back to your rooted 4.4.4 and then start from the steps.
(i did just select 4.4.4 .108 in flashtool, selected both wipe checkboxes, and installed that. and then started newroot program and rooted it, and then steps as above)
Hope I could help! I am very sure it will work
skochxxl said:
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?
Click to expand...
Click to collapse
I had a similar problem and lost root too (perhaps installing Dualrecovery .22 over .21 without removing the older one was the culprit).
After long searching and trying this did help me:
http://forum.xda-developers.com/crossdevice-dev/sony/root-how-to-root-5-0-lollipop-t3212108
You need only first flash this firmware 14.5.A.0.270
KingRoot and other similar software did not help.
Unlocked Bootloader - No Root after update
Thanks for the hints! - Now I have 5.1.1 (.216) running with root. What I did:
1. Flashed .108 with Flashtool (.108 is easy rootable and I still had it in my download folder )
2. Rooted with EasyRootTool
3. Installed SuperSU
4. Installed DualRecovery
5. In TWRP (Vol- when starting) I installed this prerooted zip (.216)
Before that I tried the same procedure but used PhilZ Touch to install this zip (5.) and got the same error as mentioned some posts before. So I think the problem could also depend on the recovery and flashing this zip only works with TWRP.
Thanks for your effort!
Installation on a rooted/unlocked phone with xposed v75 via TWRP worked fine. Thank you very much!
Yes,i can confirme the bug with the preerooted zip file posted above also.I was flashing the preerooted zip and lost root.My way was the same.Downgrade to 4.4.4,root with newroot tool and flash my own preerooted zip, but now with TWRP. All work fine now.Its definitly a problem with Philz Touch....
Hi Szturchen_pl , I have xposed 74 , but in Framework , I can not perform uninstall , how can I uninstall please ????
Thanks
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards