Database Users

[INFO] 8.2.3.12 modded update

This is a quick mod for those who would like to apply the new patches but retain root.
This is the 8.2.3.12 US mod, it installs the new kernel and all patches. The mod is so it can run from clockwork and also adds root/superuser to the patch. This mod includes the 208 keyboard flash. If you want 209 it needs to be copied to the /system/etc/EC folder.
The original patch did not include the new kernel or the vold/netd patches Without those the sd slots did not work and the dock % did not show.
You will need to start with a clean 8.2.3.9 rom, one can be downloaded from ASUS support. If you have already upgraded to 3.12 or 3.13 you can use the asus rom to downgrade. Next use gingerbreak and install clockwordmod using the existing guides. Once that is done you can then run this update using clockwork. This patch mounts system so no need to manually do it.
Im not a rom builder and this is just a quick patch to get 8.2.3.12 and root so use at your own risk. It does'nt touch the bootloader or the recovery image so you should always be able to recover with clockwork.
http://www.megaupload.com/?d=PLPA389X
MD5 Hash:71b8e3f039912f0ccc5a41d650fd2adf
Edited with new info.

I got assert failed: apply_patch_check("system/app/AWS.apk" ..

That would mean the md5sums not match. Besdes clockwork mod are you sure your comletlely stock?

Is this US, WW, or does it not matter?

i got a similar error. im rooted and thats all.
Sent from my US Transformer TF101 using Tapatalk

The error is probably because system was not mounted. You have to have the new kernel in order to get the dock % to show. I am tweaking that and adding in root and will post a new patch shortly.

I updated the first post with a new version. It should take care of the install issues as long as your stock. It adds the new kernel and the vold patches back since they were needed for % and sd cards. It also adds root/superuser.apk. Please let me know if there are any issues.

superdave said:
I updated the first post with a new version. It should take care of the install issues as long as your stock. It adds the new kernel and the vold patches back since they were needed for % and sd cards. It also adds root/superuser.apk. Please let me know if there are any issues.
Click to expand...
Click to collapse
Thanks superdave!
Just one more favor, could you verify for me if the md5 has of the file i downloaded is correct?
8.2.3.12_with_root.zip 71B8E3F039912F0CCC5A41D650FD2ADF

That is the correct md5 71b8e3f039912f0ccc5a41d650fd2adf
There is no bootloader or recover image in there so it is not as critical to check, but, its always good to know you have data integrity. I'll add the md5 to the first post.

Same checksum I got

so can someone else that this works before I try it..

kingrat said:
so can someone else that this works before I try it..
Click to expand...
Click to collapse
Works perfectly for me. Took a while to boot for me after the installation but i think that's normal.

superdave said:
That is the correct md5 71b8e3f039912f0ccc5a41d650fd2adf
There is no bootloader or recover image in there so it is not as critical to check, but, its always good to know you have data integrity. I'll add the md5 to the first post.
Click to expand...
Click to collapse
Thank you!
I don't want to come back again and say that its not working without checking if my downloaded file is corrupted or not.
I've flashed it and works flawlessly. I still got my root.

It worked ok for me, after restart I made sure it was ok checked the build no. and kernal, and shut off. then I attached the dock and restarted, it showed update redady for dock so I downloaded it. So now I have build no 8.2.3.13-20110511, kernal 2.6.36.3-00004-go69b8b5, and the dock ver shows EP101-0209, dont know what it was before.. It said after the download it was installed to the dock.. So will I later get the 8.2.3.9 upadate or will the next one be to OTA that is supposed to come in a week or two??

I cannot update, It is failing on Polaris Office. Likely because I removed it, Any workaround. Can someone post that apk so I can put it back?
Thanks!

this worked for me. thanks!!
www.asustransform.com
Sent from my Transformer TF101 using Tapatalk

superdave said:
This is a quick mod for those who would like to apply the new patches but retain root.
This is the 8.2.3.12 US mod, it installs the new kernel and all patches. The mod is so it can run from clockwork and also adds root/superuser to the patch. This mod includes the 208 keyboard flash. If you want 209 it needs to be copied to the /system/etc/EC folder.
The original patch did not include the new kernel or the vold/netd patches Without those the sd slots did not work and the dock % did not show.
You will need to start with a clean 8.2.3.9 rom, one can be downloaded from ASUS support. If you have already upgraded to 3.12 or 3.13 you can use the asus rom to downgrade. Next use gingerbreak and install clockwordmod using the existing guides. Once that is done you can then run this update using clockwork. This patch mounts system so no need to manually do it.
Im not a rom builder and this is just a quick patch to get 8.2.3.12 and root so use at your own risk. It does'nt touch the bootloader or the recovery image so you should always be able to recover with clockwork.
http://www.megaupload.com/?d=PLPA389X
MD5 Hash:71b8e3f039912f0ccc5a41d650fd2adf
Edited with new info.
Click to expand...
Click to collapse
Hey, what did you have to do to make it rooted? How would I do the same with the 13 ota that was just released? Thanks! I'm in the #asus-transformer channel of that's a better place to explain.
Sent from my PC36100 using XDA Premium App

To root the mod just adds su and superuser then sets the permissions for them. To make it be able to run from clockwork you need to remove the key checks and youll want to remove the recovery image from the blob.
If you want to run .13 the prime rom is a very good rom that is now based off of .13. The gingerbreak vold exploit was patched in .12 and .13 so youll need to downgrade if your already running the ota. You can use the 8.3.9 update from asus support to do that.

superdave said:
To root the mod just adds su and superuser then sets the permissions for them. To make it be able to run from clockwork you need to remove the key checks and youll want to remove the recovery image from the blob.
If you want to run .13 the prime rom is a very good rom that is now based off of .13. The gingerbreak vold exploit was patched in .12 and .13 so youll need to downgrade if your already running the ota. You can use the 8.3.9 update from asus support to do that.
Click to expand...
Click to collapse
Yea, I'm not on the OTA yet. Just rooted. Going to back up a few things with Titanium Backup and then try flashing Prime. Pretty excited! Thanks for the tips on rooting an update. I don't like waiting for things so knowing that I could do it myself when the next one rolls out is good for me.

Thanks for posting this superdave!
I'm trying to map out what combinations of tablet/dock firmware display the independent dock battery meter. Here's what I've got so far:
Known to display dock %
-Tablet 8.2.3.12 + Dock 208
Known to NOT display dock %
-Tablet 8.2.3.9 + Dock 209
-Tablet 8.2.3.13 + Dock 209
Unknown
-Tablet 8.2.3.9 + Dock 208
-Tablet 8.2.3.12 + Dock 209
-Tablet 8.2.3.13 + Dock 208
Anybody tried any of the above 'unknown' scenarios? I'll probably do some testing tonight, but would appreciate any feedback in advance.

[Q] How to install Aurora ICS on default 2.2.1

Hey!
I've been looking at ways to make my phone a little bit faster as well as more aesthetically pleasing, and i ran into the Aurora ICS 4.03 - thread.
However, i have next to no knowledge of smartphones and android, and i am completely baffled by the instructions, and i can't seem to be able to find a noob-friendly guide to installing the ROM.
Can you fine gentlemen help a beginner along?
The thread had links to two different guides, one of which made no sense to me plus it was a guide to convert from Cyanogenmod to the Aurora ICS, thus useless to me, while the other referenced a rooting tool that had no working download link and the one torrent i found for it, the program didn't work at all.
TL;DR; Need help, have no android mod experience.
Model n. U8800
Android v. 2.2.1
Baseband v. 129005(Whatever this is)
Kernel v. 2.6.32.9-perf

Simply install the latest 2.3 update from Huawei then follow the steps on opening message of the Aurora ICS topic.
So you have to:
- download and install the 2.3 official update
- root the 2.3, for instance with GingerBreak
- install CWM recovery, e.g. [RECOVERY][04.01.2012][U8800] ClockworkMod [v5.5.0.4]
- go to CWM and do a factory reset
- still on CWM flash the ics-aurora zip
and you're done.

VuDuCuRSe said:
Simply install the latest 2.3 update from Huawei then follow the steps on opening message of the Aurora ICS topic.
So you have to:
- download and install the 2.3 official update
- root the 2.3, for instance with GingerBreak
- install CWM recovery, e.g. [RECOVERY][04.01.2012][U8800] ClockworkMod [v5.5.0.4]
- go to CWM and do a factory reset
- still on CWM flash the ics-aurora zip
and you're done.
Click to expand...
Click to collapse
Thanks, i just updated to 2.3.5, but z4root started freezing and crashing. I'll try out gingerbreak.

SuperOneClick do the job

Loureiro said:
SuperOneClick do the job
Click to expand...
Click to collapse
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.

pepejovi said:
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.
Click to expand...
Click to collapse
try doomlord method. worked for me. make sure your computer is able to run adb platform.

Loureiro said:
try doomlord method. worked for me. make sure your computer is able to run adb platform.
Click to expand...
Click to collapse
...What? Never done this before mate, you're going to have to explain that a little more..

pepejovi said:
Didn't work, it wouldn't find my phone for some reason.
Also, Gingerbreak doesn't work either. Ran it thrice already, each time for at least 20 minutes, no go.
I've been at this for at least 4 hours already, constant problems.. About to throw in the towel.
Click to expand...
Click to collapse
Do you have you USB drives installed correctly? When i rooted my phone i had no issues with SuperOneClick. Also, are you using USB debbuging? I think mine only worked when i turned that on.

Driftie said:
Do you have you USB drives installed correctly? When i rooted my phone i had no issues with SuperOneClick. Also, are you using USB debbuging? I think mine only worked when i turned that on.
Click to expand...
Click to collapse
Looks like i was using SuperOneClick 2.3.2 version, downloaded the 2.3.3.0 version and it's rooting right now just fine.
At least i think it is.
It's at Step #7 of Shell rooting device... Not responding. Should that happen?

I will give you a step-by-step guide.
-First turn off Fastboot, under Settings->Applications->Fastboot
-Check Unknown Sources
-Go to Development-> check usb debugging and allow mock locations.
now go to your home screen and open the dial and enter this code:
*#*#2846579#*#*
->ProjectMenu - >background... -> Log dump -> Log on.
Restart your phone and voila, you're ready to root via SuperOneClick.

Loureiro said:
I will give you a step-by-step guide.
-First turn off Fastboot, under Settings->Applications->Fastboot
-Check Unknown Sources
-Go to Development-> check usb debugging and allow mock locations.
now go to your home screen and open the dial and enter this code:
*#*#2846579#*#*
->ProjectMenu - >background... -> Log dump -> Log on.
Restart your phone and voila, you're ready to root via SuperOneClick.
Click to expand...
Click to collapse
Thanks, the guide i was following did not mention turning off fastboot.
Works now, +Thanks.

grateful thanks

also thanks

[Q] Rooting, Upgrade, ROMs etc.

hey!
I'll be getting my X5 u8800 black this monday.
it comes stock 2.2
and i have had an iphone for quite some time, so im very outdated on the android systems.
Is there a complete guide for this phone on how to root, upgrade, which roms are best etc.? I tried browsing the android development forums, but wasnt very successful in finding too good answers.
My intention anyhow is to get ICS on it(if it's working yet?) and/or possibly install other cool ROM's. Remembering fondly CM with my x10 mini, this would probably where i would start. battery improvement seems to be a must on this phone for my use, and i guess there are rom,apps etc. that are great at these tasks.
if anyone could point out where to look, or where to be reading, i'd be extremely happy.

This is the best topic there is about ICS in huawei U8800:
http://forum.xda-developers.com/showthread.php?t=1492957
Little guide for rooting and installing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1420728
Good backup mirror from the fellow user R4DK0:
http://forum.xda-developers.com/showthread.php?t=1546883
I have latest version of Aurora ICS (2.02) and everything I need for phone is working, but as we all can read from the dzos topic there still are some bugs.

is there a working guide for the 2.2?i need to get a new sd card before upgrading to 2.3, but i would like to root it now anyhow
i tried the guide for 2.3. and superoneclick claims it to be working, but no SU command pops as one would expect. it does not show in root check, root explorer and other root checking devices either...

erkkiboy83 said:
is there a working guide for the 2.2?i need to get a new sd card before upgrading to 2.3, but i would like to root it now anyhow
i tried the guide for 2.3. and superoneclick claims it to be working, but no SU command pops as one would expect. it does not show in root check, root explorer and other root checking devices either...
Click to expand...
Click to collapse
Did you follow exactly the specified steps?
Maybe you didnt enable log? or maybe you enabled the usb cable to the PC?
I am only asking cause you might have slipped a step and noone else had any problem using this guide
http://forum.xda-developers.com/show....php?t=1420728

didnt work with superoneclick, but managed to root it with superboot from modaco

So,
I followed the guides for rooting, installing cmrecovery, and installing aurora.
stuck on aurora bootscreen now...for about 20 minutes...what to do!

erkkiboy83 said:
So,
I followed the guides for rooting, installing cmrecovery, and installing aurora.
stuck on aurora bootscreen now...for about 20 minutes...what to do!
Click to expand...
Click to collapse
Did you wipe data/factory reset, cache partition and dalvik(this one is in advanced subfolder) before installing aurora.zip?
All of these should be wiped in first time. When you upgrade 2.0x to the newer version then only cache and dalvik needs to be wiped.

It's imperative that you upgrade to the official 2.3 version from Huawei before installing any ROM based on the 2.6.35 Linux kernel. Note that there are several 2.3 updates due to severe bugs in the earlier ones. Also note that only some of them come with an unlocked bootloader. You'll make your own life easier if you get one of those, as you won't have to root the system first then (in fact, you don't need to root 2.2 before installing CWM on it), only enter the pink screen and copy CWM over. As far as I know, the B518 update is the latest you should install. Get it from R4DK0's mirror: http://qrac.zapto.org/Stock%20ROMs/U8800V100R001C00B518G001%20(Beta1.0)(Overseas%20Normal)(Gingerbread).zip
Install that (copy dload folder to SD card, turn off phone, hold volume up+down + power), then download one of the 2.3 CWM recoveries, 5.0.2.7 or 5.5, and install that. Now you can flash any 2.6.35 based ROM, including Aurora.

[GUIDE] How to: Install CM10.2 on LOCKED bootloader [Xperia SP]

Disclaimer:
I am not to be held responsible for any actions that you take by following this guide that result in harm to your device. Sony devices are almost impossible to brick.
pre-requirements:
You're going to need the following things:
Flashtool
CWM Xperia SP Package
.266 4.3 kernel
.257 firmware
DooMLoRD easy rooting toolkit
CyanogenMod 10.2 Package & gapps
Step 1:
extract Flashtool, place the .257 firmware file in the firmwares folder and then run flashtool, flash the .257 firmware. This process could take 5-10 minutes.
To do this, click the electric bolt symbol in FlashTool, and select Flashmode, select .257 and then when the prompt says to connect your device in flashmode, power off your phone and holding volume down, plug your phone into the computer. This will then flash the files.
Turn your phone back on and enable USB debugging in android development settings.
Step 2:
Extract DooMLoRD's easy rooting toolkit and make sure that you have your phone connected and adb is enabled, while the phone is powered on run the script and this will then root your phone, do this by double clicking runme_win.bat, your phone will reboot in this process and it will be rooted.
Step 3:
Time to install a custom recovery, unpack the CWM Xperia SP package listed above. Make sure your phone is still turned on and in adb mode (USB debugging enabled) and then run install.bat from the package. You will need to accept a superuser request prompt on your phone meaning that you will need your phone screen on. Recovery is now installed.
Step 4:
Copy the CyanogenMod 10.2 package & google apps package to your phone, reboot into clockwork recovery by pressing the volume UP button once when you see the blue LED light up and feel a short vibration while your phone is booting. In CWM choose factory reset, and then install the two files we put on your phone using install zip from sd card option. Use volume rockers to navigate and power button to select options. Make sure you install CM zip then Google apps zip
Step 5:
After installing the ROM, power off your device in CWM and then connect your device in FlashMode again (hold vol down while plugging into computer) and then flash the .266 kernel only file. Reboot your phone.
Step 6:
Enjoy! You now have CyanogenMod and CWM installed on your phone, even with a locked bootloader. Recovery is now accessed with volume down.
I appreciate thanks greatly, and any issues I can help with and you can discuss them in this thread. I hope I have helped.
KeiranFTW

awesome

That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk

can this rom be flashed on ROOTED device running 4.3

zolaisugly said:
That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I don't see why it can't be as stable as normal CM.. The only thing that isn't working at the moment is GPS, everything else to be honest it runs smoother than stock.
I'm going to work on getting AOKP to work if they have a compilable 4.3 branch. I'm also going to try and encourage ROM devs to add locked bootloader support and I shall show them how
pchetan2 said:
can this rom be flashed on ROOTED device running 4.3
Click to expand...
Click to collapse
Just follow the steps, if you have CWM installed on your XSP with 4.3 already all you need to do is flash the ROM in CWM nothing else..
I posted method for 4.1.2 because I'm presuming the user does not have root, and this is only rootable firmware.
Sent from my C5303 using Tapatalk

Awesome job to able get this rom on my lock xperia sp bro. And also am looking forward from you ,that you will bring other roms on my lock xperia sp which is the best phone ever.:good:

To have root on CM I need to flash SuFix as in existenz?

I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk

radeon6002 said:
To have root on CM I need to flash SuFix as in existenz?
Click to expand...
Click to collapse
Nope, su binary is included and root is already in the ROM.
CyanogenMod also features its own root permissions app (Settings -> Superuser) so you dont even need to install supersu or any equivalent, it works out the box.
zolaisugly said:
I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Theoretically yeah, these scripts should run. I will look into it soon
Sent from my C5303 using Tapatalk

I had just posted a thank-you in another thread for the same - outstanding work. A big thank-you from one who prefer not to touch the BL
And thanks for the lucid instructions. Will download the stuff when I am off work.:good:

yeah i did it succesfully ..need to wipe data and factory reset .then install the rom and gapps....... thank you a lot

Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!

headache59 said:
Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!
Click to expand...
Click to collapse
If you flashed the .254 kernel your Phone won't boot...you just get a bootloop. You need. 266
don't downgrade kernel without downgrading rom as well.
Sent from my C5303 using Tapatalk

Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks

neXus PRIME said:
Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks
Click to expand...
Click to collapse
No need to, I am creating build repository that will be able to build CyanogenMod using the cyanogenmod build system, basically I just add the files that are needed for the hack into the repository and then I will be able to build CM and flash it straight off - I'll do this so when the ROM is built it includes recovery and hijack in the /system partition and so when you flash it, it will still be there.
As soon as I get access to a build server I will build AOKP for locked bootloader (jb-mr2)

All work except my wifi. It's grayed out. I got data though...
Just to note: that I was on 4.1.2 (254) rooted when I flashed this rom and GAPPS. After which I flashed the 266 kernel.
Edit:
I did a factory reset under recovery (CWM) and now my wifi has turned on (blue). Unfortunately I am away from my wifi (home) point, so can't test it out fully.
Back to reinstalling of data...

babicsbalu said:
Well done, nice job! :highfive:
Click to expand...
Click to collapse
Don't quote the whole post.

Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?

Oblox said:
Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?
Click to expand...
Click to collapse
The link on both threads only feature the .266 kernel - for use after installing cyanogenmod.
The .257 is the full firmware for rooting purposes.
I have already rooted my SP previously therefore, I merely installed CM and flashed the .266 kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - worked for me.

headache59 said:
The link on both threads only feature the .266 kernel.
I flashed the kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - and it worked for me.
Click to expand...
Click to collapse
Ahh ok, does the countries kernel make any difference whatsoever?

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.