yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] jake21:
Is it available yet (where will it show up when available) ? Actually I'm still on the defunct cleanrom and is it smart to upgrade or just stick with cleanrom. I know it is dated but I need a phone that works reliability and I don't seem to be missing any featurs I need on a daily basis...
[Verizon Samsung Galaxy Note II] mistermagic87:
Thanks for all the hard work to everyone involved. Will the new modem require a Odin flash or will it be an all in one package we can flash through recovery?
[Verizon Samsung Galaxy Note II] rayjr13:
[MENTION=497842]scoobysnack[/MENTION]

Is sKKy_n3b being developed/managed in this thread?
[Verizon Samsung Galaxy Note II] scoobysnack:
I've been working on it some in my spare time. Why what's going on with it?
[Verizon Samsung Galaxy Note II] lacoursiere18:
New modem(it's flashable thru recovery) is already up in Downloads tab on top of thread..updating slowly.. we are deknoxing/deodexing the build now..
[Verizon Samsung Galaxy Note II] tgyberg:
Where, in the OP? Thanks!

**NM, I had to change xda to 2013 to see the tabs!
[Galaxy S 5 Q&A, Help & Troubleshooting] ScubaInstructor:
Hi,

I had my S5 rooted after I bought it.

When I updated to the latest firmware (using KIES as OTA was not working) I lost root.

CF autoroot won't root my phone anymore. How can I get root back?

Thanks

J
[Galaxy S 5 Q&A, Help & Troubleshooting] Michael_P:
Try updating using Odin.
[Galaxy S 5 Q&A, Help & Troubleshooting] ScubaInstructor:
Not sure I understand what you mean.

What I did!

Bought S5. Rooted with CF autoroot.

On 24.5. a firmware update was available from Samsung.

Installation OTA not possible due to root.

Samsung firmware updated using KIES.

After update root was gone.

Odin and CF autoroot fails now:

<ID:0/003> Firmware update start..

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL! (Auth)

Any ideas?

The button in Odin does not go to yellow as mentioned.
[Galaxy S 5 Q&A, Help & Troubleshooting] ScubaInstructor:
I got it to work again.

-> I removed the SDCARD and disabled the Reactivation Lock.
[Xperia Z2 Q&A, Help & Troubleshooting] SavCom:
I've been using my Z2 for about six weeks now and on the whole I've been very, very pleased. However, recently I have noticed that when turning it on it occasionally doesn't wake up and stays resolutely black. It doesn't hang - more it doesn't respond to the power switch or the screen.

Another issue I have is one where the wifi goes into a sort of inbetween state where it isn't on and it isn't off and won't turn on or off via settings. This clears after a reboot thankfully but it is annoying.

Can anyone shed any light on these issues at all? I'm running 17.1.A.2.55 on EE in the UK.

Sent from my Xperia 2 while my back was turned.
[M.O.J.O. General] AmigaWolf:
Your unbelievable zektor, first you act like a little child to me because i was saying this for a long time, and you was making stupid posts of how stupid my phone is and how stupid you must be to have a phone like mine, and more.

And now you are saying this, make up your mind.
[M.O.J.O. General] zektor:
Your phone and your attitude DOES suck. I did not change my mind about that :) Your stupid posts compound the issue and make the Mojo less desirable...or at least the Mojo forums. Congratulations for that. You should be given a "major award". Your posts have nothing to do with mine. You were just a crybaby because you bricked yours and they had no more in stock to replenish it for you.

As for the Mojo, I still stand my ground that it is the most powerful (currently) Android TV box on the market. That is fact, not me just saying it. It is a shame the way it has turned out however with the lack of support, no development, and a weak forum with only a handful of helpful and encouraging people and one real dipstick (hint, the post above)
[M.O.J.O. General] AmigaWolf:
Oh wait i forgot, is it bed time for you little child, Yes i hear your mother yelling that you must go to bed, because you must go to school in the morning.

