Database Users

Just got a Nexus 7 but think they sent me the wrong one

So I just got a Nexus 7 refurb from Amazon, quite happy with the price. I went ahead rooted it, installed SmoothRom and even tested out Ubuntu 13.04. Here is where it gets odd. I didn't check to verify it was the 32gb tablet when I got it, I should have but it slipped my mind, I got too excited heh. After I had put Ubuntu on it I decided to go back to my smoothrom so I restored the backup with TWRP and when I was copying some movies to it I got a "your low on storage space" type alert which I found odd since I was only putting 4-5 gigs of files on it and I had not installed that many apps. I went into the storage manager and it reported I had like 6gb of space total, and 4 used. I thought it was really strange so I tried a bunch of different partition info apps and all of them basically reported the same thing. So I went back into TWRP and formatted everything, and restored the Smoothrom I had before. Now its reporting 13GB, so I am assuming now they sent me a 16gb and not the 32gb, but is there anyway to verify that is accurate? Could something else be eating some of the space and not reporting it to TWRP or android? I'm assuming Ubuntu did something funky when it was installed which made it look like it was only 8gb and not 16.. Ijust want to make sure its truely not a 32gb before I go through returning this to stock and sending it back. Sorry of the newbie questions.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

You can get a pretty good idea by rebooting and capturing the dmesg output (as soon as possible!) .
e.g.
Code:
...
<6>[ 5.867778] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 5.879277] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name MMC32G BOOT_MULTI 0x10
<6>[ 5.881183] mmc0: new high speed DDR MMC card at address 0001
<6>[ 5.881431] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 5.881759] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 5.882064] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 5.882306] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 5.884469] Primary GPT is invalid, using alternate GPT.
Look for "mmc" 5 or 6 seconds into the boot.
I think I might have captured the above using a terminal emulator app, as in
Code:
$ su
# dmesg > /sdcard/dmesgboot.text
but the important thing to remember is that /proc/kmsg has a limited size, so don't dilly-dally after the boot. You could also do the same from your PC if you have ADB setup.
Note that there have been several people that reported mysteriously short ext4 file systems in the /data partition (including me) - but I don't know exactly how it happened. Search for those threads.

bftb0 said:
You can get a pretty good idea by rebooting and capturing the dmesg output (as soon as possible!) .
e.g.
Code:
...
<6>[ 5.867778] [mmc]:mmc_decode_cid:113 cid.prv 0x1
<6>[ 5.879277] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name MMC32G BOOT_MULTI 0x10
<6>[ 5.881183] mmc0: new high speed DDR MMC card at address 0001
<6>[ 5.881431] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 5.881759] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 5.882064] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 5.882306] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 5.884469] Primary GPT is invalid, using alternate GPT.
Look for "mmc" 5 or 6 seconds into the boot.
I think I might have captured the above using a terminal emulator app, as in
Code:
$ su
# dmesg > /sdcard/dmesgboot.text
but the important thing to remember is that /proc/kmsg has a limited size, so don't dilly-dally after the boot. You could also do the same from your PC if you have ADB setup.
Note that there have been several people that reported mysteriously short ext4 file systems in the /data partition (including me) - but I don't know exactly how it happened. Search for those threads.
Click to expand...
Click to collapse
Excellent thanks a ton. Yeah mine says 14.7 GiB so I guess they did screw it up. I also have various "mnc0: invalid maximum block size, assuming 512 bytes" above that, assuming thats not a big issue as I didn't find anyone talking about that on the forums.

You can also try flashing stock with adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It's something you might have to do anyway if you're returning you're device so it's worth a try.

vortico said:
I also have various "mnc0: invalid maximum block size, assuming 512 bytes" above that, assuming thats not a big issue as I didn't find anyone talking about that on the forums.
Click to expand...
Click to collapse
I have that too - I just didn't want to make the cut-n-paste too long.
good luck with the refurb-return.

Cool will try that as well, thanks
Sent from my Nexus 7 using xda app-developers app

