yashsingh1/xdaforums huggingface dataset:
[JAMin, XDA Neo, S200 Software Upgrading] cedrick:
It is sad indeed...

At least the good news is that you're back... so welcome back Jesterz :)
[JAMin, XDA Neo, S200 Software Upgrading] slvrbllt:
History teaches us nothing.

It is not by taking the ROM archive dowm that MS can stop ROMs from going around!

Why don't they simply try to release ROMs that WOULD NOT require any interventions from the final user instead.

Looks like the "prohibitionism" has taught these guys nothing at all.
[JAMin, XDA Neo, S200 Software Upgrading] bitbob:
i suggest we can use http://www.mydatabus.com host to share our roms. (up to 5 G space pro person and stable).

Rapidshare, megaupload, uploading...etc are not good solutions for us to download and exchange file. Because it will be deleted in limited times.
[JAMin, XDA Neo, S200 Software Upgrading] P4k1t0:
looks great this site!! i will use it!

EDIT. One question in this site...ours files don´t are delited?
[JAMin, XDA Neo, S200 Software Upgrading] bitbob:
it is yourself's private storage space, it depends on you, if delete a file or not. but when you want to share the file, you must make it public.
[JAMin, XDA Neo, S200 Software Upgrading] arvind09:
Any idea where i could download jesterz G4 rom? Am in urgent need of it.If someone could help me out i would be really greatful.
[JAMin, XDA Neo, S200 Software Upgrading] conix:
Thanks Jesterz,

please keep us posted of the possible new roms!
[JAMin, XDA Neo, S200 Software Upgrading] Matterhorn:
Does anyone know of official archives for ROMs outside of XDA ftp?
[JAMin, XDA Neo, S200 Software Upgrading] deezer:
type "RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe" in google...
[JAMin, XDA Neo, S200 Software Upgrading] sabych:
We demand our freedom

I came into this forum a couple of weeks back with a bricked prophet G4 & a O2 XDA Exec(UK). Since then not only i have been able to restore my prophet ,I have been able to learn a lot abt PPC as a whole. Its a shame that M$ feels thereatened by this forum as we have done nothing wrong except to give people choice!!! Isn't it our right to choose & develop??? Who's MS to stop us?? Where were they whan I was running from pillar to post to get my bricked prophet running....
[JAMin, XDA Neo, S200 Software Upgrading] tanim_1976:
I signed the pitition happily

MS ant stop them selv! They cant think anyone except them doing the developings, as if they may want to close all the sites where our great friend and developers discussing the facts, it wont be a surprise!!!!! all we want is our freedom to developers!
[JAMin, XDA Neo, S200 Software Upgrading] wade:
I Am Going To !
[JAMin, XDA Neo, S200 Software Upgrading] lizh.cn:
hI......:) :) :)
[JAMin, XDA Neo, S200 Software Upgrading] The_Fire_Ball:
We can use the "BitTorrent" Protocol, it has proved to be the next-gen sharing or swaping files ! maybe replacing the ftp server of xda-dev with a seeding server :D just my little thoughts ....
[JAMin, XDA Neo, S200 Software Upgrading] l3v5y:
That would be really good, they'd have to knock out all of the hosts to stop the sharing :)
[JAMin, XDA Neo, S200 Software Upgrading] z830:
Damn fool M$!

It acts just as PRC government or Nazi.

They can't shut down all the share sites...
[JAMin, XDA Neo, S200 Software Upgrading] l3v5y:
They don't though. They could have taken down this site a long time ago but they've realised it is helping them and not damaging them.
[JAMin, XDA Neo, S200 Software Upgrading] dioxda2:
So ...... Agreed!
[M.O.J.O. General] Unjustified Dev:
Currently the M.O.J.O has been a very unsuccessful device and there hasn't been any recent development. I would like to give a try at a few things such as a custom recovery

I am asking for someone to provide with me with the output of the following commands

Start adb shell

cat proc/iomem > iomem.txt

cat proc/partitions > partitions.txt

getprop > prop.txt

I've attached a test cwm recovery.img DO NOT FASTBOOT FLASH RECOVERY!!! use the below command to test the image

fastboot boot recovery.img
[M.O.J.O. General] gwaldo:
Hi,

Thanks heaps for helping dev on the mojo!

I'm keen to help!

Done.. I"ll try the image now.

It does nothing for about a minute, then the blue light comes on the screen says 'mode not supported', tried on a monitor (with a HDMI to DVI) same 'mode not supported' then no signal.

Not sure how you would get debugging info out ... that's been the main problem :(

Anyway, if you need any more info or test, just ask.
[M.O.J.O. General] Unjustified Dev:
Thanks it helps a lot with the device tree. How did the recovery turn out?
[M.O.J.O. General] gwaldo:
Didn't do anthing, or at least I couldn't see it on my TV nor monitor :/
[M.O.J.O. General] Unjustified Dev:
Thanks it could be a kernel issue I'm working on kexec hardboot I'm going to remove that for now and build again.

edit: Attached new image as well as a new adb and fastboot binary for you with adb and fastboot id added

https://github.com/TeamRegular/android_system_core/commit/effaa8a925b68651dbb1a0d50cffb81e57df9f5d

I replaced mine in /usr/bin/ with these and they still work as normal for me.
[M.O.J.O. General] gwaldo:
Wow, I didn't even know fastboot had a github, you're very pro sir! :good:

I run it now:fingers-crossed:

using your exe (on my 32bit Mint linux 17):

But again same result :(
[M.O.J.O. General] Unjustified Dev:
You can build those in an android environment that's actually from the source you would use to build a full rom I just forked the tree from CyanogenMod added the id and compiled it.
[M.O.J.O. General] gwaldo:
Not sure what else to do, to get into the existing mojo's recovery, is pretty hit and miss for me (I get unsupported display a lot until it work) so not sure if that's normal... i'm a android dev noob, so don't really know how to use adb to debug the boot image.

Not sure if having a usb keyboard/mouse plugged in will help?

Edit:

Also the nvidia shield (Tegra4) is similarly spec'ed but not sure about the HW components.

It is a well documented and hacked device.

I'm sure so of what they do is applicable to mojo also?
[M.O.J.O. General] Unjustified Dev:
You should be able to run adb reboot recovery while the device is booted.

edit to your edit: The shield work is not applicable to the mojo but I have worked with the shield as well as ported cwm easily I'm wondering why this img won't boot I've seen the troubles in the other thread. I'm thinking maybe install the image to your recovery partition and adb reboot recovery it will not brick the device as the recovery image is safe on a partition that doesn't effect the booting process the boot partition on the other hand I would never fastboot flash it without testing if it boots first. I'm wondering if the img is too big for the partition maybe. I'm not sure the partition is 8mb the image is 7.6 I'm going to change the compression and see if it boots. You also no longer need the -i 0x0738 when using fastboot

Last edit could you pull proc/config.gz
[M.O.J.O. General] gwaldo:
I think it is booting, I just can't get a working display.

With a keyboard I can boot your recovery image and do a ALT Printscreen O and it turns off as expected.

I know a few of these keys from here: http://xdaforums.com/showpost.php?p=54517256&postcount=32

I'll get that file for you now, I don't have adb set up.
[M.O.J.O. General] Unjustified Dev:
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.
[M.O.J.O. General] gwaldo:
I'm running this update mojo-signed-ota-MO0202-WW.zip

from ftp://86.54.116.234/pub/software/mojo/firmware/

I think the kernel src version is from the first firmware update (mojo-signed-ota-MO0110-WW.zip) or it could be even before that.

I think the problem (maybe just mine) is I can't get a display in recovery with out a lot of F'ing around.. ie: randomly pressing home up/down ALT PRNTSCRN I etc... but like I said, your image does work as it responds to ALT PRNTSCN O

---------- Post added at 01:49 PM ---------- Previous post was at 01:33 PM ----------

SH!T IT WORKS!!!

I couldn't get a display, so I ran it through my HDMI capture device, not expecting to record anything any it worked!!!

I'm uploading a vid now!

Congrats dude! you did it! :)
[M.O.J.O. General] Unjustified Dev:
Here's the change https://github.com/TeamRegular/andr...mmit/e82e271131d30290022f301b70089cf2fb9224d3

