yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rgoyena:
So its advisable to flash thw at&t one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I have been using the 5.8.4.5 version of the clockworkmod.com release and have had no problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rgoyena:
How do you download from clockwordmod.com? Sorry noob

---------- Post added at 06:29 AM ---------- Previous post was at 06:25 AM ----------

nevermind. lol Rom Manager
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
http://xdaforums.com/showthread.php?p=28612095

ROM Manager will install the latest version, which does not allow you to make backups or install zips from the external SD card. Version 5.8.4.5 allows that. You can download one of the two from the link above and flash it using your current recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
I am running CWM 5.5.0.4 and my ro.product = d2can in the build.prop. Is there anywhere else I can look for the infamous d2spr?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Are you checking that while booted into recovery or while booted into your ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Is that from Android or Recovery? I promise that your Recovery doesn't even have a build.prop, and in default.prop you'll see ro.product (and everything else) defined as "d2spr" or "d2att" depending on which recovery you flashed.

Canadian models have been ignored simply because they're hardware-compatible (or at least seem to be so far) with AT&T models. We'll probably never see custom software of any sort even acknowledge the existence of a "d2can".

The issue with this, is that anything checking ro.product (or anything other than ro.bootloader, which thankfully is fed in from the bootloader itself and will [probably] never get messed with) can't be trusted to get the right result, because that information is obtained from the ROM or Recovery installed on the device, and since nobody's made one that actually identifies as a d2can, all Canadian models will be stuck saying they're from AT&T or Sprint, which could make a lot of "poorly written" scripts tell you your device isn't supported by the ROM/recovery/mod you're trying to install.

---------- Post added at 02:46 PM ---------- Previous post was at 02:46 PM ----------

Dammit, you beat me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks guys. I have to say, I have flashed dozens of ROMs and never had to deal with this issue, albeit, I haven't used CWM in over 6 months thanks to 4ext Recovery (a compatible version is currently being developed for our phones according to the Dev, can't come soon enough!).

Where do I find the CWM ro.product? I went into recovery/show log and saw "ro.carrier"=unknown, but no ro.product?

On the Canadian issue you mentioned, is it possible to modify recovery to use d2can? I guess we just have to hope for a Canadian dev with the knowledge, and inclination to fix this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
You can find it in /default.prop while booted into recovery or you can flash the attached zip to display it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks.....I have the d2spr....for cm roms look like I would have to switch to the att cwm version then? I may just wait for the imei issue to sort itself out first.....I saw a post there from a rogers user that switched cwm version from spr to att, then flashed aosp rom from stock, and bye bye imei. Nothing is definitive there but risk is enough for me to stay put for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gavingreystone@gmail.com:
Maybe a silly question I'm sorry but I can't seem to answer if the rogers i747m is exactly the same as the telus i747m. If I can flash any of the at&t rooms without problems. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
All Canadian 747's should be treated as AT&T models.

I can't believe there isn't a sticky about this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RiNo808:
Okay I need help with this... Where do I find the default.prop at when I'm in recovery... I know that I'm on 5.5.0.4...thanks in advance...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
It's no longer relevant. I don't need any information from any more .prop files, the bootloader gives a unique ID for each model that can't be messed up unless someone flashes another carrier's bootloader to their device.

And if someone does that, I'll assume they either want a brick, or know what they're doing and don't need my help in the first place.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Are you saying that having a cwm default.prop from another carrier will not cause any issues with flashing (via cwm) cm9, or any other rom, as ID verification is done through the bootloader? I thought certain scripts were causing problems because of this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm not saying that.

I'm saying that once we get unified ROMs in the works, they'll be able to detect your correct device model no matter what recovery or ROM you're currently running. The reason I was asking for getprop outputs was to see what each device identifies as in Android and recovery. I no longer need any more data.

I'm hopeful that ROM developers will be interested in 2 things:

A wider target audience for their ROM, with anyone with a Snapdragon S3 able to install their ROM from a unified source,

and

Making sure nobody ends up with a brick because they flashed a ROM for the wrong variant and users (somehow) blaming the ROM developers.

