Database Users

[REF] [NS4G] Stock ROMs | How To Root/Unroot | OTA Files & Images

Why another post for stock files? Well for a few reasons, mainly the lack of quality found amongst the files in similar threads on the web. When I got my Nexus S 4G I took a look around the web, downloaded the stock roms that were floating around and noticed they were very flawed. The update scripts used in them were poorly done, seem to be the result of copy and pasting many update scripts together. The boot.imgs were also flawed, some of them even 8mbs in size, the stock boot.img is 2.8mb. After running them through one of my scripts, I also noticed many apps were not even zipaligned. Needless to say I did not flash these files. I took it upon myself to remake all these files. Stock files are essential to a development phone and can save many people in a sticky situation. Also, I have noticed that the official stock software images have not been released yet, so I went ahead and uploaded those for you all as well. These images include radio, boot, recovery, system, userdata, and bootloader. Please note, this post is not intended to bash anyone's work. I am simply trying to provide much needed files to the community. If you have any questions feel free to ask. Also, I may forget to keep this post updated so please check the downloads page on my website as it will always be maintained.
http://www.peteralfonso.com/p/downloads.html
Downloads: (Most can also be found in ROM Manager)
GRJ06D Stock Rooted ROM (Odexed)
GRJ22 Stock Rooted ROM (Odexed) (DeOdexed)
GRJ90 Stock Rooted ROM (Odexed) (DeOdexed)
GWK74 Stock Rooted ROM (Odexed) (DeOdexed)
GRJ22 Software Images
GRJ22 from GRJ06D OTA
GRJ90 from GRJ22 OTA
GWK74 from GRJ90 OTA
D720SPRKD8 Radio
D720SPRKE5 Radio
D720SPRKE1 Radio
Tethering Fix For Android 2.3.5 ROMs
How To: Root Nexus S 4G
1. Download GWK74 Stock Rooted ROM from above
2. Download CWM Recovery
3. Open a terminal and use the following commands:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
4. Navigate to "recovery" in the bootloader and select it
5. Navigate to "mounts and storage" > "mount USB storage"
6. Place the GWK74 Stock Rooted ROM on your sdcard
7. Navigate to "Unmount" > "+++++Go Back+++++"
8. Navigate to "install zip from sdcard" > "choose zip from sdcard" > choose "GWK74ODEXED.zip" > choose "Yes – Install GWK74ODEXED.zip"
9. Navigate to "reboot system now" and enjoy.
How To: Return Nexus S 4G To Stock
1. Download the GRJ22 Images from above
2. Open a terminal and use the following commands:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Pete did you get a Nexus S 4G? Thought you were on Verizon?
Any ROM development plans?
Sent from my GT-P7510 using XDA Premium App

oxeneers said:
Pete did you get a Nexus S 4G? Thought you were on Verizon?
Any ROM development plans?
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
My work provided me with the Nexus S 4G. I still use my OG Droid and will continue to develop for it. I have successfully built an entire AOSP ROM for the Nexus S 4G and am running it now, not sure what I will release for this device though seeing as how it is for work. Time will tell...right now I am really busy though.

Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone

mikeyinid said:
Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone
Click to expand...
Click to collapse
Really hope I didn't offend anyone, that was not my intentions. Having said that the only way to learn is to try to put things together yourself, compare them to others, etc. I was there not long ago. Keep it up and soon you will know more than you imagined.

You plan on making a ROM for the NS4G? You also mentioned that the ROM's that were out there were not zipaligned. Is the stock version posted above zipaligned?

dalvarez7 said:
You plan on making a ROM for the NS4G? You also mentioned that the ROM's that were out there were not zipaligned. Is the stock version posted above zipaligned?
Click to expand...
Click to collapse
Not sure what my plans are as of now to be honest. You can guarantee anything I release will be zipaligned.

BuglessPete said:
Not sure what my plans are as of now to be honest. You can guarantee anything I release will be zipaligned.
Click to expand...
Click to collapse
I for one would be very grateful if you made us a ROM for the NS4G.

well thanks for this, you are correct on many points except one.. the stock images were released but most people had to work to get them

You are my HERO! Thx man

Looks like the GRJ06D file did not upload right, I will drive to the library tomorrow and reupload. I live in the country where there is no internet lol.

Sweet! Can you post a deodexed rom for the GRJ22? I would love to start changing some of the stock apks for the ones in CM7

obsanity said:
Sweet! Can you post a deodexed rom for the GRJ22? I would love to start changing some of the stock apks for the ones in CM7
Click to expand...
Click to collapse
Sure, once I get some free time I can deodex them.

Im having issues flashing the recovery... Im somewhat new to flashing via adb got it all except recovery. Bootloader is unlocked but when tring via adb I just get error cannot load.. Any suggestions? Thx kindly

Thanks were off to a great start

