yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] onilink67:
We'll was grabbing some code out of google git repository today and came by this. Sure looks like a Nexus S with Wimax code being this close to the 8th should be any day now for all of it.

http://android.git.kernel.org/?p=kernel/samsung.git;a=tree
[Epic 4G General] qbking77:
What's a kernal? ;)
[Epic 4G General] onilink67:
whats a source ? ;)

thanks though don't know if I can edit titles on this forum but I'll try. If not can a mod fix this please ;)

stupid spelling

edit : fixed thanks for pointing it out
[Epic 4G General] shabbypenguin:
yea 2.3.4 added some of the modules :D its not everything but its a start :P
[Epic 4G General] onilink67:
kinda surprising they are gonna use the same kernal since there will be a lot of extra crap in it we don't need and a lot the standard nexus s won't need.
[Epic 4G General] shabbypenguin:
theres a lot of extra crap that the nexus doesnt need but the nexus s does.. yet they share the same stuff :D
[Epic 4G General] onilink67:
We'll once the final code is released (if this isn't it already) I may have to try and find the time to do some cleanup. From my experience extra code in the kernel can slow things down quite a bit especially when in USB OTG mode.
[Epic 4G General] kalico17:
i get my Nexus activated Sunday.. giving my Epic to my girlfriend..

HELLOOOO GOOGLE :D
[Epic 4G General] apatcas:
wait... this is a good thing right? we get the ns4g code and we might have some similar hardware with it... including wimax right?
[Epic 4G General] onilink67:
Yes this is a good thing
[Epic 4G General] apatcas:
YAY! 50$ from me for whoever gets 2.3 working with wimax.
[Epic 4G General] iSaint:
Not even excited 8(

Something like this is a few months late IMO
[Epic 4G General] apatcas:
I'll buy u sammiches
[Epic 4G General] 063_XOBX:
There's a saying about opinions...
[Epic 4G General] bricky23:
Oh ya. they're like assholes, everyones got one. Oops, was I supposed to say that out loud? Mmm
[Epic 4G General] ksweat2292:
lol +1
[Epic 4G General] iSaint:
... you guys don't think we're a few months behind developement compared to other devices?...

And it's no fault of our Devs so im not complaining about them they have done a great job ...with what they have
[Epic 4G General] onilink67:
correct anyone that feels that way needs to do some research and try for themselves. Android is not as difficult as it looks.
[Epic 4G General] apatcas:
bumb

10 char
[Epic 4G General] 063_XOBX:
Why exactly did you "bumb" this thread?
[Epic 4G General] nullghost:
If any NS4G hardware is similar to the Epic instead of the same as the NS, color me surprised. I think the best thing for everyone to do would be to hope for the worst (which would mean the NS4G is the exact same as the NS, and with a wimax chip that isn't the same chip in the Epic), and be pleasantly surprised if anything is usable. It'll prevent a lot of butthurt and unnecessary forum posts.
[Epic 4G General] 063_XOBX:
I find it unlikely Samsung would use a different WiMax chip than the Epic's since they probably have a surplus of them.
[Epic 4G General] onilink67:
A lot of the NS was compatible with the epic the reason we could not use it was that it was a GSM phone. This should be very close. Obviously NFC isn't in ours.
[Epic 4G General] 063_XOBX:
Not at all, Nexus S Roms won't even boot on the EPIC, even with heavy modification.
[Epic 4G General] Darkshneider:
Well find out as soon as someone with a NS4G takes a dump on the phone and uploads it.
[Epic 4G General] onilink67:
IMO a dump is not that great unless you want some applications. I'll be waiting on the source.
[Epic 4G General] onilink67:
when did I say you could use a nexus S rom? only a fool would flash something for a different phone. Porting =/ flashing
[Epic 4G General] 063_XOBX:
I never said flashing. Even with all the months of work Tmillar put into porting the Nexus S rom it still won't boot on the EPic.
[Epic 4G General] onilink67:
There is a reason why most never looked to much in the Nexus S porting gsm to cdma is difficult ... not impossible but difficult. I'd recommend doing some of your own research rather then regurgitating what others have said.
[Epic 4G General] 063_XOBX:
I'd recommend not being so condescending to people on the internet.

I am aware that porting between CDMA and GSM is difficult but far from impossible. The problem is that is is nigh on impossible when you can't even get the Rom to boot after heavy modification, let alone begin to work on the radio/modem.
[Epic 4G General] Darkshneider:
We know its not impossible, I had a Hero and saw all sorts of ports of GSM ROMs to a CDMA one, and it wasnt even the same model! But Sammy is different than HTC in their coding... idk.
[Epic 4G General] onilink67:
Trust me in real life I'd do it as well

As it was someone else's work I will not comment on it. Never saw the code or real progress made. I remember him posting a lot but not a lot coming out so don't quite know the quality of the phone enough. What I can promise you is the NS4G will be a lot more compatible with the epic then the NS and would be willing to put money on it.
[Epic 4G General] Darkshneider:
Just saying...
[Epic 4G General] Mike_77:
Actually, we have MIUI 1.5.6 Nexus S booting on the Epic, with working phone calls, it's other features aren't working though :)
[Epic 4G General] Art2Fly:
Great news!
[Epic 4G General] Mike_77:
Well, actually we have phone and sms.. 3g isn't working, there are some graphics glitches, camera doesn't work.. but overall, still proof nexus s roms will boot on an Epic. Looking forward to some Nexus S 4G source though :)
[Milestone XT720 General] stlifey:
Hi guys!

