Database Users

Spreadsheet to help track bugs versus manufacture date

Reddit Thread - http://www.reddit.com/r/nexus6/comments/2orklt/spreadsheet_to_track_bugs_and_manufactured_date/
Spread Sheet - https://docs.google.com/spreadsheets/d/1-a4wwAeaE01D_tS09PnO9GMYH5Ol90fZDnabwEB85GQ/edit
Cross-posting this from Reddit to get more data. Here is the post text:
I put this spreadsheet together after /u/rchallender helped me figure out how to get the (assumed) manufacture date of a Motorola device.
Boot to Bootloader
Scroll using Vol Down to Barcodes
Select with Vol Up
Date (bottom barcode) lists the (assumed) manufacture date
So far the columns are:
Username
Color (Midnight Blue, Butt White)
Size (32GB, 64GB)
Purchased From (Play Store, Motorola, T-Mobile, Sprint, AT&T, other)
Purchased Date
Manufacture Date
Burn In (Yes, No)
Defective Display (Yes, No)
Lag Issues (Yes, No)
Encrypted (Yes, No)
Defective Vibration Motor (Yes, No)
Other hardware issues (provide steps to reproduce if applicable)
I'd love any input regarding if more or less information is needed. I neglected to put battery performance because everyones usage is different and it would be really tough to determine if its personal usage vs battery issue.

Looks like I got an early one. 10/28/2014 build.

Samsung Tab 4 - 7.0" SM-T230 - Service Manual

Afternoon,
Really need a service manual for Samsung tab 4 SM-T230NU.

See if that's ok.

Trying to rewrite the eMMC without BGA rework... I can find all the points except CLK. That one's kinda important :- )
The CMD and D0-D7 all have resistors connected and I would expect CLK to have one too. But I just cannot find it! And the resistors aren't shown on this schematic. In fact, the eMMC itself is not shown.
I have a scrap PCB that I've pulled the proc and eMMC from, and I can probe the pads. I've found the CLK pad on the proc footprint,, which proves I've got the correct pad on the eMMC, but if I have to pull a BGA it's going to be the eMMC and definitely not the proc/RAM sandwich! So knowing the pad under the proc is not helpful.
We have a bunch of these tablets that are MDM locked, and the MDM provider removed support for old Android versions so even though we have access to the MDM dashboard the server will no longer talk to the tablets to unlock them.
I know it's a long shot for an old tablet, but has anyone found a point on the PCB to access the eMMC CLK without pulling a BGA? Sure would be nice...

New Nook Glowlight Plus

According to B&N's fact sheet, this baby runs KitKat and has a 300 dpi resolution. I wonder if it will be hard to root it? There are a couple of apps I'd love to run on such a device. No microSD card slot, though, and 2.8 gb of free space in internal storage If it csn be rooted, I'd be tempted to buy one.

Stoked! Esp. the amount of space available compared to the previous model. Definitely hoping someone can root this quickly so I can put Dropsync on it.

I have one.
I'd be happy to TTD, if you like. Just tell me what to do.

Can't wait to pick one up - this looks pretty sweet! :good:

Yow! How did I miss this?
I know where I am going after work tonight, the local B&N!
They have them in stock.

Renate NST said:
Yow! How did I miss this?
I know where I am going after work tonight, the local B&N!
They have them in stock.
Click to expand...
Click to collapse
Great! I know you did a lot of work to help develop a rooting method for the last Glowlight. I plan to pick one up soon. I wonder if this one will be hard to root.

Well, I bought my Glow Plus, turned it on and it said, "Let's Get Started".
So I did.
The entire display is simply glued to the frame.
You can work a knife carefully around the rim and detach the display, folding it gently to the left side.

Yow! I could kiss B&N!
Code:
[email protected]_6sl:/ # getprop
...
[ro.build.version.release]: [4.4.2]
[ro.build.version.sdk]: [19]
4G storage, only 512M RAM, no Bluetooth.

Renate NST said:
Yow! I could kiss B&N!
[email protected]_6sl:/ # getprop
Click to expand...
Click to collapse
Does it mean your new Nook is rooted?