This recovery (and all recoveries to date) make the mistake of being usable on multiple device variants, but always identifying as a single device, which is why, up until now, there have been issues with ROM install scripts claiming you have the wrong device, even when you clearly don't. They need to be parsing the ro.bootloader for the model number, and really need to steer clear of ro.product or any other default/build.prop-related strings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SysAdmNj:
How exactly do you do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psycopanther:
all LTE variants include vzw?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
All variants have their own official CWM version available now. Try Rom Manager after rooting.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericc191:
mount /sdcard doesn't seem to work. any thing i can do this fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
ROM manager is not the same thing... it does not install to you recovery partition
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Micronads:
Um, yes it does. At the top it says install clock work mod recovery. That will install the latest recovery for your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] onei0077:
My device doesn't show up, and I can't do anything with the img from cwm website. I can't seem to find a recovery that works for me. I get a error 7 when trying to flash a new Rom.
[Galaxy S III General] jeet92:
Hey, to all of you lucky guys would it be possible for one of you to dump the stock radio by any chance? Thanks in advance guys.
[Galaxy S III General] joshnichols189:
This is the international S3 forum. You might want to try the US forums.
[Nook Color Q&A, Help & Troubleshooting] CubeCloudOS:
I have a old honeycomb version and was good until I found the microsd card slot was bent so I can't boot any sd... then I wiped data/cache and it will only show the setup wizard and I can't click the android guy. I then followed the directions in various posts trying to use the 8 failed boot attempts and format system but to no avail. NOw it won't boot at all... Can I use adb to flash a stock system boot and data img?
[Nook Color Q&A, Help & Troubleshooting] Nikola_r:
I read somewhere something like this,you can try it

1. turn the Nook completely off

2. turn it on and immediately on seeing the first message "the future of reading" press and hold the power button until it turns off again

3. repeat this 7 more times for a total of 8

4. on the 9th time, let the Nook completely reboot without holding the power button - you will see a message saying "installing a software update..." and after this everything will be back to factory new (the system will be totally restored)
[Nook Color Q&A, Help & Troubleshooting] biohazrd51:
If you're missing the timing, I believe there is a way to use a script with adb to cause 8 fail boots and force the restore. I can't find it off hand, but I'm sure if you do some searching it'll come up.
[Nook Color Q&A, Help & Troubleshooting] dparrothead1:
You don't even have to count....Just keep doing the interrupted boots until the nook tells you that it is resetting.
[Galaxy S III Android Development] Faryaab:
Android 4.1.1 JellyBean

​

There will be no more updates to this ROM as I have released my SuperNexus ROM.

SuperNexus ROM: http://xdaforums.com/showthread.php?t=1817345

​

This ROM is built entirely from Google's JellyBean source code. I'm actually working on my upcoming ROM "SuperNexus". So I just compiled a pure AOSP JellyBean for the Galaxy S3 so i know that I can add support of it in my SuperNexus ROM. This ROM might only get 1-2 more updates because I will release SuperNexus very soon. I'm using Teamhacksung's Device Tree and patches in this ROM so Big Kudos to Teamhacksung (Donate To Them). Also big thanks to Codeworkx and Xplodwild for working so hard to fix Galaxy S3 stuff and making it compatible with JellyBean.

System Details:

Android ICS 4.1.1 (JRO03H - Android-4.1.1_r3)

Latest CM Source Compiled Kernel

All JellyBean Features and Apps (Nothing excluded from AOSP)

No Visual Changes!

Stock JB Look and Feel

This will turn your Samsung Galaxy S3 into a JellyBean'ed Galaxy Nexus :p

ROM Features:

Fully Deodexed

Zipaligned APKs

Rooted (Super SU)

BusyBox Installed

No 3rd Party App

ZERO Bloatware

Official JB Bootanimation (From Official Galaxy Nexus Android 4.1.1 Factory Image)

Init.d Support

What's Working

WiFi - BT - NFC

HW Composer - Sensors - Audio

Data - Calls - SMS - MMS

Mostly Everything is Working :)

Known Issues

Wi-Fi tethering is semi-broken

Memory Leak

Found one ? Report it.

Screenshots:

Video by TotallyDubbed:

[youtube]p-meVHQIToY[/youtube]

Requirements:

Clockworkmod Recovery (CWM)/Any custom recovery

Wipe if coming from any other ROM

Instructions:

Copy Google Apps and ROM to your internal SD Card

Enter Recovery

Do a Wipe/Factory Reset

Flash Android 4.1.1 JB ROM

Flash Google Apps

Reboot your device!

Voila! :D

Downloads

Latest Build:

AOSP-JB-I9300-BUILD3 MD5: 6FB936B0F8CD57E0789192C50E638344

Google Apps:

gapps-jb-20120724-signed.zip

Previous Builds

AOSP-JB-I9300-BUILD2

