yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 General] xperian.ir:
hi all

This is the new firmware for Xperia Z3

Android 5.0.2

Build number: 23.1.A.0.690

CDA: 1288-4387 Customized MEA

Size: 1.43 GB

with full support arabic and persian language

download: https://mega.co.nz/#!JhsQnawB!5FGPo4C-nBJsBnR15tC1FbobJvx5KCjtx7JK8Br7vIw
[Xperia Z3 General] gregbradley:
Please use the mega collection thread to share ftf files

Thread closed
[XDA Assist] swedekins:
Hello XDA,

I'minterested in creating a custom rom, however I have no idea where to start and what programs I need. I'm on Windows right now and I have Android Studio installed, but I'm not sure I'm able to create a rom with that. I would like a program with the highest level of customization. The
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. I'd suggest you take a look at this thread:

[Guide]Complete Android ROM development and essential tutorials
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
Rooting and Bootloader stuff

Bootloader and Modem for MM Build:-

Both Here

BOD4 Bootloader and Modem for G900H users :-

Get Both Here

Bootloader and Modem for G900F users :-

Bootloader :-

BL_BOC7.tar.md5 1.9 MB - Here

Modem :-

CP_BOC3.tar.md5 59.5 MB - Here

Installation and Rooting Guide for G900H users :-

FIRST OF ALL. I'm not responsible for any bricked phones or UFO abductions so Do it on your own responsibility!

For Rooting :-

There are 2 methods to Root G900H :-

1)By CF-AutoRoot, For this Check This Thread

2)By Installing Custom Recovery

i)First download a custom recovery (You must be able to do that otherwise stop and gain some knowledge first)

ii)Then, Download SuperSU

iii)Install the zip via Odin (Like the normal PDA or AP way)

iv)Then boot into recovery and install the SuperSu.zip and Voila! You are rooted!

For Installing :-

1)Boot into Recovery

2)Install Zip

3)Voila! Done lol

4) Give it some time to boot and install apps
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
Reserved
[Galaxy S 5 Android Development (Exynos)] biyolog4472:
Voooovvvv good working. Bravo ☺
[Galaxy S 5 Android Development (Exynos)] varosmuhendis:
screenshot
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
Thanks. Btw Damn I forgot to Reserve :P

Will add after the testing phase is complete.
[Galaxy S 5 Android Development (Exynos)] ignatemanuel:
Good Job! Go for it!
[Galaxy S 5 Android Development (Exynos)] xtmzone:
For G900F will be a version ?
[Galaxy S 5 Android Development (Exynos)] RIPPER:
Grrtt work bro.. Keep it rocking!
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
I could make it but somebody else already did I think.

Sent from my SM-G900H
[Galaxy S 5 Android Development (Exynos)] rubencho21:
hello friend could do this ROM devices s6 for our galaxy s5 G900F / M ..... because it is very popular, I would try this rom :)[COLOR="Silver"
[Galaxy S 5 Android Development (Exynos)] lucky_sidhu:
Congratulations for your ROM. Keep up the good work :good::good::good:
[Galaxy S 5 Android Development (Exynos)] Brawler7:
Please make one for the G900F ☺
[Galaxy S 5 Android Development (Exynos)] Kiperdefter:
Great

Awesome! I know it's still in testing phase but can we have some screenshots please?
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
Ok will try making one in free time.

Ok will put screenshots in an hour or two

Edit: Screenshots Up

Sent from my SM-G900H
[Galaxy S 5 Android Development (Exynos)] twint14:
how to flash this rom ?:confused:
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
How about flashing it in cwm? Or Philz touch? :P

Sent from my SM-G900H
[Galaxy S 5 Android Development (Exynos)] twint14:
i flashed it using philz it game me an error and instalation abored
[Galaxy S 5 Android Development (Exynos)] KL643:
S5 model?
[Galaxy S 5 Android Development (Exynos)] Samkitpalecha:
Damn its my fault. I'll fix it. New build will be up in 2 or 3 days, because currently trying to port S6 Phone and Contacts

Sent from my SM-G900H
[P3600 ROM Development] delivery1979:
where is the mms folder for mms on wm6.I can't find it!!!:confused:
[P3600 ROM Development] NeilM:
It isn't enabled by default, but the installation file is in the Windows folder.

Open Windows and look for HTC_set.cab , tapping which installs the MMS folders in Messaging.

There is also an HTC_List.cab file, which adds a list of operator settings to the MMS Server settings, but I found the Orange ones didn't work, though using the Settings file via the HTC Website's WM5 ROM update page worked OK.
[P3600 ROM Development] delivery1979:
thakns a lot;)

