[Q] Compressing CM-11 Nightly/Stable post binary update

[Q] Compressing CM-11 Nightly/Stable post binary update - G2 Q&A, Help & Troubleshooting

Hi, So twice today I've tried flashing CM-11 on my G2 d801 variant. I tried the nightly first and then the stable version and neither of the zips would make the initial pass through recovery. Already had it in mind that it had something to do with outdated binary, as I was using, as is recommended in the OP, TWRP to flash.
This just turned out to be confirmed in the Unofficial CM-11 thread, to which I am unable to post. Vertigo offered up the updated binary for download, I snagged it and went on to switch out the compressed binary with the update.
My question is whether there is a certain compression rate I should use when zipping the ROM again or whether standard compression (on Android) is well enough. I'd appreciate any help the community might offer. I've simply never disassembled a ROM before with the intent of ever using it again.
Thanks in advance,
tinydynamite00

Related

[ROM][OFFICIAL] P7300XXLQ6 (OpenAustria) cwm+odin (2012-12-16)

Hello guys,
so I've seen others do this before, and I thought, I should be able to do that too I'm a computer geek by training, but never got very deep in Linux/Android hacking.
Anyways, I made a CWM-flashable zip out of the Odin package for the latest ICS for P7300. (PDA: P7300XXLQ6; CSC: P7300OXALQ6; "OpenAustria")
Odin package: (source sammobile)
info: http://www.sammobile.com/firmware/?page=8&view=8417
download: P7300XXLQ6_P7300OXALQ6_ATO.zip (from hotfile)
I initially flashed the Odin package on my tab, and kept all my userdata, user apps, and even my homescreens. But I came from official, odin-flashed P7310UELPB ICS for USA released 3 months ago (yes, that's wifi-only, but runs fine on P7300); so that may have an influence.
If you are concerned about the integrity of your device, I do recommend you install the Odin package, as it is straight from Samsung, so you can be assured not to suffer from the error injected by anyone else (not that I made any errors, mind you :angel: ).
CWM-flashable package: (by direct conversion from the Odin package - no modification, not rooted, nothing added/removed/altered)
downloads:
- ROM: P7300XXLQ6-ROM.fred-v01.zip (for links, see post #3)
- MODEM: P7300XXLQ6-Modem.zip https://www.sugarsync.com/pf/D6778724_7163149_619563
md5:
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
How to install
- if coming from stock ICS or HC, I suspect only wipe /cache is needed. From any other ROM (like CM or AOSP) I suspect you need a /data wipe (warning: deletes all your application data; but not your /sdcard)
- flash from any CWM recovery (I tested only 5.1.2.6). Turn OFF signature validation, as these zips are not signed. It took about 3-5 minutes on my tab
- (ps: the updater-script was borrowed from a recent kallt_kaffe ROM, so it's pretty bog-standard Just added a few outputs to show progress)
Other info
- the Odin package also includes a newer bootloader. I don't know if it's essential to have that newer bootloader, but I can add it later.
- It may not be necessary to flash the MODEM, but I would recommend keeping the MODEM+ROM combination.
Optional additions & tweaks
- any root package should work. (Update: I recommend either v3.1.3 or 3.2 from the original developer of Superuser: http://androidsu.com/superuser/ )
- if you have rooting problems, first uninstall other root packages, including superuser/superSU updates from Market. There is an "unroot" procedure in the sticky on General forum.
- you can get voice-call mod by flashing these 2 from cwm
* P7300XXLQ6_ENABLE_VOICE_CALL.zip from suwandiapr - http://forum.xda-developers.com/showpost.php?p=35264752&postcount=36
* the I9103 modem - http://forum.xda-developers.com/attachment.php?attachmentid=1309125&d=1347032493
- if you hate the boot sound, remove/rename the /system/etc/PowerOn.ogg
- fix for system freezes: see FAQ link under "reading"
- fix for wifi: see tracid's thread linked under "reading"
- OCUV kernel: see AAccount's thread for A1 kernel (careful, some versions work only on stock, others work only on cm10/aosp versions. Use e.g. the well-tested 1.7.3; or the much less tested 1.8.3c. Read carefully his posts and know that custom kernel involves experimentation, trial&error and potential instability)
- attached to this post is a flashable zip to easily return to stock XXLQ6 kernel (or you could flash the who ROM again, if you want)
Interesting reading
A MUST: my FAQ regarding ICS issues (especially if you are first time upgrading from HoneyComb to ICS)
http://forum.xda-developers.com/showthread.php?t=1895496
tracid's thread - he had the first "stock" ICS for P7300 2 months ago (it required a heroic effort to pull the update from an OTA package, that was available on Samsung servers, but not being pushed out by Samsung). As such, his thread (and esp the first post) has lots of useful info for Stock ICS on P7300, gathered over last 2 months.
http://forum.xda-developers.com/showthread.php?p=31720406
Credits
for inspiration, for sharing, for a couple lines in the updater-scripts, for being great devs, or great modders, or for letting me think I can do this...
kallt_kaffe
tracid
suwandiapr
safariking
and others who posted info that I used to make this
Returning a favor?
PS: I use SugarSync cloud storage for sharing this file - and will keep it there as long as I can. Help me keep the file alive by creating your own SugarSync account with THIS link (we both get 500mb extra - but only if you install the app on computer or smart device): https://www.sugarsync.com/referral?rf=cw2yimm8cchga. I also spend 10 hours of my life making this conversion, most of it in the middle of the night, so that must count for something, right
Alternatively, hit thanks - it gives a warm feeling too

reserved by OP
screenshot attached, unfortunately xda resized it to 640x400
Update 2012-12-25:
I received twice the question "what is the difference between this and tracid's rom". (e.g. here
Both are stock ROMs from Samsung with no modifications. (tracid added root, busybox; but this can be easily added yourself on this ROM as well)...
tracid's ROM = ZSLP7, regional variation: Taiwan. Obtained by *manually* applying an OTA file found on sammobile, to the P7300ZSKK2 honeycomb ROM. Samsung never officially pushed out the ZSLP7 as far as we know; so it may have been an internal test build.
here = XXLQ6, regional variation: Austria; An official and distributed build, as far as we know.
Samsung is not releasing changelogs, so the actual differences are hard to find, other than the fact that different regions (have slightly different set of added application (e.g. kobo, Polaris, ...). XXLQ6 came with swype keyboard. Not sure if ZSLP7 came with that.
Most importantly, XXLQ6 has a more recent build date, and seems to be officially distributed, so one can *assume* it has more fixes.

initial hosting on sugarsync broken: files blocked because of a "Fair Usage" violation. Probably it broke the "10GB per day max download on Free accounts" limit that I was not aware about
For a limited time, you can get the files from my Adrive (no download limit, but only 10 concurrent downloads possible - links expire after 14 days) / links valid 2012-12-22 until 2013-01-05
ROM: http://www.adrive.com/public/BAMDga/P7300XXLQ6-Modem.zip
MODEM: http://www.adrive.com/public/srnfuF/P7300XXLQ6-ROM.fred-v01.zip (830 downloads until 2012-12-22)
User x24 has a mirror up -> see his post on page 3: http://forum.xda-developers.com/showpost.php?p=36135549&postcount=25
here are md5's in case anyone wants to mirror/verify.
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
cheers, Fred.
PS: referral signup for dropbox - should you feel interested to give yourself and me an extra 500mb on dropbox: http://db.tt/g26Egj0

Thank You a lot for the upload because today is the second day that I try to download the Odin Package of this P7300XXLQ6 Rom... But without success... This Hotfile link is "out of ordrer" since 2 days...
Your "NON Odin package" is only around 400Mo and the Odin package is around 600Mo... Is it normal?

about smaller size... The odin package is poorly compressed. Also, it contains some 100mb stuff that does not get installed, at least not on my tab (these are mostly demo apk in a hidden.img - I can make them available, but as I said, they were not even installed on my tab)

Ok! Thanks! :good:

installed in on my P7300 tab just now and it's running okay. I did not do any factory reset. Just wipe cache, as stated in OP, coming from stock honeycomb. Um. But I always run into "Android is updgrading, optimising application 1/1" every reboot. is that normal?
UPDATE:
Upon installing the kk_root_ics.zip, tab won't respond after some seconds. I reflashed the rom and it responded fine again.

Optimizing apps is the message when creating the dalvik-cache for a deodexed APK. It should happen after initial install, and then again if you add apps through recovery or so. E.g. I got it (once only) after flashing root package, as this added superuser.apk.

Other than the ROM itself, what else have you flashed (the more exact, the better to diagnose)

Even if I didn't install from CWM, it always show the optimising app 1/1. I'll further check since I'm always trying to root my tab to no avail.
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
I only flashed ROM+MODEM then reboot. Everything runs well. but whenever I flash a flashable cwm file to root the tab, that's when I experience the hang.
Update:
Tried to odin CF-Root, but failed. Got stuck on "Leave CS" thrice~ and stuck on 1/8 progress bar so I flashed the rom again.
Update 2:
I uninstalled SuperSU and Superuser from tab. I then flashed Stock Recovery (from here) via Odin. Flashed kk_root_ics.zip and booted okay. I found Superuser installed. But when I try to update binary, it says failed. I downloaded superSU, and it also failed to install the binaries.

haramizuki said:
Even if I didn't install from CWM, it always show the optimising app 1/1.
....
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
Click to expand...
Click to collapse
See my FAQ. There's a bug in many stock Samsung ics, that mean that any application FC, leads to full OS hang. I made a fix for that....
As for the optimizing 1/1 on boot: might be a corrupted apk file on your data partition.

Full wipe/factory reset fixed it. I actually didn't have any backup because I accidentally hit the full wipe forgetting that it will wipe internal files as well. I installed rom via Odin since it's the only way coming from a full wipe. :thumbup:
Btw, Which do you prefer: Supersu or superuser?
sent from S2 running latest pa+dori ,unless stated otherwise ^^

Superuser serves me fine. I never tried superSu

not bad. So far 600 ROM downloads on the Adrive link
If you installed this successfully, let others know!

Will this work on the 7310, or will it freak out because there's no phone?
Sent from my GT-P7310 using xda app-developers app

upconvert said:
Will this work on the 7310, or will it freak out because there's no phone?
Click to expand...
Click to collapse
Until somebody tries, we don't know
However, why would you want to. There are recent enough ICS packages (e.g. on sammobile)
In theory, I somewhat expect it might work, and if it doesn't, should be easy to overwrite with p7310 ROM.
No promises, no warranty !
Sent from my HTC Desire using xda app-developers app

Was this the one you had suggested to me over on the a1 kernel thread?
Sent from my GT-P7310 using xda app-developers app

Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.

fred_be9300 said:
Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.
Click to expand...
Click to collapse
No prob, I just wanted to make sure I wasn't missing something. I really want a rom with working face unlock, so I think my only options right now are stock or the mostly stock discovery.
Sent from my LG-VM670 using xda app-developers app

If you are coming from cm10, do you need to flash modem.zip also? Also what version of cwm to use? Thanks
Sent from my GT-P7300 using xda premium

MultiROM with Lollipop builds coming out...

14 November 2014
There are several great lollipop builds out there currently with a lot of work being done to give us all a great product. So far multirom is working perfectly in Primary slot as well as secondary slots in multirom with @scrosler AOSP builds 5-7, Build 7 here as well as @scrosler Factory Stock Rooted ROM LRX21P which can be found here
If your favorite dev is making a Lollipop build for the Nexus 7 and you have successfully used it with multirom, please let us know so we can tag it and place a link for future users to this thread.
06 November 2014 (ORIGINAL POST)
Ever since I mentioned this in an email, I have received a few requests on how I got @scrosler Pure AOSP 5.0 Build to work with MultiROM on my Nexus 7 flo.
First off, I have only done this with the build by @scrosler which can be found HERE, but I would guess that it can work with similar builds.
Secondly, this worked perfectly on my device. If you mess up your device, I am not responsible.
Thirdly, and most importantly thank you to:
@scrosler for the lollipop build and all the extras
@Chainfire for SuperSU
@sykopompos for the permissive boot image
@flar2 for the ElementalX Kernel
@Tasssadar for MultiROM
if I forgot to mention someone, please holler at me
Okay, on to the easy stuff...
This has been tested and is successful on Nexus 7 flo (2013). For information on Deb procedures, please refer to this post by @drewski_1 but at the request of @scrosler, please bring all multirom questions back to this thread. Also for Nexus 7 deb, @darkobas has given us a modified boot image to use which can be found here
This ROM (this particular build I've been working with) cannot go into a secondary slot of MultiROM, I have tried everything. If you found a way, please share it.
1. go HERE and read the OP, download necessary files, (latest build, latest gapps, busybox flashable, etc), update bootloader if needed, and goto step 2.
2. go HERE to get ElementalX Kernel for Lollipop
3. go HERE to get a very permissive boot image that works perfectly with this setup.
4. go HERE to get the latest SuperSU
After you have everything in order, reboot into recovery...
1. Move your primary ROM into a secondary slot in TWRP recovery.
2. Go back out to the main TWRP page (outside of Advanced/MultiROM)
3. Install Scotts Pure AOSP build 5.0
4. Install Recovery Saver
5. Reboot Recovery (just to make sure your recovery is still intact)
6. Install GAPPs
7. Install Permissive boot image
8. Install SuperSU
9. Install ElementalX Kernel
10. Reboot and Enjoy
When you get into your ROM, check to verify that your SuperSU is functioning properly and set your ROM up to your likings. :good:

appreciated clarification
OP said:
I've gotten a few requests about multirom with this build since I posted something earlier. If you need to know how to do it (you should already if you're using multiROM), you can check it out HERE.
I didn't want to post the info in here and muddy up the dev thread.
http://forum.xda-developers.com/showpost.php?p=56558107&postcount=802
Click to expand...
Click to collapse
I know but tend to forget details over time - THANKS. I like to verify procedures before committing anyway - saves me from bricks soft or hard. With the file structure changes, etc I like to know what I'm getting into and how best to do it safely.
I'm in the process of moving roms and should have this latest L in slot #1 before dusk, heh.

Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.

hhairplane said:
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
Click to expand...
Click to collapse
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.

Megaflop666 said:
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Click to expand...
Click to collapse
It might just be with Deb, then...

hhairplane said:
It might just be with Deb, then...
Click to expand...
Click to collapse
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?

Megaflop666 said:
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Click to expand...
Click to collapse
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?

hhairplane said:
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
Click to expand...
Click to collapse
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks

Megaflop666 said:
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Click to expand...
Click to collapse
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.

hhairplane said:
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
Click to expand...
Click to collapse
Its all good. There's been conversation scattered everywhere, that's one of the biggest reasons I wanted to start this thread.
Edit: Link has been updated to the correct post.

I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!

dadeo1111 said:
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
Click to expand...
Click to collapse
Try going into twrp into one of the secondary ROMs and fixing it's boot? Something must've gotten missed in the setup or something happened because this issue is new.

Megaflop666 said:
Try going into twrp into one of the secondary ROMs and fixing it's boot sector?
Click to expand...
Click to collapse
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
edit to add:
I am able to install/add roms, btw. I successfully re-added a jellybean rom from nandroid backup just fine. I'll probably throw them out except one anyway. I'm not sure what happened or when but I followed your steps verbatim. thanks again.

dadeo1111 said:
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
All the multiform specifics can be found in that thread here.
I would try restoring your backup first and see if that fixes the secondary ROMs. Especially since you don't have much time in the lollipop ROM yet. If you restore and it works, let me know.

@scrosler has build 4 up, please see his thread which can easily be found in the OP, second paragraph.
OP will be updated shortly if necessary.
Okay, I've gone through this a few times now. @scrosler work is perfect unless we want to use it on multirom. Continue the same steps listed in the OP or you will lose root, as well as the ability to boot multiple Roms.

Build 6 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:

Megaflop666 said:
Build 5 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Click to expand...
Click to collapse
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work too - as usual. If not I'll post so here.
This is going to be my daily driver now. :good:
I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.

dadeo1111 said:
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work - as usual. If not I'll post so here.
This is going to be my daily driver now. :good: I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
Click to expand...
Click to collapse
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.

Megaflop666 said:
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Click to expand...
Click to collapse
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.

dadeo1111 said:
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
Click to expand...
Click to collapse
Are you using the permissive boot image from the OP and elementalX kernel 3.01? Just curious why I have full function with ES and other people don't.

[Q] Accelerometer/Modem Help D800

Alright, so, I'm not a huge modder, but I do like to remove the stock OS once things start slowing down (as they always do).
When I upgraded my LG G2 D800 to Cyanogenmod 11, I noticed the Accelerometer was no longer working. No big deal, I thought, it would eventually be fixed. So I just used a manual control app in the meantime.
Well, Yesterday I got a ColorCross VR headset, so I want that Accelerometer to work again. I've tried nearly everything. short of going back to stock. I think I know the solution but can't find a reliable download/get TWRP to work with my downloads. I had cm-11-20140504-SNAPSHOT-M6-d800 Installed
I found this thread http://forum.xda-developers.com/showthread.php?t=2705509 stating that a modified Kitkat Modem/baseband is needed, but the files are gone.
Then, I found this thread: http://forum.xda-developers.com/showthread.php?t=2451426 with these downloads http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems it had two modems or the LGD800, "10D_Radio" and "10O_Radio" neither worked when trying to flash the zip as downloaded using TWRP. I tried both wiping data/Cavik and flashing it right before and right after a fresh install of Cyanogenmod, both Lollipop and Kitkat versions but no luck. Couldn't open the zip file TWRP said.
So I tried a few 5.0 ROMS, CM 12 (second to latest nightly and a few others), Cloudy, Vanir, but none of them turned on my Accelerometer.
So, what I need, is an explanation on how to flash those modem files or if I was doing it correctly, a link to valid modem files. Preferably one that works with an Android 5.0.x ROM, but if I have to go back to KitKat, I can live with that, I just want my sensors to work.
Failing that, I guess I can revert all the way back to stock. But let me ask one question: Can I just flash a .zip file using TWRP if I'm not worried about making it appear completely stock (not planning on returning or selling it) without having to do the extra stuff in the guide intended for a complete return to stock? I don't need recovery to be reverted, just the original stock ROM (I tried to flash just the ROM, but either the download was damaged or I can't simply flash the stock LG G2 AT&T ROM).
I have five bucks in bitcoin I can tip whoever helps me out, either a custom ROM that installs the right modem/baseband by default and is KitKat or above or some instructions on how to get the right modem files to install + a link to them.
If a new build needs to be compiled to get the accelerometer working again, I might be able to donate a little more than that.
Right before posting this I tried downgrading to CM11-20140210-SNAPSHOT but while it installed, it still says there is no accelerometer (and doesn't auto-rotate, even when on). I also tried downgrading to CM10 (the only LG d800 CM10 on the official site) but TWRP didn't want to open the zip.
Thanks!

Neverminc, figured it out, sorry for the noob questions

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

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.

Lineage does not work

It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!

garfius said:
It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!
Click to expand...
Click to collapse
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?

i think not..?
kurtn said:
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?
Click to expand...
Click to collapse
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?

garfius said:
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?
Click to expand...
Click to collapse
Delete data for clean install.

garfius said:
It's been 5 days since i installed lineage in my Oneplus One...
Click to expand...
Click to collapse
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Can't save update script for lineage version 14.1
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?

asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse
What twrp?

Probably found it!
It seems to be a problem with the wifi firmware, seems to be pretty common :crying: :crying:
Anyways, thank you for your time.
Regards.
Ibuprophen said:
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse

Try latest
I used lineage tuto, and flashed the latest TWRP and worked like a charm (wifi issue apart).
asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse

Database Users

welcome