Installing the best ROM nowadays for Defy (+) - Defy Q&A, Help & Troubleshooting

Hello everybody I got brand new Motorola Defy+ and I want to have newest version of android on it. I am not familiar with rooting etc and unsure if this is possible theres instruction in videos description on youtube "How to Install Android Nougat on Motorola DEFY+ (Android 7.1.1/CM14.1)" ( I can not post links) If not I am curious what is the safest and easiest way to root the device and if theres available newer system than KitKat for my device
Moreover I wanted to install roehsoft ram expander as the phone got only 512 MB of RAM but test says it has to have compatible kernel from what I remember. Not sure if I have to install new operating system in the first place and then root the phone or the opposite and what kernel it has to have to work properly. As I said before I am not experienced android user its my first device with this system
Thank you in advance ppl peace!

Amazing, Motorola Defy+ is cool in its segment but can this slim hardware keep up with such a bulky Android version?
It's said in KittyKat threads here phone has a tendency to stutter with KK (as such a demanding OS), and how about Nougat?
Anyway it'd be nice if somebody adjust Nougat to work worth Defy+. Especially it is needed to optimize battery consumption in idle.

And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck! ?

pawwaap said:
And about rooting, you can just run apk called FramaRoot and job is done
Afterwards run SndInitDefy_2.3 and you will have custom recovery installed (CWM), it is just as simple as it!
http://cloud.tapatalk.com/s/5965fe184202f/Framaroot-1.9.3.apk
http://cloud.tapatalk.com/s/5965fe43f2a32/SndInitDefy_2.3.apk
Afterwards, make a nandroid backup and, using already installed custom recovery CWM (which is clumsy, without touch support), you may want to flash TWRP. If so then flash defy_twrp_recovery_2.6.3.0.zip, e.g. from this link:
http://d-h.st/users/tejus.k.v
Although attention: this flashes recovery TWRP to the system partition (probably the phone's recovery partition is to small) overwriting the android system which is already there, so after doing this you must flash some ROM.
It is described in the second post of this KittyKat ROM thread: [ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]
And see Installation Instructions section, good luck!
Click to expand...
Click to collapse
Thank you for your help! My phone dont want to turn on anymore. I've done everything carefully up to the following point"Wipe /data, /cache, and /system in TWRP or use defy_safewipe.zip" (after that I wanted to flash this: "Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip" cos its ROM right?), but and when it asked me to slide back to the right blue arrow to confirm, my phone booted up and then died after motorola logo. Green led lighted up before death. It seems that it wasnt safe thing despite the name. What to do now? Can I recovery it?
--
UPDATE: ok its working again :angel:, Ive tried combo "up volume" and "power" buton.
Now Ive got no idea what "Gapps" or "Slimroms addons you want" are, but after mad long startup (with SlimKAT logo on the screen), it seems that this system is working. Its much faster than befo I can see. It's RUNNING! :laugh:
--
UPDATE 2: Play Store refuses to open on this new system after I installed it. "Unfortunately, Google Play Store has stopped."

I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)

