yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] its the peanut:
Can you also post a mirror on mega or android file host for the base firmware? Mega downloads in full speed in 15 minutes download Is finished.

Btw I will be off xda sometimes for a long time, I met with a very nice and sweet girl (hot too, damnnn) and it takes an hour to get to her place so have to work hard to pay the bus to her house and back... and of course will spend alot of time with her.

So expect that ill pop up time to time in the thread. Hope you guys won't miss your favorite peanut.

Btw nice you decided to a newer base, looking forward to the second gen custom touchwiz roms for our mega ;)
[Samsung Galaxy Mega] KennyLG123:
Huawei P8 Max the price isn't coming down much..lol http://www.amazon.com/Huawei-Standb...&qid=1437343859&sr=1-1&keywords=huawei+p8+max
[Samsung Galaxy Mega] butchieboy:
So does the P8max work on At&t or not?...i saw people post that question..the answer was yes..then several questions later it was no

Galaxy Mega..(MegakatV30)
[Samsung Galaxy Mega] megalomanic14:
I dont get Huawei pricing... the X2 is identically spec but bigger battery and screen for near half

Mega
[Samsung Galaxy Mega] its the peanut:
Ehm guys you might want to look somewhere else then the P8max... as huawei puts more crap into the system, xposed doesnt work on those devices.

The Mate 7 does work with all type of mods (most of them) but my p7 is newer and I had already more problems on the same version of android and Emui v3

You can root and may have an already unlocked bootloader (in my case the bootloader unlocked immidiatly after rooting with kingoroot android apk). After this you can flash a recovery.img with flashify but thats it... the system has alot of weird security installed.

One of them is called SET_IMMUTABLE.LIST and that file can only be removed if you have a modified Boot.img. this file prevents you to do anything on the system (viper4a, xposed and even prevents you from restoring your backup from custom recovery!!!)

And if you removed this file (you need busybox, root and command emulator installed) you still stuck with the fact you cant use xposed.

Me and megalomanic took a look at the build.prop of the p7 and disabled the same things as with the Mate7 and on the Mate it worked but with the newer p7 it failed.

You can use xposed but the only way to let it work is to disable Resource-hooks in the settings from xposed.

And you have to keep in mind that the P8Max comes out of the box with 5.0... and there may or may not be roms, root, recoverys etc and its lollipop...

You might just want to look in other brands then huawei guys, cause you'll be really dissapointed in the development of it... performance and battery etc are ok so its a phone that you most likely keep on stock.

If I where you and you want a huawei phone, I should take the mate7, its a nice phone and got very good specs.

This is just to really warn you guys about the big downsides of huawei... maybe they even put more weird things into the system who knows. But I also found out they may or may not also use old source codes that have weird bugs in them.

Consider again man... you really should.
[Samsung Galaxy Mega] KennyLG123:
I also have the huawei mate 7 and mate 2 Both are bootloader unlock, rooted, both have xposed, both busybox, both gravitybox, both i got wanam to work. they went pretty easy and no fc's But the mate 2 is still on JB and the mate7 is still on KK.
[Samsung Galaxy Mega] its the peanut:
Cause they are older devices then my ascend P7, they implemented some new "features" in that time into the p7 and they will most likely do it more in the next gen devices.

At least they dont put knox into the devices like samsung... so you most likely also have your warranty if you revert back wich is very easy on Emui.

It just sucks that they do this with newer devices.

But the risc of having new security put into the system like set_immutable.list (thats stands for the system folders that can be edited and is marked with I from immutable) is very high with the mate7 when it receives lollipop. But I recommend to get the it instead of p8max due to all of this stuff cause the mate7 doesnt have those security patches.
[Samsung Galaxy Mega] megalomanic14:
I mean you're making it sound like roms and development are not possible instead of essentially theming or modding the build which takes further modifications to enable on your device...you have root so it's just a matter of what further hw theme mods or need enabled or removed for the theme or mod you want to work...but as far as builds and development vs xposed...xposed barely works in general on lp but as long as we have a recovery and unlocked boot we can have builds and performance/efficiency optimizations like always

Theme and modding may be more difficult as the builds themselves are...but that's also on xposed and the modules as well for not supporting those devices properly....so it comes down to is wanam style theme more important then a samsung is your best bet...but for the price vs hw and size I'll take an optimized X2 with no theme all day lol

Mega
[Samsung Galaxy Mega] KennyLG123:
Yea i knew the mate 2 and 7 was slated for LP so it was best to get them then to buy one on LP out of the box. lol. Same thing i'm thinking about the note 5. Between samsung and at&t i'm pretty sure it's going to be patched tighter than the at&t note 4.. The days of buying a new phone to tinker with is almost at a end..

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

