yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] kinkybookworm:
If you open the camera you then go to the settings (second icon from the right) this will bring up the setting page. On the bottom left you will see the "Tools" option. Go to Tools>Options>General tab, you can then choose where to save your photos/videos by using the pull-down menu.

Happy snapping :D
[JASJAR, XDA Exec, MDA Pro General] Bluediss:
Damn, I always forget the two buttons at the buttons... :shock:

Thanx for pointing that out...
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] vcu_paul:
I have a Samsung Galaxy S4, the Sprint version. I wasn't able to send or receive picture messages and I thought it might have something to do with my APN being wrong (I bought the phone on eBay and had it flashed to nTelos, my provider) but I wasn't able to edit the APN and nTelos was, as usual, no help. So I figured I'd just root it and be able to edit it then!

It was at that moment I stuck my shovel into the soft dirt and started digging.

Essentially, I believe my phone is without an OS at this point. I have tried using ODIN to put a recovery on there so I can at least do something, but now even ODIN is freezing up when I try and flash the Clockwork recovery. I am stuck on the Samsung S4 logo screen and while I can enter download mode I don't think I can enter recovery mode - at least, it hasn't been working tonight. I don't remember everything I've done to my poor phone, but it has to be hurting after the beating I've put it through. I originally tried to root it though I don't think I was successful because the Root Checker said I wasn't, though I'm not sure what I was doing wrong then. Things went downhill from there.

I've read through thread after thread hoping for something that would work, but I've given up trying to use other people's problems to solve my own. This is me saying "Uncle". I require assistance. Let me know what you need from me to provide me with the help I need.

Also - I have ADB on my computer and I think I have a basic understanding of how to use it, but since I can't enter recovery mode I can't do anything other than pat myself on the back for figuring it out. I think my first problem at this point is ODIN. I uninstalled KIES so that's not interfering (and don't even get me started on KIES - I installed KIES and it told me to install KIES3 which told me my device wasn't supported... which is crap because it's running Android 4.3 - or was before I got to it).

Thanks,
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Darnell0216:
If you're sure the phone was on 4.3, then your options are limited thanks to Knox. You can only restore a 4.3 (MJA) based ROM to the phone via Odin, whether it is stock or custom. Easiest giveaway is if you see a line for "Knox" on the Download Mode screen.

At this point you should look in the ROM directory here for a full ROM (xxxxx.tar.md5), either MF9 (4.2.2) if it doesn't have Knox or MJA (4.3) if it does. If you cannot use Odin to put a full ROM on there, then you will need some more serious help.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] l0udude:
Odin the stock 4.3 MJA OEM. Will return your phone to a stock unrooted state.

http://xdaforums.com/showthread.php?t=2522810
[Sprint HTC One (M7)] tdhite:
Hi,

Installing ViperONE 3.5, it's sitting at 0.00% for quite a while -- anyone else experience that?
[Sprint HTC One (M7)] Sloth:
Aroma does that once in a while just restart it
[Sprint HTC One (M7)] tdhite:
Thanks -- how long would you wait -- I'm Happy to wait a while, but, oh... 10 minutes seems plenty?

And by restart -- you mean the phone into recovery?
[Sprint HTC One (M7)] Sloth:
10 mins should be plenty and yes go back to recovery and start the install again
[Sprint HTC One (M7)] tdhite:
Man, you're one dude we like having around here. Looks like it's going. I saw that concept on the InsertCoin threads -- never saw it around ViperONE. Restarted -- seems to be rocking. Thanks so much -- first time on HTC One, love the device, and naturally concerned with any errs.

All flashed Up -- big kudos to you for even seeing this tonight (US)!
[Sprint HTC One (M7)] tdhite:
crap -- boot loop.
[Sprint HTC One (M7)] tdhite:
Heard of anyone having probs with PhilZ flashing ViperONE -- I searched hard and no one seemed to have probs. Backup worked flawless so I'm back up, but I'd love to get ViperONE up. I'll go see if folks are flashing stock kernels or using the Viper included one.

Hmmmm is right. Should have worked.
[Sprint HTC One (M7)] Sloth:
There are no kernels for Sprint so if you picked one in Aroma that could be the problem
[Sprint HTC One (M7)] tdhite:
Well, I tried again -- there's no option for any kernel -- just possible 'flash stock'. I did that and it flashed a kernel, that's it. Cripes. I'll have to go play noob over in the ViperROM thread because something doesn't make sense here. I'd love to get it working, just doesn't get there. Sigh ...

