Related
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
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.
OTA2 US was released today. Here is the update.
Would it be possible to make a version that can be flashed in CWM that keeps root and doesn't do the system verification?
Would you provide the full name of the update, please? I'm trying to save it properly for future reference. Thanks.
toenail_flicker said:
Would you provide the full name of the update, please? I'm trying to save it properly for future reference. Thanks.
Click to expand...
Click to collapse
I don't know the full name, it downloaded as update.zip on my TpT.
Okay, usually it sits in the download folder with its full name as the file name. Thanks anyway.
agree CWR removal
or, at least a way to restore the factory recovery partition, because following the steps in the CWM thread doesn't work....hitting vol+ or even adb reboot recovery, will not take you to the recovery area after you use the dd if=/recovery-from-boot.p
it places a VERY tiny file in the recovery partition and in no way restores it to the factory functionality.
Seems to be this one from here:
http://download.lenovo.com/slates/think/tablet1
ThinkPadTablet_A310_02_0039_0086_US.zip
Thanks, but I'm not finding any US files there, only WE. If your post is only for the file name, thanks, that does help.
toenail_flicker said:
Thanks, but I'm not finding any US files there, only WE. If your post is only for the file name, thanks, that does help.
Click to expand...
Click to collapse
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
That does work
Has anyone updated using ClockworkMod Recovery or is it necessary to flash the original recovery? Also has anyone who updated and used OTA Rootkeeper tried flashing ClockworkMod Recovery after the update? Does it still work?
Perfect. Thanks.
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!
Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol
Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...
Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip
If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE
sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.
With the stock rom, can I just flash it using a custom recovery?
yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.
Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download
I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA
Could you post the stock recovery image of the 4.4.2 ROM, please?
ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.
Thanks anyway. It'd be awesome if someone who has it posted. Anyone?
Yep, the update just popped up. How do you capture it by the way? What's the path?
devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.
samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...
samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?
There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed