Develop Bugs

[GUIDE][09-12-2011] XOOM 3G Euro Root Instructions + Files[3.2-UPDATE]

I have rooted the boot image from my XOOM, this is a UK 3G XOOM, DO NOT USE if you are NOT 3G, or use at your own risk, attached.
Before you proceed you will need to unlock your bootloader, note this will erase all of your data, you have been warned!
UPDATE for 3.2
Use the following to get root on your 3.2 updated euro xoom. Please note, the modules here from the earlier boot image are most probably not functional anymore. I will try get an updated set. For now, here are the instructions, the new boot image is attached to this post.
Get the boot_3.2_insecure.zip from this post which also contains an su binary i just compiled.
Code:
adb reboot bootloader
fastboot oem unlock
Follow the on screen instructions!
Extract the files into you current directory, then reboot into fastboot mode and do:
Code:
fastboot flash boot boot.img
fastboot reboot
This will get you a rooted bootloader but you still aren't rooted yet, get a prompt or terminal open in the folder where the root_files are from the attached zip you will need the su file.
Make sure you have a computer with adb set up then from the computer perform the following commands with the xoom connected:
Code:
adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
NEXT: Go to the Market and install "Superuser" by ChainsDD and you will probably want to install busybox too.
Congratulations on rooting your euro 3G XOOM all by yourself, and remember "one click" is for noobs who like to brick their devices (like me) don't do it.
OLD Modules(tun/cifs/etc) 3.0.1:
Code:
I have attached an archive containing cifs.ko, tun.ko, nls_utf8.ko, option.ko
and usb_wwan.ko with correct version magic. I did not compile them,
and I can not provide others (unless I can find them).
How to use:
Copy the modules to "/system/lib/modules", reboot.
If you don't know how to do that, you probably shouldn't be using them.
Disclaimer: I take no responsibility if either this boot image, the tutorial, or the files attached murders you violently, in fact, don't even use them.

alias_neo said:
Guys, I have been through this process, STOP using the US root instructions and images, they don't work on the european 3G XOOMs.
I have boot and recovery images that I need someone with a little experience to contact me about testing before I can release them to anyone else as working.
If a mod could sticky this please to stop people bricking their euro XOOMs until I can get the images tested and get a dump of the recovery partition!
Click to expand...
Click to collapse
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
If there's been an OTA update for the UMTS Xoom already, and you have a recovery-from-boot.p binary patch and the boot image, you can make the recovery image by using applypatch.
I don't have a device yet, sadly, so I can't test yet.

ydaraishy said:
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
I don't have a device yet, sadly.
Click to expand...
Click to collapse
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.

alias_neo said:
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.
Click to expand...
Click to collapse
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.

ydaraishy said:
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.
Click to expand...
Click to collapse
I flashed a stock 3G boot image that I rooted myself.

alias_neo said:
I flashed a stock 3G boot image that I rooted myself.
Click to expand...
Click to collapse
Ah, got you. Thanks for the info.

The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)

ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk

alias_neo said:
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Oops, you're right; I thought you said you had the stock boot image, which is why I got confused.

Xoom Brazilian 3g and wifi
ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
In brazilian 3g gsm and wifi works fine tks

rickjardim said:
In brazilian 3g gsm and wifi works fine tks
Click to expand...
Click to collapse
May can you give me a your framework-res.apk file?
Thanks so much

Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?

mlokane said:
Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?
Click to expand...
Click to collapse
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.

alias_neo said:
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.
Click to expand...
Click to collapse
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!

mlokane said:
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!
Click to expand...
Click to collapse
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.

alias_neo said:
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.
Click to expand...
Click to collapse
PMed now - we can update this thread if it works...

i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.

aefelix said:
i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.
Click to expand...
Click to collapse
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.

alias_neo said:
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.
Click to expand...
Click to collapse
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )

aefelix said:
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )
Click to expand...
Click to collapse
I flashed a complete Verizon dump on mine and everything worked except the radio, so I imagine it would be the same the other way around. By all means though give it a go, bear in mind they are different models and so most likely have hardware differences (no LTE upgrade in europe).

[ROM] Official Factory Image ITL41F