AOSP-JB-I9300-BUILD1

Source Code:

CM GT-I9300 Kernel @ Github

Changelog:

[B]AOSP JB I9300 BUILD3 (30-07-12):[/B]
[LIST]
[*]Fixed Play Store issue
[*]Fixed SD Card issue
[/LIST]

[B]AOSP JB I9300 BUILD2 (30-07-12):[/B]
[LIST]
[*]Fixed Google Now FC Issue
[*]Added APN List
[*]Added SPN List
[*]Added Device Asserts in Updater-Script (So noobs don't flash this on a different device)
[/LIST]

[B]AOSP JB I9300 BUILD1 (29-07-12):[/B]
[LIST]
[*]Initial Release
[/LIST]

Credits:

Codeworkx

Xplodwild

Teamhacksung

CyanogenMod

Nebkat

Chainfire

Goo.im (Buildbox)

Thanks to all who donated or thanked

Follow Me On Twitter:

Donate:

If you like my work please consider a donation as it will help me keep this development alive and it will be contributed in my MacBook Pro fund.
[Galaxy S III Android Development] NOZdroid:
God
[Galaxy S III Android Development] Faryaab:
For now launcher is giving me FC's so can't explore it much but I went into the settings and man this is FAST!
[Galaxy S III Android Development] Baldilocks:
Now just to make it function properly with specific hardware, sensors, etc.... :)
[Galaxy S III Android Development] joshnichols189:
...

SO FIX IT >:O

Thanks :)
[Galaxy S III Android Development] NaimC:
In all honesty though, how much faster can it actually get? The S3 is already lightning fast imo. Not really sure how it can get much faster lol.
[Galaxy S III Android Development] brojoe11:
WOW! Looking forward to see what can be done with this...
[Galaxy S III Android Development] kulzboy:
Quick someone give this guy a medal :D
[Galaxy S III Android Development] apisfires:
Good job bro, I can't wait for it.
[Galaxy S III Android Development] Sensamic:
Is it functional?

Does Google Now work?
[Galaxy S III Android Development] adz63:
Faryaab the 15 yeah old genius :)

Giving it some beans on my blue s3 Powered by CheckROM EvoHD™ V2
[Galaxy S III Android Development] joshnichols189:
I would say no.
[Galaxy S III Android Development] npompei:
This is awesome. In all likelihood, what timeframe do you think until this hits a real nice "vanilla" rom for the GS3?!
[Galaxy S III Android Development] ijeff:
Maybe we should get some pledges in for the first functional 4.1 port!
[Galaxy S III Android Development] Cyb3rGlitch:
It's fast, but not fluid.
[Galaxy S III Android Development] furt890:
That's like asking why cars such as Bugatti Veyron exist lol.
[Galaxy S III Android Development] BobFL:
ICS/S3 combo is plenty fast. Imho, it is going to be about feats and neatness in near future rather than about speed.
[Galaxy S III Android Development] ceo.mtcl:
Amazing!
[Galaxy S III Android Development] KKTHX:
Waiting for working rom... :)
[Galaxy S III Android Development] hefonthefjords:
Fantastic work dude!

Keep playing with it plz. We would love to see what you can get working with it.
[Galaxy S III Android Development] ddeluxe:
Notification bar pulldown in full screen

Hi guys, really like your attitude :victory:

I have a short question for someone who flashed JB on the SGS3. Is it possible in JB to pull down the notificationbar even if it isnt present in a fullscreen app?

On the stock Samsung Rom, Samsung implemented the ability to swipe from the top to bring up the notification bar in a fullscreen app!

Thanks for a response:)
[Galaxy S III Android Development] TotallydubbedHD:
Can't believe Faryaab, my man didn't tell me this :p!

Video coming of it on my S3, soon :)!

---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------

soon :D
[Galaxy S III Android Development] sam razzy:
Even v r waiting for your come back... ;) love you

sent from TapaTalk

Rom: PARANOIDANDROID phone mode v1.5a

Kernel: Dorimanx Kernel 3.8v ... Best on my Galaxy s II

GOOGLE EVERYTHING
[Galaxy S III Android Development] blend.:
hahaha : )

can't wait to see how this thread evolves.
[Galaxy S III Android Development] TMaLuST:
Thank you for pointing that out, I didn't know :D

Anyway I just tried using the fullscreen mode in the browser on this rom and it didn't work.