Sleep tight, and don't let the bedbugs bite.
[M.O.J.O. General] buggin0915:
I agree with zektor I biught this cuz it said was going to be rooted and was good quality but was very disappointed with the extra stuff I had to do. Not for the average person. Hes right the more people the more development from devs amd if it takes mad catz giving some free out to high level devs to make thier product better then they need to hurry up. There used to be a mad catz rep here but ive seen nothing for a while I ciuld be wrong. Maybe cause he has blno answers anymore
[M.O.J.O. General] gwaldo:
Strange that a week ago you wrote Reasons you SHOULD buy a M.O.J.O.. the mojo hasn't changed,Android hasn't changed, the community hasn't changed.. so what's changed? " because I feel the lack of support, updates, news, development, anything at all"

Well there was an update 2 days ago: http://madcatz.com/4k-coming-to-mojo/

Apart from that, it hasn't changed.

Obviously, it's not a cheap toy like Ouya, so yes less devs and I would agree with you: "No way to get in and install a custom rom (or even stock rom if bricked) is just asking for trouble. "

But

I'm guessing

, like rooting, madcatz can't do it or release the image due to legal reasons (it's android/nvidia's software) obviously it would be nice if it "leaked".. then yeah sure I too would try more risky stuff..

Price point I think it's great value and a complete package

with the ctrlr

... ie I don't like the amazon firetv controller, moga etc.

re Advertising etc, I think they are timing it, it's not cheap to advertise.. I'm guessing they are waiting to finish kit-kat/ouya everywhere before doing so? I don't know.. don't really care

"I wish the Mojo was the ultimate answer (in hardware it nearly is for me) but software/development/support ends up being even MORE important than the hardware contained. It's like someone giving you an 8-Core CPU but only providing software that takes advantage of one core. Ugh. "

Madcatz is a hardware vendor, TMK they don't do software... and that's one of their selling point, no vendor lock in.

It's like you bought an Dell laptop and returned it because Dell didn't put out enough patches/upgrade? :silly:

What community mods makes you think your not running on all 8 cores?

I mean you had a good set up... what exactly couldn't you do?

Anyway, I'm still optimistic and it's still early days, MOJO is future proof, it's spec's are still top of the line and will continue to be for a while yet.

I wouldn't be surprised if kitkat/ouya comes out closer to the holiday season. ;)
[M.O.J.O. General] zektor:
Yes, it was a nice setup and yes, I still do believe there are reasons to buy the Mojo. But, it is not future proof. It is getting older by the day (the Tegra 4) and more and more devices will have the processor (or something more powerful) built in. When that happens, the Mojo will become less exclusive and less desirable. It is also not future proof because the minute you run a rogue app that requires root and it bricks it (or you brick it in any other way) the Mojo is essentially done for. Not having a way to recover from a brick is not something that is acceptable nowadays.
[M.O.J.O. General] christoph80:
It's nice to see some news. The 4k support means they are doing something. Not hearing anything for almost 3 months since ouya announcement and kit Kat upgrade has made it hard to have faith in improvements, but it sounds like it may still be coming
[M.O.J.O. General] rickyd1982:
What is future proof nowadays things are changing at a very fast pace but I'm in no rush couldn't be happier with my mojo there may be new hardware coming but its not out yet and there is nothing on the play store that this baby won't run at this time horse before the cart
[M.O.J.O. General] gwaldo:
I agree about not being able to unbrick it ourselves is an issue.. but it doesn't make it less future proof IMO.

Having an active community helps.. but with android/nvidia in it, we/I can 'piggy back' on other groups for info ie shield, ouya, other T4 products.

As you may or may not know, there are very few pieces of technology that have stood the test of time.

I can name a few from personal experience here:

Commodore 64

MS Windows XP

Nokia N900 & Maemo(native linux)

The mojo & CTRLR are so versatile, I'm sure I'll still be using it well after it's product lifecycle... that's future proof!
[M.O.J.O. General] zektor:
It is funny you mention the C64. Not only do I know it...I lived it :) I ran a BBS for many years and was a part of a demo group in the mid-late 80's for the C64. I know all well how it stood the test of time, and still own and use one (and develop on it) today. It is well documented, I can fix them, mod them (now with SD2IEC and other neat stuff) and they will essentially last as long as the hardware does.

The Mojo IS a cool system, I have never said otherwise in regard to the hardware. But I honestly cannot say that it will stand any test of time...sadly. It is a flash in the pan as compared with the likes of the other items you mentioned, *especially* the C64. It almost feels like blasphemy to put the two in the same sentence :)

