Related
Ok so I got the GSM version today, I was using this http://www.youtube.com/watch?v=oSmd9ZbUH50&feature=player_embedded to help me unlock the bootloader, flash CWM, and flash the SU files. I unlocked the bootloader without a problem, just It did not delete all my data like the video said.
Once I try flashing CWM and looks like its fine, but after reboot when trying to boot into recovery, I get the Red Triangle with exclamation mark. I have tried flashing it a couple times, it still does the same thing. Can anyone help me please?
I just got mine today also, did you rename the stock recovery image before flashing cwm? I renamed it after and had the same issue so I reflashed cwm and all is good.
Sent from my SGH-T959V using xda premium
try using this tool http://forum.xda-developers.com/showthread.php?t=1400871
1) Play Store devices do NOT wipe when unlocking the bootloader. (We are still trying to figure out why.)
2) The Android with the red "!" IS the stock recovery. There are two files in you /system that reflash the stock recovery on every boot. If you want you custom recovery to stick, you need to delete/rename one or both:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
manuelsavino said:
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
Click to expand...
Click to collapse
Did you not read what I wrote? You NEED to rename one of those files for CWM to stay installed.
Sent from my Galaxy Nexus using Tapatalk 2
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
manuelsavino said:
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
Click to expand...
Click to collapse
Yup. Or if you reboot before renaming the files, just reflash cwm again once you delete then. No big deal.
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Thank you all! I will report back once I do it!
manuelsavino said:
Ok. Thank you all! I will report back once I do it!
Click to expand...
Click to collapse
This would have taken less than 5 minutes with the V7 Toolkit- boot loader unlock, root, rename recovery file, and install CWM/TWRP.
It is good that your trying other methods, though.
Sent from my Galaxy Nexus
bhowanidin said:
This would have taken less than 5 minutes with the V7 Toolkit
Click to expand...
Click to collapse
If he did it using a toolkit as you suggested, we would have learned nothing.
Sent from my Galaxy Nexus using Tapatalk 2
Mate I had the same problem. I got my device yesterday and unlocked my device with the tool Galaxy Nexus Root Toolkit v1.4. But it didn't allow me to root it. As I had ADB installed I tried to flash recovery trough it. But still no success. Here's how I did it.
Download Galaxy Nexus Root Toolkit v1.4. Enter the advanced settings.
Transfer su.zip to your internal memory and then "Boot into Temp CWM" trough that tool. Then you can root your device. Once it's rooted, download "ROM Manager" from the market. Accept the permissions it's asking for. And flash CWM recovery from it.
And voila. It worked for me.
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Ran into this version in a video I watched. So I just downloaded it.
Oh right you should check the development section for the newer version it is far more simple & self explanatory.
I'm done with rooting and unlocking. I did it already. Just explained how above.
No need for a tool no more.
Its useful if you want to relock your phone and go back to stock
replied..
ste1164 said:
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Click to expand...
Click to collapse
I'm guessing it just worked for him..:good:
If it anit broke why try to fix it
Ended up using the toolkit. One question, the two files that need to be renamed/deleted so it wont go back to stock recovery, on the toolkit it says rename, though once i go on root explorer to see if the two files are still there, they disappeared. So if I ever wanted to go back to stock recovery for any reason, are those two files available anywhere? Or is there a stock recovery image?
I'm in quite a pickle here. For 2 days now I have been trying to install the BAMF Jellybean ROM with no success. My device is currently running the latest CM9 nightly. I have tried multiple different recoveries, used superwipe done the manual wipe, tried different ROMS, re downloaded the files, went completely back to stock and re unlocked and rooted the phone.....I am out of ideas. It absolutely will not go past the boot animation no matter how long I let it sit. I am out of ideas. Any suggestions?
I'm pretty new here, but this Rom you're using is it for gsm GN or cdma.
atifsh said:
I'm pretty new here, but this Rom you're using is it for gsm GN or cdma.
Click to expand...
Click to collapse
Its for the CDMA VZW Nexus. Its frustrating the hell out of me.
Try another kernel maybe?
Or potentially another JB rom?
And Jelly Bean boot times can be long.
Actually, I though I was one of those that had zero problems on Jelly.
But I flashed a LeanKernel experimental build a few days ago and thought I was bootlooping for sure.
I went downstairs and made myself a sandwich just in case...and came back to the "Upgrading your applications" menu that pops up after dalvik wipes. So that means ~10 minute boot time.
Other than that ONE time however, it's been booting fast.
I'd say take a shower or something while it loops.
You may be wrongly assuming it's looping.
And sitting there staring at your phone just makes it seem longer.
Jubakuba said:
Try another kernel maybe?
Or potentially another JB rom?
And Jelly Bean boot times can be long.
Actually, I though I was one of those that had zero problems on Jelly.
But I flashed a LeanKernel experimental build a few days ago and thought I was bootlooping for sure.
I went downstairs and made myself a sandwich just in case...and came back to the "Upgrading your applications" menu that pops up after dalvik wipes. So that means ~10 minute boot time.
Other than that ONE time however, it's been booting fast.
I'd say take a shower or something while it loops.
You may be wrongly assuming it's looping.
And sitting there staring at your phone just makes it seem longer.
Click to expand...
Click to collapse
I have tried several differnt JB ROMS. I waited for almost an hour a few times and it just stays at the "X" boot screen. I have not however tried a different kernel. I will give it a shot.
cshort0982 said:
I have tried several differnt JB ROMS. I waited for almost an hour a few times and it just stays at the "X" boot screen. I have not however tried a different kernel. I will give it a shot.
Click to expand...
Click to collapse
I've waited several hours with many different kernels and can never get past the X. That glowing X might as well be red when it comes to my device. Let us know if you ever get past the boot screen.
cshort0982 said:
I'm in quite a pickle here. For 2 days now I have been trying to install the BAMF Jellybean ROM with no success. My device is currently running the latest CM9 nightly. I have tried multiple different recoveries, used superwipe done the manual wipe, tried different ROMS, re downloaded the files, went completely back to stock and re unlocked and rooted the phone.....I am out of ideas. It absolutely will not go past the boot animation no matter how long I let it sit. I am out of ideas. Any suggestions?
Click to expand...
Click to collapse
I am having the same problem. Did you ever get JB running on your phone? I have tried 3 ROMS and a variety of starting points, formats, etc.
Nope. Never got it working. I'm gonna see if I can get this one exchanged with the live wallpaper reboot trick.
Sent from my Galaxy Nexus using xda app-developers app
I am very much interested in how that works out. Replacement and if it solves the problem.
Same problem Here.. but the first time vicious jb rom been public I manage to flash it without problem and I was able to use it for a couple of days.. then I decide to try different jb rom then BOOM! infinite boot loop.. been jumping from different forums and I couldn't find any solution. Try all kind of cwm ,kernel,jb rom.. kernel and rom combo with no success. Also flash jb boot loader.. but I can restore flash ics rom with out any issue.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same problem Here.. but the first time vicious jb rom been public I manage to flash it without problem and I was able to use it for a couple of days.. then I decide to try different jb rom then BOOM! infinite boot loop.. been jumping from different forums and I couldn't find any solution. Try all kind of cwm ,kernel,jb rom.. kernel and rom combo with no success. Also flash jb boot loader.. but I can restore flash ics rom with out any issue.
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Same problem here minus the using an earlier release of JB. Im a little upset because I got rid of my S3 so I could use JB. FML!
Are you toro or toroplus
Sent from my Galaxy Nexus using xda app-developers app
jmileti said:
Are you toro or toroplus
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He said vzw nexus, which is just the toro.
Walk us through the steps you take?
I'll tell you what worked for me.
I was stock 4.0.4
i put the .zip i want to flash on to the phone.
then from fastboot i boot into clockwork "fastboot boot clockwork.img"
then i apply the .zip AND the associated G apps package.
Wipe/factory reset, wipe cache, wipe/factory reset
booted right up the first time......
Sorry. Must have missed it.
Sent from my Galaxy Nexus using xda app-developers app
Galaxy Nexus Tool Kit
Do a restor to factory image using the Galaxy Nexus Tool kit 7.5 using the options under the main menu.. You will have to download the image first and drop it in the folder for factor image restore files under the Galaxy Nexus Toolkit folder under your C drive on your computer
mdschmid1978 said:
Do a restor to factory image using the Galaxy Nexus Tool kit 7.5 using the options under the main menu.. You will have to download the image first and drop it in the folder for factor image restore files under the Galaxy Nexus Toolkit folder under your C drive on your computer
Click to expand...
Click to collapse
lulz, might as well just do it from command prompt. I never have faith in toolkits. They only carry out a set of instructions. If anything doesn't go perfectly they fail.
once imm76k is unzipped:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
Aren't you suppose to wipe before flashing ROMs not after.
Sent from my Galaxy Nexus using xda app-developers app
jmileti said:
Aren't you suppose to wipe before flashing ROMs not after.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
never made a lick of difference to me.
animal24 said:
lulz, might as well just do it from command prompt. I never have faith in toolkits. They only carry out a set of instructions. If anything doesn't go perfectly they fail.
once imm76k is unzipped:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
Im about to give this a go and see if it will work
Here is a logcat from my phone while trying to boot
I am pretty new to flashing and rooting android phones. I have a GNex 4.1.1 JB Stock ROM. It was stuck in a boot loop somehow and I wasn't able to fix it by factory reset. Someone told me to unlock and root the phone to install a new stock ROM.
I unlocked using the Wuz toolkit. But rooting wasnt possible because I couldnt push files through ADB. Then I tried doing an ODIN flash using this method (http://forum.xda-developers.com/showthread.php?t=1827685). But I got stuck at NAND Write Start.
Now I have a Phone <-> Yellow Triangle with Exclamation <-> Computer. Which I believe is download mode for Samsung.
Then I tried an OMAP Flash using this method (http://forum.gsmhosting.com/vbb/archive/t-1465412.html). I was successful installing the OMAP drivers and running the bat file. However I am still have the phone/yellow/triangle/Computer logo on my screen.
I tried to do an ODIN flash again but still stuck at NAND Write Start.
I already tried to do this:
1.) Repartiion using the PIT file [ODIN]
2.) Then OMAP flash
3.) Then Flash PDA file using ODIN.
I also tried it by swapping steps 1 & 2 but no progress.Can someone tell me the exact sequence of steps or any advice what to do now?
First of all, let me list your mistakes before I help you out:
Mistake #1: You used a toolkit. By doing so, you skipped over the entire learning part of unlocking and flashing your device, so you have no idea what went wrong or what you did.
Mistake #2: You used Odin when you didn't have to. You can mess up your device with Odin, while it is next to impossible to do so using fastboot. We have a Nexus device, i.e. a device with an unlockable bootloader and the ability to use fastboot. In my opinion, Odin should only be used as a last resort.
Mistake #3: You did not read enough before you decided to fix your bootloop. There are a bunch of stickies in the General and Q&A sections. Did you read any of them?
Now, on to fixing your issue.
Go to the Dev section and find the IMM76D Odin file in a thread started by Chainfire.
Follow the instructions in that thread to flash the complete package. Odin should be able to flash your device even though you are on the screen you currently see. Do not use a JB Odin package, use an ICS package.
Sent from my Galaxy Nexus using Tapatalk 2
I read a few articles and i know it wasnt enough. I posted a thread on android central and a senior wrote down some steps and i followed that. But going for odin and omap was totally my experiment.
I links to the imm76d image do not work any more. File not found error. There were no other sources i could find. Do you have another link to the file?
Sent from my cm_tenderloin using Tapatalk 2
shravanm18 said:
[snip]
I links to the imm76d image do not work any more. File not found error. There were no other sources i could find. Do you have another link to the file?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I can't remember if I have them on my PC (I'm not near it at the moment) -- if i do, i will upload them tomorrow. But in any case, you should be able to find links somewhere via a Google search, no?
Sent from my Galaxy Nexus using Tapatalk 2
Worse comes to worse I have the Odin files too if you guys need them. I've used so many times to save my ass
Sent from my Galaxy Nexus using XDA Premium HD app
efrant said:
I can't remember if I have them on my PC (I'm not near it at the moment) -- if i do, i will upload them tomorrow. But in any case, you should be able to find links somewhere via a Google search, no?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have my stock rooted files in a twrp backup. I'm unclear how that works they Odin but I'll pm you the dropbox link.
EDIT guess it would be if great importance to know if you are Sprint or not..
And i meant to quote the guy needing them. Oops
JediNinjafication said:
I have my stock rooted files in a twrp backup. I'm unclear how that works they Odin but I'll pm you the dropbox link.
EDIT guess it would be if great importance to know if you are Sprint or not..
And i meant to quote the guy needing them. Oops
Click to expand...
Click to collapse
I just looked at the thread I was referring to earlier, and someone already had posted another link to the files. The OP did not read the entire thread.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I just looked at the thread I was referring to earlier, and someone already had posted another link to the files. The OP did not read the entire thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Isn't that what got him into this in first place?
JediNinjafication said:
Isn't that what got him into this in first place?
Click to expand...
Click to collapse
He cannot load a recovery if he has no fastboot access. His only option now is Odin.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
He cannot load a recovery if he has no fastboot access. His only option now is Odin.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
at least Odin is easy enough
I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?
Sent from my cm_tenderloin using Tapatalk 2
I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?
shravanm18 said:
I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
You shouldn't need the .pit file. That's what probably messed things up in the first place.
If Odin is not working, I guess you can try Omap flash and then Odin. Note that if you try omap flash, and then Odin still doesn't work, I don't think you have any other option besides sending it in for repair.
Sent from my Galaxy Nexus using Tapatalk 2
I tried the OMAP Flash. It executes perfectly in the command window but my phone still shows the "connect phone to PC" picture with yellow excalmation. After that I tried ODIN flash the IMM76D tar file but I am still stuck at NAND Write flash. What I want to know is that what are the reason for getting stuck at NAND write flash and what should have happened to my phone after OMAP Flash was complete?
Furthermore I was also thinking if using a USB jig would help me get back into fastboot.
shravanm18 said:
I tried the OMAP Flash. It executes perfectly in the command window but my phone still shows the "connect phone to PC" picture with yellow excalmation. After that I tried ODIN flash the IMM76D tar file but I am still stuck at NAND Write flash. What I want to know is that what are the reason for getting stuck at NAND write flash and what should have happened to my phone after OMAP Flash was complete?
Furthermore I was also thinking if using a USB jig would help me get back into fastboot.
Click to expand...
Click to collapse
After OMAP Flash, you should still see the "connect phone to PC" picture with yellow exclamation, but now Odin should have worked. Not sure why it gets stuck on NAND write flash. Maybe try un-checking the F. Reset Time option. Someone about a week ago said that it worked for him.
Hi guys. I recently tried rooting my phone and messed it up pretty bad. I didn't realize the root method was for ICS and not the recently deployed JB update until after I did it. Here's what's going on:
- Can't boot into android. The screen just goes black after the first Samsung logo fades. I do get an AT&T sound afterwards, but it's very distorted.
- I can boot into CWM (which was included with the root?) just fine by holding vol + pwr + home.
Now I've tried a million things from googling around, but I can't seem to find any way to flash my phone (or recover it) back to stock. I know I may get some people saying "an easy google search would show you", but I'm at a complete loss at the moment. Everything seems to be for ODIN + download mode which I can't get to since CWM is installed.
Is there any way I can flash my phone back to stock? Step by step instructions would be great (and where to download firmware).
Thank you!
grazed said:
Hi guys. I recently tried rooting my phone and messed it up pretty bad. I didn't realize the root method was for ICS and not the recently deployed JB update until after I did it. Here's what's going on:
- Can't boot into android. The screen just goes black after the first Samsung logo fades. I do get an AT&T sound afterwards, but it's very distorted.
- I can boot into CWM (which was included with the root?) just fine by holding vol + pwr + home.
Now I've tried a million things from googling around, but I can't seem to find any way to flash my phone (or recover it) back to stock. I know I may get some people saying "an easy google search would show you", but I'm at a complete loss at the moment. Everything seems to be for ODIN + download mode which I can't get to since CWM is installed.
Is there any way I can flash my phone back to stock? Step by step instructions would be great (and where to download firmware).
Thank you!
Click to expand...
Click to collapse
Download mode and recovery are different. Cwm is recovery, if you can get to recovery, use adb to push a ROM over. If you go to download mode, use Odin to load a tar few package. What phone are you using? D2att or international?
Edit: Nvm the phone type. Use vol- and home combination to get download mode. Vol+ and home for recovery. Go to the stickied thread on how to root and load ROMs. It has an index of TW and AOSP ROMs. All of them prerooted.
http://forum.xda-developers.com/showthread.php?p=27745443.
Sent from my SGH-I747 using xda premium
gunz.jones said:
U
Download mode and recovery are different. Cwm is recovery, if you can get to recovery, use adb to push a ROM over. If you go to download mode, use Odin to load a tar few package. What phone are you using? D2att or international?
Edit: Nvm the phone type. Use vol- and home combination to get download mode. Vol+ and home for recovery.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
How would I go about using adb (I'm apparently clueless)?
I just tried download mode and it worked. How would I use Odin to flash it? I have the stock firmware image (and CM10 which is what I wanted to eventually flash) already downloaded, but I think you need Odin specific zips, right?
EDIT: I just browsed the phone's internal SD and everything is still there, is there a way to just undo what I did in the first place? Or if anything, I still need to backup my IMEI and such from what I've read... I think.
grazed said:
How would I go about using adb (I'm apparently clueless)?
I just tried download mode and it worked. How would I use Odin to flash it? I have the stock firmware image (and CM10 which is what I wanted to eventually flash) already downloaded, but I think you need Odin specific zips, right?
Click to expand...
Click to collapse
Odin uses tars. Different compression type. If you hook the USB up to the phone while in recovery, it should load adb mode drivers on the comp. Did you have a ROM already on internal? If so, just factory reset, wipe system, load ROM and gapps.
Sent from my SGH-I747 using xda premium
gunz.jones said:
Odin uses tars. Different compression type. If you hook the USB up to the phone while in recovery, it should load adb mode drivers on the comp. Did you have a ROM already on internal? If so, just factory reset, wipe system, load ROM and gapps.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Well, I was just going to root the phone first so I could use Titanium before flashing, so I never ended up putting the ROM on the internal SD.
When I connect the phone when CWM is up, drivers attempt to install but fail.
There are threads literally for every question you have asked I would suggest reading them before ever flashing anything on your phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
aaroncal said:
There are threads literally for every question you have asked I would suggest reading them before ever flashing anything on your phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Trust me, I have read them. I saw the thread on flashing the international GSM image, but I don't get how I would get back to stock after doing that.
Honestly, I wish I hadn't done it and made a thread before I did anything, but it seems as if curiosity and laziness got me.
grazed said:
Trust me, I have read them. I saw the thread on flashing the internation GSM image, but I don't get how I would get back to stock after doing that.
Honestly, I wish I hadn't done it and made a thread before I did anything, but it seems as if curiosity and laziness got me.
Click to expand...
Click to collapse
Get a tar of the stock ICS firmware. Follow the directions while in download mode to flash. TiBU is useless to freeze anything if you're going to load a ROM anyway. Don't be lazy and just reload apps manually. You should always have a backup plan.
For sh*ts and giggles, go into cwm and just factory reset.
Since adb drivers arent loading for you, I'm not going through that process with you. For future though, you will want adb knowledge. Look it up.
Sent from my SGH-I747 using xda premium
gunz.jones said:
Get a tar of the stock ICS firmware. Follow the directions while in download mode to flash. TiBU is useless to freeze anything if you're going to load a ROM anyway. Don't be lazy and just reload apps manually. You should always have a backup plan.
For sh*ts and giggles, go into cwm and just factory reset.
Since adb drivers arent loading for you, I'm not going through that process with you. For future though, you will want adb knowledge. Look it up.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I used this thread to flash back to stock AT&T ICS:
http://forum.xda-developers.com/showthread.php?t=1727443
Didn't work. It still boots into a black screen with a blue LED after the Samsung logo fades. Factory reset also went through, but nothing worked. It just booted into a blank screen again, but with the AT&T sound afterwards.
Sorry for being an idiot, I'm getting kinda desperate here, and I totally realize that this was a bad call on my part without more research.
grazed said:
I used this thread to flash back to stock AT&T ICS:
http://forum.xda-developers.com/showthread.php?t=1727443
Didn't work. It still boots into a black screen with a blue LED after the Samsung logo fades. Factory reset also went through, but nothing worked. It just booted into a blank screen again, but with the AT&T sound afterwards.
Sorry for being an idiot, I'm getting kinda desperate here, and I totally realize that this was a bad call on my part without more research.
Click to expand...
Click to collapse
Did Odin show a pass on flash?
Sent from my SGH-I747 using xda premium
gunz.jones said:
Did Odin show a pass on flash?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
This is what it showed:
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Sounds like problems Motorola gave grief with on the droids and their flashing tool. I'm looking for a jb tar file. When you used cwm and used Odin, both of them should have removed any times that would cause and issue. Especially since odin of stock fw would be like ghosting an image. Try using the toolkit to lock everything up and go back to stock completely.
Samsung stock image for jb : http://samsung-updates.com/device/?id=SGH-I747
Sent from my SGH-I747 using xda premium
gunz.jones said:
Sounds like problems Motorola gave grief with on the droids and their flashing tool. I'm looking for a jb tar file. When you used cwm and used Odin, both of them should have removed any times that would cause and issue. Especially since odin of stock fw would be like ghosting an image. Try using the toolkit to lock everything up and go back to stock completely.
Samsung stock image for jb : http://samsung-updates.com/device/?id=SGH-I747
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Unfortunately can't use anything in the toolkit since it's needing me to be booted into the OS first with debugging on (I'm stuck with download mode or CWM).
grazed said:
Unfortunately can't use anything in the toolkit since it's needing me to be booted into the OS first with debugging on (I'm stuck with download mode or CWM).
Click to expand...
Click to collapse
Tried using the jb stock image?
http://developer.android.com/tools/help/adb.html for adb use and information. To get the drivers to work, try loading the naked drivers pack. It includes Samsung drivers. Remove all Samsung installed crap from your comp and reboot. Manually install drivers by forcing legacy devices or by telling the computer you have the disk if needed after hooking phone back up.
Sent from my SGH-I747 using xda premium
gunz.jones said:
Tried using the jb stock image?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Couldn't find it, but I'm in the middle of downloading this to see if it works:
http://forum.xda-developers.com/showthread.php?t=1739426
Holy crap it worked! Thank you for all of your help.
grazed said:
Holy crap it worked! Thank you for all of your help.
Click to expand...
Click to collapse
Good deal.
Sent from my SGH-I747 using xda premium
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I've got a Verizon Galaxy S3, rooted, CM10, and CWM 6.0.1.2. My friend wants to root his galaxy nexus after he saw my phone, and was wondering if I could use the same method of installing clockwork mod recovery as I did with mine. Can I use the same file, and flash it though Odin (v3.0.7)?
Sent from my SCH-I535 using xda app-developers app
The GNex is extremely easy to root through adb. If you don't know how to set up adb and fastboot you should probably learn for your own sake as well as his.
Noooooooooooooooooo please don't use the same file.. Very very bad things will happen.. I mean like time paradoxes.. The doctor himself warned me.
You can grab a copy of CWR or TWRP for the Gnex (Toro) and go into fastboot (boot loader) make you sure you have fastboot.exe dropped into your windows folder on your computer.
Run these commands:
fastboot OEM unlock (everything on the device will be wiped incl SD space)
Accept the agreement and let it go back to the bootloader.
Fastboot flash recovery "your-recovery-name-.img"
Choose reboot recovery on the fastboot screen
From here you can go ahead and push over a ROM or su.zip file and flash it... All done.
Sent from my Nexus 7 using Tapatalk HD
Guide in Sig or stickied at the top of this forum...
ThePatelBros said:
I've got a Verizon Galaxy S3, rooted, CM10, and CWM 6.0.1.2. My friend wants to root his galaxy nexus after he saw my phone, and was wondering if I could use the same method of installing clockwork mod recovery as I did with mine. Can I use the same file, and flash it though Odin (v3.0.7)?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Please let your friend know that he himself should learn how to do it.
Sent from my i9250