Database Users

[STOCK-ROM] [LB/UB] [4.4.4] [Pre-Rooted] C6603 10.5.1.A.0.283 GenericDE DualRecovery

Hi folks
To give something back to the community that always helps other users through countless useful roms, tipps and tweaks, I decided to make the ROM available that I just created to update my Xperia Z to the newest firmware version - Android 4.4.4 10.5.1.A.0.283. I was really annoyed from the bugs (laggy settings menu, battery drain, etc.) of the previous official 4.4.2 ROM, but this one - up to what I experienced until now - really runs like a charm again.
The creation of this firmware was no rocket science and probably most of you could have done it on your own. However, providing the ROM to you may save you some time and enables you a hussle-free update process since you don't have to combine all those tools like SuperSU and Dual Recovery on your own.
Here some facts:
Based on: Official 10.5.1.A.0.283_GenericDE for C6603 (obtained from here, thanks @AlexX-DE)
Pre-rooted using latest SuperSU v2.02 (obtained from here, thanks @Chainfire)
Latest Dual Recovery 2.7.154 Beta included (obtained from here, thanks @[NUT])
Flashable firmware file created using PRFCreator v0.5 (obtained from here, thanks @zxz0O0)
For your information: I came from this firmware from @[NUT] when installing this update.
To install this firmware:
Download this ZIP file
Extract it
Open the extracted folder Pre-Rooted_C6603_10.5.1.A.0.283_Generic_DE_DualRecovery
Connect your Xperia Z to your computer
Copy the flashable.zip onto your SD card
Disconnect your Xperia Z from your computer and turn it off (remember to have it charged to at least 50-70% battery power prior to flashing the firmware)
Boot into one of your existent recoveries - CWM or TWRP (I used TWRP)
Install the flashable.zip located on your SD card, wait for it to be successfully finished
(optional Clear cache/dalvik (I did it)
Reboot
IMPORTANT: Now wait! The reboot can take up to 10 minutes and eventually the screen might keep black showing nothing at the first startup.
When I flashed this firmware the first time and rebooted afterwards, it rebooted and vibrated, but the screen did not turn on for at least 5 minutes and I already thought I bricked it. But just when I started to panic and smash my head against the wall, the screen suddenly turned on and everything was perfectly fine again. It seemed that there was just a slight problem initializing the display for the first time after the flash while booting up and optimizing the apps (you know this process can take quite long, depending on how many apps are installed).
I tried to reproduce this error flashing the firmware again but I couldn't. After the next flash the screen worked fine even when starting the newly flashed firmware for the first time.
So remember, please don't panic when the first startup might take long and the display shows nothing as this is most likely only a temporary condition.
Nevertheless, I of course don't take responsibility for any potential damages or bricks that may be caused using this firmware, although I don't see major risks since it is the official release and I did not change anything at this firmware. Everything you do is on your own risk!
I know there is also a similar release by @luala, but he based his firmware on the swedish SG firmware, mine is based on the german generic DE firmware, so probably of special interest for people from Germany.
In case of any problems or questions, please ask here. Even though I'm no professional developer I'm sure we will find a solution.
If this post was useful to you, please show it by clicking Thanks!
Wish you a lot of fun with your lag-free Xperia Z running on 4.4.4!
ceLsiuZ
@ Mods: Please move to the Development forum if more appropriate, I unfortunately couldn't post there.

You should move this to the development section
TapaTalked from my MultiROM Xperia™ Z (C660²) running Dirty Unicorns OR PAC MAN ROM!

Yeah I wanted to, but I couldnt since I did not have 10 posts yet.
So I guess a moderator would need to do that...
Best regards
ceLsiuZ

Installed
Belgium speaking, I flashed it with CWM recovery, cleared cache and had no black screen delay: phone booted immediately.
Thank you a lot, I'm going to test it now

auricgoldfinger said:
Belgium speaking, I flashed it with CWM recovery, cleared cache and had no black screen delay: phone booted immediately.
Thank you a lot, I'm going to test it now
Click to expand...
Click to collapse
Haha, hello Belgium, that's very good to hear and thanks a lot for sharing your experience!
And, how's the test going?
I'm not quite sure, but could it be that the battery management is not the best again? It's quite misleading, cause after flashing one always tends to using the phone more extensively than before, but somehow I got the impression that the power usage of "Android System" and "Android OS" is relatively high.
But as I said, my impression might be quite subjective - what do others say?

Hi,
flashed it and Xperia stays in black screen.
Had to flash the original ftf file and root it by myself.
But now I dont know which recovery works with 4.4.4 ^^
Have to find it now ^^

if you are rooted, Than install Flashtool and find Advanced stock kernel and flash it, you have your recovery. or try doomlord cwm recovery.

Thank you very much for this. I needed something like this because my C6616 doesnt have official 4.4.4 so far.
I followed your instructions and had no problems at all.

Thank you very much for the file.
Flashed it through CWM, only wiped cache after and worked perfectly! only issue I had was a missing baseband directly after rebooting but that was fixed after the second reboot (or just some time waiting).
Came from eXistenZ Ultimate 1.5.5

It worked!
Hi,
thanks to celsiusZ !!
I just flashed with TWRP, wiped cache/dalvik cache, rebooted. No black screen, reboot took about 2 minutes. All seems to work!
Greetz!

Danke!
I also flashed it on a pre-rooted phone (with locked bootloader) with t-mobile Austria branding using TWRP without any problems.
The phone is still rooted, SuperSU still works, as does TWRP.
Even after a factory reset everything works fine.
thx!

Nice thanks, perfect found on my Z :good:

PHP:
imm1304 said:
Thank you very much for this. I needed something like this because my C6616 doesnt have official 4.4.4 so far.
I followed your instructions and had no problems at all.
Click to expand...
Click to collapse
Man I have the C6616 and it was officially updated to 4.4.4 , but I don't know how to root my phone, do you know how to do that? Thanks

So this is safe to flash on the C6606 TMO USA? I'm on the stock 4.3 firmware and not rooted and locked

do i have to do something other if i come from 5.0 AOSP?
except format data

oskarhds said:
PHP:
Man I have the C6616 and it was officially updated to 4.4.4 , but I don't know how to root my phone, do you know how to do that? Thanks
Click to expand...
Click to collapse
Hi, just saw this message late. For me, the best route was to root the bell 4.4.2 I was on using the towelroot.apk and then flash the pre rooted latest rom. I remember 4.4.4 root being more complicated as outline here in the forums so I decided to skip that route.

Hi need help
I flashed your rom, im successful at doing it but, i cant use gplay and i cant hard reset my phone, i just want to ask if u can help me with it? And if i use the companion to repair the software it will be back at bsod state, sorry for the grammar TIA

Couple of post rooting/flashing questions and assumptions

Yesterday I bit the bullet, rooted and flashed my N9005 with CWM and Temasek's CM12.1 rom.. and wow, wished Id done this sooner..
Device is now so clean and slick, and I just need to hunt down and find the apps I want to put on. I did think I may lose some functionality, but I wasn't a heavy user of some of the Note's features, so wasn't too worried, and since I found Spen Command, the stylus is now better than before!
The process was very easy, and the guides I used were very good.. however, I seemed to have some screens that weren't referred to or documented, and although everything seems to be working.. I just had a few question...
After I used ODIN to install CWM Recovery, the phone booted, however, the guide implied the device should fully reboot to then copy SuperSU... but I was prompted with a recovery menu asking if I wanted to root the phone, so I said yes.. then rebooted to copy the SuperSU over, reboot into recovery and install the zip, rebooted and confirmed root.
Nothing I had read had mentioned about the first menu asking if I wanted to root, and I thought the rooting process was the installation of SuperSU?
I then flash the ROM and Gapps... few issues at first, but after applying the Rom OTA update, all is well! SuperSU is gone, but I assume that being a Custom Rom it is essentially already rooted so doesn't need it.
I installed CW Rom Manager but this actually told me the latest version of recovery was actually older than the one I had installed, and that my devices wasn't actually supported... Also, much of the content available through it seem out of date, so I removed it.
Think ill stick with this ROM anyway and await the Offical Note3 CM12.1.. although not really seeing much info about it, so don't even know if it will!

DocSoton said:
Yesterday I bit the bullet, rooted and flashed my N9005 with CWM and Temasek's CM12.1 rom.. and wow, wished Id done this sooner..
Device is now so clean and slick, and I just need to hunt down and find the apps I want to put on. I did think I may lose some functionality, but I wasn't a heavy user of some of the Note's features, so wasn't too worried, and since I found Spen Command, the stylus is now better than before!
The process was very easy, and the guides I used were very good.. however, I seemed to have some screens that weren't referred to or documented, and although everything seems to be working.. I just had a few question...
After I used ODIN to install CWM Recovery, the phone booted, however, the guide implied the device should fully reboot to then copy SuperSU... but I was prompted with a recovery menu asking if I wanted to root the phone, so I said yes.. then rebooted to copy the SuperSU over, reboot into recovery and install the zip, rebooted and confirmed root.
Nothing I had read had mentioned about the first menu asking if I wanted to root, and I thought the rooting process was the installation of SuperSU?
I then flash the ROM and Gapps... few issues at first, but after applying the Rom OTA update, all is well! SuperSU is gone, but I assume that being a Custom Rom it is essentially already rooted so doesn't need it.
I installed CW Rom Manager but this actually told me the latest version of recovery was actually older than the one I had installed, and that my devices wasn't actually supported... Also, much of the content available through it seem out of date, so I removed it.
Think ill stick with this ROM anyway and await the Offical Note3 CM12.1.. although not really seeing much info about it, so don't even know if it will!
Click to expand...
Click to collapse
Seriously dude. Go to temaseks thread and care to read at least first two posts. Please do it for all roms. Because if you did you would know that :
TWRP is RECOMMENDED.
To get root access you have to flash SUPERSU in RECOVERY. In that rom at least.
Unbelievable

[D5503][Stock][PreRooted][DualRecovery] 14.6.A.1.216 Customized CE5 (Central Europe)

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

Help! Marshmallow 6.0.1 ROM has been flashing for hours!

Over the weekend my Nexus 4 decided not to start. Saturday night it was working, and I hooked it up to charge. By Sunday morning it had turned off. When I restarted it, it got as far as asking for my password (encryption key), and then the four circles just danced around for hours. After letting it sit for a few days, the phone started again. But the experience made me decide it was time to update the system from Kit Kat.
So, more or less, I followed the instructions on the Team Android site. (As a new member of this forum, I'm not allowed to include the link. But Google "Update Nexus 4 to Android 6.0.1 Pure Nexus Project Marshmallow Custom ROM.") The main differences were (1) I only copied the ROM file over and (2) I used TWRP instead of CWM for the recovery. I was having trouble copying the Gapps file, so I thought it would be easier to install Marshmallow first and do the apps later.
Everything was backed up and copied around 7 PM yesterday, when I then wiped the data, did a factory reset, wiped the cache, wiped the dalvik cache, and finally started the installation. It's now almost 1 AM, and the ROM is still being flashed.
What should I do next?

Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.

mohsinkhan35 said:
Well it seems like the ROM you downloaded is a corrupt zip file.
I would like you to go to Original Development and download one of the ROMS from there, and then google opengapps, choose, ARM>6.0.1>Pico package (or any other package of your choice). I recommend Pico for your first install which is barebones google play services and Google Play store.
TWRP is perfectly compatible with most recent roms.
And for 6.0.1 , Flash the ROM and then flash GAPPS right away. After flashing, wipe dalvik/cache and then reboot.
If you have any questions, do not hesitate to post them here. good luck
EDIT: If you want Vanilla android with zero modifications, get this one:
http://forum.xda-developers.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900
Also, if it helps, I got 4 hours of Screen On Time on this ROM, I never got it on any other ROM so it is very light and is exactly what you would be getting on a nexus device.
Click to expand...
Click to collapse
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?

Von Neumann said:
Thanks, Mohsinkhan35. I followed the link you included and downloaded the ROM and TWRP 3.0.0-0, as the site requires. (I currently have TWRP 2.7.1.0 installed.) I was unable to download the Pico Gapp from that site, since the link seems to be broken. No problem. It's available from lots of locations.
So, as I understand it, my first step should be updating TWRP. I found instructions on how to do this at PhoneArena.com. Although written for Windows users, basically one starts the phone in bootloader mode and then uses adp commands to flash the new recovery (TWRP file).
But now Android File Transfer is not connecting to the phone. I wouldn't expect it to connect if the phone wasn't booted, as the file system is encrypted. Nonetheless, I tried this way without success. Then I tried using bootloader mode, with similar results. I then booted up in RM and got into TWRP, but AFT still doesn't see the phone. This is not altogether unexpected. If the new OS has settings and drivers to connect to my computer (a Yosemite iMac), and I've wiped the old one to make way for the new install, then how can the phone communicate with the PC?
For each of these cases (normal start, bootloader, and RM), I also tried issuing "adb devices" from a command prompt, but it's also returning nothing.
So any suggestions for the next step?
Click to expand...
Click to collapse
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!

Von Neumann said:
NEVERMIND!!!!
Experimenting with several different USB cords and ports finally yielded a good connection! Even a native USB port on the back of the iMac didn't work, and neither did some of the ports on my USB 3.0 (2.0 compatible) hub. But finally one worked, and I ran with it. Currently reinstalling my apps on the shiny new Marshmallow system!
THANKS Mohsinkhan35!!!!!
Click to expand...
Click to collapse
Sorry about the late reply Von I just saw your replies, I am glad that you got it to work!!
For Future purposes, The easiest way to update TWRP is to download the .img from TWRP, put it on your phone, go to TWRP recovery, and instead of flashing .zip file, choose .img from dropdown list, then select the image file, select recovery option from the list.
Enjoy your new system! Which MarshMallow ROM did you end up flashing?
I found that MM breathe a new life into my Nexus, can't imagine going back to Lollipop, I don't know how you managed to stay with KitKat haha

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

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.