I have successfully port CM7 to XT701

Here is the ROM

http://www.rayfile.com/zh-cn/files/6ac67519-7669-11e0-9deb-0015c55db73d/

Most of the functions work well.

But several problems are not fixed yet.

1.The camara focus and the flash work but when it save pictures. It will crash down.

2.The FM doesn't work

3.The DSP works but not so well

...

I think the xt720 xt701 xt711 have the same hardwares and systems. So I need cooperation to fix these problems. So if you want to help me or cooperate with me , just PM me.

Thanks
[Milestone XT720 General] fjfalcon:
Good news, have you compiled cm from source or just ported from already compiled port?

Is there any journal about your work?

Will try to help with everything i can.
[Milestone XT720 General] khalpowers:
mirror plsss:)
[Milestone XT720 General] archer88:
videi\o please

Please post a video for proof!
[Milestone XT720 General] fjfalcon:
mirror from Russia =)
[Milestone XT720 General] easye420:
So does this working xt720 as is? Idc if some stuff is broke I've been using miui and some stuff is broke but it works
[Milestone XT720 General] Mioze7Ae:
Multiupload mirror:

http://www.multiupload.com/PQQ7SR57TE

I haven't tested it on XT720 yet. Stlifey's github is here: https://github.com/stlifey

BRB (hopefully), bleaching computer following RaySource.
[Milestone XT720 General] easye420:
I'm gonna try it out ill let u know how it goes
[Milestone XT720 General] Vistaus:
Agreed. Not everything has to work, but I'll wait till the camera works before I try CM 7. The camera is one of the things I use a lot on this phone.
[Milestone XT720 General] ghostboy:
Great to hear this good news! As I know at the same time a new version of MIUI rom will also release soon.
[Milestone XT720 General] hellmonger:
fails....

code 4 aborted
[Milestone XT720 General] Mioze7Ae:
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:

assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");

Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.

Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc

I think that's where we need to start anyway.
[Milestone XT720 General] leuleu9x:
Please complete the rom to xt720/xt711
[Milestone XT720 General] hellmonger:
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...

Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more :(
[Milestone XT720 General] easye420:
thanks for lookin at it. i took a look and i have no idea. :confused: hopefully you can get it working for us.
[Milestone XT720 General] Mioze7Ae:
This ROM uses a slightly "cleaner" hijack than what we've been using (this cleaner hijack seems to be widely used in the Milestone ROMs). If you're familiar with Dexter's XT720 hijack the translations are roughly:

Dexter: 2nd-init controlled by /system/bin/mod_boot_mode.p1.sh

Milestone: 2nd-init managed by /system/bin/sh_hijack.sh

Dexter: ramdisk updated for 2nd-init from /system/ramdisk.tar

Milestone: ramdisk updated for 2nd-init from /system/etc/rootfs/

On the recent Milestone ROMs (including nadlabak's CM6, CM7 and TheFroyoMOD) all the hijacks go through skrilax's /system/bin/sh which is what controls entry to OpenRecovery. /sytem/bin/sh will either boot openrecovery or execute /system/bin/sh_hijack.sh or simply continue with normal boot. On Dexter's ROM the sh_hijack pathway is not used for 2nd-init (Dexter used a mot_boot_mode hijack later in the boot process for 2nd-init instead)

I've been working on porting Dexter's 1.3 to use the sh_hijack.sh instead of mot_boot_mode thinking that will help port Milestone ROMs, but at the moment for some reason I can't get USB to work when using sh_hijack.sh. Probably something simple. But maybe these hints can help someone beat me to the punch. ;)
[Milestone XT720 General] archer88:
go guys!!! i will support you!!!:):):):):D:D:D:D
[Milestone XT720 General] stlifey:
hi guy,i have get a XT720 from a friend:D
[Milestone XT720 General] mediaon:
you got xt720? so did you try to port the CM7 to xt720? can you share your experience..
[Milestone XT720 General] Knoedelkopf:
So is this Cyanogen Mod 7 with Gingerbread ??