Sorry :(
[Galaxy S III Android Development] Bishopandme:
Only Yess...:good:

I'm post it

B:cyclops:
[Galaxy S III Android Development] ianford10:
Fantastic work, will try this at a later date :)

Great job :)
[Galaxy S III Android Development] the2rrell:
doing my nandroid now.....i just want to see Jelly bean, even if its half functional.
[Galaxy S III Android Development] apisfires:
Try it and give review here, thanks
[Galaxy S III Android Development] TotallydubbedHD:
I'm on it right now - epic port bro - shame a lot of things don;t work - I just need internet access so that I can troll the heck outta siri!

Video is in the making!
[Galaxy S III Android Development] MadWhips:
Looking forward to the video TDub !
[Galaxy S III Android Development] TotallydubbedHD:
Have taken over 30pics too - they will come very shortly
[Galaxy S III Android Development] hefonthefjords:
I tried it out. Interface is nice. Things are fast. Couldnt really do much cuz of limited connectivity obviously, was nice just to check out the layout.

Look forward to seeing whatever comes next.
[Galaxy S III Android Development] TotallydubbedHD:
Done:

-35 Pictures uploaded

-Written guide

To come:

-Video

http://www.totallydubbed.net/2012/0...oid-jelly-bean-4-1-samsung-galaxy-s-gt-i9300/

ENJOY! :)
[Galaxy S III Android Development] Faryaab:
This port will no longer be updated as the source will be released in two weeks and we can developer a pure AOSP ROM out of it. So there is no point in wasting so much time, also without source we can't get the Galaxy S3 hardware to work. :)
[Galaxy S III Android Development] TotallydubbedHD:
there was/is a lot of things to make work haha!

So many things not working :p

Cheers for the port amigo!

I sure got my taste of some Jelly Beans!
[Galaxy S III Android Development] jameslfc5:
Subscribed
[Galaxy S III Android Development] sam razzy:
Take your time... after completing with GALAXY S III.. please do our come back for GALAXY S II .. v still need you back... even develop for GALXY S II.. :) love you :D

sent from TapaTalk

Rom: PARANOIDANDROID phone mode v1.5a

Kernel: Dorimanx Kernel 3.8v ... Best on my Galaxy s II

GOOGLE EVERYTHING
[Galaxy S III Android Development] norpan111:
In don't want to be that guy but.. You've said this 3 times in this thread now as far as I've seen.. Chill dude
[Galaxy S III Android Development] Skdi:
Hey will this work on my rooted att sgs3?
[Galaxy S III Android Development] nodstuff:
No.

This isn't the at&t forum.
[Galaxy S III Android Development] RMXO:
first person or group to get a JB ROM that is considered a "working daily driver" will get a nice $100 USD donation from me. Think of it as a little incentive for your hard work.
[Galaxy S III Android Development] Skdi:
Yeah but theres not that much different between the att and international sgs3's is there? How much would it really take to get the att model to run international roms?
[Galaxy S III Android Development] norpan111:
Just f* you
[Galaxy S III Android Development] Baldilocks:
Yes there is a LOT of difference. I suggest you read up on both models.
[Galaxy S III Android Development] sorrowrain:
congratulations for for having news for the rom on engadget.
[Galaxy S III Android Development] RMXO:
:confused: :crying: :D :p :silly:
[Galaxy S III Android Development] baric88:
Reserved till u fix a lil more
[Galaxy S III Android Development] A5J4DX:
epic stuff great work mate
[Galaxy S III Android Development] ceo.mtcl:
Well the project is abandoned so mods please close it. :(
[Galaxy S III Android Development] spncrmoo:
abandoned why?

Edit: Forget that, me being stupid. Good news I guess, I'm just so impatient!
[Galaxy S III Android Development] Faryaab:
No! I'm still working on this. :D
[Galaxy S III Android Development] norpan111:
Guys just read what he just wrote
[Galaxy S III Android Development] alexanter the great:
Its really so smooth compaire to ics!!
[Galaxy S III Android Development] gokussjx:
You've no idea how long I've been waiting to hear this statement :cool:

Thanks man.

Lets see what we, as a community, can do to make this super port a perfect success.
[Galaxy S III Android Development] alexanter the great:
Yes!!We need jelly bean and we have patience!!
[Galaxy S III Android Development] Skdi:
I mean the software isn't like super different. How hard could it be to get an att phone running international roms?
[Galaxy S III Android Development] alexanter the great:
"few hours later" hahaha!!if you are on that video i like you men!!great game! :p
[Galaxy S III Android Development] erstad:
someone gonna need to buy him a few cases of red bull.

Hope you can get this ROM to DD status by the time of my upgrade :crying:in August:crying:.

Keep up the good work !!!!
[Galaxy S III Android Development] joshnichols189:
The two phones are COMPLETELY different. They have different CPUs, different GPUs, different hardware and software radios. How hard is this to understand? It will not work on the ATT S3.
[Galaxy S III Android Development] Skdi:
I know the hardware is a little different. I'm saying the software isn't super different. It shouldn't be too hard to get an att sgs3 to run this...
[Galaxy S III Android Development] thyttel:
You obviously don't get it...
[Galaxy S III Android Development] Deliximus:
agreed.

The chipset is different. Exynos vs SnapD S4.
[Galaxy S III Android Development] apisfires:
Little different? After you brick your phone, please don't come here to cry and abuse our developer, we advice you, you choose follow or not, that's your phone.
[Galaxy S III Android Development] loranz:
Nice work on the port. Really smooth, kinda makes my ICS feel a bit old and laggy now. lol.

Looking forward to this. =D
[Galaxy S III Android Development] P1n3apqlExpr3ss:
When Faryaab mentioned earlier in the thread that the project isn't dead, does he mean he'll give a few updated versions before the AOSP code drop or it won't be updated until AOSP but will be updated then and made into a proper ROM?
[Galaxy S III Android Development] gokussjx:
He means the project isn't dead.

That should be enough for now. ;)
[Galaxy S III Android Development] ijeff:
The software is substantially different; you just can't see it. Consider the variants entirely different phones; code from the Qualcomm S4 version will never run on the Exynos Quad version. They will need dedicated developers building a new version from the ground up, or doing porting work on their own.