pawwaap said:
I have just flashed this ROM:
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+), it is the most advanced so far as I can see, the freshest release is cm-11-20161124-NIGHTLY-mb52x so half a year old.
If you read instructions on this thread you can see it's installation is somewhat tricky.
It includes rearranging partitions layout and sizes.
If you really want experimenting with flashing Nougat you will probably need the technique to change partitions sizes, and you may edit the values inside the resize.zip according to individual needs (post #5595)
And the half of the links from the first post are empty, however in the middle of the thread there are still working links.
After all it's better to follow this version of installing instructions (post #5584)
Also you can find some files here: http://defy.svolkov.name/quarx2k.ru/
I have done partitions resizing, bootstrap, and managed to flash the first ROM, version: cm11.0-defy-newlife.zip,
however wrongly have done cache & Dalvik reset just after resizing (and before ROM flashing): the result is ROM is working well but cannot boot into recovery anyway (and can't recreate recovery anyway either, even doing:
Code:
cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p1
as suggested in the post: https://forum.xda-developers.com/showpost.php?p=57221743&postcount=6510)
And I'd like have the freshest version, the only way is to flash stock and do everything from a start again. Please if you can, how to flash stock? It is said elsewhere the most critical in it is choosing the right version of sbf file, choosing inappropriate would brick a phone irreversibly! And how to know which one to choose, tutorials here are so convoluted and discussions so chaotic! Afraid of touching anything though!
As far as the ROM itself, although it is the first only cm11.0-defy-newlife.zip it works amazingly well!
It boots quickly, is fast, RAM friendly, nice!
(It has little overclocked processor and this makes using the phone so comfortably, just little overclocked so hardware friendly too!)
Click to expand...
Click to collapse
Again I want to thank you for your response. On the verion of system Ive installed I cant use my camera for video recording because of lack of some codecs it says and I cant watch YouTube. 'Google Services' crashes. The only way I could download some decent apps was from 'Aptoide'. 'Roehsoft Ram Expander' needed Google services so it wont open (ive download 'Kernel audiutor' however I dont have class 10 card yet so I dont know if its good at all). I wont be fighting with this anymore, I am going to try mentioned 'CM11 Android 4.4 for the Defy(+)'.
So I have to go "Recovery" in this secret startup menu before I install it? I mean do I have downgrade my system before instalation of new one? Or just follow the instructions straight from the beggining I dunno. But I dont want any complicated things you know..
--
The links are dead, but Ive found them files:
defy.7z
Now, you metrioned two rom's but which one is less tricky, cm11.0-defy-newlife.zip or cm-11-20161124-NIGHTLY-mb52x.zip?

You know, I have installed cm-11-20161124-NIGHTLY-mb52x.zip at last, after exciting night of attempting flashing any stock ROM and then following the procedure exactly from the first post of "[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)"
and the updated files: new_bootstrap and resize, found here
It costed many efforts of blindly "trial and error" flashing one by one stock ROMs, until found the one which turned on my phone with anything else than black screen!
And everything it was to have possibility of flashing cm-11-20161124-NIGHTLY-mb52x.zip instead of already running cm11.0-defy-newlife.zip.
And you know what? The version cm11.0-defy-newlife.zip seemed running better than the freshest one!
It was, what is most important: faster!!!
And anything else seems the same (so far)!!!
Is the any rationale behind hustle and bustle of flashing the "NIGHTLY" and exactly for what?
Question of stability which user gets know only after some time?
Anyway the speed is everything in such thin hardware like Defy+ and i can't resist an impression cm11.0-defy-newlife.zip is way faster!
And what's more, you probably can flash cm11.0-defy-newlife.zip without the whole convoluted procedure of resizing partitions! (needs checking, if you want simplest way you had better resize partitions )
In fact this version of ROM is the same as:
Quarx said:
8. Install cm11.0-defy-newlife.zip (It's latest cm11 from 23sep with changes for new table)
Click to expand...
Click to collapse
but cm11.0-defy-newlife.zip was to try if the only resizing procedure itself worked at all (and for users to send feedback).
In fact resizing partitions is needed only for the next ROM versions (of which the freshest is cm-11-20161124-NIGHTLY-mb52x.zip):
"the nightlies AFTER 01 Oct are for the new partition table".
(Aha, cm-11-20161124-NIGHTLY-mb52x.zip probably is odexed, while cm11.0-defy-newlife.zip is deodexed, it needs confirmation)

And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up! ?

pawwaap said:
And if you needed flashing stock and had doubts how, then write, I'd gladly help and share the knowledge painstakingly acquired this night.
It is amazingly simple and safe, there're few simple basic things but if you needed found them by yourself in this forum you would probably get panicked
It is about how simple things people can mess up!
Click to expand...
Click to collapse
Thank you my friend. Ive installed cm11.0-defy-newlife.zip. Its fine because my camera can now record videos but still it cant play it. :crying:
YouTube videos also wont load, however internet is fast and so on.
--
Google Play still dont work, same error. I kinda came to terms with it as I have Aptoide, but I want to use YouTube..

And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μG) (for apps refusing running without Google Services) and/or Yalp Store for Play Market access
If you insist using bulky Google then try opengapps.org

pawwaap said:
And what do you use to watch YouTube videos? Advise third party apps, e.g. SnapTube etc, instead of YouTube application. In fact forgot installing gapps at all and it makes me happy You only now made me think about it In such thin hardware it is better to have microG (μGl) (for apps refusing running without Google Services) and/or Yalp for Play Market access
Click to expand...
Click to collapse
I guess gapps are apps for new software? Ok so now that I have downloaded SnapTube I still cant play any video. Its loading but wont start just like videos on my phone storage or just recorded
Hah I think its a bit off topic what we made here, I should change name of the tread
--
Ive read on some native forum that after codecs instalation he problem disappeared I try to find some

I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.

pawwaap said:
I have just recorded a video of my dog, sent it via email (AquaMail), received it in a mail to myself and played it with system player, pretty well!
It is possible freshest NIGHTLY ROM has issues solved, how to check it (without Google)?
And can you play videos self recorded with this phone?
OpenGapps.org provides you ability to choose what package, how complex (I always choose "pico"), and for what platform (yes, KittyKat is still supported) you download.
Click to expand...
Click to collapse
OK its seems that Google Play cant be downloaded straight to the phone (.apk) after installing new system but gapps worked for me and I got my Google Play working again now. Still no luck with videos on YouTube but vlc is working on files Ive recorded.

Tritius46 said:
Ive installed cm11.0-defy-newlife.zip.
Click to expand...
Click to collapse
And how have you installed this ROM: with partitions resizing first or on stock layout?
Tritius46 said:
Hah I think its a bit off topic what we made here, I should change name of the tread
Click to expand...
Click to collapse
Yes, you can change for e.g.
"Installing the best ROM nowadays for Defy (+)"
And it is said Defy and Defy+ is the same hardware, just plus is rebranded and has overclocked processor (to 1GHz) and bit bigger battery, see section "Facts" in [GUIDE] All-in-One Defy Beginner's guide
or "Yielding Defy competitive nowadays"
It is still phone unique on the market, searched something for summer, a little waterresistant phone which could suit to any even tiniest pocket. And found Defy is just the only one in this kind, nowadays producers offer big smartphones and if you want something little & watertight then you can buy modern smartwatch - thanx, prefer Defy: bigger battery, faster, and of incomparable comfort of usage, for peanuts! [emoji106]

pawwaap said:
And how have you installed this ROM: with partitions resizing first or on stock layout?
Click to expand...
Click to collapse
Ive just followed the steps here did exactly what is written step by step from the beggining.
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags. Same for vids online, however if I choose mobile version of YouTube and try to play stream in vlc it worx but very poor quality. I tried many things without any success, for eg. Flash Fox but the problem is rather in system files than settings and apps itself.
In my custom system I could playback any video.

Tritius46 said:
Ive just followed the steps here did exactly what is written step by step from the beggining.
Click to expand...
Click to collapse
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Tritius46 said:
I think now the only is playing videos. Videos I have recorded (on the phone) can be played back only in vlc but still with lags.
Click to expand...
Click to collapse
You see, I play with phone system player any videos recorded with phone system camera application without any problem.
Is the newest NIGHTLY ROM better in the sense the issues have been ultimately repaired?
If so, make android backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
(Yet if you enjoy playing with comparing the two system you may wait )
And maybe before flashing next ROM do these newer new_bootstrap.zip & resize.zip flashing (just in case: of avoiding extra issues).
Tritius46 said:
Ive just In my custom system I could playback any video.
Click to expand...
Click to collapse
And in Defy?

pawwaap said:
It's irrelevant for video playing but I think it is better to follow the first post from the thread and use the files:
new_bootstrap & resize (instead of PrepareZip_1 & PrepareZip_2),
new_bootstrap has different size than PrepareZip_1 and is newer, something has been changed.
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
OK so I will try now cm-11-20161124-NIGHTLY-mb52x with new_bootstrap and resize. Do I have to just install them like before right? It will replace system I have now?
--
UP:
pawwaap said:
wipe cache, Dalvik, data (factory reset), and flash the newest NIGHTLY!
Click to expand...
Click to collapse
Ok I get it

If so, make nandroid backup of data partition, reboot into TWRP, wipe cache, Dalvik, data (factory reset), and only then (but immediately without rebooting after wiping) do these newer new_bootstrap.zip & resize.zip flashing!
The files you can find here
After flashing NIGHTLY successfully, boot it, follow the initial wizard etc, check if it works ok, and if so reboot into TWRP again to restore your data nandroid backup.
If you don't care about previous data give in with it and configure your Android anew

pawwaap said:
And in Defy?
Click to expand...
Click to collapse
Dont get me wrong, I meant my system version android which came to me with my phone purchase (android 2.3.6 or something dont remember). And its definitely not prob with camera but system video player, plus YouTube dont play too so definitely some playback issue..

Omg omg E:Error executing updater binary in zip '/sdcaed/kitkat 4.4/cm-11-20161124-NIGHTLY-mb52x.zip' 'FAILED' what todo? Reboot and try again?
Maybe file was corrupted

Related

[Q] Fusion ROM 5.0.2 Galaxy S5 klte. Need Explanation On How You Update it.

Hi,
I have a stable and working Galaxy S5 klte with Fusion ROM 5.0.2.
It's overclocked etc and I'd like to know how to update my ROMl without losing my settings.
I used to run with CM12 5.0.2 but that was easy update with twrp and I still had my setting and the update.
I got twrp here as well and root obviously but I'm not entirely sure how to update this ROM.
Current Fusion verison: Fusion-v5.0-2015-01-27
Dowloaded:
Fusion-v5.1-2015-02-07-fusionsp_klteusc.zip.md5sum(0,13kb)
Fusion-v5.1-2015-02-07-fusionsp_klteusc.zip(252.42 MB)
I just need to know how to install this and keep my settings because my current ROM is very stable and the kernel is up to date.
A little info about what's on it and working:
Working: Camera(amazing photos and 4K recording), NFC, Bluetooth, WiFi, LTE, Viper4android(amazing sound/surround.) And all basic stuff like calling/messages.
No crashes, lags or stutterers. It's smooth like butter(smoother than any iPhone, 6+ and note 4(testet it).
All my apps/games are working perfectly and smooth.
Specs:
klte 5.0.2(obviously) running Nova launcher, usually 1,1gb RAM available.
Antutu benchmark 47.XXX evern up to 48.XXX went above Note 4.
I/O scheduler: vr
CPU: 2,764 MHz
GPU: 657 MHz
DPI: 528
Governors: usually on performance with great battery life and not overheating.
Fast charge enabled and fully working.
I will appreciate it so much if I get an detailed explanation on how to update my ROM but still keep my settings.
You update custom ROMs the same way you update any custom ROM (apart from the very rare cases when the dev included an OTA updater)
Flash from TWRP
*Detection* said:
You update custom ROMs the same way you update any custom ROM (apart from the very rare cases when the dev included an OTA updater)
Flash from TWRP
Click to expand...
Click to collapse
So I just basically go into twrp recovery>install and check the 2 files I have downloaded?
Are you sure about this?
Thanks.
Edit: I can only see one of the files twrp install which is: Fusion-v5.1-2015-02-07-fusionsp_klteusc.zip(252.42 MB) the .md5sum(0,13kb) doesn't show up?
The MD5 file isn't flashable, just to check the ROM is not damaged before flashing
You just flash updates the same way as you flashed the ROM to start with, the updated version is a full ROM, not just an update - so you can flash over the top, or wipe and flash as a new ROM
Generally speaking, I would wipe SYSTEM and CACHE, then flash the ROM & GAPPS, but as it's an updated version of the same ROM, flashing straight over the top will likely work fine (Dirty flash)
*Detection* said:
The MD5 file isn't flashable, just to check the ROM is not damaged before flashing
You just flash updates the same way as you flashed the ROM to start with, the updated version is a full ROM, not just an update - so you can flash over the top, or wipe and flash as a new ROM
Generally speaking, I would wipe SYSTEM and CACHE, then flash the ROM & GAPPS, but as it's an updated version of the same ROM, flashing straight over the top will likely work fine (Dirty flash)
Click to expand...
Click to collapse
The whole point was to update without losing my settings but I guess that's not possible if I wipe system?
Popavalium said:
The whole point was to update without losing my settings but I guess that's not possible if I wipe system?
Click to expand...
Click to collapse
The majority of things like homescreen layout and apps etc are saved in DATA, only actual system settings are saved in SYSTEM
Just go for the dirty flash first, only wipe CACHE - if you run into issues, wipe SYSTEM and flash it again
*Detection* said:
The majority of things like homescreen layout and apps etc are saved in DATA, only actual system settings are saved in SYSTEM
Just go for the dirty flash first, only wipe CACHE - if you run into issues, wipe SYSTEM and flash it again
Click to expand...
Click to collapse
Alright, should I leave Dalvik Cache?
Sorry for so many questions I just need to be sure.
I'll do a backup and go with the dirty flash.
Wipe all CACHES, to put it simply, they are basically temp folders
*Detection* said:
Wipe all CACHES, to put it simply, they are basically temp folders
Click to expand...
Click to collapse
I just tried it both ways and got this.
E: MD5 does not match
E: Aborting zip install
Failed
You copied the ROM.zip and the .MD5 to the phone/microSD before flashing?
If I remember right, with TWRP you can disable MD5 checking before flashing
This whole process is the same as the process you flashed the previous ROM version with, apart from the wiping everything part
*Detection* said:
You copied the ROM.zip and the .MD5 to the phone/microSD before flashing?
If I remember right, with TWRP you can disable MD5 checking before flashing
This whole process is the same as the process you flashed the previous ROM version with, apart from the wiping everything part
Click to expand...
Click to collapse
You can skip doin MD5 on backups with twrp.
But I know that Fusion has his own version of twrp which might do the trick.
Doesn't sound like the TWRP version is the problem if it thinks the MD5 is not matching, unless for some reason this version can not read fusions MD5 files, but worth a shot I suppose
Did you unzip the MD5 if it was zipped?
Maybe the download of the ROM was corrupted
Where did you get it from, I can't see an XDA thread for that named ROM (Could be blind)
*Detection* said:
Doesn't sound like the TWRP version is the problem if it thinks the MD5 is not matching, unless for some reason this version can not read fusions MD5 files, but worth a shot I suppose
Did you unzip the MD5 if it was zipped?
Maybe the download of the ROM was corrupted
Where did you get it from, I can't see an XDA thread for that named ROM (Could be blind)
Click to expand...
Click to collapse
I got it from Fusions downloads/updates in the phone settings, you can also get it from fusions site
I installed fusions twrp and removed Caches did a "Dirty Flash" and it worked. Fusions twrp skipped MD5.
http://www.fusion-rom.tk/
Here's a XDA about it but I didn't get stuff from there, just fusions site.
http://forum.xda-developers.com/gal...op-5-0-1r1-t2961279/post57228165#post57228165
Thank you very much for your time and help. Appreciate it.
Ah good, pleased you got it sorted, yea they must have done something weird with the MD5 if they are providing a modded TWRP to skip checking
Thanks for the links, I`ll check it out
*Detection* said:
Ah good, pleased you got it sorted, yea they must have done something weird with the MD5 if they are providing a modded TWRP to skip checking
Thanks for the links, I`ll check it out
Click to expand...
Click to collapse
No problem.
I was really desperate to get the latest update since I made my settings exactly the way I wanted. And the only thing I wasn't sure of was how to update. Now I got the latest and I'm extremely satisfied.
You should definitely check this ROM out if you have a S5 that supports it.
With the right settings it makes the S5 top tier phone that actually beats note 4 in performance, the speed, ability to overclock GPU, CPU, increase DPI, fast charge, amazing and tons of features. I believe it's the best S5 ROM. It's unbelievable how smooth it is even with animations on it doesn't lag or stutter a single time. Simply a beast. The battery life couldn't be better either. You can see my specs on first the first post.
Take care.
My S5 is still a virgin at the minute, only had it 3 weeks or so, not even rooted yet because I jumped into Lollipop too soon before finding out about KNOX, so for now I'm just biding my time hoping for a root method that won't trip KNOX
I've favourited the fusionROM thread/site though, watched a video of it on YT too, looks a great ROM, definitely one to keep in mind for when I de-flower her
*Detection* said:
My S5 is still a virgin at the minute, only had it 3 weeks or so, not even rooted yet because I jumped into Lollipop too soon before finding out about KNOX, so for now I'm just biding my time hoping for a root method that won't trip KNOX
I've favourited the fusionROM thread/site though, watched a video of it on YT too, looks a great ROM, definitely one to keep in mind for when I de-flower her
Click to expand...
Click to collapse
Oh I see. Well, there are root methods that can bypass Knox. I've read about it before.
I believe it was towelroot or something like that but idk if it's available for lollipop though:/.
You can also mount your SD card normally and save/delete anything from the phone, so all that bull**** is gone with this ROM.
Yea, everything changed with Lollipop, no root methods available without tripping KNOX yet
I`ll eventually fold and root it / recovery / custom ROM, but for now it's still a new toy and I`m happy with it as it is (Ads aside)
Plus I use mobile banking on my phone, and from what Ive read, it's a bit more complicated than just using a root hider to get it working when rooted, so a few things putting me off rooting atm
I've spent the last 4-5 years playing with Custom ROMs and recoveries, CWM, TWRP etc with the TF101 tablet, so I know my way around fine, but thanks to Samsung, things are not as straight forward with the S5/Lollipop/KNOX
Like I say though, it's only a matter of time before I buckle and push the button
*Detection* said:
My S5 is still a virgin at the minute, only had it 3 weeks or so, not even rooted yet because I jumped into Lollipop too soon before finding out about KNOX, so for now I'm just biding my time hoping for a root method that won't trip KNOX
I've favourited the fusionROM thread/site though, watched a video of it on YT too, looks a great ROM, definitely one to keep in mind for when I de-flower her
Click to expand...
Click to collapse
*Detection* said:
Yea, everything changed with Lollipop, no root methods available without tripping KNOX yet
I`ll eventually fold and root it / recovery / custom ROM, but for now it's still a new toy and I`m happy with it as it is (Ads aside)
Plus I use mobile banking on my phone, and from what Ive read, it's a bit more complicated than just using a root hider to get it working when rooted, so a few things putting me off rooting atm
I've spent the last 4-5 years playing with Custom ROMs and recoveries, CWM, TWRP etc with the TF101 tablet, so I know my way around fine, but thanks to Samsung, things are not as straight forward with the S5/Lollipop/KNOX
Like I say though, it's only a matter of time before I buckle and push the button
Click to expand...
Click to collapse
I know exactly how you feel. The temptation to unleash all that power and speed is so strong. Not to mention the ability to outperform your friends new note 4 or any other top tier smartphone they get, just too much fun. I'm less experienced than you so I was a bit scared about the same things but in the end the urge won. And I don't regret it at all. Samsung's bloatware and stock ROM with touch wiz is just slow and unattractive. But yeah, it can satisfy you for a while the moment you get if.

[GUIDE] Flashing ROMs to the Vivo Air

Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?

J500FN rapidly running out of space

As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
webelan said:
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
Click to expand...
Click to collapse
Hi Anne,
We all have the same trouble with storage on our J5.
If you chose to root your phone then yes you will be able to uninstall alot of the bloat ware that is on your phone.
You will also have the option of using adaptable storage.
There are lots of threads on here that will guide you through the process. Just make sure that you read the guides properly and download and install the CORRECT zips.
I don't know if the one click root is safe to use.
I would advice installing TWRP and then flashing super su. Again all of the guides are on here.
If you do install TWRP via Odin then you will have the option of flashing custom ROMs..
Have a good look at the guides. Ask all the questions that you need to. People in here will be happy to help.
It's really nice to see you on here
Have fun
John
Don't need root for adoptable storage.
Hi
Did u get the info that you need ?
Rooting
johnhux7 said:
Hi
Did u get the info that you need ?
Click to expand...
Click to collapse
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
webelan said:
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
Click to expand...
Click to collapse
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
johnhux7 said:
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
Click to expand...
Click to collapse
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
webelan said:
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
Click to expand...
Click to collapse
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
webelan said:
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
Click to expand...
Click to collapse
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
more woe
johnhux7 said:
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
Click to expand...
Click to collapse
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
webelan said:
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
Click to expand...
Click to collapse
It sounds like the app has been corrupted, don't really know how to best advice you.
It sounds like you have to do s factory reset.
I would install a custom ROM.
The only trouble with this is that all the roms have just been shut down so you will have trouble downloading any.
Why model do you have ?
If you want to use a custom ROM pm me and I will send you a link.
The custom roms are much better (in my opinion )
John
Sent from my j5nltexx using XDA Labs
#Henkate said:
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
Click to expand...
Click to collapse
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
webelan said:
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
Click to expand...
Click to collapse
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Having a similar issue, i have got my phone so it boots to TWRP 3.1.1-0 but cannot find a ROM file that will install, they all seem to be for j5nlte, even if the file name states j5nltexx. I have tried to ammend/remove the assert lines in the install package to no avail...
any advice would be good
Thanks in advance
PB
ashyx said:
Don't need root for adoptable storage.
Click to expand...
Click to collapse
Then what to do
#Henkate said:
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Click to expand...
Click to collapse
Please work on camera that is the only thing cm 12.1 lackss thank youu

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.

Simple way?

Hi everyone,
So couple of year ago I worked at a start-up company that had an Android project. So I'm not new to flashing images (ROM, Recovery, radio...), and I know most basic tools like ADB (and I'm technical person in my daily life). That being said - I remember the pain when the Radio image doesn't fit the firmware, and you have to play around with stuff to make reception work again. or the Recovery image won't fit the ROM etc etc. I'm not sure if any of this probably still happen TODAY, but back then when I got my LG-G2 - I decided not to touch it. I don't need anything besides the basic options (making calls, taking pictures).
I'm still using Stock with 4.4.2 - and the phone is getting lagy each passing day to the point it's time to root it and install a custom rom.
As I mentioned above, I want it to be quick and painless. Sadly, I don't have the time to do insane amount of research right now, mainly because I have a 3 weeks old born at home - and I prefer to use my free time hanging with it that Q&N issues with my phone
So here's what I need your help with:
1. A recommendation for a tool to save all phone settings. Mostly - App settings, and OS settings (even though I probably not going to go for Stock again, but it doesn't hurt to back it up).
2. An instruction how to flash D802 (there' so many options this days...). My Kernel version is 3.4.0.
3. Recommended ROM to use. Here's what I need from a ROM.
a. I probably want to upgrade to more safe rooted Android version (I can't for example handle permissions on 4.4.2).
b. With that, I don't want to install the latest Android only to figure it's running slowly on LG G2, I want the interface to be snappy (the Stock was snappy for a while).
c. I prefer Minimal ROM if possible with Google Apps installed. If I'll need something, I can install it myself.
d. One of the reason I didn't root up until now, was because people mentioned camera quality is meh with non stock roms. If possible, I will like to have a decent Camera quality.
e. I use my phone as a music player often. So good sound quality is important to me (and maybe even build in Parametrized EQ?).
Thank you!
Reading around the forum would have taken just about the same amount of time than writing your post. A post, mind you, that will get you the same as what you can already find with ease.
You managed to write with your kid around. Last time I checked, browsing takes less effort.
Rant out.
Instead of a rant, here's an actual help for people who might find it useful in the future and lack the time to do some proper research (as it took more than the 5 minutes it took me to write the original post). Please note that I won't take any responsibility for possible damages you may do to your system. Please use at your own risk. Also, note that I only tried it on LG G2 802 with Stock Kit Kat (4.2.2) and other version/OS version might not work.
I wasn't clear to me if 'One Click Root' work with Kit Kat bootloader, so I used 'ioroot'. When your done rooting your phone, you will need to flash a TWRP recovery. The easiest way to do it is by using AutoRec. However, the TWRP recovery installed with AutoRec doesn't have Thermal protection, and is dangerous to use according to the forums. So the next thing will be flashing a new TWRP version from the recovery. Blastgater have tweaked TWRP Recovery for LG devices. You can download the latest version here. It's basically a zip file you flash from within your old TWRP.
Regarding ROM, after doing some research - it looks like Lineage will be the best 'all-around' rom to use. Liveage 15/16 were too slow for my liking, so I went with 14.1 (Android 7.1) which was enough for me and snappy to use. However, the tricky part if your plan on using Lineage, is to flash a bootstack as the one coming with Stock won't work. It's just another zip to flash directly from the recovery and can be found here.
So this is just the high-level process, and I highly suggest checking the specific on the links I sent. It also helps if you know how to handle 'adb' and know the basic stuff like what bootloader and recovery are
Good luck.

Categories

Resources