i will try
[P3600 ROM Development] tochan:
Don't have it in Windows

Can somebody post the cab file please?
[P3600 ROM Development] marcolino94:
MMS ON wm6

I dont find it!
[P3600 ROM Development] NeilM:
Some of the later WM6 ROM's have MMS integrated into the SMS folder

- have you looked there?
[P3600 ROM Development] Pumpiron579:
Just go to a picture and select send as...mms will show up and it will send. Do not know why they include sms and mms together. But as long as you downloaded the correct settings for your network, mms will work.

--------------------------------------------------------------------------------

"yes. it's now hidden. just start to create a new mms message, and you have the option to configure the mss setting under 'menu', 'option', 'message option'."
[P3600 ROM Development] dartrax:
Hello,

please, can someone upload the HTC_set.cab-file or provide information how I can enable mms support manually?

thank you,

dartrax
[T-Mobile LG G3] Eliminater74:
Please Try and let me know:

- MultiRom Installer: multirom-20150717-v32-unofficial-d851-zip

- MultiRom Installer: Mirror: multirom-20150717-v32-UNOFFICIAL-d851.zip

- TWRP Modified 2.8.6.X: twrp_multirom_2-8-7-x_d851_20150717-signed-zip

- TWRP Modified 2.8.6.X: Mirror: TWRP_MultiRom_2.8.7.x_D851_20150717-signed.zip

- MultiRom UnInstaller: multirom_uninstaller-zip-4f423237-22f2-4fe4-9509-9e52cb3dc3e6

- MultiRom UnInstaller: Mirror: multirom_uninstaller.zip

- Patched Kernel: LP kernel_hardboot_kexec_patch_20150403-signed.zip [Updated To Work Right]

-=[ Patched External HardBoot Kexec Kernels ]=-

-=[ Compiled By Eliminater74, w/permission By Respected Owners ]=-

- Updated 777Kernel: 777Kernel_Hardboot_Kexec_20150515-signed.zip [SaberMod 6.0] [LP 5.1.1]

- TootsiePop - - By [MENTION=3771760]aclegg2011[/MENTION] : LP TootsiePop_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2]

- 777Kernel - - By [MENTION=4794976]777jon[/MENTION] : LP 777Kernel_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2 ]

-=[External Patched Kernels ]=-

- Patched Kernel: [AOSP][D851]Rin Kernel 1.6.5[LOLLIPOP 5.0.2 ]

[IMG="For Testing Latest Development"]http://www.downsidaz.com/img/testing.png[/IMG]

- MultiRom Dev Test:

- MultiRom Dev Test:

--=[ D851 Flashable BootLoaders ]=--​

- D851_BootLoader_10c.zip -

- D851_BootLoader_10m.zip -

- D851_BootLoader_10r.zip -

- D851_BootLoader_20b.zip -

​
[T-Mobile LG G3] yanowman:
Firsttttttt

---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------

I managed to soft brick my phone twice on Multirom. Than I stupidly somehow made it so the ROMs would ONLY flash from OTG flashdrive and if I pulled it out it would soft brick...

Soooo... Testers? Not I. But thanks brotha
[T-Mobile LG G3] Eliminater74:
I dont blame you. After that, I wouldnt wanna try anything either...

People that test this out, Must be able to recover from a softbrick just in case.. I wouldnt want anyone that doesnt know how to Recover from a Softbrick to try this.

NOTE: I am not saying this Will Softbrick your phone, What I am saying is: Be Prepare Just in case of the unthinkable happens.
[T-Mobile LG G3] Papote3:
Will give it a try as soon as I get home and have easy access to a PC for recovery, in case anything would go wrong.

Also, I have the previous MultiROM right know, how would I go installing this?

I loved MultiROM on this device, so glad you're bringing the development back.... And just in time for LG LP
[T-Mobile LG G3] Eliminater74:
Since your version is most likely the older version, Just zap the uninstaller.zip after your take a nandroid backup.

That way, if something messes up, you can boot to recovery and reinstall your original backup.. :)

Thats the main reason, I wanted to make sure the recovery worked. ( I had my finguers crossed when I flashed that) :fingers-crossed:
[T-Mobile LG G3] Eliminater74:
I can personally verify That MultiRom Resurrected Works......... I did take the time to Flash Compatible patched Kernel and Recovery then MultiRom..

Booted menu and everything worked.

I do need to fix the res on it. Too small. Its just a tw flag or mr flag in boardconfig.mk under device tree..

Now I did compile a 2nd version with a few fixes and patches that I made.. First compile was 100% [MENTION=2174433]Skin1980[/MENTION]'s source to his device tree..