Thank gawd for backups!
[Sprint HTC One (M7)] Sloth:
Try a fresh install do not wipe in TWRP just wipe in Aroma
[Sprint HTC One (M7)] tdhite:
Will do -- just installed InsertCoin (wiped in PhilZ) and it came up flawlessly. Viper should have ... I'll get it, but for now -- 'til tomorrow -- InsertCoin it is. It's actually pretty impressive.
[Sprint HTC One (M7)] tdhite:
Grabbing lunch and wanted to update (if not close) this thread. We fixed up ViperOne (3.5) to support any recovery -- see http://xdaforums.com/showpost.php?p=48537159&postcount=1653.

Now loads like a champ.
[T-Mobile, Samsung Galaxy SIII] ortind200:
samsung announced an update to the 4.3 soon.. i think it'll be 4.3.1.. does anyone kno if this is also for the US tmo s3?
[T-Mobile, Samsung Galaxy SIII] redboys333:
its done

i dont know where you from but in canada i got allready the update 4.3 on my galaxy S3 t999
[T-Mobile, Samsung Galaxy SIII] ortind200:
i'm not talking abt the 4.3 update.. i'm talking abt the update to the 4.3 update.. i think its going to be 4.3.1..
[T-Mobile, Samsung Galaxy SIII] pgarcia777:
Do you have the link?
[T-Mobile, Samsung Galaxy SIII] space4ace:
Since the 4.4 Kitkat update should be here by March or April, then I don't think there will anything else out before that.

Unless there's a major glitch that I don't know about.
[T-Mobile, Samsung Galaxy SIII] ortind200:
but there are major glitches... huge batt drain, ram issues, wake latencies, etc.
[T-Mobile, Samsung Galaxy SIII] Naddict:
OK folks, in order to keep things tidy, going to link and close this...please go here for all future discussion http://xdaforums.com/showthread.php?t=2561670
[One (M7) Q&A, Help & Troubleshooting] flo2228:
Hi all!

This is my first time flashing a phone. I followed a detailed description on YouTube to unlock & root and finally flash the ROM but then

I received this error while flashing the [ROM][m7]Android 4.4 KRT16S Google Play Edition by bigxie

-- Installing: /sdcard/0/bigxie_m7_GPe_KRT16S_odexed-signal.zip

Finding update package...

Opening update package..

Installing update...

Warning: No file_contextsInstalling HTC One Google Play Edition ROM...

Android 4.4 Build KRT16S.H5

Provided by [MENTION=3183886]bigxie[/MENTION]

Setting permissions..

set_metadata_recursive: some changes failed

E: Error in /sdcard/0/bigxie_m7_GPe_KRT16S_odexed-signed.zip

(Status 7)

Installation aborted.

My Backup did not work and now i just receive a "blue screen" when starting my phone.

Any suggestions?

Thx in advance!
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Update recovery to 2.6.3.3

S-off..
[One (M7) Q&A, Help & Troubleshooting] flo2228:
How can i update if i can't enter to my phone and what do you mean by S-Off?

I have the CWM-based Recovery v6.0.2.8 and that is all i can enter..

I can't enter android..

Thx!
[One (M7) Q&A, Help & Troubleshooting] bigxie:
Sideload an old 4.2.2 ROM from recovery, obtain S-OFF, gain super CID, update to latest recovery, then install the ROM.
[One (M7) Q&A, Help & Troubleshooting] flo2228:
Thank you now it's working fine! :)
[One (M7) Q&A, Help & Troubleshooting] nerothehunter:
S-off achieved still showing the same failure

I have achieved S-Off (or i believe i did) it says s-off in the hboot menu, i even installed the radios and the rom still doesnt work, any suggestions?
[One (M7) Q&A, Help & Troubleshooting] harshdev:
Status 7 : Installation Aborted

Hi bigxie,

Thanks for the great rom. I tried installing a few times but i keep getting installation aborted message. I have following:

S-OFF | Bootloader - Unlocked | CWM Latest | Also tried TWRP Latest

bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.20.3263.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.23.1500.1

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: 11111111 (I changed it to gain supercid)

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-a6a74fd020

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Currently running bigxie JB 4.3 ROM

Not sure what is step that I am not doing.
[Galaxy S III Q&A, Help & Troubleshooting] skatlyup:
Hi,