tandxcstar1 said:
Im having issues flashing the recovery... Im somewhat new to flashing via adb got it all except recovery. Bootloader is unlocked but when tring via adb I just get error cannot load.. Any suggestions? Thx kindly
Click to expand...
Click to collapse
Please disregard this... I figured it out after some trial and error. Was able to flash recovery. One more question... Does this receovery stick or no? I know when I had my epic and had quickboot it would not allow to boot into recovery. thx again for your hard work on this. After reading the 100+ methods of rooting I was pleased to see this. Thx again

edit: nevermind

BuglessPete said:
Why another post for stock files? Well for a few reasons, mainly the lack of quality found amongst the files in similar threads on the web. When I got my Nexus S 4G I took a look around the web, downloaded the stock roms that were floating around and noticed they were very flawed. The update scripts used in them were poorly done, seem to be the result of copy and pasting many update scripts together. The boot.imgs were also flawed, some of them even 8mbs in size, the stock boot.img is 2.8mb. After running them through one of my scripts, I also noticed many apps were not even zipaligned. Needless to say I did not flash these files. I took it upon myself to remake all these files. Stock files are essential to a development phone and can save many people in a sticky situation. Also, I have noticed that the official stock software images have not been released yet, so I went ahead and uploaded those for you all as well. These images include radio, boot, recovery, system, userdata, and bootloader.
Downloads:
GRJ06D Stock Rooted ROM
GRJ22 Stock Rooted ROM
GRJ22 Software Images
GRJ22 from GRJ06D OTA
Please note, this post is not intended to bash anyone's work. I am simply trying to provide much needed files to the community. If you have any questions feel free to ask. Also, I may forget to keep this post updated so please check the downloads page on my website as it will always be maintained.
http://www.peteralfonso.com/p/downloads.html
Please follow me on Twitter for updates.
To return your device to stock, download the GRJ22 Images and use the following commands:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
One more thing, I also noticed that these rooting guides can be made alot simpler. Simply do the following:
1. Download GRJ22 Stock Rooted ROM from above
2. Download CWM Recovery
3. Use the following commands
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
4. Navigate to "recovery" in the bootloader and select it
5. In recovery select "install zip from sdcard" > "choose zip from sdcard" > choose "GRJ22ODEXED.zip" > choose "Yes – Install GRJ22ODEXED.zip"
6. Reboot and thats it.
Click to expand...
Click to collapse
Thank you very much for this.

mikeyinid said:
Yea, I know the stuff I posted is crap I am not a dev and say that in the threads on several occasions. I am very, very glad you posted this, I will post a HUGE link in my thread to this also. Look forward to the awesomeness you will bring to this phone
Click to expand...
Click to collapse
Hey Mike, you did mention that, but my friend, a pioneer you were! I too appreciate all your time and effort and look forward to many wonderful ROMs from you in the future. Thank you for getting us started with our NS4G's!!!!!

Thanks, and your welcome. Guess everyone starts somewhere. Glad I could help in some way...
a2k said:
Hey Mike, you did mention that, but my friend, a pioneer you were! I too appreciate all your time and effort and look forward to many wonderful ROMs from you in the future. Thank you for getting us started with our NS4G's!!!!!
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

How to remove CWM please?

Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help

Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492

1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.

Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse

When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364

Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk

Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!

I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...

Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!

FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.

Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

How to update?

Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium

Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD

Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium

Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2

oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!

udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.

OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium

Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.

OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium

Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.

oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??

oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:

udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.

oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??

udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.

Emergency Loki issues =/

So I work until 7pm tonight and I really need my phone. I flashed the mdl unlocked radios with mobile odin pro but I forgot I was on an international i9505 rom. so nothing is lokied my recovery isn't lokied my kernel isn't lokied anymore. the computers cant download anything here big cause its 1mbps they cap it to that on purpose. I have Odin on the pc here with the drivers. Is it possible to flash a loki kernel or recovery back to this phone without having to go back to stock MDL all over again and rerooting.?

Your phone isnt softbricked correct? If its still working just use this tool it will root and instal recovery for you http://forum.xda-developers.com/showthread.php?t=2297033
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
Your phone isnt softbricked correct? If its still working just use this tool it will root and instal recovery for you http://forum.xda-developers.com/showthread.php?t=2297033
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
my phone is softbricked I keep getting the AT&T unauthorized software message for recovery and booting... can someone here post a .tar AT&T stock kernel. im pretty sure if I odin that it will boot again because it doesn't need to be lokied.. so I can then flash a loki recovery and a loki custom kernel.

I am not sure about all your questions, but have you given any info on the phone you have. i337/i337m--recovery--etc
I seen folks have trouble with Mobile Odin. Don't remember which phone variant they had though.
I don't think radios require loki--?
There are flashable radio zips to install thru recovery not needing Odin
And flashable recovery zips too, TWRP 2.5.0.2