It's also enabled on the shield I can't remember but it looks like I did it when I worked on the shield as well since it's not enabled in the defconfig they give us it's probably enabled in their nvidia source builds I can't remember how all that works it's been a while since I had shield source downloaded but hopefully this is the problem.
[M.O.J.O. General] gwaldo:
I'll test it out, but your previous image works, my TV nor monitor likes the resolution (guessing).

Any chance of defaulting to a low res? or booting into a safe mode?
[M.O.J.O. General] Unjustified Dev:
I guess I would have to switch to twrp recovery I'm not sure what theme would fit but I added the size for mojo already It's just a matter of building it. Honestly most of the time twrp display code works better than cwm.

https://github.com/TeamRegular/android_bootable_recovery/commits/android-4.4
[M.O.J.O. General] gwaldo:
Here's the video, just hitting home and up/down keys.

https://www.youtube.com/watch?v=5A4yDR2Z_GU

It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.

If you build twrp, I'm happy to test it out also.
[M.O.J.O. General] Unjustified Dev:
So this is the first booting just not outputting to screen very strange I'll look into it. I'll compile twrp now it will take over an hour to build I have to setup device to compile in omni rom environment. I'll pm you the build.
[M.O.J.O. General] gwaldo:
cwm-recovery.img also boots.

Really strange that I can't see a display but I can record the HDMI output on my AverMedia Capture HD II C285 as it's really sensitive to HDMI.

Maybe a frequency/refresh rate setting?

With the MOJO's recovery menu on my monitor I get:

MODE NOT SUPPORTED

H: 67.5KHZ

V: 60.0HZ

With your firmware:

MODE NOT SUPPORTED

H: 67.2KHZ

V: 59.7HZ

My TV is PAL, if that helps.

I'm guessing because the MOJO has no screen it's not sending a 100% correct HDMI stream.

Whatever the issue is, it's also in the default recovery.

Anyway, I'm sure others will try out your recovery image and we'll get feed back.

No problem, happy to test it out :)
[M.O.J.O. General] Unjustified Dev:
I'll take a look into some later commits from nvidia git the mojo kernel is quite outdated. I found last merged commit on this page

I tried to pick each one and ended up with a ton of issues I will try again in the next few days doing page by page only and building

https://github.com/somcom3x/android_kernel_nvidia_tegratab/commits/cm-11.0?page=24
[M.O.J.O. General] shabbypenguin:
Interesting, im using a monitor which supports many formats and it wasnt able to pick up when i tried my hand at CWM, alas i didnt have a screen capture device so i just assumed it was something wrong with foxconn's programming/setup than just graphics not displaying properly.
[M.O.J.O. General] gwaldo:
Hey :)

Same.. I didn't think to try back then :/

But I still think your right about foxconn's :cowboy: programming lol

Good to know that it's a real issue and not just my old HW

Comparing Ouya's recovery HDMI/video config settings would help?

It has to work better then mojo's :confused:
[M.O.J.O. General] Unjustified Dev:
I'm reading through all 24 pages of later commits where mojo seemed to stop merging and see if anything interesting comes up. I did see quite a few hdmi and fb changes I might just pick those rather than all the other commits.
[M.O.J.O. General] gwaldo:
That's really cool of you, PM your paypal email so I can shout you a drink!

---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------

That would be really good!

The rest I can have a go at after getting set up again.
[M.O.J.O. General] Unjustified Dev:
I had to change the compression and remove a few things but it finally builds and fits in the partition size :good:
[M.O.J.O. General] gwaldo:
It says:

And it didn't boot the OS.

Still has the same issue with display