Well said but you know what i mean, spending more money for the cost of the new devices and you just can't set it up the way we want it. Like knox, put it on a corporate phone not the consumer/customer phone..am i saying this right..lol
[Samsung Galaxy Mega] megalomanic14:
Yea I agree with you...and to some extent peanut but he was having an issue with running xposed which has issues on lp in general add on top his huawei has touchwiz type tethers in the system but more extreme...just made it sound like trouble theming and no development or roms were the same...Huawei in general get very little dev work as is but I just wanted to make sure we're all on the same page as there's a huge difference between no xposed and no rom...like I'd buy one and not the other

Mega
[Samsung Galaxy Mega] KennyLG123:
[MENTION=5451734]megalomanic14[/MENTION] The LeTv is still up there too in price. The x2 is still holding the best price for the size and specs. The new zte x8 was going to be a 5.8 now it shows 5.5.

---------- Post added at 09:05 PM ---------- Previous post was at 08:54 PM ----------

[/COLOR [MENTION=5451734]megalomanic14[/MENTION] Did you get a chance to see this..http://www.xda-developers.com/xda-external-link/moonshine-icon-pack-is-now-open-source/
[Samsung Galaxy Mega] butchieboy:
My Mega is blazing...true Beast Mode..lol

Galaxy Mega..(MegakatV30)
[Samsung Galaxy Mega] megalomanic14:
I'm excited to see what the new base is like...waiting to hear the feedback about updating to the new base before finalizing the build but def stoked to see what next phase is like for our mega

Mega
[Samsung Galaxy Mega] butchieboy:
Im ready when you are

FIRENOTE V23...JELLYBEAN WARRIOR
[Samsung Galaxy Mega] megalomanic14:
I have the new build done...it's just a matter of odin flashing the new base and testing Phil recovery and root...then testing the build itself...but otherwise were pretty much ready to rock an roll

Mega
[Samsung Galaxy Mega] trurl3:
I made first steps:

- factory reset of Mega Fire v2.9

- odin flashing I9205XXUDOA1_I9205OXXDOA1_XEO Poland

- odin flashing philz_touch_6.48.4-meliusltexx.tar without rebooting to system

- making nandroid backup

- reboot

- installing SuperSU from Play & binary actualisation

- run SuperSU and blocking KNOX

- root checking - root acquired!

During reboot two red lines at top of the screen - WP_STAUS_CHECK.

UNFORTUNATELY NO WI-FI ! An attempt to enter into Settings/More nets/VPN results in FC Settings and reboot of the phopne.

Let's somebody look into screens and say what could be the problem? Could it be the matter of modem? I thought that flashing stock rom will set all what is needed, especially because this rom is dedicated for my country... Should I flash rom once more?

Next - stepping back with odin flashing UDNE4 stock rom... will see.

Edit//

- factory reset of DOA1

- odin flashing I9205XXUDNE4_I9205TPHDNE4_I9205XXUDNE4_HOME.tar

- odin flashing philz_touch_6.25.0-meliusltexx.tar

- reboot

- installing SuperSU from Play & binary actualisation

- run SuperSU and blocking KNOX

- root checking - root acquired!

Looks like all is OK (except my Wi_Fi :crying:)

STILL NO WI-FI !!! I do not know what to do with it... please advise...

Now it's time to MegaKat...

- installing MegaKatI9205V30.zip from recovery

- rerooting in recovery

- reboot

- installing SuperSU from Play & binary actualisation

- root checking - root acquired!

STILL NO WI-FI !!!
[Samsung Galaxy Mega] KennyLG123:
Is that stock kernel for that build?? What other kernel option do we have on that build...stock ver.
[Samsung Galaxy Mega] KennyLG123:
[MENTION=3947355]trurl3[/MENTION] When flashing the new base did you happen to notice if there was wifi before rooting?
[Samsung Galaxy Mega] trurl3:
I have re-rooted in Philz recovery immediately after flashing base and only then went to system for installing SuperSU. In this point there was NO Wi_Fi. It's kind strange because AS BASE I have flashed ROM dedicated for my country... and never before have any problem with Wi-Fi (ofcourse on 4.2.2)
[Samsung Galaxy Mega] megalomanic14:
Yea the same issue as coming from mf to kk a long time ago...if odin doesn't flash the baseband and Boot properly having mixed systems will jack your wifi up...you need to use odin 3.07 or 3.09...3.10 is out now so you can try that as well but that's the main thing we need tested is a properly flashed stock build of the actual DBT german base that were using for root and downgrading from the full proper build...Thanks

Mega
[Samsung Galaxy Mega] KennyLG123:
I was just wandering if rooting has a play in wifi not working. I know you said this base was for your country. But i was just wandering about kernel which can affect modem in different ways and rooting somtimes. I'm trying to figure this out in my head right now. I did have this happen before but with a htc device but i know they are two different devices and os. But i did change stock kernels and wifi worked. If knox is involved on this rom this is where i'm stuck...
[Samsung Galaxy Mega] trurl3:
I thought so there is some problem with radio... I have used Odin 3.09 but now try once more with 3.07 to flash stock 4.4 but there is one question - is it important, bearing in mind the future MK build, which ROM i will flash? Could it be that which I used first - dedicated for Poland, or better to use german DBT which you already disassembled?

Is there any fix for two red lines at the top of the screen? I waguely remeber something about flashing stock kernel but probably it was for another model... or maybe it is result of improper flashing...
[Samsung Galaxy Mega] KennyLG123:
Does this new base change the bootloader in any way, like for example A2 to A3 this is like note 3 example. or did secure boot remain the same..on the mega. mega i'm still wandering if rooting has something to do with this. Just trying to put my finger on the issue. LET ME KNOW AND I"LL STAND ON THE SIDE LINES. lol
[Samsung Galaxy Mega] megalomanic14:
If you search wifi in Megakat thread you'll see where alot of people have run into this same thing...it's something with some odin versions just simply don't flash the bootloader and baseband properly for the new base over the old one and you end up with a messed up wifi when the bases mix cuz on kk the boot base and system have to match from the same base...literally Chris just had same exact thing happen in metro Megakat...slightly different issue same outcome

Imo yea it makes sense to use the base everyone else will with the german one but that's not the issue exactly now at this point getting it simply up and running

Mega
[Samsung Galaxy Mega] trurl3:
It is quite easy to check - I am almost ready to flash 4.4 anew because of lack Wi-Fi. You can see on screens in my post what bootloader version was installed with DOA1 during first flashing 4.4 on my Mega. Now i will install german DBT and we will see if something changed :)
[Samsung Galaxy Mega] KennyLG123:
Ok now got it. did he do a hard reset wipe before odin. then flash the new base.

