yashsingh1/xdaforums huggingface dataset:
[AT&T LG Optimus G] slicingtaco:
Your talking about "redraws" it has to do with the launcher (TouchWiz) or in some cases, RAM.
[AT&T LG Optimus G] whoamanwtf:
Where as I do not use the stock launcher, I use NOVA and well we have 2 gigs of ram... Plus mine have certainly been full reboots and the G2x did this same thing... we need to just hope for am unlockedbootloader.
[AT&T LG Optimus G] hegemytouch:
I have had 1 random reboot so far. Hope it doesn't happen again.
[AT&T LG Optimus G] mbonus:
I haven't seen any on my device. 11 days. Stock launcher.
[AT&T LG Optimus G] *Omnipresent*:
All stock since Nov. 2nd. Zero reboots.
[AT&T LG Optimus G] whoamanwtf:
I returned my device for another, haven't seen a reboot so far.
[AT&T LG Optimus G] niclz:
I've had reboots as well. Around 4 times now and purchased the phone nov. 3. a couple times it was when the phone is just sitting there on stand by. one time it was while posting a picture on instagram. Another was taking a picture and looking at the photos... and when it does re start, it will restart 2 or 3 times at a time, like i see the lg logo 3 times, then finally the "rethink possible" logo, then the phone boots up and while or just after my media scanning of my sdcard finishes, it will automatically restart again... and this happens 2 or 3 times. for some reason I feel like it has something to do with me 64gb sd card but am not sure, i used to think it had something to do with eco mode but phone has restarted while it wasnt activated too... dunno how to fix, hopefully an update will come for a fix :/
[AT&T LG Optimus G] g4m8i7:
Same here. Must have been a hardware thing.
[AT&T LG Optimus G] vanlon:
I'm going to have to send mine in for warranty too, put a reboot logger on it and it's around 4-5 times per day. I should probably unroot it before I send it in I guess.
[Nexus 4 Q&A, Help & Troubleshooting] doubleojon:
I, along with many others, will be cancelling my contract and porting my number for the Nexus 4. After checking the Verizon site and reading about the ETF, it directed me to a list of "advanced" phones, which seemed to include every smartphone- except the Galaxy Nexus. Weird.

Anyway, what I'm wondering is what can I expect in terms of an etf if I purchased my Gnex the day it came out, and in doing so, renewed my contract?
[Nexus 4 Q&A, Help & Troubleshooting] scott62185:
They quoted me $250
[Nexus S Android Development] WugFresh:
Unlocking, rooting, relocking and unrooting simplified! (and much more!)

VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.

~ my goal for this project is make the entire process as smooth and simple as possible ~

Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/

Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/

More information & Download Links: http://www.wugfresh.com/nrt/

Changelog: http://www.wugfresh.com/nrt/changelog/

Enjoy! ^_^

{{ WugFresh }}
[Nexus S Android Development] WugFresh:
Root with NRT (Video by Rootjunky)

[YOUTUBE]K25n7i6zgb0[/YOUTUBE]

More videos here: http://www.wugfresh.com/videos/
[Nexus S Android Development] WugFresh:
Big thanks to ej8989 for asking me to post this here for the benefit of Nexus S owners. This program supports all the Nexus devices but I had only posted it the Nexus7 thread.. Now I will maintain multiple threads although its the same program.

I will do my best to keep this program updated to support the latest builds for as long as possible. Cheers. ^_^

{{ WugFresh }}
[Nexus S Android Development] ej8989:
updater seems to freeze after downloading (v1.5.4)
[Nexus S Android Development] WugFresh:
Right.. Sorry about that, I forgot to add that information to my site.

The updater in v1.5.4 had that problem if the toolkit was in a path with spaces in it. Just replace the Wug_Updater.exe in the toolkit directory with the new one from v1.5.5: http://wug.rootxs.com/NRT_extras/Wug_Updater.exe