But, Mad Catz could definitely redeem themselves if they became a little more proactive in the area in which the system's target audience resides. Namely HERE, and in other forums concerning Android TV boxes. Maybe some of there techs can get involved in conversations, provide useful tips, and check with their senior technicians regarding in depth questions that we may have. As it stands now it is a ghost town. I wonder if the Mad Catz employees read these forums and chuckle at what suckers we are for buying in. I REALLY hope that is not the case.
[M.O.J.O. General] AmigaWolf:
But you forget Zektor nothing nowadays is made to last, back in the 80 and 90 hardware was made to last 20 a 30 years, like the

Commodore 64 (and i have one with a floppy drive and a tape drive, and also had Commodore Amiga for years, still have a Amiga 2000 from

1987 and it still works.

But all the stuff that is now made is not made to last, they (the manufactures) want that you buy new hardware every view years, thats why

Android phones only get 1 a 1.5 years of updates if your lucky and then nothing, when a Samsung Galaxy S3 can run Android 4.4 KitKat easily.
[M.O.J.O. General] zektor:
I can agree with you here. We live in a throw away society unfortunately. However, there are still items that are made to last, but they are "hidden gems" more or less. The vast majority of items are made like garbage, but every once in awhile you find something that is built like a rock. My Canon Powershot S80 comes to mind...which is actually quite a few years old now. Out of the items made today (in terms of these devices) the Minix is build VERY nicely, same with the Ouya. The Mojo is of decent quality, but it still feels like a hollow piece of plastic to me for some reason.
[M.O.J.O. General] christoph80:
Computer cpu's are built to last, just in the past they got outdated so fast. These days you can get a new cpu and be good for a very long time and it will outlast any other piece of computer equipment. I've actually never had a cpu go bad. But at the non component level, most consumer electronics have very short shelf life.
[M.O.J.O. General] gwaldo:
I don't agree, there are still companies out there that make great and out lasting products!

They add extra features that others don't, yes it's more expensive but less disposable.. like the SID chip on the C64 and the BT4/USB3,etc on the MOJO... it didn't have to be there and it's really at the manufactures risk/expense because it's their profit margin that it effects.

But it gives the company integrity for not selling out like their cheaper competitors.

I think things now are built for the lowest common denominator and only the brave step out of that.

IE: mobile phones, In Australia, it's next to impossible to buy a new mobile with a keyboard :(

Anyway, it's interesting
[Xperia Z2 Original Android Development] DooMLoRD:
Hey guys I dont know how many of you have noticed this but the Xperia Z2 has a "two step" booting process... first an initial kernel is booted, the one which shows the "Sony" logo.. and after that the custom kernel get booting... it might be using some sort of Kexec may be?

i noticed this when i saw that it was taking longer in boot process and it was not showing my custom bootlogo... so i investigated and this is waht i found in the dmesg:

root@D6503:/ # dmesg | grep logo
dmesg | grep logo
<6>[ 3.378925] Skip drawing logo. Already drawn in boot.
<3>[ 9.679902] init: cannot open '/initlogo.rle'

if i compare it against the Z1:

root@C6902:/ # dmesg | grep logo
dmesg | grep logo
<6>[ 4.366685] Drawing logo.
<3>[ 10.875083] init: cannot open '/initlogo.rle'
root@C6902:/ #

i have hacked the code to show my custom bootlogo so i am happy but it might be interesting to see what we can do if we can access that "base kernel"... may be we can explore proper multi-boot solutions?

what do you guys think?

P.S.: this is ment ONLY for DEVELOPERS to discuss... noobs/thank-you posts ARE NOT WELCOME!

only post if you have something useful to contribute...

regards,

DooMLoRD
[Xperia Z2 Original Android Development] pvyParts:
yo dude,

i am assuming that it is not part of the "boot.img" and is in another partition ( bootloader ? )

pvy
[Xperia Z2 Original Android Development] Desperanto86:
Can fotakernel has some part of it? If we unpack it we can see general kernel. Also we can flash recovery to fota and it will work (tested on Z1).
[Xperia Z2 Original Android Development] DooMLoRD:
fota kernel is different...

u cant fash recovery on fotakernel and use it to boot... what was done for Z1 was to use fotakernel as a location to store recovery ramdisk... main kernel still has to boot to extract the recovery ramdisk..

nope... it stored on some other partition...

need someone with more knowledge of booting process of these new msm8974 chips
[Xperia Z2 Original Android Development] vishal_android freak:
Is sony going the Google way somewhat? Nexus bootloaders have their Google images into them by default. Hence kernels don't have any boot logo. May be something similar to it. Not exactly but something in relation with it
[Xperia Z2 Original Android Development] DooMLoRD:
Interesting
[Xperia Z2 Original Android Development] vishal_android freak:
Even Samsung and LG are like that if you see. On each boot the device name appears along with samsung logo. On LG, the LG logo appears. If it doesn't change with kernels, either all kernels use that bootlogo only, which is very big coincidence or the images sit in the bootloader.
[Xperia Z2 Original Android Development] Jackos:
Did previous Xperia phones allow you to change the "first" Sony bootlogo in kernel? That would be weird and unusual for Android phones.
[Xperia Z2 Original Android Development] DooMLoRD:
there was never a "first" sony logo... u change logo.rle and it will show you that at every boot...

but this is different behavior, typical of 2-stage/chain loading...

may be the Z2 uses a LK type bootloader?
[Xperia Z2 Original Android Development] Jackos:
Welcome to normality ;)
[Xperia Z2 Original Android Development] DooMLoRD:
well for sony xperia phones this is a BIG abnormality! of all the devices i have worked on so far (25+ xperia phones) this is the first one to do something like this!
[Xperia Z2 Original Android Development] Abhinav1997:
Seems quite different. Nothing like that in my Xperia T2 ultra.

