yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] NaughtyBot:
Okay, so I took a deep, nervous breath and gave this a shot. For the most part...success! Flash counter is reset, phone is unrooted and it looks like everything is back to stock (as far as I can tell anyway).

There were just a few issues. The Bell radios would not flash, got about half-way through and failed every time. Everything else went like, well, clockwork. Shortly after I rooted the phone, I used cellunlocker.net to carrier unlock the phone, don't know if that had anything to do with it.

Also, the part using adb was a bit tricky (especially given that I didn't know what adb was to begin with). I found that I had to unplug the phone a couple of times before adb would correctly recognize it. Also a few driver issues. I don't know if it helped but in CWM I mounted everything except for the USB Storage. Once it recognized the device, it installed recovery.img just fine.

Had to try it a couple of times. The first time, I reset the flash counter before I flashed the stock Bell kernel. I figured that since the Bell kernel was stock, it wouldn't trip the flash counter (but it did). The second go-round, things went fine.

Here were my steps: installed CWM (didn't have it on there at first), flashed everything but recovery (used pda-odin-bell-stock-system-boot.zip, not pda-odin-bell-stock.zip), reset the flash counter a la Braway, and finally used adb to reinstall stock recovery. Oh, by the way, make sure phone is in USB debugging mode before flashing with Odin. You'll need to turn if off a time or two to copy some things to your SD card, so remember to turn it back on afterwards to use Odin.

One small "gotcha"...I found that, after you remove root from the phone, you're stuck with Superuser in your apps (won't uninstall, period). To get rid of it, I had to (finally) restore my phone. That meant that I had to redownload my apps and reconfigure some things but it's a sure way to get rid of all those little root leftovers that are still hiding on your phone after unroot. For those who are resetting to stock for warranty purposes, you'll probably want to do that anyway.

So, there ya go. Thanks to marshals, braway, Da_G, baybal for starting the thread, and especially to MrJoran (also from this fair island I call home!) for all the hard work.

By the way, if you make any changes that might allow flashing of the Bell radios, I'd be interested to hear.

Peace out guys!:D
[AT&T Samsung Galaxy Note I717] MrJoran:
Thanks for the feedback, NaughtyBot! Also, so nice to see a Newfoundlander! I was surprised when the first thanks I received on this project was from Paradise :)

I'll look into doing something different with the stock radio, hopefully to make it work better. Also, pterry30 is working on making the radio/modem into a CWM flashable zip, so he may have better luck than I did.

Sorry about the stuck Superuser app. I thought I removed it completely from the ROM but I guess I missed something. I'll look into it and fix the download.

With regards to what trips the flash counter, its not so much what your flashing (e.g.: radio, system, recovery etc). The only things that flash through Odin without tripping the counter are packages signed by Samsung and system images. Because my tar with the system image also includes boot.img, its my understanding that it will trip the flash counter.

Thanks for taking a chance on this. It's my first ever project and I'm very glad to hear it was successful. You have no idea how much I appreciate what you've done! Let me know if there is anything else I can do for you!
[Galaxy S II Q&A, Help & Troubleshooting] dahem:
HI all

I started having a problem with the external speaker three days ago. It stopped working three days ago for about half a day. Then suddenly worked again. Yesterday night the speaker stopped working again and has been so since then!

I contacted Samsung support in the US and was not helped at all. I was directed to the UK support. Is there anyway that I can get my phone fixed here in the US. Sending the phone overseas to get fixed is quite hard at this moment. There is also a good chance that the origin of the phone is not the UK. I bought it from a small store and was told that the phone came from the UK.

Any help is highly appreciated!

Thanks
[General Accessories] gumdoc:
Got my 3800 mAh Trexcell battery and loving the extra power...but not loving the fact that I can't seem to find a case for it. Anyone seen anything that would fit? Trexcell makes one for the Epic 4G but I can't seem to find one for the Galaxy Nexus yet.

Thanks for any help.
[Thinkpad Tablet General] jlove:
Hello Everyone,

I do have a Thinkpad Tablet and cant root. So the only way would be nvflash.

But we need the SBK Key.

There is a new SBKDump tool from Androidroot.mobi.

Can someone with root test the tool? Maybe this is the tool we all have been waiting for.

http://androidroot.mobi/2012/04/01/sbkdump-v1-0/
[Thinkpad Tablet General] Koshu:
I was doubtful because of the date, the tool was released. Well tried it anyway just to make sure ;)

