Develop Bugs

[ICS][SOURCE][ROM][GAPPS] ICS 4.0.3 from source with google apps

Compiled from source with no modifications
ICS 4.0.3 crespo4g install via fastboot
DO A FULL WIPE! then flash.
adb reboot-bootloader
fastboot erase userdata
fastboot erase cache
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
# It might error a few times on first boot that's because I suck at this but it'll work just fine upon reboot
I shouldn't have made any changes to my first upload the current one will get stuck booting sorry give me a few minutes
I should have mentioned previously that I don't know how to make a zip installer for cwm yet but I'll work on it and I have to work out the double apps thing I'm new to all of this so it'll take more than the 2 hours of compiling and the 5 minutes of adding the proper apks
Boot Image: http://ns2.srv.so/boot.img
Untouched Stock AOSP: http://ns2.srv.so/crespo4g.7z
Somewhat Stable: http://ns2.srv.so/system.7z
Nightly: http://ns2.srv.so/system-nightly.7z
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ There's an actual nightly which is full stock no mods and I'll create an ota package when it's done compiling AGAIN because ****ing windows likes to reboot (updates) which kills the ssh session I'm using to compile android...
real 162m27.018s
user 576m10.937s
sys 43m59.849s
That's how long it takes to compile android on a dual xeon box with 12 gigs of ram and 10k rpm SCSI Drives

RSVP
Sent from my BB GPA19x Linux S 4G using xda premium

root access? this will be deleted. im almost positive this user just stole the build from the other user and put gapps in the system/app folder....please remove as this will have 0 progress.

Sorry I messed up the system image I just updated the zip and it's uploading now and I didn't steal this I compiled it on my own hardware
This has root and the superuser apk built in check out the file
ns2.srv.so/proof.png

that picture looks nothing like any other rom i've ever downloaded. what is up with all those files...doesnt look right to me

vinnypel2ella said:
that picture looks nothing like any other rom i've ever downloaded. what is up with all those files...doesnt look right to me
Click to expand...
Click to collapse
those files in the screeny have nothing to do with the rom except for the image files I don't yet know how to make a cwm flashable zip so you have to flash this via fastboot

No offence white, but in with vinny on this. You have 3 posts ever so I too am a bit lerie
Sent from my Nexus S 4G using XDA App

where's the file to download ?
Sent from my Full Android on Crespo4G using XDA App

CHINESKATO said:
where's the file to download ?
Sent from my Full Android on Crespo4G using XDA App
Click to expand...
Click to collapse
ns2.srv.so/system.7z is the system image extract with 7zip
ns2.srv.so/boot.img

not like it will matter to most of you.. but I vouch for nitesn0w. him and i have worked together on NS4G related stuff a lot.
and the links are weird looking because its hosted on a personal server.. no free hosting BS.
its up to you whether you want to use the rom or not.. but its certainly legit.

it boots! like stated in OP some double system apps but it runs really really smooth. and my phone hasn't exploded yet

thedudejdog said:
it boots! like stated in OP some double system apps but it runs really really smooth. and my phone hasn't exploded yet
Click to expand...
Click to collapse
I only have one nexus s 4g so I'm intent on making things not explode and or brick

autoprime said:
not like it will matter to most of you.. but I vouch for nitesn0w. him and i have worked together on NS4G related stuff a lot.
and the links are weird looking because its hosted on a personal server.. no free hosting BS.
its up to you whether you want to use the rom or not.. but its certainly legit.
Click to expand...
Click to collapse
Matters to me autoprime. If you vouch for him then I will try this build as well
Sent from my SPH-D710 using xda premium

JohnCorleone said:
Matters to me autoprime. If you vouch for him then I will try this build as well
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
i can vouch that this boots. if you know fastboot you should flash this now!

pimpinkorte82 said:
nitesnow i do not know what all of these people are talking about. I will try it if it messes up my nexus s 4g i will brick it and give it to sprint and get a new one. That is what warrenty is for! Anyways I do not even know where to begin to compile a rom so what u have done is better than me. Thanks!
Click to expand...
Click to collapse
it's pretty easy download http://ns2.srv.so/system.7z extract it with 7zip and download http://ns2.srv.so/boot.img flash it with fastboot
adb reboot-bootloader
fastboot erase data
fastboot erase cache
fastboot flash boot boot.img
fastboot flash system system.img

I'm currently compiling a completely untouched copy of ICS 4.0.3 which will be posted soon and then I'll work on modifying it

"make otapackage" is the final syntax for making an update.zip (assuming you're building on Linux).
However, ROMs compiled directly from [Google's] source, should probably just be left to be fastbooted.

I did some cleanup. Please stay on topic and discuss about the freakin rom!. Some people has reported it works..so I will leave this open.
Stay on topic and let these guys work on it.
Thanks,

G+ post from android said theres a surprise coming on monday!! ns4g official ota????
Sent from my Nexus S 4G using XDA Premium App

[REQ] flash_image for ICS

Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c

Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)

nxt said:
Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
I want to flash images on my device. It looks like the version of the file that has been out for years is not ICS compatible.
Sent from my Galaxy Nexus using Tapatalk

Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)