<6>[ 1.673444] Drawing logo.
<3>[ 7.190843] init: cannot open '/initlogo.rle'

AJ
[Xperia Z2 Original Android Development] DooMLoRD:
So what do you get on that device?
[Xperia Z2 Original Android Development] adfad666:
From experience with an old LG device the actual bootloader showed its own logo, then the boot image showed its own logo, then finally the Android boot animation would start.

On a stock ROM you couldn't tell this as LG used the same image in the bootloader and the boot image. However in the upgrade from Android 2.2 to 2.3 they changed the image, so when flashing CM after upgrading the bootloader you would see two different LG logos.
[Xperia Z2 Original Android Development] DooMLoRD:
ya I have seen that on my LG Optimus One...

the point is that Sony has traditionally never used such a "Bootloader logo"... even in the Z Ultra GPe there is no such thing...
[Xperia Z2 Original Android Development] adfad666:
You had p500 too? nice :)

Perhaps they just decided they REALLY want us to see the Xperia logo...
[Xperia Z2 Original Android Development] DooMLoRD:
ya had a P500, never really developed for it as I had got it for my parents :)

well its the Sony logo...
[Xperia Z2 Original Android Development] adfad666:
Is it? I should really pay attention when my devices are rebooting! (though I did notice how the logo is aligned to the power button on the newer models!)
[Xperia Z2 Original Android Development] DooMLoRD:
its actually center aligned w.r.t. the full device height and not the touchscreen...
[Xperia Z2 Original Android Development] adfad666:
Z2 is definitely aligned to the power button, like the rear logo too!

View attachment 2777337
[Xperia Z2 Original Android Development] DooMLoRD:
ya exactly! i was just going to say the same thing!

(sorry for OT)

coming back to the topic... can we actually use this in some way?
[Xperia Z2 Original Android Development] Hans.physics:
So on this two step booting process, is that why I somehow have TWO recoveries installed at the same time? I installed DoomKernel as part of my original rooting process. I then installed Monx Rom, which installed TWRP. Using Rom Manager, I tried to put CWM back. Now, whenever I reboot to recovery, CWM will come up, but when I reboot system from CWM, it boots to TWRP. From there, when I reboot system, it then boots up to system. Some weird side effects to this too. I lose some installed apps when I finally get back to Android. RSA Secure ID and Go Launcger Ex seem to be the two that are constantly being "forgotten" when I go through this cycle. Also, I did a "Erase SD" from the settings menu. All was good, Ext SD was functioning fine, nice and clean. Then, Reboot recovery and go through the who double recovery cycle and WHAM! My ext sd has ALL the data I erased back on it.

So, is this double boot process you speak of responsible for this behavior?

Thanks,

-Hans
[Xperia Z2 Original Android Development] DooMLoRD:
No
[Xperia Z2 Original Android Development] defsix:
LOL !

As for the dual recovery problem, i'd a similar problem on a Sony Tablet S , one boot cycle i had root and X number of apps, on the second boot i had no root and Y number of apps.

Factory reset , full re-flash, factory reset and finally root was the only way I got it back to normal.
[Xperia Z2 Original Android Development] vishal_android freak:
Afaik, rom manager will install a recovery. tar format of recovery which works on chargemon hacking. Bcz we don't have a separate partition for recovery here. So that's why cwm exist in your system and twrp in your kernel :P
[Xperia Z2 Original Android Development] waynekirby:
But we have FOTA kernel partition do we not? Wouldn't we be able to utilise that for dualbooting?
[Xperia Z2 Original Android Development] Juan_Largearm:
I was just thinking about this while looking at the ROMs on offer at the moment. The googymax kernel I had on my S3 was great as it allowed me to use a stock ROM I could quickly boot in to and record in amazing quality instead of the custom ROM as that used the CM camera which couldn't use the same drivers as the official camera. The kernel also messed with my partitions and uninstalling it led me to have two recoveries, a CWM and a TWRP.

I'd love to see multiboot so I still have the bonus of a custom ROM but still have the option to boot to stock if I want better camera stuff.
[Xperia Z2 Original Android Development] HenryAdda:
Do you know how can I disable that sony boot logo?
[Xperia Z2 Original Android Development] svshift:
Did you manage to solve this? Any hints?
[Xperia Z2 Original Android Development] svshift:
[MENTION=2784807]DooMLoRD[/MENTION] I was able to locate the boot logo in my Z3C, i think in Z2 it is similar.

It is stored inside the aboot image, as a LZ4-compressed data. , which is decompressed shortly after display is initialized.

I used IDA-pro to dissassemble the aboot image as it is said in http://newandroidbook.com/Articles/aboot.html (strip the header, and provide correct "loading offset" from ImgBase from the header)

then i found "Decompressing logo failed" string in it, and a place where it is printed (dprintf)

right before it there is a call to function, which looks like LZ4_decompose_safe() and a little before it there are its arguments -- pointer to compressed data and size

(in my case: 7545 bytes at 0x0004a67c in the aboot image file)

some sorces of LK-loader and grub4android sources helped me a lot.

so, i see a way to replace it as:

1. compress the logo by LZ4

2. if it smaller than 7545 bytes, you can replace the original one, and fix the size constant (dword at 12 bytes before it)

3. or append the custom logo at the end of the image and fix the aboot headers, and data adresses inside the code.

I DID NOT test it yet, but I'll post the results as soon as get to this.
[Xperia Z2 Original Android Development] svshift:
well, look like sony does not like tempering with aboot at all. It is impossible to reflash it via fastboot command,

and once i did it on the device with dd command, it simply bricked. completely. not even the fastboot. and i am sure, that i did not break any code section. I modified only the necessary constants and image data, i double checked.

now i'll have to wait to get to the closest JTAG debugger-reflasher, to see what's wrong there ж)
[Xperia Z2 Original Android Development] Gustavo RD78:
I'm sorry for brick your device

any news about these tests?

I have also analyzed these files, aboot is directly connected to bootloader

android N preview uses white bootlogo with Sony written in black, which has new bootloader
[Xperia Z2 Original Android Development] svshift:
well, kernel can be unlocked, but aboot is signed. somewhere around here there was a thread about signature keys for old xperia Zs. cant find it now.
[Google Chromecast] Krisshp:
Hello,

I have the Avia app which I bought, like 2-3 weeks ago

i delted some files from my phone, but they keep showing (icon/name) on avia when I DON'T have them :(

How do I refresh this? I click refresh a 100 times but no luck, how do I delete the cache or rebuild it?

Does this happen to only me?
[Google Chromecast] Cuzz1369:
Go to settings>apps> find avia and clear data. Then reboot.