I've read various guides on the net on the best way to charge an S3 (or any modern smartphone).

Some say charge when the battery is at 40% and take it off when it reaches 80%.

Some say to fully discharge it, then charge to 100%.

Can anyone give me advice on the best way to charge my phone (so the battery lasts longer).

Thanks.
[Galaxy S III Q&A, Help & Troubleshooting] SlackingVeteran:
Charge your phone when the phone says connect to charger and remove it when it says Fully charged.. this is the best way to charge your phone...
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
The battery is only supposed to last 50 charge cycles, before capacity is noticeably reduced. As above, don't leave it fully charged and don't let it go below 15%.
[Galaxy S III Q&A, Help & Troubleshooting] samkent6:
It wont matter if you leave your phone on the charger when it says fully charged since they have a cut off point so when it reaches 100% it will not continue to put power into the battery. That's why I charge mine overnight because when I wake up the charger is cold so I know it hasn't been charging all night :D
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Point to note on the above reply .

We on XDA first found that users left phone on charge overnight where reporting a dead unit . After a number of these posts it was recognized as what became SDS or sudden death syndrome .

Leaving on charge overnight is not the actual cause of SDS but something i don't risk any more fixes or not .

SDS seems to manifest in 2 distinct ways.

1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced

* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen

http://xdaforums.com/showthread.php?t=2091045
[Galaxy S III Q&A, Help & Troubleshooting] SlackingVeteran:
ya its a good thing to note, never to leave it charging even if the phone says charged, remove it as soon as phone says charged!!

Sent from my GT-I9300
[Galaxy S III Q&A, Help & Troubleshooting] Geekboy26:
I'm going to start charging mine while I'm at work. I normally charge it overnight but it seems from what I've read here that it's counterproductive.
[Nook Touch General] Edgur:
I just got a new Nook GlowLight (NGL), and came here assuming I would find all sorts of wonderful information about rooting it, and cool hacks I could do to make it more usable. Imagine my surprise when I could only find a couple of threads about it at all, with almost zero information! Finding information is definitely hampered by the name of the device. Any time I google for Nook GlowLight, 99% of the results are instead about the completely different product, Nook Simple Touch with GlowLight. Frustrating!

Anyway, in an effort to get the ball rolling, I will post the little bit that I have been able to find out about my NGL.

I cannot seem to ADB into it. I plugged it in, but ADB does not recognize it. It shows up as a regular mass storage device. The USB VendorID is 2080, and the ProductID is 0007. There seems to be no information out there anywhere about 2080:0007, unfortunately.

I took the back cover off to see if there was a magical "press here to root" button. Sadly, there was not. Since there does not appear to be a NGL teardown annnnnnnnnnnnnywhere on the whole wide Interwebs, I took some amateur photos of mine to share. I didn't want to chance breaking it, as I can't really go and buy a new one right now, so it's not torn down to the individual components, sorry. Hopefully it will be enough to spark some ideas, at least.

I don't know much about hardware hacking, but I've heard about JTAG ports being used to get inside of plenty of Android devices. One of the things I noticed was four unmarked copper pads on the board. That seems about right, as apparently most JTAG interfaces have either 4 or 5 lines, plus Ground. I created a picture with the four unmarked pads + Ground marked.

I know it's not much, but hopefully this information will spark some ideas from people with more experience in cracking these devices! If anyone else has additional information to add, please post it here.
[Nook Touch General] Renate:
Wow, thanks for the photos.

It's really interesting how they reformulated the Nook to use the small PCB.

It seems to be the same hardware basically.

They are using a different WiFi module than the Jorjin in the old Nooks.

There might be hope for having Bluetooth.

No, those four point that you circled are definitely not JTAG.

Some of the tiny gold contact points near the OMAP 3621 processor could be.

There is a missing IC at the top which could be a TXB0104 level shifter for a UART.

I'd be interested to see if/what is on the bottom of the PCB.

VID 2080 is B&N. They have been using the PIDs sequentially, so 0007 is expected.

Presumably it presents a single USB interface and one UMS volume.

Try rebooting the Nook with the USB connected to a PC.

Does it ever say, "New device found"?

You are not going to find an ADB without modifying the INF file for the ADB driver.

Try downloading Microsoft's UsbView from here. (Thank you, FTDI.)

Run it and select the Nook on the left pane, select all on the right pane and copy it here, please.

Oh! Be sure to overwrite your serial number on the text dump.

It's not a big security risk, but still....

Just type "MYSERIALNUMBER" or something.
[Nook Touch General] shanks7777:
USBview

I'm not sure if this gonna be help. Anyway, I will copy the data from mine.

Device Descriptor:

bcdUSB: 0x0200

bDeviceClass: 0x00

bDeviceSubClass: 0x00

bDeviceProtocol: 0x00

bMaxPacketSize0: 0x40 (64)

idVendor: 0x2080

idProduct: 0x0007

bcdDevice: 0x0216

iManufacturer: 0x01

0x0409: "B&N"

iProduct: 0x02

0x0409: "NOOK GlowLight"

iSerialNumber: 0x03

0x0409: "MYSERIALNUMBER"

bNumConfigurations: 0x01

ConnectionStatus: DeviceConnected

Current Config Value: 0x01

Device Bus Speed: High

Device Address: 0x02

Open Pipes: 2

Endpoint Descriptor:

bEndpointAddress: 0x81 IN

Transfer Type: Bulk

wMaxPacketSize: 0x0200 (512)

bInterval: 0x00

Endpoint Descriptor:

bEndpointAddress: 0x01 OUT

Transfer Type: Bulk

wMaxPacketSize: 0x0200 (512)

bInterval: 0x01

Configuration Descriptor:

wTotalLength: 0x0020

bNumInterfaces: 0x01

bConfigurationValue: 0x01

iConfiguration: 0x00

bmAttributes: 0xE0 (Bus Powered Self Powered Remote Wakeup)

MaxPower: 0xFA (500 Ma)

Interface Descriptor:

bInterfaceNumber: 0x00

bAlternateSetting: 0x00

bNumEndpoints: 0x02

bInterfaceClass: 0x08

bInterfaceSubClass: 0x06

bInterfaceProtocol: 0x50

iInterface: 0x00

Endpoint Descriptor:

bEndpointAddress: 0x81 IN

Transfer Type: Bulk

wMaxPacketSize: 0x0200 (512)

bInterval: 0x00

Endpoint Descriptor:

bEndpointAddress: 0x01 OUT

Transfer Type: Bulk

wMaxPacketSize: 0x0200 (512)

bInterval: 0x01
[Nook Touch General] Renate:
I got a little confused between this thread and private messages.

In short, the new Glow does not have ADB enabled out of the box.

The USB dumps are showing just a single UMS storage ("flash" drive) interface.
[Nook Touch General] jwxuan:
my nook just gives the same information

my nook just gives exactly the same information, is there any hope for hacking the new nook glowlight?
[Nook Touch General] Renate:
Sure, there is hope.

There doesn't seem to be any ADB over USB.

A port scan of the WiFi would be a confirmation of no ADB over WiFi.

Check to see if any different VID/PIDs pop up when rebooting with the USB connected.

That could indicate a bootloader, fastboot.

Check to see if recovery has any options besides factory restore.

(Power up with the bottom two buttons depressed.)

Then there are all the possibilities with the case open:

a console interface

a JTAG interface

bootloader jumpers

If B&N releases an update image it could be examined for exploits.

The image could probably be loaded onto an older Nook, rooted and played with.
[Nook Touch General] Renate:
Yup, that's the TI 1st stage bootloader (before x-loader & u-boot).

The good news is that it's the same as the Nook Touch.

That means that we can try a bunch of things with the old Nooks.

We also know already where the console UART is on the old Nooks.
[Nook Touch General] Edgur:
Fantastic. Any suggestions on where to begin? I'm willing to try experiments (though I'd obviously prefer to avoid trying things with a high likelihood of bricking my reader!)
[Nook Touch General] Edgur:
I did some googling to see what I could figure out on my own.

If I am understanding this correctly, that 3 second window between when it identifies itself as 0451:d00e and when it disconnects again, it is receptive to receiving xloader code over the USB.

So we could, in theory, send it an xloader that will read a u-boot over USB as well. Then use that to boot the device into a minimal configuration that would basically "dd" out all of the partitions from the internal flash and emit it over the USB, so we could have a complete image of the built-in disk?

Of course, I have no idea HOW to do those things... :) But if you can give me some pointers, I am willing to learn.
[Nook Touch General] Renate:
Yes, that 3 second window is the place.

But it's not a big deal.

As soon as you identify down the line it will pause and you have all the time in the world.

I think the thing to do is to get the concept working on an older Nook with SD card.