I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU

nxt said:
Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
Exactly.
josteink said:
I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU
Click to expand...
Click to collapse
flash_image is a utilty that will allow you to flash images to partitions on your device using a terminal emulater on your device or via adb. There is no need to have an unlocked bootloader, and no need to plug your device into a computer.
CWM uses this utility to flash images. It looks like Koush made some changes to it to make it work on ICS, as the original version no longers works properly on ICS (worked fine on Gingerbread and earlier).
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.

efrant said:
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.
Click to expand...
Click to collapse
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk

josteink said:
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks very much. I'll pm you if no one helps out.
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
Anyone?... Bueller?... Anyone?...

efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!

josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Thanks for spending time on this, but, unfortunately it does not work on ICS. If it was from a build pre-December 18, it likely won't have the modifications in it.
I'm a noob as well, and I probably know less than you, so I don't think I'd be able to write a good step-by-step...
Hopefully someone will be able to help out. Thanks again.

josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Correction.
Using some cyanogen magic perl scripts, I managed to unpack the official 5.5.0.2 recovery (which works fine on my ICS gnex) and from that one I could extract KOush's build of flash_image, which you will find attached to this post.
It is significantly larger than the plain ICS flash_image, which I guess means it is statically built/linked and probably supports more devices, but I can't really say anything for sure.
Have a good one.
Now... I'm still looking into building fastboot FOR arm (so that I can run it from my asus transformer).
Anyone care to help me out getting gcc to build stuff for me?

Hmmm. I can't figure this out. None of the versions of flash_image seem to work in a terminal, yet CWM and ROM Manager obviously work using it.
If anyone can help shed some light on this, it would be more than welcome.
On older devices, you could use flash_image to flash radios, bootloaders, and recoveries, either through a terminal emulator on your device, or though an adb shell on your computer.
The syntax was: flash_image partition path-to-image-file.img
Trying to use this on my Galaxy Nexus produces an error:
can't find recovery partitionfailed with error: -1
Not sure what the problem is. It would be nice to get this working, as it would give users another on-device option to flash radios, bootloaders, and recoveries, without using ROM Manager.

Hey efrant, did u ever get anywhere with this?

danger-rat said:
Hey efrant, did u ever get anywhere with this?
Click to expand...
Click to collapse
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Sent from my Galaxy Nexus using Tapatalk

Trying flash_image from ROM Manager 5.0.0.1
efrant said:
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Click to expand...
Click to collapse
The apk for ROM Manager from ClockworkMod (Koush) contains a flash_image file in the assets folder. For ROM Manager 5.0.0.1, the file is 70.66K and has a MD5 checksum of a7291696dd4fc4208e397e31aa84bc9e.
I'm going to try copying it to /system/bin, setting ownership to root.root, and setting permissions to 750. I'll then see if it works on my Galaxy Nexus (LTE/CDMA) like the old CyanogenMod flash_image used to work.
I'll post back here once I'm done.
---------- Post added at 03:22 PM ---------- Previous post was at 03:16 PM ----------
chriv said:
I'll post back here once I'm done.
Click to expand...
Click to collapse
No luck. I used the flash_image that was in ROM Manager 5.0.0.1, and I had the same problem:
Code:
[email protected]:/mnt/sdcard/Download # flash_image recovery recovery.img
flash_image recovery recovery.img
can't find recovery partitionfailed with error: -1
255|[email protected]:/mnt/sdcard/Download #
---------- Post added at 03:27 PM ---------- Previous post was at 03:22 PM ----------
I also tried:
Code:
[email protected]:/mnt/sdcard/Download # flash_image --help
flash_image --help
usage: flash_image partition file.img
2|[email protected]:/mnt/sdcard/Download #
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?

chriv said:
[snip]
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?
Click to expand...
Click to collapse
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
But I haven't had the chance to work through it yes.
Sent from my Galaxy Nexus using Tapatalk