---------- Post added at 11:24 AM ---------- Previous post was at 11:18 AM ----------

Like mega was saying about oden i did have a problem once with oden and switched to 3.0.9 and it fixed a few problems but i started doing factory resets before using odin to flash and never had anymore problems..
[Samsung Galaxy Mega] megalomanic14:
Just look your baseband is unde4, your boot is amg7 and the csc is new....you cannot flash Megakat over the new base...thats also a problem lmao don't flash old Megakat on the new setup until odin back to unde4...thats the point of testing odin back to unde4 so we could still run the earlier unde4 mk builds...flashing mk over the new base will break wifi and security every time guaranteed

You just wanna odin up to DBT...root and flash recovery and test the base is functional like wifi...then odin back to unde4 if you want or wait on the new base for new mk to finish and upload

Mega
[Samsung Galaxy Mega] trurl3:
Yeah, I understand what's going on. As you can see first time I went from DAO1 to UDNE4 and only then to MegaKat. Now I am flashing anew DBT using odin 3.07, but ... its branded ROM... After flashing rebooted without root to check Wi-Fi - still NOTHING... not working... there is still something wrong... look for screen.

Is there any other version of Odin? :(
[Samsung Galaxy Mega] megalomanic14:
Yea there's Odin 3.09 and 3.10 etc you should download a new Odin and try that...branded rom?

Mega
[Samsung Galaxy Mega] trurl3:
Branded means with some extra apps from provider but it is not big issue. I will try to download another odin 3.09 ans 3.10 .
[Samsung Galaxy Mega] megalomanic14:
What provider is it? As I didn't see anything in the build files in the base I was using?

Yea I just double checked the base is not carrier tied at least the one I have broken apart...let me double check csc info

http://live.samsung-updates.com/details/42597/Galaxy_Mega_6.3_LTE/GT-I9205/DBT/I9205XXUDOA1.html

Mega
[Samsung Galaxy Mega] trurl3:
Looks like the same which I was flashing... and on Sammobile isn't signed as branded... but during setting up after flashing there was some sign in german and there was few apps already installed. Not big thing...
[Samsung Galaxy Mega] megalomanic14:
Yea it's a German base build and different regions have different stock apps

Mega
[Samsung Galaxy Mega] its the peanut:
He guys also check the video record bug! Want to know if its fixed thanks
[Samsung Galaxy Mega] megalomanic14:
I think it's mx player on hw sw decoder will play them on v30 as usual from what I've heard...I've still yet to record a single clip lol

Mega
[Samsung Galaxy Mega] trurl3:
Do you know what is the name of modem module inside ROM pack? I am still trying to flash different roms using different odins but without success. I have impression so not every rom has this module. Whatever I do every time modem version stays the same XXUAMED which is still from 4.2.2 rom...
[Samsung Galaxy Mega] megalomanic14:
Right that's why you're getting the WiFi and security problems...the new baseband is oa1 or ob1 I think...I'll have to look when I get home tho I wasn't paying attention to the baseband in the build...try another usb port on your pc and another odin 3.09 download thats what I told everyone else and one the two fixed their issue

Mega
[Samsung Galaxy Mega] trurl3:
Will try... It seems to me that modem module inside ROM has name NON-HLOS.bin
[Samsung Galaxy Mega] KennyLG123:
Most likely it's OA1 That build come out in Feb 2015 correct..
[Samsung Galaxy Mega] megalomanic14:
Yea it's oa1 from like a few months ago that I posted link to

Mega
[Samsung Galaxy Mega] KennyLG123:
I'm sure i got myself caught up on this thread, i must of missed the link. lol I think there was 3 firmware updated that came out in Feb..
[Samsung Galaxy Mega] trurl3:
You are right but I do not know how it could help me... in the mean time I used Kies to restore my firmware. Ir proposed : PDA: OA1/PHONE: OA1/CSC: OA1 (XEF) which I akcepted. But what my surprise when after quite long process i found the same problem persist: no Wi-Fi and modem still XXUAMED. Now I am totally lost and do not have any clue what to do next...

Now Kies said so I have newest firmware I9205XXUDOA1/I9205OXXDOA1/I9205XXUAMED/I9205XXUDOA1 (BGL) ??? I do not installed firmware for bulgaria!!
[Samsung Galaxy Mega] KennyLG123:
is there any file dowload with OA1 across the board or find a tar modem file OA1 to flash after flashing that firmware file you have posted??
[Samsung Galaxy Mega] trurl3:
I have already downloaded rom I9205XXUDOA1_I9205DBTDOB1_I9205XXUDOA1_HOME.tar posted by [MENTION=5451734]megalomanic14[/MENTION] .Flashed it two times but without any change in modem version. It looks like XXUAMED modem is hard fixed in my phone :)