SBK Dumper v1.0
by androidroot.mobi
----------------------------

Opening AES Engine...done
Checking AES fuse state...locked - good!
Powercycling fuses (please wait)...done.
Checking AES fuse state...unlocked - excellent!
Memory mapping into fuse area...done!
Calculating SBK offset...0xeeb81c00
Reading SBK (this could take a moment)...
Your SBK: 0xAPRIL FOOLS!!
Closing AES Engine...done

btw, have you tried the new rooting method for OTA2 ?
[Thinkpad Tablet General] O_G:
Moved To General​

As the first post contains no development this should be in the general section​
[Thinkpad Tablet General] jlove:
@koshu

thank you for the try. it was to good to be true.

I did try all rooting methods. The main problem i have is that mkdir and other commands give me a "file doesnt exist" error. Will check again and make a new post. Maybe someone else can help.

Actually i did have root but after updating with WE_089 i lost root. Maybe someone can help me out. I did have Root keeper installed but that doesnt work anymore.

thanks,

jlove
[AT&T Samsung Galaxy Note I717] Thremix:
Some one posted a picture of some sort of grip handle for the note, or small tablets... I was looking for it :(
[AT&T Samsung Galaxy Note I717] flex3269:
Are you talking about egrips? I put them on my note they work great.
[AT&T Samsung Galaxy Note I717] Restroom:
I wonder if anyone's thought to measure and compare component temperatures with various covers like this versus stock.

Sent from an Ohio-class SSBN in a bathtub using XDA
[AT&T Samsung Galaxy Note I717] SKyRocKeting727:
http://xdaforums.com/showthread.php?t=1527857

This?

-Once you go NOTE, you'd say 4 inches a Joke
[AT&T Samsung Galaxy Note I717] jietzer:
http://flygrip.com/

I think its over priced but it does work well , and i still use it a 2 months later.
[Barnes & Noble Nook Tablet] jsp254:
Can someone tell me how to claim the unused storage space on the 16gb nook? Is there more than one method? Can I adjust the amount used by the system and howmuch for storage? Can I do a "raid" like setup combining my internal and external?

If someone could point me in the right direction or even with the correct search terms I would be very grateful.
[Barnes & Noble Nook Tablet] CRE:
You've missed it. There are a couple ways.

http://xdaforums.com/showthread.php?p=24419790

http://xdaforums.com/showthread.php?t=1531120

RAID? Um, no.... and I don't think it would be very reliable or fast.
[Barnes & Noble Nook Tablet] albertwertz:
i would just take it back to barnes and noble and have them repartition it and reinstall root or rom. works fine.
[General Questions and Answers] SKAYDOU7:
hi, i was not able to find an accurate answer, so any help would be appreciated.

i have an unlocked sensation 4g originally locked to Bell canada, i rooted it without flashing a new rom, now i can't get the ICS 4 update, it just won't install, i read that i have to unroot, but first of all, will it lock my phone to Bell? And how can i tell which RUU should i get especially that i am not using it in CANADA.

Thanks in advance.
[Samsung Galaxy Nexus] smooth4lyfe:
I am a little bit concerned.

I have a GSM Unlocked Galaxy Nexus, and I know ICS 4.0.4 was released Mar 29. A lot of people have received their updates via OTA, but I have still not received mine. Every time I click "Check Now" on the software update, it tells me I am currently on the current version 4.0.2, which I know is not true.

I am pretty sure I have stock YAKJU firmware, but how I got was from flashing. At first my firmware was not Yakju, but from this site I was able to flash my phone and get Yakju. For some reason I am thinking what I flashed is not Google's Yakju but something else, even though the poster said it was stock.

I have been waiting for a long time, and still nothing, I really do not want to do it manually either, because I know it will erase everything on my phone.

My baseband is 19250XXKK6

Any suggestions? I mean I could wait longer, but idk when or if it will even update

P.S.

I know this is my first post, but I will try and be as active as I can on this site

Thanks!
[Samsung Galaxy Nexus] Vangelis13:
Why wait (I don't know how / if you'll get the update, you might not)? Flash either the 4.0.4 factory image or a 4.0.4 rom and you're done.
[Samsung Galaxy Nexus] luftrofl:
"Check Now" asks "Is *my* phone scheduled be updated?" rather than "Is an update available?"

OTA update are not all at once. I got mine yesterday- just be patient. It's not a huge difference, anyway, so just chill and don't think about it. It's not good to get so worried about a software update :p
[Samsung Galaxy Nexus] smooth4lyfe:
I do not mind flashing 4.0.4 rom, but I have some questions

1. I do not want a custom rom because I still want OTA updates...is there the stock 4.0.4 rom I can flash? (Link?)

2. Will it erase all my stuff? (Not a big problem if it does, Ill back everything up
[Samsung Galaxy Nexus] anton2009:
Have you tried this? Also, this app will tell you if you have yakju or something else. :)
[Samsung Galaxy Nexus] smooth4lyfe:
lol I know I just like having the most recent/updated stuff...maybe I will wait if its not that big of a difference, but because I flashed mine to YAKJU, thats why I am worried if I will even get the update or not
[Samsung Galaxy Nexus] smooth4lyfe:
Yes I have checked with that app and it says I have YAKJU
[Samsung Galaxy Nexus] anton2009:
Ah sorry. Weird link. I meant to link to this.
[Samsung Galaxy Nexus] yeahyeahright:
Hey Guys,

I'm riding on this thread with the same question.

I was previously running Yakjuwx and got fedup of waiting for Samsung to throw me a bone so I flashed to Yakju the other day.

I did, however, flashed it to

4.0.2 instead of 4.0.4, and then re-locked the bootloader

again. My reason for doing so is to see if Google will officially recognize my device as a stock Yakju and offer an upgrade to 4.0.4 from there without me having to do a manual flash...if it allows me an official update I can safely assume that from here on out, Google's got my back for subsequent updates rather than having to do a flash everytime an update comes along.

Till now I've not received any news via OTA though. I've

cleared the data of my Google Service Framework and restarted the phone a few times

, but I'm still at 4.0.2.

Am wondering if I did something wrong. I've attached a screencap of my GNEX for reference. If you can't see, it:

Android Version

4.0.2

Baseband Version

I9250XXKK6

Kernel Version

3.0.8-gaaa2611

android-build@apa 28 #1

Build Number

ICL53F

Anyone able to offer any assistance as to how I can "force" Google to give me an OTA?
[Samsung Galaxy Nexus] jasg001:
2 coppers: 4.0.4 is a hell of a lot better than 4.0.2.

Screen rotation lag is fixed

Faster overall response times, esp with the stock browser

Extremely stable (random reboots)

I actually ran stock rogers 4.0.2 and refused to root and one day out of nowhere my gnex started bootlooping. Unlocked, cwm, 4.0.4 factory , rooted + power apps and I'm not looking back. This thing is a monster now lol
[Samsung Galaxy Nexus] yeahyeahright:
Also, would the serial number along with the bootloader being relocked be the reason why Google isn't updating my phone?

Attaching this information as well:
[Samsung Galaxy Nexus] albert95:
I also have yakju on ICL53F tried that framework clear method - no luck - it seems that people with ICL53F have trouble getting the update
[Samsung Galaxy Nexus] martonikaj:
As covered previously in other threads, it seems as though the original IMM76D 4.0.4 OTA has been stopped because it causes radio drop-out problems with the screen off. Since the new OTA IMM76I has been pushed to fix these issues, we assume that there will be an OTA for 4.0.2 people straight to IMM76I 4.0.4.

You can always manually apply IMM76D then IMM76I if you want.
[Samsung Galaxy Nexus] efrant:
Google rolls out the updates over a period of months. Yes, MONTHS. So, you could get it immediately, or you could get it in a few weeks from now. Now, you have two choices: 1) wait for Google to push it to your device; or 2) update it yourself by reading this thread.