Heart Rate Sensor Problem

Hi guys, my heart rate monitor sensor is not working and the sensor doesn't even light up, which means it's not working AT ALL! And recently I even noticed Antutu and CPU-Z(Sensor Section) doesn't even detect it! (Screenshot below) What may be the cause of this?
Here is the logcat output of the BioSensor:
Code:
E/EnterpriseSharedDevicePolicy( 1132): isSharedDeviceEnabled
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current2
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/lib_ver
E/audio_hw_primary( 338): [MAXIM] setDSM_tx_Control()....dsm_enable : 0, dsm_opened : 1, adev->mode : 0
E/LocSvc_libulp( 1132): I/int ulp_msg_process_system_update(UlpSystemEvent): systemEvent:5
E/LocSvc_libulp( 1132): I/int ulp_msg_process_start_req(), at ulp state = 1
E/LocSvc_ApiV02( 1132): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 125 QMI_LOC_GET_BEST_AVAILABLE_POSITION_REQ_V02
E/LocSvc_libulp( 1132): I/int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*), report ZPP position to providers,report_position = 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?

DarkGuyver said:
Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?
Click to expand...
Click to collapse
I didn't try the heart sensor before, never really gave it much thought...
Yes, I've tried to do a Hard Reset, I even flashed new firmware via Kies and made the Soft Reset (Take of the battery, press power btn for 1 min, yadayada) and it still doesn't work... I've uploaded a logcat check 1st post.

I'd take your phone to a Samsung Service Center and ask them to fix it for you. Or take it back to the retailer for repairs as it maybe faulty.

Btw did u get the solution b/c I have same problem