Edit// Observed interesting thing: After conclusing flashing rom by odin (there is note PASS) phone boots up into recovery once more and reflashing something 'by itsef' and then rebooting to system. I wonder what it could be...
[Samsung Galaxy Mega] KennyLG123:
I'd say that doesn't make since, For some reason i keep thinking why can't we try the kernel on the build now on fk. Is there some security that would keep us from doing this just to see if it will help lift some issues.?? Or it may not make any difference..
[Samsung Galaxy Mega] trurl3:
Now my only concern is to successfully flash SOMETHING what will be working as needed :). Its weird so such many flashing cannot change anything. I changed odin versions from 3.07 to 3.10, downloaded odin once more, changed rom versions to no avail there is still the same modem in my phone which lasts from 4.2.2. During flashing Odin show any subsequent module flashed, among others Modem module, but after flashing modem is not changed. It's like curse..
[Samsung Galaxy Mega] megalomanic14:
Yea that's really strange...try this...as long as the mega is runnin normally and...try uninstalling the samsung drivers off your pc...then let the computer reinstall them after hooking your mega up with USB debugging on and let the drivers fully install again...cuz there's only 3 or so things that mess with odin...drivers...odin version...USB port

Mega
[Samsung Galaxy Mega] KennyLG123:
Mega it's weird that his modem remains the same. I've had this problen on a htc and changed modem and fixed my problems but yes this is a samsung, but seems he's able to flash the firmware but the modem deal. I'm setting up a htc one max now as we speak from verizon (fun). But do you think the kernel can make a difference. Or can we get a modem tar file of OA1 and flash with OA1 firmware..
[Samsung Galaxy Mega] its the peanut:
So basically if I get this a 99.99% right... your mega is now fu***d up... (till you get the modem changed)

Good luck
[Samsung Galaxy Mega] trurl3:
Thank you... you made my day :) I know it already...