Then try again, it should work without problems. it was a catch 22 for me.. I couldn't auto update the updater..lol, but now its good :)

{{ WugFresh }}
[Nexus S Android Development] ej8989:
Worked. thanks!

Just updated my custom recovery flawlessly using this tool. Took only about 5 seconds! lol

It's really fast and reliable. Great work :good:
[Nexus S Android Development] WugFresh:
Great. Thanks! :)

{{ WugFresh }}
[Nexus S Android Development] urfase:
After trying for over an hour and going through all three driver methods I cannot get the NRT to connect to my phone. When the phone is rebooted into Fastboot, the volume keys do not work for changing selection, and the computer does not detect anything plugged in via USB suggesting the phone freezes whenever it it put into Fastboot mode.

Model is a Nexus S i9020a running 4.1.1 on JRO03E.

This is on an ASUS K53S notebook running Windows 7 x64.
[Nexus S Android Development] WugFresh:
I had something similar happen to me on one machine. What I did to fix it was start at the beginning of the guide.. i.e uninstalling everything completely and rebooting my computer. Then I used driver solution#3 (RAW drivers), with a different usb port. The key is rebooting your computer after uninstalling everything.

If it persistently doesn't work, maybe I can help you out through gchat sometime.. not tonight though, I am still cranking out this next toolkit release.

{{ WugFresh }}
[Nexus S Android Development] urfase:
Yeah I did the uninstalls and reboots. Followed the guide exactly. After it didn't work I even took the next step in killing all unnecessary system processes and disabling antivirus.

I'm going to get another notebook that's been freshly formatted and try it again next weekend.
[Nexus S Android Development] WugFresh:
Maybe you could try forcing the "Naked Drivers" by 1wayjonny. When you use driver solution #3 windows just scans the sub-directories of the RAW_Driver folder in the toolkit and chooses the ones it thinks are the "best".

Use this longer path instead to force it to check only in the folder which contains those universal drivers:

[NRT_TOOLKIT_DIRECTORY]\data\Drivers\RAW_Drivers\NAKED_Drivers

Let me know if that works. Cheers.

{{ WugFresh }}
[Nexus S Android Development] szk5230:
Nice job ！ thanks~

Could you make it work on nexus 7 (android 4.2 rom )?
[Nexus S Android Development] WugFresh:
I am working very hard on a big update (v1.6) which will support that and more.

{{ WugFresh }}
[Nexus S Android Development] RealPariah:
Your website WugFresh.com is having DNS issues on the East Coast US. It resolves to Cloudflare DNS error page which states either you haven't logged in or if you have it is taking time to spread the DNS info [which is prolly not the case given you are found on google search meaning its been up for a bit] or that you changed your hosting provider and their DNS records do not correctly point to your domain.

---Error Page---

You've requested a page on a website (www.wugfresh.com) that is on the CloudFlare network. Unfortunately, CloudFlare is currently unable to resolve your requested domain (www.wugfresh.com). There are two potential causes of this:

Most likely: if the owner just signed up for CloudFlare it can take a few minutes for the website's information to be distributed to our global network. Check back in about 5 minutes and the site should be up and running and enjoying all the benefits of CloudFlare.

Less likely: something is wrong with this site's configuration. Usually this happens when accounts have been signed up with a partner organization (e.g., a hosting provider) and the provider's DNS fails.

Timestamp: Wed, 21 Nov 2012 05:50:32 -800

Your IP address: Cleansed for privacy

Requested URL: www.wugfresh.com/dev/nexus-root-toolkit/

Error reference number: 1001

Server ID: FL_16F2

Process ID: PID_1353505832.200-2-64592275

User-Agent: Cleansed for privacy I use Chrome
[Nexus S Android Development] WugFresh:
Yeah, sorry about that. I switched my site over to a dedicated IP to deal with increased web traffic and some of the new toolkit communications coming in v1.6, so the DNS needed to propagate. I still have more work to do on v1.6 but my site should be back up and running now. Hopefully the dedicated IP will help me resolve some of the web hosting issues I have been struggling with.