[R&D][FIX][REF][DIAG][DEBUG] Nexus 7 UART adapter, activation and application

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Universal Asynchronous Receiver Transmitter on previous Nexus models was really easy to use but our flo has a flaw - the bootloader prevents UART initialization on a booting kernel. To work around this limitation developers either had recompiled the stock kernel or changed boot config parameters and reassembled bootimg. However these options are not available on stuck and faulty units or in bootloops, where a look at dmesg log would most likely reveal the problem.
So I was checking some enigmatic lk (little kernel) messages in source code and text strings in "bootloader-flo-flo-04.05.img" when I noticed "oem uart-on" in the context of fastboot code. As I had a UART adapter already hooked up, I just typed "fastboot oem uart-on" and my Nexus immediately reacted, rebooted and logged the following (abbrev):
Code:
...
[427740] fastboot: oem uart-on
[427740] OdmData=0x6
...
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk
...
[820] UART is enabled!
...
[860] Machine FLO was detected
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-cyanogenmod-g8a4918a ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Tue Nov 17 02:00:34 PST 2015
[ 0.000000] CPU: ARMv7 Processor [511f06f0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine: QCT APQ8064 FLO
[ 0.000000] Truncating memory at 0x90000000 to fit in 32-bit physical address space
[ 0.000000] cma: CMA: reserved 8 MiB at af800000
[ 0.000000] memory pool 3 (start 0xfe100000 size 1e00000) initialized
[ 0.000000] Initialized persistent memory from 88d00000-88dfffff
[ 0.000000] cma: CMA: reserved 16 MiB at ab800000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] socinfo_init: v7, id=172, ver=2.0, raw_id=2289, raw_ver=2289, hw_plat=8, hw_plat_ver=65536
[ 0.000000] accessory_chip=0, hw_plat_subtype=0, pmic_model=18, pmic_die_revision=4
[ 0.000000] allocating 44236800 bytes at c30df000 (832df000 physical) for fb
[ 0.000000] PERCPU: Embedded 8 pages/cpu @c5b12000 s16768 r0 d16000 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 476163
[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=340M androidboot.emmc=true androidboot.serialno=087888a4 bootreason=Reboot fuse_info=Y ddr_vendor=hynix androidboot.baseband=apq asustek.hw_rev=rev_e androidboot.bootloader=FLO-04.05
[ 0.000000] HW Revision: ASUSTek input rev_e
...
A complete boot log is now available on untouched boot.img! Can you see the seamless log transition from the little kernel to the big one? The "fastboot oem uart-on" command did change bootloader variables and now it always boots with UART enabled, getvar reports:
Code:
(bootloader) version-bootloader: FLO-04.05
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 087888a4
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: yes
Presumably, "fastboot oem uart-off" would disable UART again.
I uploaded the full boot log here.
Let me repeat, UART is not only for developers, it is also a fantastic diagnostic tool for both hardware and software issues. While you can not buy a Nexus-specific UART adapter, it is quite easy to make - have a look at the attached schematic diagram. I did not have a FT232R IC and used an insanely cheap PL2303 general RS232-TTL-USB adapter from a different project. This PL2303 is most likely a fake and does not comply with 1.8V-level specs but I was able to get it going on a simple voltage level translator made of discrete components (att.).
I also discovered an alternative UART interface on the JTAG header but it is much harder to connect to of course.
What happens next depends on your host platform. On Windows you have to install a driver for FT232R/PL2303/etc, note a new COM port number and then use a terminal app like e.g. Putty.
Note - if UART is not activated with the above fastboot command, then the default speed after booting will be 9600, not 115200bps. To speed it up type stty -F /dev/ttyHSL0 115200 in an Android terminal app.
Don't hesitate to ask any questions on this subject.
:good:

Thanks for your guide.
I have a question, with the old bootloader from Android 4.4.4 i could type shell commands to interact with it but now with bootloader 04.05 it does not work and i only get a log.
Is there a way to fix this? Or do i have to type the commands in another way?
I want to do this because my screen is broken so UART is the only way to interact with it and I want to make it into a media center with hdmi through my slimport adapter.
I have a arduino hooked up to uart and an remote to send the commands, it works perfect with Android 4.4.4 but i would like it to work with a never version.

petanque said:
I want to make it into a media center with hdmi through my slimport adapter. I have a arduino hooked up to uart and an remote to send the commands
Click to expand...
Click to collapse
This is a very interesting UART application.
Bootloader v4.05 and CM12.1 let me interact in OS.
Anyway, you can downgrade to v3 bootloader and use new OS by application of selective flashing commands instead of the factory script.
EDIT 1
Why don't you use bluetooth for remote control?
EDIT 2
...or Kodi with WiFi remote control?

Thanks for your advice, will try CM and hope i get lucky.
CM12.1 is better than Android 4.4.4 but i hope to get CM13 working.
I got no screen or touch so i have to configure it with ADB or UART and the remote control can make it a little easier moving around. When configured then I will use a PS3 controller and Yatse with Kodi.

Fingerprint problem with G900t on cm13

Hi Guy's,
I've got a problem with my fingerprint after reflashing. I flashed the phone to cm13 and the fingerprint works well. All my phones are encrypted, so wanted it to on my S5. But that was a miss decision! After the was rebooted and typed in my pin, it hang on boot screen. I gave it another try by removing the batterie. Than it comes up, but with a full wipe. Strange was, that my internal storage shows only 3gb free, on an empty phone. I tried to flash it back with the original firmware, but it won't except my encryption pin. At least I flashed it back to cm13. But now my fingerprint won't work! What a mess! The setup for the fingerprint shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got an terminal error, but I don't know if it regards to the fingerprint error:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
CM Version: '13.0-20160820-SNAPSHOT-ZNH5YAO0J4-klte'
Build fingerprint: 'samsung/kltetmo/kltetmo:6.0.1/MMB29M/G900TUVU1GPE1:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 26949, tid: 26975, name: Terminal 0 >>> com.android.terminal <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 a8d9e69c r1 00000010 r2 00000000 r3 00000000
r4 0000efff r5 00000010 r6 a86c5138 r7 ffffffff
r8 00000000 r9 0000003c sl a86c50e0 fp 00009fff
ip aee8efdc sp aec9e448 lr aee86b7d pc aee86bc2 cpsr 600f0030
backtrace:
#00 pc 00005bc2 /system/lib/libjni_terminal.so
#01 pc 00005503 /system/lib/libjni_terminal.so
#02 pc 00007239 /system/lib/libjni_terminal.so
#03 pc 00003d3d /system/lib/libjni_terminal.so
#04 pc 000039c7 /system/lib/libjni_terminal.so (vterm_push_bytes+410)
#05 pc 00002545 /system/lib/libjni_terminal.so (_ZN7android8Terminal3runEv+452)
#06 pc 0029330d /data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex (offset 0x17d000)
I'm not a developer and can't analyse this message. That's why I wrote to the XDA developer forum. I got a post for that issue at the cm forum, but no replies.
Can somebody please give my a hint!
Best
Schlombie
Sent from my SM-G900T using XDA-Developers mobile app

[Dev] [kmsg] Very strange issue after water damage

So I tried to revive a water damaged galaxy s4 i9505 and everything seemed to be working. Always when booting finishes it hangs and hard reboots. TWRP and bootloader mode work just fine and I was able to backup the whole system with it.
It gets even more strange because LineageOS without gapps boots fine and works fine. When I flash the gapps it boots and get's stuck and hard reboots. Could a part of the RAM be damaged by the water, so it starts rebooting after it gets allocated?
I managed to grab a kmsg just before it rebooted and would be super excited if someone can find anything about why it's happening. It has been driving me mad as I don't know the cause. Everything is working on LineageOS even the wifi connects.
kmsg: http://pastebin.com/xx6NNNRr

another last_kmsg: http://pastebin.com/1sDAqK4B

I managed to trace it down. Seems like the L1 cache is somehow corrupted after the water damage.
Another log if someones interested:
Code:
[ 37.401977] L1 / TLB Error detected on CPU 2!
[ 37.402130] CESR = 0x00010002
[ 37.402374] CPU speed = 810000
[ 37.402526] MIDR = 0x511f06f0
[ 37.402679] D-cache data parity error
[ 37.402801] D-side CESYNR = 0x00002144
[ 37.402954] Kernel panic - not syncing: L1 nonrecoverable cache error detected
[ 37.403137] CPU0: stopping
[ 37.403289] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.403381] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.403533] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c0105780>] (__irq_svc+0x40/0x74)
[ 37.403656] Exception stack(0xdeda5c20 to 0xdeda5c68)
[ 37.403747] 5c20: 00000001 ffffffff ffffffaa 00000001 c4998e40 c0f1a1c0 c0f1a1c8 00000003
[ 37.403869] 5c40: c0f17e40 00000000 00000001 03a81000 00000004 deda5c68 c017de58 c01d10f4
[ 37.404022] 5c60: 20000113 ffffffff
[ 37.404113] [<c0105780>] (__irq_svc+0x40/0x74) from [<c01d10f4>] (smp_call_function_many+0x26c/0x2a4)
[ 37.404266] [<c01d10f4>] (smp_call_function_many+0x26c/0x2a4) from [<c01d1174>] (smp_call_function+0x48/0x70)
[ 37.404388] [<c01d1174>] (smp_call_function+0x48/0x70) from [<c070d3b0>] (cpuidle_latency_notify+0x18/0x24)
[ 37.404541] [<c070d3b0>] (cpuidle_latency_notify+0x18/0x24) from [<c01a8bcc>] (notifier_call_chain+0x40/0x68)
[ 37.404693] [<c01a8bcc>] (notifier_call_chain+0x40/0x68) from [<c01a8e18>] (__blocking_notifier_call_chain+0x40/0x58)
[ 37.404846] [<c01a8e18>] (__blocking_notifier_call_chain+0x40/0x58) from [<c01a8e44>] (blocking_notifier_call_chain+0x14/0x1c)
[ 37.404998] [<c01a8e44>] (blocking_notifier_call_chain+0x14/0x1c) from [<c01bfdb8>] (pm_qos_update_target+0x118/0x130)
[ 37.405151] [<c01bfdb8>] (pm_qos_update_target+0x118/0x130) from [<c072c4b8>] (msmsdcc_enable+0x24/0x158)
[ 37.405242] [<c072c4b8>] (msmsdcc_enable+0x24/0x158) from [<c070fa9c>] (__mmc_claim_host+0x180/0x190)
[ 37.405395] [<c070fa9c>] (__mmc_claim_host+0x180/0x190) from [<c055a8c4>] (sdioh_buffer_tofrom_bus+0x50/0x118)
[ 37.405548] [<c055a8c4>] (sdioh_buffer_tofrom_bus+0x50/0x118) from [<c055ba14>] (sdioh_request_buffer+0x1e4/0x2ec)
[ 37.405700] [<c055ba14>] (sdioh_request_buffer+0x1e4/0x2ec) from [<c0559d58>] (bcmsdh_recv_buf+0xe4/0x110)
[ 37.405853] [<c0559d58>] (bcmsdh_recv_buf+0xe4/0x110) from [<c057e408>] (dhd_bcmsdh_recv_buf.constprop.8+0x68/0x84)
[ 37.406005] [<c057e408>] (dhd_bcmsdh_recv_buf.constprop.8+0x68/0x84) from [<c0581210>] (dhdsdio_readframes+0xbc8/0x183c)
[ 37.406158] [<c0581210>] (dhdsdio_readframes+0xbc8/0x183c) from [<c0585204>] (dhd_bus_dpc+0xa24/0x1230)
[ 37.406311] [<c0585204>] (dhd_bus_dpc+0xa24/0x1230) from [<c0576b60>] (dhd_dpc_thread+0x108/0x1a0)
[ 37.406402] [<c0576b60>] (dhd_dpc_thread+0x108/0x1a0) from [<c01a3040>] (kthread+0xb0/0xbc)
[ 37.406555] [<c01a3040>] (kthread+0xb0/0xbc) from [<c010673c>] (kernel_thread_exit+0x0/0x8)
[ 37.406677] CPU1: stopping
[ 37.406829] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.406982] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.407135] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c010595c>] (__irq_usr+0x3c/0x60)
[ 37.407196] Exception stack(0xddfa5fb0 to 0xddfa5ff8)
[ 37.407348] 5fa0: 0000001b 12def1c0 00000002 12def000
[ 37.407501] 5fc0: b4284e00 b4283f00 00000014 133087b8 12c15b50 b4284e00 00008001 12e41f00
[ 37.407562] 5fe0: 71111850 acfcb010 b3ebc2d1 b41b125a 000d0030 ffffffff
[ 37.407714] CPU3: stopping
[ 37.407836] [<c010b85c>] (unwind_backtrace+0x0/0xec) from [<c010abc8>] (handle_IPI+0x144/0x238)
[ 37.407989] [<c010abc8>] (handle_IPI+0x144/0x238) from [<c0100554>] (gic_handle_irq+0x138/0x164)
[ 37.408142] [<c0100554>] (gic_handle_irq+0x138/0x164) from [<c010595c>] (__irq_usr+0x3c/0x60)
[ 37.408294] Exception stack(0xdcd71fb0 to 0xdcd71ff8)
[ 37.408386] 1fa0: 00000000 9c747600 00000034 00000034
[ 37.408538] 1fc0: a7b3bc80 a7b3bc80 b42d5140 00000034 9ec9b5b7 9c747600 a7b3bc98 97f33e30
[ 37.408599] 1fe0: 00001002 97f33d30 b409aafb b3ec69b0 200f0030 ffffffff
[ 37.810028] Rebooting in 5 seconds..
[ 42.825500] Going down for restart now
[ 42.825927] msm_restart : clear reset flag
I don't think there is hope for this board anymore :silly:

I got this little guy for cheap and swapped the motherboard into my functional screen, and guess what...everythings working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}