It looks like odin do not want to flash modem.

But there is another strange thing - when I looked at screens from Root checker I posted after first attempts I have seen so not only modem version is not changed but bootloader version too... and that is really very weird as I am coming from 4.2 without KNOX and flashing 4.4 ROM should install new bootloader. But maybe I am wrong.

Edit// I have flashed once more I9205XXUDOA1 rom and then extracted from it NON_HLOS.bin package. Next made from it .tar.MD5 for Odin. Flashed it by odin - nothing. In my Mega modem is still the same...
[Samsung Galaxy Mega] megalomanic14:
The modem bootloader and system all have to match...so it wouldn't really matter if he flashed the kernel he needs the boot and baseband as well and vice verse

Exactly what I've been trying to explain...Odin is not flashing the base properly so it's either the Odin, your usb slot, or drivers ime

Mega
[Samsung Galaxy Mega] trurl3:
Yes, there is something wrong but I do not know what! I have downloaded 3 odins: 3.07, 3.09 and 3.10 and use every one. I have changed USB cables akd slots (those on MB too). I have fresh installed Kies so drivers should be OK... what else I can do? Maybe try to reinstall drivers once more.
[Samsung Galaxy Mega] megalomanic14:
Don't install kies install the drivers from the mega itself...simply plug it in and let it setup the drivers

And make sure you're running Odin as administrator...

Mega
[Samsung Galaxy Mega] its the peanut:
Its really weird... I dont know if you use a usb hub or something? But if you do, dont. But as mega says, remove kies and the drivers completely, plug in your mega and let it install new drivers by itself.

But still is doesnt make sense cause I also used samsung kies to install drivers etc and then with odin flash the udne base...

If all of this doesnt work, maybe try an other pc maybe?

---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------

Odin cant run without administrator rights... if it does it would not flash the base on the mega, or you cant even boot into the mega after flashing.
[Samsung Galaxy Mega] KennyLG123:
He's right kies can mess with odin
[Samsung Galaxy Mega] megalomanic14:
Yea and its obviously not flashing the base on his mega lol ...so it's not an ordinary situation that was the whole point lol

Mega
[Samsung Galaxy Mega] trurl3:
- Kies with drivers uninstalled

- Administrator rights for odin granted

- New drivers installed

- Another USB cable used

- Another USB slot used

NOTHING

Now is only one hope - another PC...

Is it normal so after reboot there are two red lines at the top of screen? Something about STATUS... Definitely SOMETHING was flashed at the first time
[Samsung Galaxy Mega] megalomanic14:
Typically only when your base system doesn't match...I only got it running mf but I don't think I've seen it since coming to mk

I mean those are i9205 bases just to make sure you don't have the i9200 which is the only other possibility I can think of

Mega
[Samsung Galaxy Mega] trurl3:
Thak you for attention! Problem SOLVED!! I sat to my wife's PC with Win8 and without any problems flashed base with all elements. So there is warning for anybody who wants to flash with odin: do not do it on Win10 !! At least until there will be new version suitable for Windows 10 :).

Thank you for help folks.

[MENTION=5451734]megalomanic14[/MENTION] - I hope my odyssey was useful for you - I think so aside problem with Wi-Fi, it is proven now so there is way to go back from DBT base to MegaKat?

Good night for all - in my place is now 1:15 AM
[Samsung Galaxy Mega] megalomanic14:
Are you on the new stock rom? If so we really just need to see if Philz recovery and root work...yes very useful that's interesting the drivers don't work for Windows 10

Mega
[Samsung Galaxy Mega] KennyLG123:
Thank you for your hard work.. Well it will be day light there soon might as well stay up like mega. lol..
[Samsung Galaxy Mega] trurl3:
Yes, I am on new stock rom I9205XXUDOA1_I9205OXXDOA1_I9205XXUDOA1_HOME.tar and root is achieved without problem.
[Samsung Galaxy Mega] megalomanic14:
That's all we needed...will test the build tonight

Mega
[Samsung Galaxy Mega] trurl3:
Will it make difference so I am on such base? Or it will be necessary to switch to your base before flashing new Megakat?
[Samsung Galaxy Mega] megalomanic14:
If your already on the dbt base I posted then just stay until the new build is out...if you flashed another base yea you'll have to Odin the dbt base before flashing the new mk when it comes out

Mega
[Samsung Galaxy Mega] KennyLG123:
I was going to put windows 10 on one of my laptops, I may have to hold off or just go for it. I'm sure the new drivers should be coming out around Aug. or run programs backward compatibility with win 7..