Again, sorry for the inconvenience and lack of communication during the temporary outage. I just was busy traveling for Thanksgiving plans.

Cheers,

{{ WugFresh }}
[Nexus S Android Development] noobiekins:
This program looks to be something VERY useful, however, it seems to be a little too late for it to pick up steam, but nice to see support for dying devices
[Nexus S Android Development] rodem77:
Thankyou for Nexus S thread!

Now I've 4.1.2, if i change to a custom rom, your tool will continue to work for flashing something or to "back to stock" function or it work only on official nexus rom?
[Nexus S Android Development] WugFresh:
I have been coding like crazy and I am releasing a major update by Saturday that will support all the latest Nexus devices and will make updating it in the future nearly instantaneous. Your comment is just frustrating.

{{ WugFresh }}
[Nexus S Android Development] WugFresh:
Yes, it will work just the same on a custom ROM. :)

{{ WugFresh }}
[Nexus S Android Development] rodem77:
This tool support ALSO Nexus S but it support ALL new and old nexus devices:

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

Take a look on Views and Reply, he opened ALSO a Nexus S thread just to better support us.
[Nexus S Android Development] szk5230:
oh, good working~

i waiting for it ^_^
[Nexus S Android Development] 1024k:
This method wipe also the USB storage or only internal?
[Nexus S Android Development] rodem77:
Hi, if you have to unlock your phone (and later root), yes, it will wipe everything so you need to do a backup of your important documents.

Consider that without root you can't easily save all your app data (for example you may lose all you savegame ar some app configuration). Before root you can backup everything only using ADB method.
[Nexus S Android Development] jorim.tielemans:
Is Android 4.2.1 by greenblue also supported?
[Nexus S Android Development] rodem77:
Hi, a lot of functions of this tool work also on custom rom (I personally asked this to Wugfresh in his nexus 7 thread some weeks ago) so you can use it to flash everything, to use a temporary custom recovery, to backup etc...
[Nexus S Android Development] WugFresh:
v1.6.1 is up.

{{ WugFresh }}
[Nexus S Android Development] tankhun:
I can't use any function in program

it always stop at "Fastboot device was not found" screen