Kramar111 said:
Does it mean your new Nook is rooted?
Click to expand...
Click to collapse
It means that I have full control of my new Nook.
I still have to figure out a bunch of stuff.
Currently, to gain this access requires opening your Nook.
We may gain enough knowledge to make it possible to root without opening the Nook.

Wow, you are good !
I have the Plus too, lmk if you need testers

I also have the Plus now, and I could be a tester, too.
I had a hard time getting my MacBook Pro with Android File Transfer to see my new Nook, but I finally succeeded. Then I tried Calibre. I got a "failure to communicate" error message from Calibre. I persisted and tried to send a book to the Nook. Calibre couldn't see the book on my Nook. However, it showed up in the Nook library after a few minutes. I also noticed that I can't create a new folder on the Nook using Android File Transfer. I only mention these things in case they might give someone else a clue in figuring out a rooting process.

So, to let the cat out of the bag, getting a root console connection to the new Nook Glow Plus is quite easy.
There is a connector location, J4, which is quite clearly labelled with the pinout.
The output is 115200-8-N-1 on a 3.3V signal level.
TX refers to the output of the Nook, RX is the input, connect up ground, leave the V alone.
(Don't connect anything to this unless you understand the description above,
it's not anything related to a 9 pin RS-232 signal without a converter.
There are plenty of cheap USB-UART converters that run 3.3V that you can buy for $3.)
You can:
Code:
setprop persist.sys.usb.config mtp,adb
setprop sys.usb.config mtp,adb
Then you will have (unrooted) ADB over USB, which is still useful to load things.
Those who don't want to scuff up their new Nook would do better to wait a bit.

I've been following this since I heard that a new nook is available. Funny that I stumbled over the waterproof Kobo h2o a week ago and thought, I could get me a new ebook reader (I had a couple of Sonys and then switched to LCD tablets). I just don't know if I should jump the gun and get one or if I wait until I see what you all can achieve. Tinkering with my toys is important to me, but loosing the waterproofing due to opening would be a bummer.
BTW, how does that aluminum shell feel. I like the front looks of the nook, but am not too convinced about the aluminum back.
Anyways, great work. Keep up with it. I'll probably see if the local B&N has them, and I may end up buying one without knowing about how this here will develop
Getting new toys is just too tempting.

I've thought about the latter problem of reassembling the Nook.
The edging is a double-stick foam tape.
That's easy and convenient for the factory assembly.
You could just press it all back together and it would be 98% so waterproof as before, there's a lot of stick still left.
You could also clean all the tape off and put this back with a thin bead of silicone caulking.
This would actually be better waterproofing and not impossible to re-open your Nook.

FreeScale i.MX 6SoloLite
I am sure you already have it, but just in case FreeScale documentation for MCIMX6L8DVN10AB is easy to find (I cannot post external links here)

Here's the internal memory layout.
The good news is that there is no UMS and therefore no division of the useful space.
Code:
/dev/block/mmcblk0p1 /boot emmc 19 MB
/dev/block/mmcblk0p2 /recovery emmc 32 MB
/dev/block/mmcblk0p5 /system ext4 384 MB
/dev/block/mmcblk0p6 /cache ext4 384 MB
/dev/block/mmcblk0p7 /device ext4 8 MB
/dev/block/mmcblk0p8 /misc emmc 4 MB
/dev/block/mmcblk0p4 /data ext4 2925 MB
I tried, but I don't think that there are any UART muxes on the micro USB.

What's J9 for?
Renate NST said:
....
There is a connector location, J4, which is quite clearly labelled with the pinout.
The output is 115200-8-N-1 on a 3.3V signal level.
Click to expand...
Click to collapse
OK, what's J9 for?

There are only two things I'm waiting on before I upgrade from my beat to heck Nook Simple Touch.
1) Root- I know this will take a little while, I can be patient
2) I would like to know if the issues with the glow light have been resolved.
I've actually been looking for a new e-reader for a few months now, but couldn't find anything I liked on the market. But a Nook Glowlight with Android 4.4 + water resistant + metal case? I'm in . You should see the gouges my poor old NST's screen has lol. Thanks for your work so far Renate.