Video: https://www.youtube.com/watch?v=fvdKo5mug5U

Edit did another longer video,

After "Key driver not found... Booting OS"

It says "Booting download image"

Then it goes back into bootloader mode (where ./fastboot devices list it as active).

https://www.youtube.com/watch?v=CLlMyy7PE38
[M.O.J.O. General] gwaldo:
So I got adb running, I"m using the one you attached.

Here are my notes on getting it to work:

I'm no Android expert, but the below worked for me, it's probably not 100% correct.

in fastboot mode ( when the mojo has the male-male USB cable plugged in)

lsusb: Bus 002 Device 033: ID 0738:a210 Mad Catz, Inc.

dmesg:

in recovery mode (./fastboot -i 0x0738 boot cwm-recovery.img )

lsusb = Bus 002 Device 030: ID 18d1:d001 Google Inc.

dmesg:

Setup adb, do this once:

Start the adb server before turning on the mojo

When mojo is off, plug the male-male USB into the mojo and PC.

Plug in the power, your mojo is in fastboot mode.

Now, to put the mojo in recovery mode, if you get

run it using sudo, sudo ./fastboot devices

15C40C1C30400000012FC8380	fastboot

if you get

< waiting for device >

when ./fastboot -i 0x0738 boot cwm-recovery.img

again, use sudo ./fastboot -i 0x0738 boot cwm-recovery.img

./adb devices

List of devices attached

15C40C1C30400000012FC8380	device

If you get ???????????? no permission

Try restart the adb server, leaving the mojo in recovery, just unplug a USB cable end and plug it back it, run:

./adb devices

./adb pull /tmp/recovery.log

./adb shell cat proc/kmsg > kmsg.txt

for a mojo shell:

./adb shell

helpful links:

https://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/

http://xdaforums.com/showthread.php?p=29314820#post29314820
[M.O.J.O. General] Unjustified Dev:
Could you grab a kmsg from the device when booted with display just to alleviate any ideas.
[M.O.J.O. General] gwaldo:
What do you mean with display?

I can't see the display (tried on three devices now), but i'm sure it's the same as the youtube video I posted.
[M.O.J.O. General] Unjustified Dev:
I meant when booting into the android system where the display actually works

attached new image hope this works.
[M.O.J.O. General] gwaldo:
That image takes about 45sec or more before the light comes on and goes into adb mode.

Same issue with the screen.

I've enable USB debugging on jellybean, but I don't get anything on lsusb, fastboot nor adb.

Not sure how to debug in jellybean.. i'll google it.

Edit:

look at the start of recovery log file

That's a huge resolution, doesn't look phone friendly?
[M.O.J.O. General] Unjustified Dev:
Here's another image that's the hdmi output resolution by default
[M.O.J.O. General] gwaldo:
http://en.wikipedia.org/wiki/Magic_SysRq_key

Very handy keys, ie:

Hold both right hand ALT + Sysrq keys and then hit:

b = reboot

o = power off

i = SIGKILL signal to all, if done a lot of times, it will boot into recovery

To get jellybean USB debugging

sudo ./fastboot continue

resuming boot...

OKAY [ 0.000s]

finished. total time: 0.000s

To get into the factory recovery ALT + Sysrq + i or in jeallybean I use rebootmenu app which has reboot into recovery option.

I normally get a blank screen, same issue with your roms, but I can ALT + Sysrq + i a few times and hit home and i get the broken android image, hitting home brings up a small menu, with an option to update an image via adb, I selected that but adb doesn't work (ie usb isn't detected).

---------- Post added at 11:27 PM ---------- Previous post was at 11:06 PM ----------

Hey!

It boots up quick again, and goes into unsupported screen mode, but a (right)ALT + Sysrq + i and it's up!

I've tried it a 5+ times now and it works all the time!

I'm guess there's something not 100% right in that initial process/program and when its restarted it works, works good!

I tried it on your cwm-recovery.img and it worked the same also.