This is not a Rom Manager backup or a 41D upgraded to 41F but an official 41F stock image build by Google obatined from
http://code.google.com/android/nexus/images.html
I have added a batch file to automatically fastboot flash this under windows and restore your phone to stock.
turn the device on with both volume buttons held and enter fastboot mode. connect usb and execute flash-windows.bat (included) you may need to install samsung adb driver and boot unlock the device though (which you can find on this forum)
tested on my galaxy nexus and restored successfully.
https://rapidshare.com/files/352067458/itl41f.zip
mirror
http://www.filesonic.com/file/4075307854

zyo said:
This is not a Rom Manager backup or a 41D upgraded to 41F but an official 41F stock image build by Google obatined from
http://code.google.com/android/nexus/images.html
I have added a batch file to automatically fastboot flash this under windows and restore your phone to stock.
turn the device on with both volume buttons held and enter fastboot mode. connect usb and execute flash-windows.bat (included) you may need to install samsung adb driver and boot unlock the device though (which you can find on this forum)
tested on my galaxy nexus and restored successfully.
https://rapidshare.com/files/352067458/itl41f.zip
mirror
http://www.filesonic.com/file/4075307854
Click to expand...
Click to collapse
Thanks OP worked great!

Why would you upload mirrors when Google themselves are hosting the files? Wouldn't it be more reliable to just download straight from Google?
Also, I'm assuming that they'll be updating the recovery images for each official update as well... Meaning your mirrors would be outdated soon anyway. Just a thought.
Thanks anyway though, these will come in useful!

Google's package is compressed in tgz and comes with sh script, also doesnt include fastboot windows.
I put all necessary utils together with a bat script so user can just double click and restore.

Radio Image
can you change the radio image like this XXIK6? http://forum.xda-developers.com/showthread.php?t=1374077
greetings pittrich

pittrich said:
can you change the radio image like this XXIK6? http://forum.xda-developers.com/showthread.php?t=1374077
greetings pittrich
Click to expand...
Click to collapse
I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it