DeanGibson said:
OK, what's J9 for?
Click to expand...
Click to collapse
That's for you to wire in your GPS to make a really cool hiking map.
Um, it's apparently unused.
Ok, just to make your Nook livable for now:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd /system/priv-app
mv partner.apk partner.bak
This gets rid of the forced registration screen.
There is a launcher installed, but the HOME intent was removed from the manifest.
Install your own favorite launcher and it will reboot on that.
Can't install a "Launcher2.apk"? Try this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
cd /system/priv-app
mv Launcher2.apk Launcher2.apk.bak
mv Launcher2.odex Launcher2.odex.bak
Now I throw on a few pretty fonts from my old Nook, install my Library and my Reader
and now I have the basic NGP that allows me to read the library book that I was reading.
That's the main point of this exercise.

Glowlight Plus 7.8" 2019

Apparently Barnes and Noble has a new Nook.
http://www.barnesandnobleinc.com/press-release/barnes-noble-introduces-new-nook-just-time-summer/
They are apparently (over)using the name "Nook Glowlight".
It's 7.8" and has 8GB storage and sells for $199.
The last I checked, 16GB microSDs cost about $3.
The main B&N website still doesn't have anything about this.
Supposedly it will be available online on Wednesday, May 29, 2019.
I'm not sure that I like either 7.8" or $199.

I'm not sure I will like the 7.8" screen yet, but I haven't read anything yet. I think I will like the new size for reading, but dislike it for portability... It really looks and feels exactly like a NG3 that took an extra dose of vitamins...
I do like the fact that the rooting procedure was exactly like the NG3, though! Up and running with alternate launcher, fixed boot animation, and of course Calibre Companion. Thanks for all your help on the previous models - it has carried over to this one quite nicely.
---------- Post added at 04:11 PM ---------- Previous post was at 03:52 PM ----------
Also, saw your post on the other site - short of a teardown, is there any diagnostics, etc. that I can run on the thing to give you some tech details?
I will try to see if I can pair any BT devices to it tonight - I have a couple keyboards and a BT remote that I can try out...
I agree the 8gb is a ridiculous storage - esp. since they obviously have in mind at least audiobook capabilities with the new audio jack...

spedinfargo said:
Up and running with ...
Click to expand...
Click to collapse
Wait a minute. You have one?
Could you please get me some info?
Code:
# cat /proc/cpuinfo [color=red]<-- copy/paste all the lines except don't paste your serial number!!![/color]
# cat /proc/meminfo [color=red]<-- we only need the first line[/color]
spedinfargo said:
short of a teardown...
Click to expand...
Click to collapse
You mean that everybody doesn't immediately do a teardown on their brand new device?

Renate NST said:
Wait a minute. You have one?
Could you please get me some info?
Code:
# cat /proc/cpuinfo [color=red]<-- copy/paste all the lines except don't paste your serial number!!![/color]
# cat /proc/meminfo [color=red]<-- we only need the first line[/color]
Click to expand...
Click to collapse
I thought you'd never ask
Yeah, I was going to pick it up last night (friend works at BN) but had to wait until noon today. They are doing a "soft release" of this thing (for lack of a better term). Guy at my small-ish town said they had almost sold out of their initial shipment (fourteen or so) which actually surprised me a bit.
Code:
Processor : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 790.52
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : Freescale i.MX 6SoloLite NTX Board
Revision : 60200
Serial : 0
MemTotal: 995848 kB
---------- Post added at 04:35 PM ---------- Previous post was at 04:31 PM ----------
By the way, jptiger's summary post of how to root the GL3 (based mostly on your work, I think... and properly credited) very much works on this device. The only thing I changed was the model number in the .sh file...
https://forum.xda-developers.com/no...set-nook-glowlight-3-t3802331/page2?nocache=1

spedinfargo said:
Code:
Hardware : Freescale i.MX 6SoloLite NTX Board
MemTotal: 995848 kB
Click to expand...
Click to collapse
Oh, so in short, it's exactly like the Glow 3 except they switched from 512M DRAM to 1G.