2nd one is from my patched device tree.

Update: I found out how to fix the small looking boot screen. Will compile fix and re-up it later.

Fix was: MR_DPI_FONT := 350 # Was set at 219, and since 340 would be for a 4.95" screen.. I figure try out 350.
[T-Mobile LG G3] marcdw:
I'm still using the original MultiROM and still have all the files. Couple of questions...

1. Uninstaller. I can use the one I have now or the one you provide (assuming there's some difference).?

2. Can I still use skin1980's kernel or is it preferable to use Rin?

On a related note, there was a time when if a ROM's kernel would crash when flashing a secondary I would go to 777jon kernel (because it was new and cool). After awhile, though, it no longer worked with ROMs released in the past month. Furnace kernel, too, on a few tests. Only the tootsie-pop kernel works for me.

Was just wondering why 777jon worked in the past with this MultiROM but no longer does. Is it the kernel, this aged multirom, or something in newer ROMs.

Fusion ROM is one secondary using 777jon kernel w/out issue. It's from February. Validus includes that kernel but it doesn't work. With tootsie-pop it's A-OK.

Am I rambling.? Sorry. ?
[T-Mobile LG G3] Eliminater74:
You experienced kernel panics because of this:

MR_RD_ADDR

This option might not be needed for your device. It sets address in boot.img to unpack ramdisk into, and most devices can handle MultiROM changes even without this option. But, some devices (Nexus 7 and Nexus 4) will panic on boot when the ramdisk is bigger than expected. As to what value to set, well, it's more about guessing than anything else. Look at default ramdisk address in your boot.img and try to use a bit higher address.

I set it too MR-RD-ADDR 0x2500000

I took the ramdisk address of a common boot.img which came out at 0x2200000 So I made it 0x2500000 Should be just the correct size.. If not. I change again.. its more of a guessing game.

You can use any kernel that has the patch.. So yes. and as to uninstall.. I think they are all pretty much the same.. but better use the one that came with your multirom version.. since skin's version. Multirom has changed alot,

but also the uninstaller I have should clean up the older version as well. its all pretty much touch and go kinda thing.
[T-Mobile LG G3] arifqur:
I was one of the testers of the skin1980's multirom port.

Stopped using it since it was not updated and the roms from the last month or so did not boot as secondary.

Now I installed TWRP 2.8.6.1 and deleted all secondary roms.

So now I should use the un-installer from you and then flash the multirom TWRP and the Multirom file?

EDIT: Secondary roms install but when selected during the boot options, only the primary rom boots in its place
[T-Mobile LG G3] marcdw:
Many thanks sir for the quick response. Always fun having something new to try (and break and fix).

Will check this all out tonight.
[T-Mobile LG G3] arifqur:
Anybody other than me try this?
[T-Mobile LG G3] jobella:
I used MultiRom for about a month. I had a ball with about half a dozen Lollipop Roms. I even sent a donation ;). It was fun but now I need the G3 for work and can't take the risk.
[T-Mobile LG G3] Eliminater74:
Can you tell me where you installed secondary rom to, and what file system if other then internal.. also ill check into this.

Im still working on getting the screen in place.. Dont forget you have to inject the multirom into every secondary install.

you might want to reinstall, and make sure that box is clicked. Im not sure, but that could be the problem why its not booting that rom after you install it.

Ill check into it though.
[T-Mobile LG G3] Eliminater74:
hmm.. There is a problem with the booting of the secondary roms.. It seems to only boot the internal only.

Im looking into this. I got so much going on right now, ill try and see what the problem is and fix it.

Yea, seems to install just fine, and everything works up to the point it only boots the Primary rom and nothing more.

So, could be one of my settings that I added to the boardconfig.mk for ramsize. Ill delete it and recompile and try again.

I did manage to get the screen size correct at least.. dpi set too 430 corrected that..

ramdisk address Ill remove that setting and recompile.

Ill let you know when I get a fix for this.

Update: Booting works when installed on External Drive. If install on Internal It wont work right. Im looking into that.........

But like I said, it worked for me installing it on my external Drive thats 128gb /fat32 ....
[T-Mobile LG G3] arifqur:
Thanks for your response.

Yeah installed it to my Internal Storage as you mentioned.

Waiting anxiously for a working Multirom.

Good to know that you got the DPI fixed
[T-Mobile LG G3] Eliminater74:
Im trying to get a fully working multirom. I would say this is about 75% working...

I did find out that it only boots the first listed on internal rom and first listed on external rom.

Example:

internal storage: 1:Primary rom 2: blisspop 3: Nobody would have 3 on their internal I hope.