will OTA updates works if i flash this image (assuming i've also cloclwork mod recovery)?

idan_mo said:
will OTA updates works if i flash this image (assuming i've also cloclwork mod recovery)?
Click to expand...
Click to collapse
Since it's 100% Google image, I don't see why OTAs wouldn't work.

ok, thanks!

qwer23 said:
I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it
Click to expand...
Click to collapse
You could do what my idiot brother did to my Nexus S. Format /boot from Clockwork mod (under the storage options I believe) and then turn the phone off. The only way to unbrick it is to send it to Samsung, or the guy on XDA who runs that company that uses JTAG to fix it (which is what I did)

SphericalPuma said:
You could do what my idiot brother did to my Nexus S. Format /boot from Clockwork mod (under the storage options I believe) and then turn the phone off. The only way to unbrick it is to send it to Samsung, or the guy on XDA who runs that company that uses JTAG to fix it (which is what I did)
Click to expand...
Click to collapse
Why would that brick the device? Can't you still get into the bootloader or recovery and flash a new boot image?

I'd prefer the Google Images untouched to be honest.
Guys, a little OT question, but I don't want to open a new thread just for a noobish question:
How could one actually brick the GNex? Is it possible to brick the GNex so serious that it won't even get recognized by fastboot?
If not, it's literally unbrickable. If yes, what would I need to do to brick my phone like that? Just wann know so I can NOT do it
Click to expand...
Click to collapse
where there is a will, there is a way

Worked great for me. Thanks very much.
Rik.

@ OP
Thank you man, a million times. Now I was able to replace Samsung's screw up Stock.

@ zyo will this factory image also work for lte or is this strictly GSM image? I have an issue where neither cwm or adb will restore my stock nandroid and I want a full stock backup just to be safe
Sent from my Galaxy Nexus using xda premium

Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!

psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
just execute the scripts for your platform.

psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
If you can read German I can give you the link to my step-by-step guide. However I am not able to post it here directly, yet. Too much of a noob still.

psero said:
Hello, can someone post a step-by-step guide to revert back to ITL41F? After I unlock the bootloader, what are the steps I need to perform?
Any help will be appreciated!
Click to expand...
Click to collapse
That's a good idea & hopefully someone will.
+1

I wouldnt flash this on LTE model. I have heard it comes with different radio and stuff (obviously)

New Galaxy Nexus owner

Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.

Pete720 said:
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Click to expand...
Click to collapse
Unlock the boot loader firstly but beware it will wipe your sdcard.
Use fast boot to unlock it, type oem fastboot unlock and go from there.
Flash cwm using fastboot by typing fastboot flash recovery xxxxxxx.img (xxxxx.img is whatever the filename is)
You are probably familiar with cwm so I won't bother explaining that.
All the rooms here have everything working on them. We'll except sense 4.0 and touchwiz ports etc. But that's obvious.
Ps. All phones have locked bootloaders!

Yeah, you might mean unlocked bootloader. You do have to unlock it first, but it doesn't take an exploit to do so. See here for a starting point:
http://forum.xda-developers.com/showthread.php?t=1400871
As for the best rom, impossible to say, so many . It depends on what exactly you're looking for. aokp is probably the most features-popular, but there are many others. I use cm9 with the reloaded mod, personally.
sent from my Zerg Hatchery.

Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?

Pete720 said:
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Click to expand...
Click to collapse
SDK, Fastboot, ADB

anton2009 said:
SDK, Fastboot, ADB
Click to expand...
Click to collapse
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?

Pete720 said:
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Click to expand...
Click to collapse
Options 8 (Extract and Flash Google Factory Stock ROM), 10 (Reflash Stock Recovery [just to be safe]), and 11 (Relock bootloader) will return it all to stock. I know, because I just had to do this to 3 GNex's this past week to send them back to Verizon

Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.

Okaay said:
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Click to expand...
Click to collapse
Only if you are stock and rooted.
He is running a custom rom and kernel and has cwm flashed, that method will not revert them to stock.

nodstuff said:
Ps. All phones have locked bootloaders!
Click to expand...
Click to collapse
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader

nicholaschum said:
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
Click to expand...
Click to collapse
My apologies, I totally forgot to update my signature. I do not have the GSII anymore.

Can anyone point me int he direction of the box stock rom file I need to work with Toolkit to restore my phone? I followed the directions and got the image from code.google.com but it wont install. ALways says something is missing.

Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.

Pete720 said:
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Click to expand...
Click to collapse
I believe that the toolkit will auto download if you just run the option.

[HELP] Bricked my S3 i747M.

Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!

First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!

Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.

Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse

I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.

I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse

Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.

After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse

Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium

pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app

Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks

You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....

Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?

just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices

jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?

I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium

JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.

Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium

Is there a root method for SGH-l317m yet?

Got my canada rogers note 2 today and i know its kinda soon but has anyone tried any of them other methods for example the sprint root, to root their SGH-l317m?
EDIT: Solved root Acquired
http://forum.xda-developers.com/showthread.php?t=1970162

turilo said:
Got my canada rogers note 2 today and i know its kinda soon but has anyone tried any of them other methods for example the sprint root, to root their SGH-l317m?
Click to expand...
Click to collapse
Hell yea bro!
Heres a root video:
http://www.youtube.com/watch?v=O6BweCW5ck8&feature=plcp
Heres how to unroot/ unbrick : http://www.youtube.com/watch?v=UaZiO8vfrME&feature=plcp
-All variants by the way. the dude happens to be rooting a sprint one xD

Hmm you try it on the sgh-l317m model?
Sent from my SGH-I317M using Tapatalk 2

Doesn't look like mskip has added i317 model yet.
I flashed CWM 6 for i317 and installed superSU 0.97 via CWM. It seemed to do the trick.
Be wary that the phone not only counts flash attempts, but also has a flag for whether the phone has been modified. If the phone is flagged you will lose the ability to do OTA updates.

Oogar said:
Doesn't look like mskip has added i317 model yet.
I flashed CWM 6 for i317 and installed superSU 0.97 via CWM. It seemed to do the trick.
Be wary that the phone not only counts flash attempts, but also has a flag for whether the phone has been modified. If the phone is flagged you will lose the ability to do OTA updates.
Click to expand...
Click to collapse
Ah nice where may I find these? So your fully rooted now? What phone you have and carrier
Sent from my SGH-I317M using Tapatalk 2

could you post your *#1234# ???? i would like to get the firmwares for samsung-updates.com

turilo said:
ah nice where may i find these? So your fully rooted now? What phone you have and carrier
Sent from my sgh-i317m using tapatalk 2
Click to expand...
Click to collapse
i'm with Rogers, but from my limited knowledge the big three Canadian carriers are using the i317 model?
You can grab the i317 cwm recovery from here:
http://forum.xda-developers.com/showthread.php?t=1901196 - scroll down to "first upload(2012/09/23)"
you can grab supersu cwm flash zip from here:
http://forum.xda-developers.com/showthread.php?t=1538053 - third link under download
again i warn you that you can't ota update after this, but getting rid of rogers bloatware through titanium backup was much more worth it for me for the time being :d.
Perhaps you can tell me this, are there any ota updates out of the box? Or is it updated already?
somean said:
could you post your *#1234# ???? I would like to get the firmwares for samsung-updates.com
Click to expand...
Click to collapse
ap: I317mvlalj2
cp: I317mvlalj2
csc: I317moyaalj2

Oogar said:
Doesn't look like mskip has added i317 model yet.
I flashed CWM 6 for i317 and installed superSU 0.97 via CWM. It seemed to do the trick.
Be wary that the phone not only counts flash attempts, but also has a flag for whether the phone has been modified. If the phone is flagged you will lose the ability to do OTA updates.
Click to expand...
Click to collapse
nice!! looks like we have root for the sgh-l317m also all went well for me m8! im now rooted!:laugh:

Oogar said:
ap: I317mvlalj2
cp: I317mvlalj2
csc: I317moyaalj2
Click to expand...
Click to collapse
thanks, weve added all canadian vatiants to the 'monitored' list, as soon as sammy with carriers will push the firmwares to servers we will report and publish them
thanks

SoMean said:
thanks, weve added all canadian vatiants to the 'monitored' list, as soon as sammy with carriers will push the firmwares to servers we will report and publish them
thanks
Click to expand...
Click to collapse
Awesome! That's great to hear . Looking forward to it.

turilo said:
nice!! looks like we have root for the sgh-l317m also all went well for me m8! im now rooted!:laugh:
Click to expand...
Click to collapse
Would you recommend this root process, or do you think it best to wait for mskip to post an update to add 317 support to his tools? I have rooted many an android tablet, but have never had to deal with a phone before. Why no OTA updates after achieving root? I noticed people passing their #1234# on, does this mean that we are overwriting our EFI partitions which hold some of our unique identifier number, etc. As I said, I'm not used to the phone partition structure, or the use of odin, but have spent quite a bit of time in adb and cwm.
Cheers
EDIT: Sorry, I just reread your post and noticed the quote about the 'modify flag', and then being denied OTA updates. Stupid me, I then decided to go to the source, Triangle Away, and found out it is related to the counter in a hidden boot block. Ignore basically everything I had asked, I know better than to post without searching first. Sorry.

I just got mine from Rogers today. Am with Virgin, and since Virgin is owned by Bell (or Virgin uses Bell network), I took my sim from iphone and put it in GN2 and it worked instantly.
Let me know if you need any info...
Im an anroid noob, so need to do some research before I root. I dont have ANY bloatware, so thats not an issue.

savethehumans said:
I just got mine from Rogers today. Am with Virgin, and since Virgin is owned by Bell (or Virgin uses Bell network), I took my sim from iphone and put it in GN2 and it worked instantly.
Let me know if you need any info...
Im an anroid noob, so need to do some research before I root. I dont have ANY bloatware, so thats not an issue.
Click to expand...
Click to collapse
You SIM unlocked your Rogers unit first....right?

WorldIRC said:
You SIM unlocked your Rogers unit first....right?
Click to expand...
Click to collapse
****, I meant BELL, not Rogers. No need for the unlock, because virgin is owned by Bell.
Wow cant believe I said Rogers. Sorry!

savethehumans said:
****, I meant BELL, not Rogers. No need for the unlock, because virgin is owned by Bell.
Wow cant believe I said Rogers. Sorry!
Click to expand...
Click to collapse
Hello Everyone i would like to know is it best to wait before rooting that Variant of Note 2 device
I got mine from Telus yesterday, an i try to learn a thing or 2 since i come from an Iphone.
If there's a post for newbies i would love to take a look Thanks
Thank You

OK just so im sure....
-Reboot device to download mode
-Open odin and select downloaded file for PDA tab (cwm6-recovery-i317.tar.md5)
-Connect device to PC, and wait till device successfully added to com port
-Flash
then again
-Reboot device to download mode
-Open odin and select downloaded file for PDA tab (cwm6-root-note2.tar.md5)
-Connect device to PC, and wait till device successfully added to com port
-Flash
Then that should root and install supersu?
LMAO, I looked at 3 different root methods and now am not sure what you guys did in this thread to root your i317...and im a droid noob.

savethehumans said:
OK just so im sure....
-Reboot device to download mode
-Open odin and select downloaded file for PDA tab (cwm6-recovery-i317.tar.md5)
-Connect device to PC, and wait till device successfully added to com port
-Flash
then again
-Reboot device to download mode
-Open odin and select downloaded file for PDA tab (cwm6-root-note2.tar.md5)
-Connect device to PC, and wait till device successfully added to com port
-Flash
Then that should root and install supersu?
LMAO, I looked at 3 different root methods and now am not sure what you guys did in this thread to root your i317...and im a droid noob.
Click to expand...
Click to collapse
The second part no! Do the first part you mentioned. But put superuser97.zip in root of phone first! Then reboot into cwm vol up/home and power together then let go at boot screen. Then flash the superuser97.zip via cwm done
I'll post proper instructions tomorrow your right can be confusing for the average noob
Sent from my SGH-I317M using Tapatalk 2

turilo said:
The second part no! Do the first part you mentioned. But put superuser97.zip in root of phone first! Then reboot into cwm vol up/home and power together then let go at boot screen. Then flash the superuser97.zip via cwm done
I'll post proper instructions tomorrow your right can be confusing for the average noob
Sent from my SGH-I317M using Tapatalk 2
Click to expand...
Click to collapse
Thanks that worked perfect.
I did actually do the second part (before you replied) but just reflashed with recovery and all is well. ...I think.
Is there a good FAQ somewhere? I have looked at a couple but they seem device specific. My questions are regarding the actual root then ROMs. I would imagine that since a ROM changes the entire OS, it must change the root? Or once the stock rom is rooted, they all are? Stupid noob questions, that im sure a FAQ would answer.
Cheers, and thanks again!

amzi said:
Hell yea bro!
Heres a root video:
http://www.youtube.com/watch?v=O6BweCW5ck8&feature=plcp
Heres how to unroot/ unbrick : http://www.youtube.com/watch?v=UaZiO8vfrME&feature=plcp
-All variants by the way. the dude happens to be rooting a sprint one xD
Click to expand...
Click to collapse
Yea thats mskip great work and tool kit! hes adding our devices into his toolkit as we speak

Hi turilo,
I apologize for the noob questions - I'm new to the Andriod ecosystem and I just got a Note 2 (Rogers) and have a couple of questions.
1. You rooted your device and what exactly did that accomplish? It appears you were able to get rid of the Rogers bloatware. So all the red colored Rogers app icons and software are gone? What else is the benefit of rooting your device in particular? Is it faster and the battery lasts longer? Please be as specific as you can.
2. Did your device retain all the TouchWiz and S-pen funtionality after being rooted? In other words rooting did not make your phone a pure Andriod system? I also have a Google Nexus 7 and can see differences in the OS compared to the Note 2, so I'm assuming the differences are "enhancements" (depending on your perspective ofcourse ) that Samsung put in.
3. As someone else mentioned, now that you will not be able to get updates OTA, does this mean that when Samsung releases the update to allow multi window or any other update for their software, you won't get that automatically? Is this not something to be concerned about? I would want to get any updates to the S-pen or TouchWiz for instance.
4. Does the above also mean that when Android 4.1.2 becomes available, you will have to update your device manually using some archane process? ie, you won't be able to do this simply from the Settings menu and click on update software?
5. Last noob question - for Andriod idiots like me (I'm a little bit techy - I jailbroke my iPhone back in the day, but would rather not root my Andriod phone unless the benefits outweigh the disadvantages - get rid of Rogers bloatware, keep the Touch Wiz and S-Pen functionality, improved battery life, faster processing etc), can you point to a link that explains how to do this for Andriod dummies?
Thanks!