Think of the differences between the two as large as the differences between the Galaxy S II and the Galaxy S III. You can't expect developers to just tweak a ROM and have it work on the other. It takes a lot of work.
[Galaxy S III Android Development] mcduck$:
Cool proof of concept brother.:good: up
[Galaxy S III Android Development] TMaLuST:
Just posting hoping that this can be useful:

https://developers.google.com/android/nexus/images#nakasi

Factory image from nexus 7 :)
[Galaxy S III Android Development] Lennyuk:
You could still do loads before aosp drops, plus it's always late anyway ;-)
[Galaxy S III Android Development] talisin:
this s why i love this comunity with awesome devs like this
[Galaxy S III Android Development] furt890:
Damn, only 2 days and we have a half-working port ? That is some crazy fast work OP.
[Galaxy S III Android Development] AdamLange:
Instead of copying files (odexing/deodexing whatever) from nexus dump and using CM9 kernel what exacly you ported to this rom?

Is there any JB specific changes to CM9 kernel? (i see there is no commits to source after JB release)

I see that everything that is stock android compatible is working, but not SGS3 specific things.

Where we can expect a real port? like with ported drivers to most of phone H/W ?

Im just curious
[Galaxy S III Android Development] Faryaab:
You can buy a Galaxy Nexus and have a fully function Jelly Bean ROM or you can try by your self to make things work. If it was so easy to port Jelly Bean then why I get 11-12 PM everyday about porting it to other devices and why don't we see another Jelly Bean port in the Galaxy S III forum? If it was that easy then why didn't you ported jelly bean ? DON'T COMPLAIN IF YOU CAN'T DO IT ON YOUR OWN!
[Galaxy S III Android Development] chrisd1a1:
thread cleaned
[Galaxy S III Android Development] theonlyanil:
amazing. Thanked. but I fear installing it on my SGS3. I love its camera. :)
[Galaxy S III Android Development] brian6685:
Did anyone put up a video yet?
[Galaxy S III Android Development] Faryaab:
Video is in the OP. Video is made by TotallydubbedHD
[Galaxy S III Android Development] brian6685:
Oh sorry, didn't look ;/
[Galaxy S III Android Development] TAT1980:
which app do i have to install, to have google search as siri konkurrenz?

is it working on s3? or only on jelly bean???
[Galaxy S III Android Development] naddie:
Maybe just poor choice of words. Fixed. Should be less demanding sounding and more "asking for tech/dev info to improve the port".

Despite the poor maner, I also would like to know how the OP ported the ROM. If it's how Adam said it was done, I'm interested. ROM porting was always such a magical art, but maybe I should start learning how it's made. :)
[Galaxy S III Android Development] jayharper08:
Thread cleaned. Again. Keep it polite and on topic guys.