@spedinfargo one more thing, could you:
Code:
getprop ro.build.fingerprint
getprop ro.model
cat /sys/class/android_usb/android0/idVendor
cat /sys/class/android_usb/android0/idProduct
(I added some stuff before to that rooting post, but most of it was someone else's vold exploit.
I'm old skool, I root with a screwdriver!)

NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/50.0.114_user:user/release-keys
nothing for getprop ro.model
2080
000c
And it's 9.8 ounces if you're wondering.

spedinfargo said:
nothing for ...
Click to expand...
Click to collapse
Oops, I meant getprop ro.product.model
So, in short, the GL4 as compared to GL3:
Is 7.8" instead of 6"
Has 1G DRAM instead of 512M
Has Bluetooth
Has audio and headphone jack
VID/PID is 2080/000c
Everything else is exactly the same.
I can see that the 7.8" would be useful for PDFs, but why not go overboard and get an expensive 10" or something?
And I really hate the Neonode zForce IR touch sensing.
In ambient light the bezel creates annoying shadows and it's a dust catcher.

Renate NST said:
And I really hate the Neonode zForce IR touch sensing.
Click to expand...
Click to collapse
Better this than poorly implemented elan touch like in GLP. Also, higher image clarity.

RyogoNA said:
Better this than poorly implemented elan touch like in GLP. Also, higher image clarity.
Click to expand...
Click to collapse
Huh? You mean the metal cased, white GL2? That's Elan and the display is fine.
Isn't that the only Nook eInk with capacitive?

Renate NST said:
Huh? You mean the metal cased, white GL2? That's Elan and the display is fine.
Isn't that the only Nook eInk with capacitive?
Click to expand...
Click to collapse
I mean Glowlight Plus, so yeah.
I have GLP, GL3 and Tolino Shine 2 (IR sensor) - image is perceivable sharper on both GL3 and Shine 2 than on GLP.
Also, GLP have one very annoying issue - it registers false touches very often and this issue is not related to nook fw, I'm using GLP with tolino fw currently and issue is still there.

RyogoNA said:
it registers false touches very often...
Click to expand...
Click to collapse
Do you mean "Home" touches? That is a known problem (with a known cure: https://forum.xda-developers.com/showpost.php?p=79438405&postcount=614 )
I've never found the screen itself to have problems with false touches.

Renate NST said:
Do you mean "Home" touches? That is a known problem (with a known cure: https://forum.xda-developers.com/showpost.php?p=79438405&postcount=614 )
I've never found the screen itself to have problems with false touches.
Click to expand...
Click to collapse
I've read your solution regarding "home" button, but no, it is not about it.
It is actually a false touches in random places and they occur mostly when there is some animation on screen (like sliding left panel, or sliding keyboard) - I can record a video if you're curious. I heard that few other people was also suffering from this issue, but afaik it is not a wide-spread issue.

Bluetooth doesn't seem to work, at least with a keyboard or remote (the remote I have is just an emulated keyboard I think). When I turn on the BT in the standard Nook settings screen, I get an icon spinning (which I assume means it's i pairing mode) but it doesn't seem to detect any devices... I guess I could take it out to my car and try to pair to my stereo - maybe the BT is only intended as an output device for speakers/headphones (because of the audiobook capability).
All in all it probably won't be the best $200 I've ever spent, but by far not the worst either...

spedinfargo said:
Bluetooth doesn't seem to work, at least with a keyboard or remote (the remote I have is just an emulated keyboard I think). When I turn on the BT in the standard Nook settings screen, I get an icon spinning (which I assume means it's i pairing mode) but it doesn't seem to detect any devices... I guess I could take it out to my car and try to pair to my stereo - maybe the BT is only intended as an output device for speakers/headphones (because of the audiobook capability).
All in all it probably won't be the best $200 I've ever spent, but by far not the worst either...
Click to expand...
Click to collapse
I was able to pair the Nook to an audio device - in this case the stereo in my car. So that seems to confirm that the BT is meant for audio output.
I don't know enough about BT and Android to know if there is another secret setting somewhere that can be exposed to see if there is also input capability. It would be a shame if there wasn't some way to take advantage and have some sort of input capability (I'm thinking of Renate's remote page turner capability...)

I just got the Nook GL 7.8 for my birthday but I've found that I don't have a screensaver setting like I did on my first GL (meaning the screensaver setting doesn't show up AT ALL). Anyone know how to fix that? My software is up to date.

Just a heads up.
The case is a bit hard to split.
After you get there you'll see that everything is coated with a pesky conformal coating, much like Elmer's glue on your skin.
There is the standard root console available on 3.3V, 115200-8-n-1
Photos to follow.

Here's a blog with some info and a teardown:
http://www.temblast.com/blogs/glow4/blog.htm

Renate NST said:
Here's a blog with some info and a teardown:
http://www.temblast.com/blogs/glow4/blog.htm
Click to expand...
Click to collapse
Thanks for the info. Given that one has to apply voltage to trigger the OTG mode. does that mean e.g. we cannot hook up a flash drive to the glowlight plus?
Does the GL+ support A2 mode for e.g. web browsing? What about pitch-to-zoom -- for epub AND for pdf?
Could some who own a GL+ kindly sideload
* alreader and see if the eink mode works?
* vncviewer and see if it is usable? (for text/pdf, NOT graphics/videos)
I called/visited 5 BN stores within a 100 miles radius and I couldn't find a single one Either GL+ sells really well or BN messes up their supply chain...
THANKS for the info!

case-sensitive said:
Given that one has to apply voltage to trigger the OTG mode...
Click to expand...
Click to collapse
The actual trigger for OTG is the (disconnected) ID pin which we are sneakily manipulating.
The problem is that the Nooks apparently don't have the hardware to supply power.
The smallest solution for an external SD card would be a special USB Y cable, a thumb drive and a USB power pack.
There is the potential to wire in an SD card inside the Glow4.
There is not an actual SD socket footprint on the PCB but there are test points.
I'll check that out.
Still, as I've proven, you have to be very careful opening the case.

[FIX] Nvidia Shield Android TV 2015 PRO (500GB) - Beeping SSHD with black screen or frozen image

I'm making this post hoping that I can help others with the same problem like I had. I apologize if something close to this was posted here before, tho' I can't find anything.
So, after a like a month or 2 of not using my SATV, I wanted to watch something on it. When I tried to bring it back from sleep mode the green light turned on but was no image on TV and a beeping sound (for like 20 seconds) was coming out from it.
After reading a few threads in here and on Nvidia forums I found out that my SSHD is "dead".
I was so sad thinking that I lost all my DRM Widevine L1 keys and angry on myself for not switching to and SSD earlier. I was prepared to junk it when, luckily, a few days later, I found the solution to fix it thanks to Youtube.
Before you start make sure you have all the necessary tools for the job. Do not use your fingers or unappropriated bits.
1. Open the SATV and take the SSHD out. Best tutorial that I found is this video.
2. Take the SSHD apart and unstuck the reading head from the platter by following exactly the instructions in this video.
I can confirm that my reading head was stuck in the same position as in the video. Whatever you do, do not touch the platter!
Note: Our SSHD is slightly different on the outside than the one in the video. First remove the label completely. Second, take out the 6 screws on the sides. Third, there is a 7th screw towards the center hidden under a round silver patch which becomes visible after you take out the label.
3. Put everything back together and, voilà, you should have an working SATV again.
On mine, after I powered it back on, the SSHD was making at first a pretty loud grinding noise and felt like everything was slower that I was remembering from before. But after several minutes the sound on SSHD came back to normal and the OS was again as quick as before. I connected an external HDD to save about 200GB of personal stuff from the SATV and everything worked fine. Even I was able to update to 8.2.3 after.
Last, I powered off the SATV and unplugged it from everything until I will buy this one as it was suggested here. I don't want to push my luck further before I do a clone to an SSD and, just in case, to another 500GB HDD that I have laying around.
Also this might work for the 2017 PRO model since there is no major difference from 2015 one.
I hope this guide will fix yours too. Cheers!
Sorry for my English. Romania here.