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.
Related
HELP!
Tried using the method to unlock and root and when I used the boot img now I am in a bootloop, sits at Google and just keeps going. Can anyone point me to the factory LTE boot.img? PLEASE?
Thank you in advance.
Would this help? http://rootzwiki.com/topic/11459-updatedvzw-g-nexus-full-nandroid/
I am having the same issue. The root tool included boot.img gets the phone stuck on the Google logo when the 'fastboot boot boot.img' command is used
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
im in the same boat. used superboot r3 ....
---------- Post added at 01:25 PM ---------- Previous post was at 01:25 PM ----------
wilshyre said:
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
i did the OTA then superboot
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
hmm, i managed to get into recovery. i did factory reset... looked like the phone froze for a while but i believe i pressed power and volume (cant remember if i was both or just one. but i was able to boot up just fine.
Factory Images for CDMA/LTE Verizon Galaxy Nexus: https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Source: http://groups.google.com/group/android-building/msg/f6002e27c9b41a5d?pli=1
jbqueru Jean-Baptiste Queru
Factory images for Verizon Galaxy Nexus at goo.gl/SOSa6 - more goodness will follow.
14 minutes ago Favorite Retweet Reply
Click to expand...
Click to collapse
looks like superuser was installed as well...
wilshyre said:
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I tried superboot and the manual method, no dice. Stuck on the Google logo for both
I had to wait at least five minutes before it finally rebooted again after fast booting the boot.img. I was sure that I wasn't booting but it turns out it was just taking a long time
Sent from my Galaxy Nexus using xda premium
Are you sure it's in a bootloop?
If your following this guide, step 4 rooting, give it some time. I thought mine was froze at that step as well, but I waited and it booted up. Probably took about 2 minutes or so (though it felt like 20).
Edit: Ha, swm beat me to the punch
Nevermind... apparently it worked and gave me SU without getting past the Google logo. Did a battery pull and superuser worked. Very strange.
Natolx said:
Nevermind... apparently it worked and gave me SU without getting past the Google logo. Did a battery pull and superuser worked. Very strange.
Click to expand...
Click to collapse
people here http://forum.xda-developers.com/showthread.php?t=1352413&page=12
are saying it takes about 5 minutes, not actually a boot loop...
I found the LTE img here , I actually loaded odin and wiped data and it solved my bootloop, wasnt stuck on the animation it was stuck at the actual Google, then it would vibrate and reset Google just keep doing it. Apparently that old img works fine with 4.0.1 but 4.0.2 sends you in the loop
There's also this tarball recently issued direct from google:
http://groups.google.com/group/andr...hread/9a944a4dbc8d23c5/f6002e27c9b41a5d?pli=1
It's not 4.0.2 though, that puts you back on 4.0.1.
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Wngman200 said:
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Click to expand...
Click to collapse
Same. I downloaded the tgz file from Googles site but I dont know how to flash it on my phone. Odin im assuming could work but Ive never used it.
Wngman200 said:
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Click to expand...
Click to collapse
Johnpg said:
Same. I downloaded the tgz file from Googles site but I dont know how to flash it on my phone. Odin im assuming could work but Ive never used it.
Click to expand...
Click to collapse
Do you guys have fastboot set up and do you have 7zip or something comparable to unzip the tgz?
Sent from my Galaxy Nexus using xda premium
davehasninjas said:
Do you guys have fastboot set up and do you have 7zip or something comparable to unzip the tgz?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah my computer finds the serial number. I tried to use ODIN but ODIN wont find my phone(where it shows up with the ID and yellow) I also have something to unzip it. Still havnt figured out how to flash the stock image
How to flash the stock image file for those of you having issues:
http://forum.xda-developers.com/showpost.php?p=20344760&postcount=2
Johnpg said:
Yeah my computer finds the serial number. I tried to use ODIN but ODIN wont find my phone(where it shows up with the ID and yellow) I also have something to unzip it. Still havnt figured out how to flash the stock image
Click to expand...
Click to collapse
ok, when you unzip it, go to the image-mysid-itl41d.zip folder, and move system.img and boot.img to the same directory as fastboot.
Now once you have fastboot up in a terminal and your device is in fastboot mode the commands are:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Unless you're going the method from the noob thread, in which case thebfastboot commands should be (correct me if I'm wrong):
fastboot-windows.exe flash system system.img
fastboot-windows.exe flash boot boot.img
fastboot-windows.exe reboot
And that should have you booting back to stock.
I ran into this issue myself since I was on 4.0.2. Once I was back on 4.0.1 I used super boot straight from [email protected]'s thread and it worked fine. Upgraded back to 4.0.2 afterwards and still kept root.
Let me know if this helps.
Sent from my Galaxy Nexus using xda premium
yup, i'm that noob you guys complain about... totally open to all general flaming attacks....
decided it was time to unlock and root....
being a total dumbass, i first did this: http://forum.xda-developers.com/showthread.php?t=1362957
phone stuck in reboot cycle. this was for gsm and i have lte, yup major oops.
tried gn toolkit 2.2 and now constantly get a write error on anything i try for all options.
didd i brick my phone? anything i can do to just get back to factory? thought i knew what i was doing after my droid and droid x. apparently i should stick with stock. so sorry guys. any help appreciated.
Can you boot into fastboot or recovery? If you can get into either you'll be fine.
i can get into fastboot just fine. just don't know what to do from there. i get write errors from toolkit 2.2
I have no idea about the toolkit, you can just use fastboot to flash clockwork recovery or boot a boot.img or system.img
As long as you can get into bootloader mode ... you can still follow the manual steps in the same post (post # 3) if automated Toolkit doesn't work. give that a shot.
Edit: lol, ikon8 beat me to it ...
enaybee said:
As long as you can get into bootloader mode ... you can still follow the manual steps in the same post (post # 3) if automated Toolkit doesn't work. give that a shot.
Edit: lol, ikon8 beat me to it ...
Click to expand...
Click to collapse
Yea, just follow the directions in post #3 of that thread. Forget that toolkit mess and just do it all manually.
everything either says cannot write too many.... or it says failed to write or failed to load...
Have you already unlocked the bootloader? fastbook oem unlock
---------- Post added at 10:01 PM ---------- Previous post was at 09:47 PM ----------
Try Paul's Superboot, it contains all the binaries you'll need to get it rooted. Make sure to unlock bootloader first then just follow his instructions.
No flame here brotha we all know what it feels like. From reading the posts above you can get into boot loader so you'll be ok. Just read thoroughly, maybe drink some coffee, read again and you should be good to go.
Sent from my Google phone
may be simpler than i thought... problem is my pc is not unzipping the google .tar file. winzip free can't figure it out. good way to go about unzipping this without paying?
wadec22 said:
may be simpler than i thought... problem is my pc is not unzipping the google .tar file. winzip free can't figure it out. good way to go about unzipping this without paying?
Click to expand...
Click to collapse
I don't know anything about windows but I think 7zip will work, it's free and open source.
ikon8 said:
I don't know anything about windows but I think 7zip will work, it's free and open source.
Click to expand...
Click to collapse
7-zip will, in fact work. It's my go-to compression/decompression tool.
1.21Gigawatts said:
7-zip will, in fact work. It's my go-to compression/decompression tool.
Click to expand...
Click to collapse
why did you necro a thread from 8 months ago?
Zepius said:
why did you necro a thread from 8 months ago?
Click to expand...
Click to collapse
Not just this thread.
Sent from my Galaxy Nexus using xda premium
He's going for 10 posts and pulling up old threds cause he has no idea how to contribute ;/
Sent from my Galaxy Nexus using xda premium
I own the VZW Galaxy Nexus , and I just unlocked the bootloader and now my phone will not boot-up. The device is stuck on the Google logo splash screen with the lock icon at the bottom of the screen signifying that the bootloader is unlocked. I used the program called Galaxy Nexus Root Toolkit v1.4 from Wugfresh to unlock my phone's bootloader, and now my phone is currently bricked. I can still go to the bootloader by holding down volume and power. Can someone help me restore my phone to a working state?
EDIT: Also I'm sorry if this is the wrong place to be posting this, I don't use this site often and the site would not let me post to Galaxy Nexus Android Development for some reason. I can still go to the bootloader by holding down volume and power.
the reason why ur stuck is because ur stock recovery might be blown up. try and flash stock recovery ....or cwm recovery...
Sent from my Galaxy Nexus using xda app-developers app
actually try a battery pull and startup ..
Sent from my Galaxy Nexus using xda app-developers app
afma_afma said:
actually try a battery pull and startup ..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You think I didn't try that already? And I don't know how to flash a stock recovery, help?
My phone also got stuck at the google screen when it tried to boot. Turned out it was a bad flash when I was trying to install jelly bean. I just went back in and flashed jelly bean again and everything was back to normal. I think you'll be just fine if you just flash a stock rom or whatever rom you want to run on. Look for one of the guides on how to return to stock and just skip the part about relocking your bootloader.
Sent from my Galaxy Nexus using xda app-developers app
In the toolkit there is a "flash back to stock" option. Boot back into bootloader and use it.
Thank you very much wish to continue your work
z06mike said:
In the toolkit there is a "flash back to stock" option. Boot back into bootloader and use it.
Click to expand...
Click to collapse
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Where's your folder located?
Sent from my ADR8995 using xda premium
johnc7995 said:
You think I didn't try that already? And I don't know how to flash a stock recovery, help?
Click to expand...
Click to collapse
I didn't mean to thank your post so you owe me one.
Why be an ass to someone who is trying to help you. A simple I tried that and it didn't work would be fine.
If we assumed everyone did what we would suggest then half of people's issues would probably not have gotten fixed.
Like I would assume you new how to flash stock recovery so I would not want to offend you buy telling you how.
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Now to be nice because I know a non working phone sucks : )
Put your phone into the bootloader screen to use in the toolkit. To do this. remove battery, place back in....Then hold volume up and down at the same time and then power the device on while holding the buttons. You will then be in bootloader and the toolkit should recognize your device from there.
If it does, try the steps over again or if you can flash back to stock everything and start over. The tollkit give you the instructions where to get the files if you choose that option.
johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Shoot me your email and I'll try and help you out through G talk.
blackscreen but fastboot will work? There are no responses, unless i plug it in. i get a driver that is enabling and then disabling. The Driver is called OMAP4440.
I believe that ubuntu team will be posting there galaxy nexus image rom here at this link
http://cdimage.ubuntu.com/
please dont yell at me if im wrong..
nullbesign said:
I believe that ubuntu team will be posting there galaxy nexus image rom here at this link
http://cdimage.ubuntu.com/
please dont yell at me if im wrong..
Click to expand...
Click to collapse
Also check: https://wiki.ubuntu.com/TouchInstallProcess
I haven't seen anyone link to this yet, what's this about?
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
SkuzFoz said:
I haven't seen anyone link to this yet, what's this about?
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
Click to expand...
Click to collapse
I wondered there too and was wondering myself. it has the codenames for all the nexus devices, Galaxy Nexus (GSM), Nexus 4, Nexus 7 ect
i wlii try to flash the maguro file size 48mb....report at once....hope not to brick my gnex...lol
adambala said:
i wlii try to flash the maguro file size 48mb....report at once....hope not to brick my gnex...lol
Click to expand...
Click to collapse
I would have gone ahead but I'm not sure why there are different versions. Totally confused on boot and recovery images, but I've been out of the ROM loop for a long time.
nothing.....no boot.....just restoring my xenon rom...
The zip is flashable, contains a boot.img and has scripts to install stuff. the others are .IMG files, and the main phablet one is the biggest file at over 400megs.
edit: the one that is almost 500megs is a flashable zip too, has updater script. since that is the only one of that size, i bet that is the main ubuntu, and the others are the drivers, boot images, ect, specific to different devices.
yeap...i am downloading the img file now but i am not sure if i want to enter fastboot to flash it...
adambala said:
yeap...i am downloading the img file now but i am not sure if i want to enter fastboot to flash it...
Click to expand...
Click to collapse
We can flash it via fastboot like google images???????
Sent from my GT-I9001 using xda app-developers app
kagouro said:
We can flash it via fastboot like google images???????
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
No one knows yet. but you can try, but you risk bricking your phone. My galaxy nexus is dead now, charging the battery. Not going to experiment with my nexus 4, since it's my daily phone. by the time my gnex charges someone will figure it out or they'll be instructions posted on the ubuntu site.
I think we should fastboot flash all the img boot recovery system and then flash the zip. So start from the bottom of the page
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
Page offline ! They took it down.
j3r3myp said:
I think we should fastboot flash all the img boot recovery system and then flash the zip. So start from the bottom of the page
Click to expand...
Click to collapse
I'm going to guess you might need their recovery to flash it. Otherwise why bother making one.
So nice I hope to use it soon~~
The files are still there, they just put up a blank index.html file so you can't see the directory I have all the files for nexus 4 and Gnex
Here's the links to Gnex
http://cdimage.ubuntu.com/ubuntu-to...wc-demo/quantal-preinstalled-armel+maguro.zip
http://cdimage.ubuntu.com/ubuntu-to...mo/quantal-preinstalled-boot-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...uantal-preinstalled-recovery-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to.../quantal-preinstalled-system-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip
the last one is the ~500 meg file.
Luxferro said:
No one knows yet. but you can try, but you risk bricking your phone. My galaxy nexus is dead now, charging the battery. Not going to experiment with my nexus 4, since it's my daily phone. by the time my gnex charges someone will figure it out or they'll be instructions posted on the ubuntu site.
Click to expand...
Click to collapse
Brick it? Really?
As long as you dont flash a new bootloader, there's really no risk of bricking your phone, because, via your old bootloader you can always boot back into fastboot mode.
I'm not sure you know what the word "brick" means: Dead as a brick. Unrecoverable. Useless.
If it's recoverable, it's not a brick. Being in a state where you have to reflash some things in fastboot hardly constitutes a brick.
Sorry about the nitpick, but as a owner of much less open devices, where the risk of bricking $1k worth of equipment was a real risk when rooting/flashing, I find myself offended every time I see people whine about Nexus'es being "bricked".
Is the 500MB img for GNex, to your opinion?
Luxferro said:
The files are still there, they just put up a blank index.html file so you can't see the directory I have all the files for nexus 4 and Gnex
Here's the links to Gnex
http://cdimage.ubuntu.com/ubuntu-to...wc-demo/quantal-preinstalled-armel+maguro.zip
http://cdimage.ubuntu.com/ubuntu-to...mo/quantal-preinstalled-boot-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...uantal-preinstalled-recovery-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to.../quantal-preinstalled-system-armel+maguro.img
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip
the last one is the ~500 meg file.
Click to expand...
Click to collapse
From a shell, just type the following:
Code:
# wget http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-ubuntu_stamp
Guys why new thread when v have already one Ubuntu discussion.. This makes people search more... close this thread
Sent from my Galaxy Nexus using Tapatalk 2
josteink said:
From a shell, just type the following:
Code:
# wget http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-armel+maguro.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-boot-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-recovery-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-system-armel+maguro.img.md5sum http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-ubuntu_stamp
Click to expand...
Click to collapse
I also mirrored the original page with all download links:
http://invalid.ed.ntnu.no/~jostein/ubuntu_images.html
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