Hey I recently got a glxy nexus, have some questions about rooting and flashing and some problems,
1.the first thing I don't understand is why my phone doesn't update to latest android? Still on 4.2.1, its a nexus ,so I think it should get update since first boot, anybody else have this problem?
2.so the device is not updating, I plan to root and flash it, so I'm doing this, 1. Unlock bootloader via fastboot ,,2. Flash twrp via fastboot , and start flashing roms! (These steps are my mind generated) so tell me , did I miss anything? Do I need to do something else, ? Really appreciate your answers,
Sent from my Galaxy Nexus using xda app-developers app
or you can use toolkit, if you are not sure of what u are doing.
razi914 said:
Hey I recently got a glxy nexus, have some questions about rooting and flashing and some problems,
1.the first thing I don't understand is why my phone doesn't update to latest android? Still on 4.2.1, its a nexus ,so I think it should get update since first boot, anybody else have this problem?
2.so the device is not updating, I plan to root and flash it, so I'm doing this, 1. Unlock bootloader via fastboot ,,2. Flash twrp via fastboot , and start flashing roms! (These steps are my mind generated) so tell me , did I miss anything? Do I need to do something else, ? Really appreciate your answers,
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
1- it will not update (or take a lot longer to) unless you're running yakju/takju.
2- perfect, you did your homework.
a manta wrote this.
beekay201 said:
1- it will not update (or take a lot longer to) unless you're running yakju/takju.
2- perfect, you did your homework.
a manta wrote this.
Click to expand...
Click to collapse
hey just curious , is flashing a kernel the same way as rom? i mean do we have to flash boot.img via fastboot? and what is download mode? i heard it is used to flash stock roms on samsung devices , does it do the same on a galaxy nexus ?
razi914 said:
hey just curious , is flashing a kernel the same way as rom? i mean do we have to flash boot.img via fastboot? and what is download mode? i heard it is used to flash stock roms on samsung devices , does it do the same on a galaxy nexus ?
Click to expand...
Click to collapse
kernels are normally packaged into recovery flashable zips. some include all they need inside a boot.img, some don't. if all they need is boot.img, then yes, 'fastboot flash boot boot.img' would be the correct command.
download mode is indeed the interface by which normally Samsung devices interact with a computer. It's far more easier to get an updated factory image in "fastboot format" than in Odin package files, in part because, if you're running yakju or takju, Google takes care of the software, and that's why fastboot should always have higher priority than Odin.
But yes, download mode is one more option.
Read this: http://forum.xda-developers.com/showthread.php?t=1812959
Ok, one more thing , that one thing which is scaring me , what is this omap44 thing going on? I read somewhere that galaxy nexus bricked after installing cm,, or while charging,, is this thing has anything to do with unlocking bootloader or flashing roms?
Sent from my Galaxy Nexus using xda app-developers app
razi914 said:
Ok, one more thing , that one thing which is scaring me , what is this omap44 thing going on? I read somewhere that galaxy nexus bricked after installing cm,, or while charging,, is this thing has anything to do with unlocking bootloader or flashing roms?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
who knows.. maybe, maybe not.
beekay201 said:
who knows.. maybe, maybe not.
Click to expand...
Click to collapse
ok , just tell me,, what are the basics to avoid bricking gnex?! i had a htc desire s before , which was not very easy to brick,bcoz i knew the basics,,but im a newbie here,
razi914 said:
ok , just tell me,, what are the basics to avoid bricking gnex?! i had a htc desire s before , which was not very easy to brick,bcoz i knew the basics,,but im a newbie here,
Click to expand...
Click to collapse
don't operate the device while on low battery, put it to charge, don't let it shutdown by itself;
flash stuff for your own variant (variants: maguro, toro, toroplus) i.e. try to stick with your own variant's dev subforum, although kernels should be compatible across all variants;
give priority to fastboot, it seems you're no stranger to the tool, you have way more "freedom" with the Nexus's fastboot than with HTC's (which also uses it, I believe?);
keep platform-tools (bundled with android-sdk or in a separate package) up-to-date; current version is R17
read the thread i linked you to, you'll also want to read up on http://forum.xda-developers.com/showthread.php?t=1626895
Related
First, pardon my ignorance on this matter. Since Google released the factory imagines for the Galaxy Nexus does this allow you to restore the phone no matter how bad you brick it? Thanks in advanced
Sent from my Galaxy Nexus using xda premium
Zeon45 said:
First, pardon my ignorance on this matter. Since Google released the factory imagines for the Galaxy Nexus does this allow you to restore the phone no matter how bad you brick it? Thanks in advanced
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Pretty much, as long as some how you dont break fastboot
thanks, I was deciding on whether I should flash YAKJU on my YAKJUXX, knowing that there is a way to fix a possible mistake is reassuring
Sent from my Galaxy Nexus using xda premium
Zeon45 said:
thanks, I was deciding on whether I should flash YAKJU on my YAKJUXX, knowing that there is a way to fix a possible mistake is reassuring
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Well to do that you need to flash the bootloader.
If you screw up flashing the bootloader (like unplugging the cable when it's transfering the file), then you're dead.
nxt said:
Well to do that you need to flash the bootloader.
If you screw up flashing the bootloader (like unplugging the cable when it's transfering the file), then you're dead.
Click to expand...
Click to collapse
Exactly.
On some of the SGS phones its possible to mod them to be unbrickable. Basically you can make it so it boots via USB (at least that's what I understand it to do)
http://forum.xda-developers.com/showthread.php?t=1310865
Actually fastboot is a very safe protocol, it checks for sums before sending and before flashing so that the image is still intact. However if your bootloader is already corrupt on your computer or you dd (flash) some crap into the bootloader partition, your phone will be bricked.
I know a guy who wanted to return his HTC Desire HD. He replaced his bootloader with a porn image. I don't think I have to mention that the phone did not boot anymore
What is the method to fix a phone that is in a boot loop or something else.
Sent from my Galaxy Nexus using XDA App
No phone is idiot proof and as a previous Galaxy S II owner I have seen guys flash a i9000 (Galaxy S) ROM to their phone and then wonder why it does not boot and the amount of guys who flashed the partition table which also screwed their phones is unbelievable.
Bottom line is read the documentation and read it again and any questions ask on here and from there you cannot go wrong.
jkoljo said:
I know a guy who wants to return his HTC Desire HD. He replaced his bootloader with a porn image. I don't think I have to mention that the phone did not boot anymore
Click to expand...
Click to collapse
hahahahahaha you just made my day
freebordjunky said:
hahahahahaha you just made my day
Click to expand...
Click to collapse
lol how the hell did they manage to do that?
spacecasespiff said:
What is the method to fix a phone that is in a boot loop or something else.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Boot it into fastboot and flash the latest official Google image, I would imagine.
SQFreak said:
Boot it into fastboot and flash the latest official Google image, I would imagine.
Click to expand...
Click to collapse
LMFAO
10 chars
Evostance said:
Pretty much, as long as some how you dont break fastboot
Click to expand...
Click to collapse
If you braek fastboot, dont you still have Odin?
jkoljo said:
Actually fastboot is a very safe protocol, it checks for sums before sending and before flashing so that the image is still intact. However if your bootloader is already corrupt on your computer or you dd (flash) some crap into the bootloader partition, your phone will be bricked.
I know a guy who wanted to return his HTC Desire HD. He replaced his bootloader with a porn image. I don't think I have to mention that the phone did not boot anymore
Click to expand...
Click to collapse
that ws ****in hilarious!!!!
josteink said:
If you braek fastboot, dont you still have Odin?
Click to expand...
Click to collapse
Good point. Yes.
No idea how to use it though
Sent from my Galaxy Nexus using Tapatalk
josteink said:
If you braek fastboot, dont you still have Odin?
Click to expand...
Click to collapse
Quite probably not.
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Follow instructions in Method 1 here.
simms22 said:
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
Click to expand...
Click to collapse
He's asking how to root, not how to flash a rooted custom ROM...
efrant said:
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
simms22 said:
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
Click to expand...
Click to collapse
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
simms22 said:
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
Click to expand...
Click to collapse
Which is exactly what i said to do: flash cwm and flash su.zip. nothing else.
morfic said:
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
Click to expand...
Click to collapse
Not sure I understand what you are saying.
Sent from my Galaxy Nexus using Tapatalk 2
Moved to Q&A
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
i think this method is pretty easy. i had no issues using it.
http://forum.xda-developers.com/showthread.php?t=1392310
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
thos25 said:
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
morfic said:
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
Click to expand...
Click to collapse
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
thos25 said:
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
the newest twrp touch recovery is sweet, cwm doesnt even come close. when you do decide to set your nexus free, give it a try
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Install GNex Toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310. First do option 1 (drivers) and than option 7 (one-click for all). You have root and cwm, works like a charm and is the easiest way to do it.
Jubakuba said:
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
Click to expand...
Click to collapse
Im bootloader unlocked, cwr.
im very computer savvy, and tech savvy, i know what im talking about, so everything i say i am completely positive of, i am experienced with android, i just dont know how to root. I have the su.zip on my sd card btw.
Good Lord,
One question and so many answers, no wonder new users are confused--
Don't pay attention to me--just bored atm and trying to decide btw the GN tmobile or One S to replace my N1--
Nothing like hijacking a thread either--
I prefer to use Galaxy Nexus Root Toolkit. Its very simple and do the job well. Never experiencing any problems with it.
Sent from my Galaxy Nexus using Tapatalk 2
OK, this method was out since long time ago, but since not a lot of people know about this simple method, I am thinking of posting this thread to help a lot of people
Source: http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
Just follow the instruction and you should be able to temporary use the Clockworkmod recovery and able to backup all of your data (Make sure you got ADB driver installed though)
kyokeun1234 said:
OK, this method was out since long time ago, but since not a lot of people know about this simple method, I am thinking of posting this thread to help a lot of people
Source: http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
Just follow the instruction and you should be able to temporary use the Clockworkmod recovery and able to backup all of your data (Make sure you got ADB driver installed though)
Click to expand...
Click to collapse
1. Root is not required for backup through recovery, whether running recovery that is on the device or booting recovery from your PC. Being rooted and having a custom recovery installed are two different things. Title is misleading.
2. Method still requires unlocking the bootloader (which still wipes your phone), you might as well flash recovery anyway.
It is neat that this is possible, but it seems rather redundant and unnecessary once you realize the only difference between booting into recovery from fastboot and flashing recovery is where the recovery is stored. The bootloader still has to be unlocked, if I'm not mistaken. If it doesn't have to be unlocked, then I can see the significance
JaiaV said:
1. Root is not required for backup through recovery, whether running recovery that is on the device or booting recovery from your PC. Being rooted and having a custom recovery installed are two different things. Title is misleading.
2. Method still requires unlocking the bootloader (which still wipes your phone), you might as well flash recovery anyway.
It is neat that this is possible, but it seems rather redundant and unnecessary once you realize the only difference between booting into recovery from fastboot and flashing recovery is where the recovery is stored. The bootloader still has to be unlocked, if I'm not mistaken. If it doesn't have to be unlocked, then I can see the significance
Click to expand...
Click to collapse
As much as you're right, some people just wants to get OTA and stuff... For example, 3 of my friend who owns android wants to get OTA. Of course this isn't the most recommended way, at least it is there for people who wants it
Sent from my Galaxy Nexus using xda app-developers app
kyokeun1234 said:
As much as you're right, some people just wants to get OTA and stuff... For example, 3 of my friend who owns android wants to get OTA. Of course this isn't the most recommended way, at least it is there for people who wants it
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I understand, it's just that the difference between the methods is negligible.
JaiaV said:
I understand, it's just that the difference between the methods is negligible.
Click to expand...
Click to collapse
I understand what you're saying too. It's just good to have choices you know?
Sent from my Galaxy Nexus using xda app-developers app
Titanium Backup is just so useful. Such a helpful utility. I guess the easiest without root would be through imaging of userdata?
Sent from my Galaxy Nexus using Tapatalk 2
Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.
colomob said:
Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.
Click to expand...
Click to collapse
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.
kyokeun1234 said:
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.
Click to expand...
Click to collapse
and thats where my problem comes. i cant find a stock rom. im on a custom rom.
colomob said:
and thats where my problem comes. i cant find a stock rom. im on a custom rom.
Click to expand...
Click to collapse
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus
kyokeun1234 said:
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus
Click to expand...
Click to collapse
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?
colomob said:
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?
Click to expand...
Click to collapse
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250
bk201doesntexist said:
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250
Click to expand...
Click to collapse
Im on sprint..
anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???
colomob said:
anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???
Click to expand...
Click to collapse
Yes you can use that guide for toroplus (i.e., Sprint) devices as well if you have the images. But since you don't have the userdata image (and therefore you skip that step), you may need to boot CWM and wipe /data and /cache, but only if you experience a bootloop.
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You cannot flash image files on any recoveries. You need to do those in fastboot mode using command prompt.
colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's not at all what I said.
Follow the guide. But for the userdata image (which you don't have), boot into recovery and wipe data.
I finally did it!! If anyone needs help let me know. PM me.
Sent from my Nexus 7 using xda app-developers app
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
why would you use odin? thats an awful hacker tool, leaked, no documentation, press one wrong button and your nexus is dead. google has made fastboot, use that to flash images. you find a tutorial in the galaxy nexus toolkit thread, you might aswell use that, though, it relies on fastboot and adb.
For people that came from samsung devices Odin is a very useful and the most comfortable tool. Fastboot is safer indeed but....sometimes u just don't want to write plenty commands in terminal when in Odin is just a one click.
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Ok guys i repaired. From so diffcult way
Sent from my Galaxy Nexus using xda app-developers app
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
molesarecoming said:
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Click to expand...
Click to collapse
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Click to expand...
Click to collapse
Thx very much.
Sent from my Galaxy Nexus using xda app-developers app
m.kochan10 said:
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
Click to expand...
Click to collapse
Long story...
Sent from my Galaxy Nexus using xda app-developers app
yashade2001 said:
Long story...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This information can be useful for other users. U sure you don't wanna share it?
m.kochan10 said:
This information can be useful for other users. U sure you don't wanna share it?
Click to expand...
Click to collapse
Ok. İf you wanna know,
İ unpugged my phone. Then its bricked of course. And i unbricked this using linux. İ installed ubuntu to my computer. İ used terminal. But it isnt finished . İ have to use mac os x. For a program. İts command line osx. Then its unbricked and i flashed original rom with odin.
Sent from my Galaxy Nexus using xda app-developers app
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum..
Click to expand...
Click to collapse
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
I wouldn't exaggerate though. I owned Galaxy R, then S2 for more than year totally. I've never had one single issue with Odin (and I am a flashoholic ). Yes there were some instances when people messed around using it in a mindless way (or simply had bad luck...or Kies turned out to be a villain...) but the majority used it regularly without bigger problems. I'm not trying to say that Odin is perfectly safe...no no but if you follow the guide, have all required drivers installed (and Kies turned off) I don't see the reason why I should discourage users from running it.
odin
molesarecoming said:
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
Click to expand...
Click to collapse
yeah, i perefer fastboot and gnex toolkit too but this time i hav to use odin.
use always odin and don't post if you will have problems.as molesarecoming sad you,fadtboot it's the way to go.odin works too,but fastboot is better,and don't say "fastboot has command to write,it's more difficult bla bla bla" all ****,there are not more than 5 commands to know for the major parts of operations.tools works withouyt commans,but i prefer manually because i know what i'm doing and i know if seomething goes wrong,at which type of command the phone was when occured the problem.