The difference with the mojo's custom recovery, for me it doesn't work on a single (right)ALT + Sysrq + i, but randomly.
[M.O.J.O. General] Unjustified Dev:
So we're good to go? Does usb drive etc mount correctly? All these changes came from milaq for the ouya

https://github.com/TeamRegular/andr...mmit/475bb047d270086d4d565904e29e857ee9bcfc5a

I don't know about the CONFIG_TEGRA_CEC_SUPPORT if needed to be removed to work but only lollipop supports that anyway so it's useless anyway. Now to test kexec hardboot if you want you can fastboot flash recovery the image and make a backup etc as you want I'll build a new one later that should support both usb ports for usb drive
[M.O.J.O. General] gwaldo:
Good to go, I guess, it works.. it has the same issue that the madcatz recovery has with the keys, the up and down keys, I have to hit it twice to move it and it skips a line when it moves :/

I'm using an old USB keyboard but it works fine, any tips?

I'm not sure of the changes you made, but your early image worked as above, like I said I think the first time the recovery program runs it's output isn't correct, but once restarted it's fine.

Does usb drive etc mount correctly? I can't get to that option because of the key issue, i'll try a mouse.

Edit: mouse detected but did nothing
[M.O.J.O. General] Unjustified Dev:
Try caps lock for down and left shift for up enter key should works as select
[M.O.J.O. General] gwaldo:
It did the same thing.. there's an issue with the keys.

The key test confirms this.

ie,

hit up once, nothing happens

hit up again, it print the up asci code twice

etc.. same for every other key on the keyboard

It looks like it's mounting, i tried the sdcard, said it mounted it.

Getting to the menu items is hard, when it loops it gets to the alternative (olds, even, etc) items.
[M.O.J.O. General] Unjustified Dev:
What's the model of the keyboard if I may ask
[M.O.J.O. General] gwaldo:
Its a cheap no brand, model numb: KU-8933

The mojo's CTRLR pairs with it's dongle, I did the key test with it, it detects all digital buttons, but not the d-pad.

And it too need two press and it then would display the asic code twice.

It's 1.30am, going to sleep..

Catch ya in a few hours
[M.O.J.O. General] shabbypenguin:
had a similar issue on the qualcomm s4, turns out a custom recovery_keys.c was needed.
[M.O.J.O. General] Unjustified Dev:
What would I change in the custom recovery keys to stop it from sending the input twice?
[M.O.J.O. General] shabbypenguin:
I would suggest with getting the controller working, as everyone should have that. in advanced you can do key test and get the key numbers for each button and then take teh stock key settings (in bootable/recovery) and add in the ones you wish to add in teh rigth spots. then you can clear out teh otehrs and have a set custom layout that you can design.
[M.O.J.O. General] gwaldo:
Hi,

Yes, I can get the button numbers, no problem.

The issue is the hitting a key/button doesn't do anything, until you hit it again but it then gets two key/button presses which is next to useless.

How did you fix this on the S4?

Edit, CTRLR actually works on mouse mode, up/down Dpad and A as enter, back as back.

Still has the same issue above.

Any clues [MENTION=2614663]shabbypenguin[/MENTION]?
[M.O.J.O. General] sippidigital:
Hi,

i have a bricked (and erased) Mojo. Via fastboot i can boot into CWM Recovery but USB 2.0 port is not working

(testet with CTRLR + mouse mode and keyboard). Any other way to flash a firmware?? :confused:
[M.O.J.O. General] Unjustified Dev:
How did you get bricked and why did you erase it?

You can flash firmware from fastboot itself the recovery is not needed. You will need to pack the system as a system.img and you need boot.img I will pm you.

you will run

fastboot flash boot boot.img

fastboot flash system system.img
[M.O.J.O. General] sippidigital:
I have no idea, this is not my Mojo :cyclops:
[M.O.J.O. General] Unjustified Dev:
Sorry for the delay I nuked my laptop and finally got set back up. Here's the image
[M.O.J.O. General] gwaldo:
Hi,