(I'm already install driver)

Sorry for my poor English.
[Nexus S Android Development] rodem77:
When you installed drivers did you also check correct driver installation? The "step 3" full driver test? And a second question: did you activated the usb debug on your device? Check in system setting --> developer.
[Nexus S Android Development] tankhun:
reply

Yes I check full driver test and it also stop at "Fastboot device was not found" screen

For debugging, My device's status is BOOTLOOP and I can't check. but I remember its enabled

Please lead me to the correct way.

Sorry for my poor English.
[Nexus S Android Development] rodem77:
Your english is ok, so now you cant use your nexus s because it is in bootloop... specify all operations that you did from beginning, did you start from a stock rom and kernel? After this what did you do? What toolkit function did you used? Please give all details.

You can also try to change USB port using the ones on the back of your PC (if it is a desktop) to se if it finally find your phone... In the toolkit there are also emergency tool (back to stock --> status bootloop) but I don't know if you have a backp of all your data...
[Nexus S Android Development] tankhun:
reply

Ok...I'm using CM10 nightly with their kernel and CWM recovery ver.6

That day I flashed a new version of CM10 and everything's ok.

After that, I tried to flash CWM touch by ROM TOOLBOX PRO APP and it has some error.

So I flashed my current version of CWM(ver.6) by using ROM MANAGER APP and the message show everything complete.

The last one, I tried to change Wifi icon by ROM TOOLBOX PRO APP and it need to restart my device.

After restart it is in bootloop......

I intend to flash CM10 again in recovery for solve the problem.

I pulled the battery and used vol.up+power button start my device to bootloader screen

BUT in bootloader screen I can't use vol.up/down button to select recovery menu (power button still work)

I do that again and again and again but result is the same.

For toolkit, I already try "back to stock --> status bootloop" function but it also stop at "Fastboot device was not found" screen.

Thank you very much for your attention.
[Nexus S Android Development] rodem77:
Ok, the problem didn't come from the toolkit... Try this manual method:

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

If you don't have experience with fastboot method, before read also this thread:

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

It is about nexus 7 (but you need to do the same for nexus s) and explain very well how to install sdk and how to check if fastboot or adb can see your phone. If you can't see your phone I can't help you anymore, if you can see your phone from your PC come back to ale.landra guide for nexus s and follow the fastboot command.
[Nexus S Android Development] ej8989:
Offtopic: Can you share the windows theme you're using? Thanks :cyclops:
[Nexus S Android Development] nanny07:
it's called Windows 8 :)
[Nexus S Android Development] WugFresh:
v1.6.2 is up in the OP and the update package is also live via Help > About... in the toolkit. Enjoy! ^_^

{{ WugFresh }}
[Nexus S Android Development] Waynesta:
Hey I need some help I am using the Nexus S running 4.1.2 i passed the drivers and unlock test but have problems rooting, when i get to the part where it uses TWRP it doesnt work and gets stuck there.
[Nexus S Android Development] WugFresh:
Make sure that you select the correct device and build before rooting. If that isn't working than use "Any Build" mode for your device. There are different Nexus S devices out there so make sure you are choosing the correct one. If you select the wrong device or build it won't automate the process in TWRP which is exactly what you are experiencing.

{{ WugFresh }}
[Nexus S Android Development] Waynesta:
okay thanks I got the root to work by selecting any build, i thought it would work because theres on one 4.1.2. Also what do you recommend for roms and stuff like that? my first time and idk about any flashing/kernels
[Nexus S Android Development] rodem77:
There isn't an answer to your question, every rom may have different features that may like to me and may don't like to other people, with this toolkit you can make a backup of your system and later try some roms to see what is better for you.

I like cyanogen mod because it is update to last android version (4.2) and a lot of people try an work on it (this mean that it is a well know rom with less bug and with a good support). At the moment, cyanogenmod 10.1 (the last one) is not yet stable so i suggest to wait some weeks before try with this.
[Nexus S Android Development] Pumpino:
I've tried many ROMs on my Nexus S, and JellyShot 1.3 has been the best. I installed the black theme for it and also run the latest Marmite CM kernel with it. I think you'd be hard pressed to find a better combination.
[Nexus S Android Development] jeremysherriff:
Hey, thanks for this tool it made recovery of my work-mate's bootlooping Nexus easy.

I noticed an issue with some of the logic though:

when using the "unroot and flash factory" option, the dialog box described Recovery (android on its back) rather than fastboot mode, making it a bit confusing as to whether I was in the right place

the warnings and dialog for flashing the factory image did *not* specify that the bootloader needed to be unlocked, which of course it does.

to unlock the bootloader it required ADB mode, but it should have been able to proceed from fastboot mode.

you should be able to "reboot recovery" from the fastboot mode, under Advanced Utilities

I'm pretty familiar with adb and fastboot so none of this was an issue for me, but some of the less experienced guys would be confused.

Toolkit v1.6.2, Nexus S crespo on 4.1.2. cheers!!
[Nexus S Android Development] smashcz:
does this install recovery too?
[Nexus S Android Development] jeremysherriff:
Yes if you want it to.

TWRP by default.
[Nexus S Android Development] WugFresh:
Thank you for the feedback.

Regarding your first suggestion, you are right. I didn't take into account that fastboot mode does not look the same on all the nexus devices. I was basing that description from my experience with my gnex and n7. I will update that text description to be more universal.

I am aware of your second point. My reasoning for doing it this way was to start the script with the device on in adb mode because the subsequent root operation will require this anyway and seeing as unlocking is one of the first operations an end user will perform, I figured it wasn't unreasonable to assume the end user would be able to start the script from this state. I.e. it would be unlikely to be locked and unable to boot your device past bootloader mode. So this decision was intentional. I suppose I could add radio buttons under the unlock button for the user to specify if their device is on or in bootloader mode, but I fear this adds complications. I guess I could also just automatically check for fastboot connectivity if an adb device is not found, however this makes it more difficult for me to make a relevant prompt if neither an adb or fastboot device is found. I guess I could write some more generic all encompassing error message about device connectivity, but I like the details I included for the adb one and the fastboot one respectively. If I combined them it would be too long. Any suggestions for this?

Regarding your third point... I am not aware of this. As far as I know there is no fastboot reboot recovery command, there is a fastboot reboot bootloader commend but not a reboot recovery to my knowledge. I haven't seen any documentation on this, nor is it in the fastboot help command. So I am not sure what you are suggesting.

Thanks again, let me know what you think and I will do my best to incorporate these changes in v1.6.3.

Cheers.

{{ WugFresh }}
[Nexus S Android Development] jeremysherriff:
I believe there is a fastboot reboot recovery command, as in fastboot mode you can manually select 'reboot to recovery'. It wasn't my device so i can't experiment but i'll see if i can get hands on it again.

Re the other bit, my issue was a boot-looping device so adb mode wasn't possible. You have some options already around a boot-looping or bricked device, maybe explore that as an avenue? My issue was really that I had chosen "boot-looping device" but then you insist on adb mode...

Assuming a completely stock user who never unlocked or changed recovery or rooted their device, the only option would be fastboot or recovery as a starting point (and fastboot is generally easier to get into for a novice). Perhaps assume fastboot mode (many of us would boot to that from powered off, it's quicker than booting the OS) and start the script with a simple question: are you in fb mode? If so, press yes to continue. If not, press no to have me reboot to fb mode for you (requires usb debug and adb). I personally think fb mode covers more scenarios easily, and then that covers the option of a bricked or boot-looping device too.

Edit - ahh i understand what you mean now, you'll need adb later so start in adb mode to ensure that it will work later on. Damn. Not sure what is best then.

Sent from my GT-P7510
[Nexus S Android Development] WugFresh:
I kind of of like the simple question idea. That's a really easy way of doing it and makes logical sense. I will implement that. I will probably just reverse the yes and no in your question, so the default (ok) behavior is consistent with previous toolkit releases.

"Do you need me to reboot your device into bootloader mode? Press ok to do so. If you are already in bootloader mode press no."

I am still not sure what you mean about the reboot to recovery, but I guess you will let me know.

Thanks again for your feedback and suggestions.

Cheers.

{{ WugFresh }}
[Nexus S Android Development] smashcz:
so everything went fine, except at the end I have no root.

it goes like this.....

flashing custom recovery

booting twrp temporarly

rooting...

phone goes to TWRP

waiting for your device to finish booting back up...

and thats it, so I reboot (from twrp) it says complete, but no root, no supersu..

any ideas?
[Nexus S Android Development] raducux:
In twrp you have to manually flash the su zip in the "ready to flash " folder that has been created on tour sdcard. And then reboot.
[Nexus S Android Development] rodem77:
Manually flash root file is a good solution or you can try to use "any built" options that guide you in root processing with the same result.
[Nexus S Android Development] iceflow420:
Re: [Toolkit] Wug's Nexus Root Toolkit v1.6.2 [Updated 12/29/12]: Nexus S Thread

I am also running into the "no root" issue.

I ran it again and see no "ready to flash" file or folder on my sdcard.

***UPDATE***

I ended up just using the Flash Zip command under Advanced Utilities. With this I was able to locate the zip file on my PC and tell the toolkit to flash that.

Worked like a charm