probably with a port we can get gingerbread on our xt720 even if the bootloader is locked, right?
[Milestone XT720 General] leuleu9x:
I believe U ;)
[Milestone XT720 General] jooprzol:
better phone operation

My phone's cell radio connection was pretty much unavailable with this update, so I ended up copying all files out of the system\etc\motorola\bp_nvm_default folder from the latest STCU_U2_41.07.0-ota-full-signed-hk update that can be downloaded from the xt701 project on opensource.motorola.com (Specifically, the address is https://opensource.motorola.com/sf/...cts.stcu/discussion.general_comments.topc2065)

After I copied over those files into the proper folder, my signal went back to where it was previously, and am also able to connect to the internet via wifi and hsdpa. Hopefully that helps others with an xt701.
[Milestone XT720 General] syrenz:
Are there any differences between the XT701 and the XT720 besides for the fact that XT720 has 3 more Mp camera?
[Milestone XT720 General] Mioze7Ae:
XT701: http://developer.motorola.com/products/xt701/

XT720: http://developer.motorola.com/products/milestone-xt720/

Assuming those are accurate: the differences I see are OMAP3430 vs OMAP3440, no AGPS or HDMI. The Motoroi's difference with Milestone XT720 is only the OMAP and that seems enough to have changed the sensors (although I'm not sure if the sensors issue is an actual hardware difference or a kernel configuration difference).
[Milestone XT720 General] :
But that doesn't matter. We already have the HDMI-driver in Dexter, so it's just a matter of fact of using Dexters HDMI in this CM7-port. Probably the same for aGPS. The chipsets doesn't matter either, that'll work fine.
[Milestone XT720 General] syrenz:
And would this port from XT701 give us true haptic feedback back or would he have to get it from an official 2.2 (if that ever happens)? Whatever the case, would be awesome to have CM7 working someday on XT720 :).
[Milestone XT720 General] :
The Haptic Feedback as it is now is superb IMHO. It doesn't need any improvement.
[Milestone XT720 General] syrenz:
For me it's barely noticeable most of the time and often enough I'll get no feedback on an interaction. It also doesn't register on certain interactions like selecting an option on screen generally (i.e. putting a widget or shortcut on screen) which it used to do. Prefered the way it used to be. :(
[Milestone XT720 General] :
That's most likely a hardware-problem then as it works fine here.
[Milestone XT720 General] c19932:
haptic is also 100% fine on mine
[Milestone XT720 General] syrenz:
Haptic is as sensitive as it was in 2.1? It's very muted here and I know others have said the same...
[Milestone XT720 General] Tavinsky:
Someone has already ported the XT720??
[Milestone XT720 General] easye420:
shoot i wish. i dont even know if anyone is working on it. Mioze7Ae said he cant look at it for a week. :(
[Milestone XT720 General] mchlbenner:
Hi I don't read anybody who has got it on their xt720 it looks like are phone truer to install error 7 you are talking about xt721 that's not are phone!
[Milestone XT720 General] leuleu9x:
waiting :( May be very hard
[Milestone XT720 General] Tavinsky:
I would love to help but I do not understand almost nothing of what is said in this thread ... I still wish someone luck and hope it succeeds.

Greetings!
[Milestone XT720 General] jun980219:
Touch is not working

I already tested on XT720 Korean Version(MOTOROI)....

it's booting, but touch is not working :(

and USB, ADB, RIL, Battery Status is not working too.

If you has flashing problem, open the update.zip and edit the update-script

(sorry to poor english)
[Milestone XT720 General] tubekeeper:
I like to thank all of you spending the effort for this rom and looking forward it will work fine
[Milestone XT720 General] Mioze7Ae:
Can you share which files you modified to get this booting on Motoroi? I keep getting stuck and the M logo and can't get back into OR. So I have to keep going back to sbf. Clearly it's crashing before the sh-hijack? I can't figure out what's messing up prior to the sh-hijack or why changing /system/ would cause that. I have no idea how to debug anything prior to the sh-hijack...

This is the latest thing I've been trying:

Delete boot.img

Update META-INF/com/android/metadata

Update META-INF/com/google/android/updater-script

Combine Dexter's init.mapphone_umts.rc with stlifey's init.choles.rc to create /system/etc/rootfs/init.mapphone_umts.rc

I've attached my latest versions of these files in case some fresh eyes see something wrong. I think I'm going to go back to my initial idea of first porting Dexter's system221v13 to use the same hijack and then come back to this. Grrrr.
[Milestone XT720 General] Mioze7Ae:
Ok, I've successfully switched my Dexter ROM to the sh_hijack.sh method instead of the mot_boot_mode hijack without problems. It now occurs to me that the problem is probably incompatibilities in executables (very probably kernel modules) used by init before the sh_hijack runs. Doh. Well, at least I have an new idea where to start looking... sometimes you just have to read your own stupidity in text to see what's blatantly obvious :rolleyes:
[Milestone XT720 General] Mioze7Ae:
It turns out the "getting back into openrecovery problem" is different than I thought--it's not a module incompatiblity, it's that the orbootstrap isn't being installed.

On XT720 we have to use a bootstrapped recovery (i.e. we use 2nd-init to enter OR). When you install openrecovery you create a /system/persistent/orbootstrap directory that Skrilax_CZ's /system/bin/sh hijack looks for when booting OpenRecovery. nandroid restore in OpenRecovery knows to backup and restore /system/persistent/orbootstrap every time you flash a system.img so that OpenRecovery doesn't become broken. This isn't true for "Apply update" and the cm7 update.zip for XT701 doesn't include the XT720 orbootstrap.

According to the Skrilax_CZ's Open Recovery install page, it looks like XT701 is able to install OpenRecovery directly into the recovery partition (this is also true of the Milestone 1 with the vulnerable recovery). In other words, XT701 doesn't use bootstrapped recovery (/system/persistent/orbootstrap does not exist). That's why we can't get back into OR after flashing stlifey's update.zip. If you manually reinstall openrecovery for XT720 over adb after applying stlifey's update.zip you are able to get back into OpenRecovery.

Reminder of how to manually install the XT720 openrecovery bootstrap:

su
cp /sdcard/OpenRecovery/orbootstrap/install_script.sh /tmp
chmod 755 /tmp/install_script.sh
/tmp/install_script.sh STR

I'll try and add orbootstrap install to stlifey's update.zip and upload it. CM7 still won't work, but it will be easier to monkey with on XT720 because we hopefully won't have to go back to sbf all the time.

Edit:

Here's the modified update for XT720 with working orbootstrap:

update-cm-7.0.2-11.05.04-XT720-A01-signed.zip (89.44 MB) http://www.multiupload.com/MSREXVWYKQ

I've been able to apply it, get back into OR and apply it again and get back into OR. It does *not* boot successfully into CM7, though, but hopefully this will help others experiment with getting this up on XT720. Brief summary of what I changed:

Deleted stlifey's boot.img

Updated META-INF/com/android/metadata, /system/build.prop (otherwise your XT720 thinks it's an XT701 after first apply and you can't reapply)

Added /system/etc/rootfs/init.mapphone_umts.rc (doesn't work yet, unforch)

Added /system/persistent/orbootstrap

Added xtra/install_orbootstrap.sh (modified /sdcard/OpenRecovery/orbootstrap/install_script.sh for use by the updater-script)

Fixed META-INF/com/google/android/updater-script for sholest and to install orbootstrap
[Milestone XT720 General] :
Great job! :)

Maybe khalpowers or Dexter can finish this?
[Milestone XT720 General] Mioze7Ae:
A binary port of either the XT701 or MS1 CyanogenMod would be an excellent start even if it crashes all the time. We just need to get it booting. Then we can work on getting the equivalent source build working and start fixing everything at the source level instead of this smali morass.
[Milestone XT720 General] x2rust:
has anyone get this working??
[Milestone XT720 General] gera_nium:
Mioze7Ae, great! you hv done initial and big step for our XT720.

I would like to participate too, but don't where to start....tested your update cm, installed from sdcard and confirmed back to OR again, but stuck at M logo. anyhow i would share my little compilation of this CM7 for XT720....i would like to update until its working....here the file CyanogenMod for Milestone XT720.txt
[Milestone XT720 General] Mioze7Ae:
Enable ADB debugging during boot

I was able to turn on ADB debugging right before 2nd-init during boot and capture a log. This lets us capture error messages that occur during boot using adb via USB.

To enable adb debugging during boot modify /system/bin/sh_hijack.sh to include these lines just before 2nd-init:

/system/xbin/busybox killall usbd
echo "msc_adb" > /dev/usb_device_mode

The attached update-cm-7.0.2-11.05.04-XT720-adbdebug.zip will update sh_hijack.sh to do this (simply apply after the CM7 update).

When trying to boot update-cm-7.0.2-11.05.04-XT720-A01-signed.zip on XT720 it looks like we're crashing when the screen is initialized:

...
I/SurfaceFlinger( 1817): SurfaceFlinger is starting
I/SurfaceFlinger( 1817): dithering enabled
I/SurfaceFlinger( 1817): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/FramebufferNativeWindow( 1817): couldn't open framebuffer HAL (No such device)
I/DEBUG ( 1529): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1529): Build fingerprint: 'MOTO_RTSEA/umts_sholes/umts_sholes/sholes:2.2.1/SHOLS_U2_05.26.0/95429183:user/release-keys'
I/DEBUG ( 1529): pid: 1817, tid: 1825 >>> system_server <<<
I/DEBUG ( 1529): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000005c
...

A more complete "adb logcat" output is attached.
[Milestone XT720 General] Knoedelkopf:
You are all doing great work! Thanks!:cool:
[Milestone XT720 General] easye420:
They released a newer version of this yesterday.

http://u.115.com/file/clcvf6ct <--- download link

http://bbs.gfan.com/android-1297281-1-1.html <--- their development thread about this rom
[Milestone XT720 General] Mioze7Ae:
I happened to be reading through the #milestone-modding logs last night and for a time the mod-gods were talking about whether the XT701 bootloader could be ported to the Milestone A853 because the XT701 doesn't signature check beyond the bootloader (i.e. boot.img can be modified). It must be true because stlifey's removed 2nd-init and modified the boot.img initrd directly in this newest release (things the XT720 bootloader will not allow). They may even be able to flash a kernel.

So jealous. :mad::o:(:eek::mad:
[Milestone XT720 General] easye420:
thats a bummer. anyone tried flashing one of the xt701 bootloaders? http://www.mod2xtreme.com/showthread.php?t=8720
[Milestone XT720 General] Mioze7Ae:
If anyone wants to try this (sounds like there's a very good risk of permanently bricking your phone) I'd read the logs at http://milestone.bekaakut.de/index.php starting at 2010-11-08 and get incontact with #milestone-modding for instructions. Definitely not for the faint of heart and it's certainly above my skill level. They start trying to boot it 2010-11-14 and the quest builds to a very suspenseful climax on 2010-11-16, but in the end the XT701 bootloader bricks the Milestone. It's possible XT720 hardware is close enough to XT701, but I can't risk mine on this.
[Milestone XT720 General] easye420:
yea so maybe not such a good idea.
[Milestone XT720 General] mchlbenner:
I think it could work I extra phones but lets see what the pros can do and its a very high risk to do.
[Milestone XT720 General] gera_nium:
i think we hv chances like milestone also:)...they also start from scratch (zero) and now having the cm7....lets start our journey

1. as jun980219 from korea has done with motoroi....maybe he could share the bootloader and etc....then we could do porting.

2. as my reading, of course xt701 almost the same as xt720, but due to OMAP is different...i think there is different bootloader :p...details can check from this Bootloader_Project....at least we hv an idea....

3. is it motoroi xt720 and xt720 is a same bootloader?
[Milestone XT720 General] mchlbenner:
Hi Guy here is the leaked xt701 bootloader 80.90 here's are bootloader 80.89 I'm tryinng to get the nerve to flash it.
[Milestone XT720 General] Knoedelkopf:
good luck ;)
[Milestone XT720 General] x2rust:
anyone successful port it out??
[Milestone XT720 General] punkrocklives:
Anyone else try this on an xt701? Do we flash it through openrecovery
[Milestone XT720 General] sktjdgns1189:
I flashed XT701 Bootloader......

I flashed XT701 bootloader on my XT720....

It makes my XT720 bootanimation loop........

I'm Korean..

Sorry to poor english..
[Milestone XT720 General] mchlbenner:
Hi if going to flash the bootloader try the UK build for xt720 use bootloader 88.90.
[Milestone XT720 General] Zachary57:
Istead of trying to flash another bootloader, is there a way to run automatically a custom bootloader at phone start by using file /etc/install-recovery.sh ?

This file is the one wich is used by link2sd to automount ext partition and I see that by adding line we can run commands with but I don't know if root commands are possible.

I don't know if it's possible but I think if yes it will help.
[Milestone XT720 General] fjfalcon:
What version of bootloader do you have? 80.89 ?
[Milestone XT720 General] sktjdgns1189:
I flashed XT701 bootloader 80.94

I flashed XT701 bootloader 80.94