Tested the image, I can see a flicker when cwm restarts but still no display.

Can you please revert the changes to keyboard, the enter key now doesn't work and the double hitting of the keys/button is still there.

The controller worked on the original version anyway.
[M.O.J.O. General] opiate81:
I had the double key issue with one of the original RockChip CWMs

I found that even though you press the down button once for example and it doesnt appear to have moved, it actually did move (just not visibly)

For me pushing down once it would not move but hitting enter it would go into the menu it was supposed to have gone into
[M.O.J.O. General] gwaldo:
I'll try it in the morning when I turn my PC on, cheers
[M.O.J.O. General] windin:
Bingo

thats exactly whats happening for me, all the menu items are working some some reason the selection indicator is just not showing as having moved
[M.O.J.O. General] Unjustified Dev:
[MENTION=5638480]gwaldo[/MENTION] here's my attempt to port the ouya bootmenu.

It's basically cwm recovery but before the recovery is started it loads the bootmenu which gives you the option to load boot.img from different locations rather than from the boot partition . To test if the bootmenu works you must take the stock boot.img which you can grab from the stock zip and place it in /system/

then fastboot boot the recovery menu. If it works you will have the option to Normal Boot which will load the boot.img from /system/
[M.O.J.O. General] gwaldo:
Attached are the files from philz-recovery.img

ouya bootmenu, screen works! :good:

Edit, added ouya bootmenu files.
[M.O.J.O. General] gwaldo:
Your correct, :good:
[M.O.J.O. General] gwaldo:
Bummer it didn't work(bad res/freq issue), would make life a bit easier with testing images.

Do you think it's a program exe issue, init.rc or kernel setting?

Would the sending kill all (in init.rc) trick work with the bootmenu?

Your mojo github repo is looking pro I must say!

https://github.com/TeamRegular/android_device_madcatz_mojo

Your doing good work, happy to be helping you and very excited about what's coming! :highfive: ;)
[M.O.J.O. General] windin:
Guys

I dont seem to have the same problem it always shows up on the display first time without needing to do any key pressing when i go into clockwork recovery
[M.O.J.O. General] gwaldo:
Hi welcome!

The newer images start CWM with a working display the older ones didn't (for me anyway).

My best display is a dell OH9TOH monitor.

Did you get the bootmenu option, before CWM?

I couldn't, had to ALT-SYSreq-I out of it to get into CWM.
[M.O.J.O. General] windin:
Thanks glad to be here

All of the cwm have worked for me, this one does not display the boot menu it comes up with

"Entering RCK based on booting mode configeration" and then loads up clockwork
[M.O.J.O. General] Unjustified Dev:
[MENTION=5638480]gwaldo[/MENTION] Android 5.0 is booting

Wifi is broken as I didn't even try to implement it everything else seems to be rather ok other than the sound broken.

https://www.youtube.com/watch?v=5poTTy8DDys&feature=youtu.be
[M.O.J.O. General] gwaldo:
Wow lollypop!

Nice, haven't had a chance to get it on.. hopefully later today :)

Looks great, excellent work

congrats!
[M.O.J.O. General] Unjustified Dev:
I don't plan on releasing the build until sound is fixed. Ethernet does work as an alternative to WiFi being broken.
[M.O.J.O. General] gwaldo:
Cool, I had to reinstall my linux.. kept freezing up :/

Does the CTRLR and mouse mode work on it?
[M.O.J.O. General] Unjustified Dev:
Yes , I was using mouse mode. I am going to redo my whole device tree based on stock because I think taking the updated blobs from the adt-1 android tv developer kit along the way cause sound to break . :good: will release alpha build tomorrow whether or not I fix sound.
[M.O.J.O. General] mokdakid:
Great Job!! Unjustified. Hopefully you can get the Wi-Fi to work.
[M.O.J.O. General] windin:
So that means we may be able to get leanback launcher to work on it which is great

Thanks for this, great work
[M.O.J.O. General] Unjustified Dev:
Doesn't fully work wait on my android TV port