Easton999GS said:
my phone is softbricked I keep getting the AT&T unauthorized software message for recovery and booting... can someone here post a .tar AT&T stock kernel. im pretty sure if I odin that it will boot again because it doesn't need to be lokied.. so I can then flash a loki recovery and a loki custom kernel.
Click to expand...
Click to collapse
I dont think that will work...from what I understand odin omly flashes signed packages...if you take the kernel out and repackage it it will no longer have the same signed package...I could be wrong though
Youd be better off with heimdal...I believe somebody on here has used it succesfully, it requires you have java installed...ill see if I can find that thread
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------
http://forum.xda-developers.com/showthread.php?t=2346806
And obviously use att stock kernel...ill see if I can find a link for that too, this should work with stock kernel...however if it doesnt I am not responsible (I have not tested this method my self)
For the heimdall flash part...instead of recovery -- boot.img or whatever...just use this
Code:
heimdall flash boot boot.img
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
I dont think that will work...from what I understand odin omly flashes signed packages...if you take the kernel out and repackage it it will no longer have the same signed package...I could be wrong though
Youd be better off with heimdal...I believe somebody on here has used it succesfully, it requires you have java installed...ill see if I can find that thread
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------
http://forum.xda-developers.com/showthread.php?t=2346806
And obviously use att stock kernel...ill see if I can find a link for that too, this should work with stock kernel...however if it doesnt I am not responsible (I have not tested this method my self)
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
i think Heimdall requires me to have the factory Odin package. the massive 1.5GB that I cant download here =/ If I can flash stock kernel.img with this and that only I can do it.

Easton999GS said:
i think Heimdall requires me to have the factory Odin package. the massive 1.5GB that I cant download here =/ If I can flash stock kernel.img with this and that only I can do it.
Click to expand...
Click to collapse
No it doesnt I edited my posr, get it follow the steps until the flash part, when you get ther use the command
Code:
heimdall flash boot boot.img
In terminal/cmd prompt...just make sure you have boot.img in the same folder you open up terminal
So put the stock boot.img in a folder, navigate to that folder in windows explorer, hold shift and right click select open cmd promp here, follow the guide I linked above and when it comes time to flash use the code I provided in this post. That SHOULD work...keyword here is SHOULD im extracting the stock kernel from the mdl odin package now, ill upload it for you
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

rugmankc said:
I am not sure about all your questions, but have you given any info on the phone you have. i337/i337m--recovery--etc
Deleted
Oops, missed the posts after your first one, sorry--
Click to expand...
Click to collapse

DynamicBIts said:
Edited by mg2195...credit for guide goes to DynamicBlts
Download and extract Heimdall
Download MDL Stock Kernel
Place boot.img in that extracted folder
Navigate tpo that folder in windows explorer, hold shift and right click. choose open command window here
Verify Compatibility
With phone off and no USB cable connected, hold volume down and power. When you feel the vibration, release power, but not volume down.
Once you see the warning screen, release volume down.
Press volume up once to continue.
Connect the USB cable.
Type the following command:
Code:
sudo heimdall detect
If you don't see "Device detected", something isn't working correctly. Don't continue any further until you resolve that issue.
Code:
heimdall flash --boot boot.img
Click to expand...
Click to collapse
That should work... gotta go now, ill be back in a few hours if you have issues

mg2195 said:
No it doesnt I edited my posr, get it follow the steps until the flash part, when you get ther use the command
Code:
heimdall flash boot boot.img
In terminal/cmd prompt...just make sure you have boot.img in the same folder you open up terminal
So put the stock boot.img in a folder, navigate to that folder in windows explorer, hold shift and right click select open cmd promp here, follow the guide I linked above and when it comes time to flash use the code I provided in this post. That SHOULD work...keyword here is SHOULD im extracting the stock kernel from the mdl odin package now, ill upload it for you
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
thank you so much I appreciate it a ton. Hopefully it at least boots in general. I don't care if I have issues I can fix it from therem, Im on Omega 9 rom so lets see how this goes.

Easton999GS said:
thank you so much I appreciate it a ton. Hopefully it at least boots in general. I don't care if I have issues I can fix it from therem, Im on Omega 9 rom so lets see how this goes.
Click to expand...
Click to collapse
I made you a one click, just make sure you have java installed
when you first run it you will get a pop up about drivers no being installed follow the on screen instructions (under options click list all, choose msm8960)
***please note, once you use heimdall, you will no longer be able to use odin on that specific usb port, it installs special drivers to the current port the phone is plugged into that odin doesnt recognize...keep this in mind if trying to odin in the future...just use a differnt port for odin**
than just click flash, it appear to work for me however i flashed it on a working stock rom
SGS4 Stock Kernel one click