By the way, as others have mentioned, locking or unlocking your bootloader has no impact on the OTA notification or update, but by locking it, you have just made your life more difficult.
[Samsung Galaxy Nexus] cyrusxs:
Haha I know the feeling of waiting. I tried to manually flash 4.0.4 and ended up with an infinite boot loop animation. Something must have obviously gone wrong, but I was able to get 4.0.2 back on it and get up and running.

I'm now trying to just patiently wait for 4.0.4, but it's tough. I am very wary of trying to flash 4.0.4 on my handset again just because I don't want to end up with the infinite boot loop again. I check every night for a new update, do the checkin thing on the dialer, but no luck.

I am just hoping that I didn't screw anything up when I unsuccessfully tried to flash 4.0.4 that has somehow put my handset "out of favor" with google in terms of receiving the OTA update.
[Samsung Galaxy Nexus] efrant:
That's because you didn't use my guide here. ;)

That does nothing. Assuming you are connected to Google's services (i.e., blue bars instead of gray), you'll get notified when your number comes up.

I doubt you did.
[Samsung Galaxy Nexus] yeahyeahright:
Thanks Efrant.

I'm looking to take the more natural route cause I'm not much of a modder, the whole idea of me sticking to stock is to debunk the illusion a number of non-Android users have (including my friends) that they need to root and mod their phones in order to get it to perform adequately like iOS, and I like to prove that they don't have to, and that stock Android caters perfectly fine to the majority.