External SDCard: 1:RR 2:Blisspop 3:Noname

USB Storage: 1:BlissPop 2:RR 3:something

Here is the example in action now:

you get boot menu, now you choose to boot from USB, and you want to boot RR but it boots blispop since its #1

Now again you get to boot menu and you boot from external SD Card: you choose #2 blispop but it boots #1RR

same thing with internal storage..

Now you get it.

But im running test and checking out pluss im on #multirom on irc freenode.. the creator or multirom is there but away from his computer.

Ill talk to him when he gets back. Creator is Tasssadar..
[T-Mobile LG G3] Eliminater74:
MultiRom Logs:

MultiROM logs everything into kmsg.

Usually, when some error happens during boot, it will create /sdcard/multirom/error.txt file in which is dmesg exported.

If it does not, you can reboot to recovery and get kmesg from last boot from file /proc/last_kmsg. This only lasts through one reboot. All MultiROM's messages are prefixed with multirom, so you can just grep for that.

There is a chance that MultiROM just crashes (you'll know that when Internal ROM boots instead of the ROM you've selected).

In that case, there is message MultiROM exited with status X in the kmesg. If the X is anything else than 0, it has crashed.

Report this to me along with the rest of the log.

Update: I need people who installed this and tried to boot second rom, to drop to shell

and type: dmesg | grep multirom >multirom.txt

connect phone to computer; type adb shell

then cd sdcard

then type: dmesg | grep multirom >multirom.txt

send me the txt file.. I need to check something out.
[T-Mobile LG G3] Eliminater74:
Thank you.. I just want to makre sure its really working for you..

Because you could boot up a secondary rom using your primary kernel as long as the pri and sec roms are the same OS. like LP or KK..

But if is boots with pri kernel, Then its not working. and that means the memory locations are off the mark, and I would have to change that again.

Current Kexec_mem_min Location is set to := 0x0ff00000 system ram

That works best so far for me. But some others have said otherwise.

I just cant set it to a location that overlaps anything else.. and I need a 256megs total for the kernel and init.rc script. and that location

I listed 0x0ff00000 seems to have the most space.. at least for me.
[T-Mobile LG G3] arjuna_:
Can confirm that this works! Don't know what made you want to install a CM LP kernel on a Stock ROM but glad you had that thought!

Edit: for some reason I lost speaker function in the primary ROM after doing this. Speaker works fine in secondary ROM... don't know what to do now.
[T-Mobile LG G3] Eliminater74:
Could I get someone to try this Rom out and tell me if it works, Secondary only please.. Dont flash it as Primary.........

I personally couldnt get it to boot. But like we already learned, what works for me doesnt mean it works for you. and the other way around..

If you want to try it as primary, thats up to you.. Just keep a backup of your current one,

Link: SOKP-L-5.1-LMY47I-R1-20150413-d851.zip

I did get it to boot something after I changed the boot.img.. But that doesnt mean anything since its still flashing the boot animation..

Let me know if it worked for anyone.

Update:I changed the kernel and then it booted. I used the 5.1 kernel from Resurrection remix v5.4.1

In case anyone wants to know, I built this rom today. I was just wanting to see how it checks out.
[T-Mobile LG G3] phiz118:
Hmm

OK - I got a completely stock LP rom to work with tons of trial and error. Here's how I did it...