These (because the ROM bootloader checks the SD card) are unbrickable

and with the UART console dmesg output we'll have some feedback.

At some point we'll have to make the leap and try it on a SD-less new Nook.
[Nook Touch General] straygecko:
Some of the work has been done for the Nook Color which also uses the OMAP 3630. There is a working boot from USB for the Nook Color. It boots over USB to CWM from Linux. We have CWM for the NST. So I thought this ought to be easy to boot my NST over USB to CWM by using the Nook Color USB boot process and replace the image and ramdisk with the NST CWM. If that works someone could try it on a Nook Glowlight. So I gave it a shot but no go. For some reason the usbboot program that tests every 250ms for an OMAP USB device to show up and then sends over the initial boot program never sees it. My log shows 0451:d00e appearing for 3 seconds and disappearing. If I run lsusb when I boot the NST I see 0451:d00e. But for some reason usbboot doesn't see it and just sits there waiting for an OMAP device. I looked at the code and its definitely looking for that VID:PID. I tried recompiling usbboot but still no go. Anybody more familiar with USB internals want to take a look at usbboot and see if they can sort out why it doesn't recognize the NST? Here is some more doc on the OMAP USB boot process.
[Nook Touch General] Renate:
Edit: Oops, that solution is for Linux, for Windows this comment would be appropriate:

Do you have the generic USB device driver loaded for the OMAP3630?
[Nook Touch General] Edgur:
Am I going to break my Nook if I try this as-is (the Nook Color version) to see how far the process gets?

That is, this process does not attempt to replace the recovery partition on the device or anything, right? Just boots it by loading an image over USB serial?

As long as it doesn't make any modifications to the Nook at this point, I don't mind trying it out.
[Nook Touch General] straygecko:
Failure between chair and keyboard. Forgot to sudo when running it and couldn't claim the USB device. Now it gets through recognizing the NST and sending aboot & u-boot to the device. Now u-boot doesn't work. Its a Nook Color u-boot so I tried the u-boot from a noogie and the NST boots but not from USB. Looking into compiling a NST u-boot with USB enabled.

---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------

Its not breaking my NST so I don't think it will brick your Nook Glowlight. AFAIK your assumptions are correct but I make no guarantees as nearly the same process is used to flash a device. Might be better to wait for the process to get ironed out better on an NST where we can backup and restore the device with an SD card in case something goes wrong.
[Nook Touch General] straygecko:
OK, I sorted out how to compile the NST u-boot and applied the patches to it from the diff file provided in the Nook Color usb boot package. I ran into an issue where it won't work using virtualbox so I had to boot with a live CD to get the NST to boot over USB into CWM but it worked! ADB works fine but for some reason backup doesn't seem to work. It hangs on "Backing up boot...." - the first partition to backup. But ADB is a good start so you can explore your Nook Glowlight.

I looked at the kernel source for the Nook Glowlight and it has a different u-boot config. I'm not sure how different but I think the best next step will be to compile a Nook Glowlight u-boot before giving this a try on a new glowlight.
[Nook Touch General] Dimasio:
The best way to make a backup - through noogie.img by this manual

blog.the-ebook-reader.com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/

If this method will adapt, it will be very cool!

Sorry for my bad english.
[Nook Touch General] straygecko:
Yeah, I might try booting a noogie image over USB and see if I can get a backup that way. I'm not sure how either a CWM backup or noogie backup will translate to the Nook Glowlight as both backup methods backup to the SD card which is non-existent on the Nook Glowlight.
[Nook Touch General] jwxuan:
Do you have any progress？

Do you have any progress，I have the new Nook glowlight
[Nook Touch General] straygecko:
As I started to build a u-boot.bin from the B&N source I noticed in the config that USB booting might be built into the new Nook Glowlight. Makes sense for a device without an SD slot. Would somebody with a new Glowlight try powering off then powering on while holding down the n button and see what happens?
[Nook Touch General] Renate:
Mmm, I wouldn't want to try a noogie ramdisk.

I think it's better to do a minimal root as above.

Then we can pull romrestore.zip and factory.zip

After that we can do riskier things.

Like park busybox on /data and do a busybox fdisk -l /dev/block/mmcblk0
[Nook Touch General] usenothing:
Hi, jwxuan got something when he tried. He zipped the "boot" disk to a file ,and I upload the zip file with this post.

Hoping it will be useful for help us move on.

Thank u all for all your work.

the zip file :see the attatchment