When you mean locking made things more difficult though, are you referring that it means I will have to redo the whole unlocking thing again if I wanted to perform a mod, or do you mean once I re-locked the phone, it can no longer be unlocked via the original method anymore? Cause if it's the former, I'm not that much concern as mentioned in my first para, but if it's the latter then..oops. =\
[Samsung Galaxy Nexus] efrant:
Yes, I was referring to the former. The only thing that an unlocked bootloader affects is your ability to use fastboot commands. It does not mean you are modded, or rooted, or not stock. You ARE stock, you are NOT rooted, and there are no mods. But, you do have the ability to back up your data properly, you do have the ability to recovery any data in case something happens to your device, and a few other worthwhile features which you don't have if your bootloader is locked.

Now, you could always unlock if you need to, but that defeats the purpose, as everytime you unlock your bootloader, it does a complete wipe of your device, including /sdcard.

As an example, say you had some treasured photos on your device, which you have yet to back up to the cloud or wherever, and your locked-bootloader, unmodded, unrooted phone goes into a bootloop (which has happened). How are you going to get those photos off your device? You can't -- you are screwed. It order to retrieve them you need an unlocked bootloader... but to unlock your bootloader will wipe everything... See where I'm going here... Catch-22. With an unlocked bootloader, there are ways to recover those files.
[Samsung Galaxy Nexus] yeahyeahright:
Ah I see, thanks for the advice! I see the problems you highlighted regarding unlocking the bootloader again, I didn't have that problem cause I backed up my photos via dropbox auto upload and did a second backup, including 3rd party apps and data via MyBackup Pro, then unloaded the backup via usb onto my computer.

Guess since I've locked it for now there's no point unlocking it again, I'll wait until Google decides to drop me a bone and get me up to 4.0.4 then, for now 4.0.2's still a blast.

Thanks!
[Samsung Galaxy Nexus] efrant:
Yeah, you knew that your data was going to be erased, so you used MyBackup. What happens in 2 months when you have more data on your device, and your device decides not to boot past the boot animation (not likely, but certainly possible)? Unless you back-up your app data and contents of your /sdcard automatically (like you do your photos) or on a daily basis, you will lose something. Just sayin'.

That's why I recommend to everyone to unlock the bootloader as soon as you take your device out of the box for the first time, even before you boot into the OS. Boot into the fastboot mode, unlock and be done with it. Never worry about it again. Even if you never plan to root or mod or install custom roms. It may save that one piece of data that you really wanted to keep, but forgot to backup. :)
[Samsung Galaxy Nexus] yeahyeahright:
Ah I see where the advantage comes into play. Thanks for the advice. Will look into unlocking and see if I've got time to spare tonight to do it again and leave it as such.
[Samsung Galaxy Nexus] cyrusxs:
Haha, dagnabbit! I didn't know you had that reference out there :(

Anyway, yes I do have blue bars, and I got a notification this morning for an update - BUT (I have the worst luck, I tell you) - when I tried to run the update, it started with the blue orb circling an android, and then it stopped, went to a screen with the android lying flat on it's back with a red exclamation mark.

It sat on that screen for about a couple minutes, then rebooted. Once it had booted up, I went into the system info, and it was still on 4.0.2. Booooo :(

I haven't received another notification for an update yet.

Something to note - not sure if it matters or not - but whenever I reboot, I first get the screen with "Google" written in white and the unlocked padlock at the bottom. After that, it goes into the boot animation. During this animation, there's the iteration of colors that take place, and during this iteration, there's a flicker at the end of each iteration. Kind of like an orange flicker. Again, not sure if it means anything. It only happened once I botched my attempt to update the device to 4.0.4, and went back to 4.0.2.

I'm waiting for another notification - don't know if the outcome will be any different. I might have to bite the bullet and try a manual update if it doesn't, and follow the reference you pointed me to from your earlier post in this thread.

Why is the universe plotting against me? :)
[Samsung Galaxy Nexus] efrant:
This usually means you do not have the right stock recovery installed. If you are on 4.0.2, you need to have the 4.0.2 stock recovery.
[Samsung Galaxy Nexus] cyrusxs:
Sigh...so I guess a manual update is the only recourse I have left?
[Samsung Galaxy Nexus] efrant:
Just flash the right recovery and the update will install ota.
[Samsung Galaxy Nexus] cyrusxs:
Sorry, I still consider myself a noob when it comes to flashing images on to my device.