I installed a completely stock ROM (http://xdaforums.com/tmobile-lg-g3/development/stock-lg-d851-20b-t3062164 --> 20B Stock Images NOT UNICRON)

Once it booted up, I took a backup of the ROM.

Wipe everything to start fresh

Install your primary rom of choice (Bliss 2.3 for me)

Install Multirom including kernel

Reboot to Recovery

Add Rom --> Recover backup taken from earlier

Both roms should now boot. If I tried to install the stock rom directly with multirom, it wouldn't boot correctly. Unfortunately, I was trying so many things that I lost the log file (SORRY!!). On the flip side, this should work as an option to install your favorite rom. It really seems to like a backup install more than a direct install so if your rom isn't working, try installing it as primary, backing it up, then installing it into multirom. That might make it work.
[T-Mobile LG G3] arifqur:
Good idea. Will give it a shot

Edit: Doesn't boot for me. Stays at the LG logo while flashing green and blue led, Tried it for 15 minutes
[T-Mobile LG G3] phiz118:
Unfortunately, I spoke too soon. While everything boots, there's some noticeable issues like no service and the phone app is crashing. I'm going to guess that it is the kernel. Errr....

David
[T-Mobile LG G3] arifqur:
Boots using the rr-5.1 boot image but says that there is no SIM
[T-Mobile LG G3] Eliminater74:
Yea, the data problem is working for some while not working for others. Sorry to trouble you with that......

Thank you.
[T-Mobile LG G3] sabresfan:
I got the speaker to work by copying over a mixerpaths file for aosp roms that was floating around here when LP first dropped to get louder volume for the speaker. I can't remember who the dev was that made it. He deserves the credit.
[T-Mobile LG G3] Eliminater74:
Could you post links if you have em?
[T-Mobile LG G3] sabresfan:
Try this but its my first time uploading any file other than email lol. http://www.megafileupload.com/2BWo/mixer_paths.xml

Copy to system-etc and replace mixerpaths with this. Sound works in speaker for me.
[T-Mobile LG G3] the cronic dude:
[MENTION=5687366]Eliminater74[/MENTION] Thanks for all the hard work. Left you a few bucks
[T-Mobile LG G3] Eliminater74:
I still want to port Ubuntu-Touch over, would be nice to use MultiRom to boot Custom Rom,stock Rom, Linux

Ubuntu is being a pain right now.. so I need to figure out how to get the correct device info.. Its all based off Stock...
[T-Mobile LG G3] SonjaMichelle:
Got a kernel panic when booting BlissPop 3.0 (5.1 version 4/11/15 build) as secondary rom to a SkyDragon primary running the Furnace kernel.

BlissPop was installed using the latest MultiRom you have posted in the OP with PA-Gapps-mini-5.1 and Tootsie-Pop-test-kernel.

Logs attached.
[T-Mobile LG G3] Eliminater74:
I will run the logs by [MENTION=3418703]Tasssadar[/MENTION] when I see him next..

But I just installed BlissPop v3.0 running my TootsiePop Patched Kernel.. and it booted Just fine..

When you use an older patched Kernel, then you take the risk of kernel panics.

That patch sets aside kexec memory locations, that I dont know what he used or what.

but I used my own which is set correctly that works for me. It booted no problem.

Maybe do a few more test and see whats up..

Or if the source is on github, I can revert his patch and apply my patch and rebuild it. or you can rebuild it using my patch.

if you know git, find the commit that the hardboot patch was applied, then revert that commit, you will prob have to hard edit one or 2 files, no biggie.

If your up to the challenge then let me know, Ill set you up with all the info you need.

But that Kernel panic is caused by a faulty kernel patch..

Its not [MENTION=3771760]aclegg2011[/MENTION]'s rom.. its the primary kernel patch..

Here is the link to the commit that needs to be revert for stock G3 kernel.. Use google to search command for reverting,, I cant remember it.

https://github.com/savoca/furnace-g3/commit/c6f17149fc14773ad7a5de2ef4d8e1fff771cbf6

I know you know how to build stock kernels.. so like I said, you can remove his old [MENTION=2174433]Skin1980[/MENTION]'s patch, and repatch with my new working patch and then rebuild it.

it then will work no problem.. I have ran skydragon no problem..

Just let me know if you need help.. msg me or leave msg here.. or if you use hangouts you can contact me there also.. and facebook ect ect ect..

even IRC :)
[T-Mobile LG G3] SonjaMichelle:
If I understood correctly, it is the Furnace Kernel from the primary ROM that caused the kernel panic and the one that has the faulty patch? If so, that means all secondary installs will go wonky, right?

If I misunderstood and it is the tootise-pop test kernel, I think the source is on github. So yeah I guess I could mess with it and give it another go. A CM based rom/kernel should be easier to work with you patch than that damned AOSP source. I was going crossed-eyed hand-editing those files and I still don't know what went wrong. I really thought I had it licked. :confused:

I'm toying with the idea of letting the OTA update that just dl'ed to my phone run and go with your LP kernel. It's pretty much coming down to a flip of the coin whether I want to crossover to the dark side. My last foray with the INB4TMO update was a nightmare.

Running a bunch of ROMs and having Multi-ROM working to perfection on the first go-around isn't a high priority. It's not like my phone is in a production environment. Like I said, I'm retired with time on my hands, so, I'm open to what ya want to toss at me.
[T-Mobile LG G3] Eliminater74:
the patched roms with the older patch will work with some and not work with others..

the patch that I have, should be easy to apply to stock Kernel.. I told you how to apply it some pages up.. you shouldnt have to edit anything except maybe 1 or 2 files.. at the most..

I give you credit though, I cant seem to figure out how to build on stock, There is no device tree for the d851 that im so used too..

If you would like to show me your building instructions for stock, then ill give it a try.. Thats the only reason I havent been able to port over ubuntu-Touch, because it goes off the stock

code that I dont have any clue on how to do.