flash_image not the solution
efrant said:
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
Click to expand...
Click to collapse
I tried that. The error is the same. I also checked out the android source. The source for flash_image is bootable/recovery/mtdutils/flash_image.c .
flash_image enumerates all of the mtd partitions on the device from /proc/mtd, and compares their names with the first argument passed to it. If it doesn't find a match, it bails with the error "can't find %s partition" where %s is the first argument passed to flash_image.
You can enumerate the mtd partitions yourself. I did, and this is what I got:
Code:
[email protected]:/ $ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
[email protected]:/ $
As you can see, the only mtd partition on my Samsung Galaxy Nexus is w25q80. I could use flash_image with it, but I'm not that brave. For all I know, I could be overwriting the system partition, or the userdata partition.
The bottom line:
It is not likely that flash_image is being used by ROM Manager on the Galaxy Nexus, as flash_image is only capable of writing to the w25q80 mtd partition, and I don't know what it is! Koush must be using some other way to flash the recovery from the phone.
I'd be interested to know if other Galaxy Nexus users have something different for /proc/mtd.
I'd contact Koush and ask him how he writes the recovery on the Galaxy Nexus, but he never responds to my tweets! ;-)
I hope this helps some users, even if it just prevents other users from going on a wild goose chase with flash_image.

@chriv I get the same as you when I list the partitions.
Sent from my Galaxy Nexus using Tapatalk

Sorry to bump an old thread, but I found an alternative way to flash recovery images to my CDMA Galaxy Nexus without using flash_image (and without unlocking the bootloader/using fastboot). I found a post over on RootzWiki and the command is:
Code:
cat name-of-the-recovery.img > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
I did this and successfully reflashed the stock Google recovery image. I currently have a CM9 nightly running on the phone, the bootloader relocked and the stock recovery loaded (since leaving ClockworkMod Recovery installed would allow a thief to extract data via adb).
There are other things in the /by-name directory such as boot and radio so I'm guessing that it'd be possible to write those images as well (although I haven't tried it myself).
The only weird bug I've encountered is that ROM Manager still says that ClockworkMod Recovery is still installed for some reason (but it's not).

Recovery mode

Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver

Apparently telling people where to post is frowned upon in this establishment. Please refer to my other post

ÜBER™ said:
You did it wrong. You need to flash the toroplus big dog.zip please search before posting and do not post questions in android development.
http://forum.xda-developers.com/showthread.php?t=1614922
This has the how to.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA

So the problem is that you flashed custom recovery and when you reboot it reverts to stock recovery? If so it's because you're on the stock ROM and it's got a script that restores stock recovery upon reboot. You can either install a custom ROM or do this:
juliano_q said:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse

riggsandroid said:
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
He flashed the correct zips.

jesusice said:
He flashed the correct zips.
Click to expand...
Click to collapse
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
And I flashed the zips he posted when I rooted. I trust that Bigrushdog does know what he's doing but that zip seems to have a lot of things in there that he may or may not need. Like, why does it contain a boot.img? He only needs the SU binary to obtain root. His problem must be that he's rebooting. He should fastboot flash recovery, then fastboot reboot recovery and then flash the SU zip from there. And if he wants to stay on the stock ROM he should follow the instructions I posted. I'm not saying you're *wrong* but I am saying that I'm more right
EDIT: Rereading his post I'm pretty sure he does have root already, his problem is just that recovery isn't sticking which is a known issue with a known solution as I posted previously. Its the exact same thing on the Nexus S.

If anything we are equally correct and my method is much simpler. And yes the boot.img is required this is the stock kernel image without the recovery.sh that runs on the stock kernel. This will keep him from having to delete it manually. I know this because the same method was needed for my epic. You have to flash a tweaked stock kernel without the recovery.sh then flash the recovery. Then everything will stick. His issue is he didn't flash the tweaked kernel and upon booting the stock kernel deleted his custom recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

denverdesktop said:
Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver
Click to expand...
Click to collapse
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3

msedek said:
Ignore all the previous comments and once you follow http://forum.xda-developers.com/showthread.php?p=23229558 You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Actually he would be even more lost and confused.
Sent From My Sprint Galaxy Nexus via XDA Premium

Just do this:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak (note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
msedek said:
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
That has nothing to do with the problem.

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
Click to expand...
Click to collapse
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.

jesusice said:
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.
Click to expand...
Click to collapse
It takes longer.. takes more effort.
Its simpler to flash the su.zip and call it a day. Than have to flash recovery flash a subinary.zip delete the script the reflash recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
That has nothing to do with the problem.
Click to expand...
Click to collapse
It always has to do with the problem.. Why to do a Mess with your phone and not doing a fresh start???
Also in the way getting a wise android man while learning how to fastboot /adb?...
Thats all i got to say.. In my case id start all over and not going deep complicating things and messing up the os
Galaxy Nexus AOKP m5 Franco kernel m3

Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver

denverdesktop said:
Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver
Click to expand...
Click to collapse
Lol I'm sorry for clouding your thread with a semi-argument. Glad your up and running
Sent From My Sprint Galaxy Nexus via XDA Premium

it happens
No problem. It happens.
I can comfortably flash AOPK with CMW, correct?
Thanks
Denver

Yes but make sure you wipe all
Galaxy Nexus AOKP m5 Franco kernel m3

please help (odin)

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.

Am I doing it right , or right?!?

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