Just to make sure I understand correctly, do I boot up in fastboot mode (vol up + vol down + power) and then run only this command?:

fastboot flash recovery recovery.img

And I get the recover.img file after unzipping the .tgz file off Google's site using 7-zip, right?
[Samsung Galaxy Nexus] efrant:
Correct! Make sure you use the 4.0.2 image if you are currently running 4.0.2.

The next time you get the notification, the update will install automatically.
[Samsung Galaxy Nexus] cyrusxs:
Ok cool. Yes, I am on the 4.0.2 (ICL53F) image, so I'll look for the respective .tgz file. Do I need to back up anything before I do this? Will flashing the recovery image cause me to lose any data?

Just curious, what exactly is a recovery image used for?

UPDATE: I just went to the Galaxy Nexus Factory Images page here and it looks like the 4.0.2 factory image for yakju has been replaced with the 4.0.4 version. Any idea how I could get the 4.0.2 image?
[Samsung Galaxy Nexus] efrant:
No need to back anything up.

The recovery is like a mini ROM with limited functionality. It allows you to "recover" you main ROM.

Wow, you are right. I just checked and it's not there. I'll upload it shortly to this post.

EDIT: attached!
[Samsung Galaxy Nexus] cyrusxs:
Awesome! Thanks efrant!

Last question - as you remember, the last time I tried a manual update, I got stuck in the infinite boot loop. I know this time around, I'm not flashing the entire image or anything, but is there a risk of me encountering that again if I flash just the recovery image?
[Samsung Galaxy Nexus] efrant:
None at all.
[Samsung Galaxy Nexus] cyrusxs:
Ok, so I flashed the recovery image and you were right, no infinite boot loop (yay!).

So, I've got blue bars, and now I anxiously await the OTA update once more. Wish me luck!

Thanks again for all your help.
[Samsung Galaxy Nexus] paulosilva8200:
honestly guys, is not all 4.0.2 devices that needs updates, i have an galaxy nexus i9250xxkk6 build icl53f and there is no problem with the battery, only with missed call, that for aperant reason does not shown sometimes

---------- Post added at 07:50 AM ---------- Previous post was at 07:37 AM ----------

i will never flash my phone incase of warranty, its google job to send the ota in a simple way, i have no idea why they dont place the updates in the market, would be more easy, name,model with update, google is really doing loads of mistakes in this last few years, they promote,they build without trying, instead of giving dates for the realise of new versions, they should test it, and then sell it, i cant even send an contact by sms v card by goggle phones when my grandmother 1990 nokia can, and honestly, first 3 months i was into the apps, now, honestly, i am not a kid that needs to show the phone to other person and tell them that my phone can talk to me, when half the time cant even recall my voice. make phones for people that are grown up, and make it easy, to many bugs and to many stupid apps, i delete 90% of my apps, they a waste of space and i use it once in a month only to show people what the phone can do, stupidddddddddddddd to be honest, make it work in a professional way, i use the phone to work, still i find the keys in a stupid way, and the word rec should be not only the the sms, and in everything we type.
[Samsung Galaxy Nexus] yeahyeahright:
Need help confirming. I have a lock bootloader, and I went into Bootloader mode, then selected "Recovery Mode" and when it restarted I was lead to an image of the same 3D android character lying down, torso opened, but with a red triangle exclamation mark above it.

Does this mean I am on stock recovery or does it mean I screwed up somewhere?

If anyone last recalled, I flashed from Yakjuwx to Yakju stock 4.0.2 with hopes that if I did things correctly, Google will recognize my phone and send me a 4.0.4 OTA update, but so far nothing....am unsure if I flashed it correctly or made a booboo.
[Samsung Galaxy Nexus] efrant:
Yes, the android on its back with the red exclamation point is the stock recovery. Assuming you flashed all the images (including the stock recovery) when you switched to yakju, you will be fine with any future OTA updates.
[Samsung Galaxy Nexus] yeahyeahright:
What a relief! About 5 minutes before I was gonna back up and do a flash...Package has arrived! =)