Develop Bugs

Arnova 10 G2 (RK2918 based tablet)

Hello all
I just bought Archos Arnova 10 G2 few days ago and till now I would say I kinda satisfied with the device. But since we are here on XDA, enjoyment from this device could be even better
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Market in that .zip is veeery old (v1.82) so I put there new version (3.3.11) and it seems to work well too but just until I try to install some app from Market => FC.
I read something about permisions set wrong or some another component/app is not installed or incompatible with Market 3+ (btw, only version working is 1.82 and 3.3.11 -with problems. Another version give my FC during loading).
So, now to the point I managed to get some feedback from LogCat when Market FC:
Code:
D/Finsky ( 1912): [1] DownloadRestarterRule.run: Recovering from Market exit when restoring / downloading assets.
D/Finsky ( 1912): [1] SanityChecker.run: # LocalAssets corrected : 1
D/Finsky ( 1912): Sanity check took : 24 ms
D/Finsky ( 1912): [1] DownloadTickleReceiver.onReceive: Received tickle.
W/Finsky ( 1912): [1] DownloadTickleReceiver.generatePackageProperties: Received refund period time end string : null
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch false)
D/Finsky ( 1912): [1] DownloadTickleReceiver.parseObb: Not generating OBB (patch true)
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing Google Docs.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from null to UNQUEUED.
D/dalvikvm( 1912): GC_CONCURRENT freed 404K, 52% free 2884K/5895K, external 793K/1051K, paused 4ms+3ms
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.google.android.apps.docs added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.google.android.apps.docs from UNQUEUED to QUEUED.
I/installd( 60): free_cache(2618907) avail 195815424
D/Finsky ( 1912): [23] DownloadRecords.initializeAndPrune: Pruned 0 old downloads from the cursor.
D/Finsky ( 1912): [1] DownloadQueueImpl.startDownload: Download com.google.android.apps.docs starting
D/Finsky ( 1912): [1] DownloadRestarter.onPostExecute: Recovering restore of com.stumbleupon.android.app
D/Finsky ( 1912): [1] DownloadRestarter.handleObbResumingOrRestart: No OBB's associated to this asset.
D/Finsky ( 1912): [1] DownloadRestarter.restartAssetDownload: Restarting asset download : com.stumbleupon.android.app
E/DatabaseUtils( 269): Writing exception to parcel
E/DatabaseUtils( 269): java.lang.SecurityException: Invalid value for is_public_api: null
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.enforceAllowedValues(DownloadProvider.java:686)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.checkInsertPermissions(DownloadProvider.java:624)
E/DatabaseUtils( 269): at com.android.providers.downloads.DownloadProvider.insert(DownloadProvider.java:442)
E/DatabaseUtils( 269): at android.content.ContentProvider$Transport.insert(ContentProvider.java:198)
E/DatabaseUtils( 269): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils( 269): at android.os.Binder.execTransact(Binder.java:320)
E/DatabaseUtils( 269): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 1912): threadid=21: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 1912): FATAL EXCEPTION: download-manager-thread
E/AndroidRuntime( 1912): java.lang.SecurityException: Invalid value for is_public_api: null
E/AndroidRuntime( 1912): at android.os.Parcel.readException(Parcel.java:1322)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)
E/AndroidRuntime( 1912): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 1912): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:408)
E/AndroidRuntime( 1912): at android.content.ContentResolver.insert(ContentResolver.java:606)
E/AndroidRuntime( 1912): at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:44)
E/AndroidRuntime( 1912): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 1912): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 1912): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1912): at android.os.HandlerThread.run(HandlerThread.java:60)
D/dalvikvm( 1912): GC_CONCURRENT freed 408K, 51% free 3000K/6023K, external 793K/1051K, paused 4ms+3ms
D/dalvikvm( 79): GC_CONCURRENT freed 1041K, 49% free 5163K/10055K, external 1908K/1998K, paused 3ms+12ms
D/dalvikvm( 1912): GC_CONCURRENT freed 540K, 52% free 2994K/6151K, external 793K/1051K, paused 3ms+9ms
D/Finsky ( 1912): [1] Installer.downloadAndInstallAsset: Downloading and installing StumbleUpon.
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from null to UNQUEUED.
D/Finsky ( 1912): [1] DownloadQueueImpl.add: Download com.stumbleupon.android.app added to DownloadQueue
D/Finsky ( 1912): [1] DownloadImpl.setState: com.stumbleupon.android.app from UNQUEUED to QUEUED.
D/dalvikvm( 269): GC_EXPLICIT freed 58K, 53% free 2654K/5575K, external 793K/1051K, paused 93ms
I/Process ( 1912): Sending signal. PID: 1912 SIG: 9
W/InputManagerService( 79): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 79): Process com.android.vending (pid 1912) has died.
Can somebody advice me in which direction should I look to fix these errors?
Or another thing, /system is not RW on this device, so every change I do I have to flash whole ROM again :/
I tried these command in Terminal Emulator but without luck:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
Thanks anyone for kick
Regards
Adam

Hi There
I had faced a similar issue this morning. My advise is to install this custom rom and utility 'arctools' to install the google app pack. I did this morning and it worked like a dream.
The link is here
Good luck

Thank for the advice but unfortunatelly I tried put this custom rom to my device for the few times and it just didn't boot (maybe I have some new HW revision?).
But anyway, some guy in the original spanish forum posted updated ROM on page 7 and its working well on my device, only thing missing in RW access on /system

p1ceus said:
I tried to put a custom rom (here) to my device but unfortunatelly I'm not a lucky guy and device didn't boot at all. So I ask uncle Google for help and found this great tool that allowed me to root the tablet easily and put some extra apps into /system/app. I then encounter endless problems with Maket to even get it to work and found a way here (download the attached .zip, copy it to the device and install .apk's in order posted, reboot the device and you have Market and Google apps up and running ). And this is where my problems started to appear...
Click to expand...
Click to collapse
Could you explain what you did with that tool to gain root? Im the thread for the tool it says for step to that I need to "copy the image file into this folder,and rename to wendal.img" What image file do I copy?
I'm not overly concerned about the Market, and I do not want the custom rom that is at arctablet.com because it screws up your storage space among other issues and my tablet work really well right now I just want root. If anyone knows any other ways just to gain root and nothing else it would be greatly appreciated.

Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)

good tablet

p1ceus said:
Hi,
just DL the official ROM from Arnova, rename update.img to wendal.img and thats it. Then run the Runme.bat with option 1 first and then with option 2. When done, copy wendal_new.img to the root of Arnova internal SD and rename it to update.img before disconnection the USB. After the flash, you should have root (but its just a partial since you cannot write to system parititon :/)
Click to expand...
Click to collapse
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??

sdunne said:
Any idea if this procedure leaves one able to
1) Use marketenabler to access amazon usa &
2) get a root prompt via terminal ??
Click to expand...
Click to collapse
I was able to use the Amazon Appstore if that's what you're talking about. I also have Root Explorer, Titanium Backup, and Rom Toolbox running and get the SU prompt but haven't tried from a Terminal.
Sent from my PC36100 using xda premium

Well I have the R29xxImageTools v2.1, the Rockchip_Batch tools v1.4 and the Setup_google_app.rar file.
I've exploded the original update.img, overlaid system with the 4 subdirs from within the google rar and repacked the image, renamed the wendal_new.img to update.img and reflashed it.
Tablet just sits at arnova splash screen after a yellow recovery message. (this is the same message whether the flash ultimately works or not)
If I don't hack around with the exploded system image, other than what the lua script does itself then the tablet reflashes successfully and comes up, albeit with a non functioning marketplace.
Any idea what I'm doing wrong ??

Hi, try different gapps. It happend to me also, then I DL different zip with google apps and it was working.

try this rom with arctool v0.57 http://www.arctablet.com/blog/forum/arnova-10-g2/arnova-10-g2-improved-custom-firmware-update/

Anybody know how many mAmps the battery is on the Arnova 10 G2? I'm trying to better calibrate Battery Left Pro widget.

finless bob version 1.3
here is version 1.3 by finless bob
http://dl.dropbox.com/u/17806868/arnova10g2_v1_3_market.zip
how to install can be found here
http://www.freaktab.com/showthread....stom-ROM-by-Finless-Version-1-3&p=428#post428

finless bob version 1.3
please delete

another rom arnova 10 g2
http://www.arctablet.com/blog/archos...d-app-storage/
use arctools 0.57 to install google apps
http://www.multiupload.co.uk/EA51XONM9S link for arctools 0.57

I wonder how we can get finless to come over to xda?

laserman123 said:
I wonder how we can get finless to come over to xda?
Click to expand...
Click to collapse
Finless wants to stick to his site, since he supports several different machines, but is okay with us redirecting those looking for his ROMs there.
His current ROM is 1.4, includes the tools for flashing it and the marketplace and all gapps, and is located here. It is currently my daily on the tablet.

I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob

nice to see you on here finlessbob, nice rom you have made i am using it myself.
I also have to add it actually makes a base tablet run really great, plus the arnova hase some good connection capabilities that more expensive tablets lack.
Just need an arnova 10g2 section in development now to make things perfect

finlessbob said:
I am actually a good member here on XDA. So I am here.
Feel free to ask quetions
Bob
Click to expand...
Click to collapse
Hello bob. I've just bought a arnova preloaded with your rom however I'm unsure of the version of atm I'm without a computer.
Basically I've installed magic locker on the device but now everytime I boot I get FC on magic locker and cannot get past the screen.
I've tried to factory reset but it sends me into recovery and I cannot select any options.
I just wanted to know if I could fix this without a computer?
Join me on dropbox http://db.tt/aijaD3Wr
Follow me on Twitter _H88RRY_

Two 4.4 Roms i didn't see around here

As most of you probably are, ever since i've tried CM11, i've been searching for a "stable" KitKat rom. Didn't have much luck, but i thought i'll share my findings
First up is Gummy Rom from Team Gummy, which i didn't even see in the Android Development subforum. They're doing nightlies for the P930, but seem to have some problems right now, as the last nightly is dated 01-05-2014. You can check those out at
http://old.androidfilehost.com/main/Team_Gummy/p930/nightly/
Second one is MoKee, of which navik did a 4.3 build, but they also have KitKat nightlies for the P930.
http://download.mfunz.com/?device=p930
On to what you'll probably want to know.. do these roms work? well... kinda...
The MoKee "Release" from 01-18-2014 is pretty stable, fast and has some neat additions from CM and (possibly) AOKP. You can even finally restore your backups from Titanium, as MoKee lets you choose where to install (!) an apk... change that to internal from default and ALL apps install correctly like they should. Now for the downside... you can probably guess... yup, camera's broken *sad face panda*... you can start up any cam-app and it will show the image from the sensor, but as soon as you take a shot, it will FC and save a 2KB file in your DCIM folder...
oh, and it has some chinese crapware (baidu) installed, but you can easily remove these with Titanium Backup.
On to the second Rom... Gummy Rom from Team Gummy...it's a lean build based on AOSP with a few picks from CM, AOKP and PA, mostly visual stuff from aokp (center clock etc.) and HALO/PIE from PA. It's helluvalot fast and after a quick adb push for the newest adreno drivers, i can even play Asphalt 8 on High Details. Downside on this rom... apk install error galore, no XDA-app, some games don't install, browser crashes often, absolutely not a daily driver...
have fun experimenting, have you found something else? would like to know ^^

thanks for ur support and is like no much user+dev on this device! threads emty to compere to other devices....
dreaming of getting another device:crying:

I will have to try the later one myself, thanks for posting the info. The biggest issue is that cm is not stable so anything built on that rom is bound to have issues. Most people are sticking with jb for the time being until a better KitKat is available.
As far as activity on this forum, this is not a nexus device but it does have a fair following.
Sent using XDA Premium HD app
Nz

I thought I would look at the Mokee kernel, so the camera errors out like
Code:
I/QualcommCameraHardware( 147): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 147): stopPreviewInternal X: 0
V/QualcommCameraHardware( 147): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 147): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 147): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 147): ION allocation failed
E/QualcommCameraHardware( 147): do_mmap: Open device /dev/pmem_smipool failed!
E/QualcommCameraHardware( 147): ERROR : initraw , createSnapshotMemory failed
E/QualcommCameraHardware( 147): initRaw failed. Not taking picture.
E/CAM_AndroidCameraManagerImpl( 3247): take picture failed.
W/dalvikvm( 3247): threadid=16: thread exiting with uncaught exception (group=0x4156ec80)
E/AndroidRuntime( 3247): FATAL EXCEPTION: Camera Handler Thread
E/AndroidRuntime( 3247): Process: com.android.camera2, PID: 3247
E/AndroidRuntime( 3247): java.lang.RuntimeException: takePicture failed
A good picture taken with CM11 looks like
Code:
I/QualcommCameraHardware( 146): stopPreviewInternal: old frame thread completed.
I/QualcommCameraHardware( 146): stopPreviewInternal X: 0
V/QualcommCameraHardware( 146): updatePictureDimension: 3264x2448 <- 960x720
V/QualcommCameraHardware( 146): initRaw E: picture size=3264x2448
V/QualcommCameraHardware( 146): initRaw: initializing mRawHeap.
E/QualcommCameraHardware( 146): bool android::QualcommCameraHardware::createSnapshotMemory(int, int, bool, int) Raw memory index: 0 , fd is 67
E/QualcommCameraHardware( 146): Received following info for raw mapped data:0x44840000,handle:0x121eb48, size:11985408,release:0x405d6941
E/QualcommCameraHardware( 146): Registering buffer 0 with fd :67 with kernel
V/QualcommCameraHardware( 146): use_all_chnls = 0
As you can see the "ION allocation failed" is the obvious fail point, now where that is logged is the next big secret.. qcom/camera/qcamera2/hal/QCameraMemory.cpp has a log with the message in it, but changing the message seems to have no affect..
Other things I have tried, I have tried compiling the mokee with the hardware and kernel folders from CM11 - the camera still fails, so it must be with the device / vendor folders.
nz

[Q] Rom Bootlooping cause of systemservice SIGABRT

Hi Guys,
I'm trying to port to Android 5.0 to a new device (BQ Aquaris E5 4G) and I can't make it fully boot. I'm always hitting this error :
Code:
pid: 634, tid: 634, name: servicemanager >>> /system/bin/servicemanager <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I can't give you ADB Logcat as logcat doesn't seams to work (adb works fine, I can browse adb shell and so on). It kept giving me this error : "logcat read failure: No such file or directory"
The only thing I've got is some tombstone files witch all look similar (please see one attached)
If you could give me an hint that would be great
I tried to change the kernel also but everytime I boot it (using fastboot boot newboot.img) I get a dark blinking screen.
Thanks and merry christmas!

Thread closed as duplicated with https://forum.xda-developers.com/android/help/rom-bootlooping-cause-systemservice-t2984083

LG G3 D855 Wifi authentication problem with CM 12.1 - supplicant connection error ?

Hello everybody,
i'm new to this board as a poster, but been reading over the last ~ 10 years.
I've been searching here (and about everywhere) else for my problem and tried every suggested solution - even putting it in the fridge or restarting it during full moon reciting the most popular quotes from Linus Torvalds backwards... nothing worked. So you guys and girls are my last resort...
I am running Cyanogen Mod 12.1 (most actual nightly builds) on a LG G3 (d855) phone.
Problem:
After scanning for APs, mine (or the ones i have credentials to) are found, but i can't connect. It tells me "Authentication error".
As being an android developer myself i also tried to dig in. According to logcat the following happens after i activate wifi (with filter for "error"):
Code:
11-12 17:59:43.899 814-1537/? E/WifiService﹕ Invoking mWifiStateMachine.setWifiEnabled
11-12 17:59:44.718 814-1079/? E/WifiMonitor﹕ killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
11-12 17:59:44.733 814-1079/? E/WifiHW﹕ Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
11-12 17:59:44.865 814-1079/? E/WifiConfigStore﹕ Error parsing configuration: java.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
11-12 17:59:44.874 814-1079/? E/WifiHAL﹕ virtual int WifiVendorCommand::create() ifindex obtained:30
11-12 17:59:44.874 814-1079/? E/WifiHAL﹕ virtual int WifiVendorCommand::set_iface_id(const char*) ifindex obtained:30
11-12 17:59:44.875 814-1079/? E/WifiHAL﹕ wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-524
11-12 17:59:44.890 814-1093/? E/WifiHAL﹕ wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
11-12 17:59:44.890 814-1093/? E/WifiScanningService﹕ could not get scan capabilities
11-12 17:59:49.005 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 104, 107 -> obsolete
11-12 17:59:49.008 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 105, 107 -> obsolete
11-12 17:59:54.899 814-1079/? E/WifiStateMachine﹕ WifiStateMachine Disconnected CMD_START_SCAN source -2 106, 107 -> obsolete
11-12 18:00:07.046 814-1079/? E/WifiConfigStore﹕ rewrite network history for "ch4os"-WPA_PSK
After deactivation:
Code:
11-12 18:00:51.844 814-1789/? E/WifiService﹕ Invoking mWifiStateMachine.setWifiEnabled
11-12 18:00:51.869 814-1079/? E/WifiStateMachine﹕ Unexpected BatchedScanResults :null
11-12 18:00:51.885 814-1079/? E/WifiStateMachine﹕ SupplicantStoppingState: stopSupplicant init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
This error appeared without any direct cause but COULD be related to an update to the most recent nightly, i haven't tried wifi for ~ 1 day after updating.
What i did for solving this problem:
Complete Wipe (Factory reset / advanced wipe using TWPR)
Trying another wifi config on the router (works fine for other devices)
The superstitious deactivate-wifi/airplane mode/restart/re-activate wifi without deactivating airplane mode
Note: after this it worked for like 5 seconds; was not reproducable afterwards
Putting it in the fridge, restarting and trying again
Ensuring wpa_supplicant.conf in /data/misc/wifi/ has permission system:wifi or wifi:wifi and chmod 660 (rw-rw----)
Deleting wpa_supplicant.conf
IMHO is this issue not related to my settings, because it even did not work after a full wipe.
This just does not make any sense to me anymore... Any suggestion is very much appreciated!
Kind regards

"Welcome" Screen of ROM Fails to Respond to Touch

I rooted my SGH-T999, running Android 4.3, flashing TWRP recovery w/ Odin.
The rooting was successful.
Now, on to the part where I ran into trouble.
Problem: I can't successfully install any ROMs for Android M or later.
NOTE: I need Android M or later to have more control over individual apps' permissions.
I tried to flash Pac-ROM through TWRP, like so:
(from TWRP home menu)
1. Wipe>Swipe to Factory Reset
2. Go Back to Home Menu
3. Install>Select pac_d2tmo_MM.Beta.Official_20160920-165602.zip>Swipe to confirm Flash
Note: The first time I tried to flash Pac-ROM, I wasn't aware of GApps. So, I didn't flash it.
4. Reboot
The phone booted to the "Welcome/Language Selection" screen, but I couldn't select a language.
It seems that the UI elements belonging to the "Welcome" screen fail to respond to touch, while other UI elements respond normally (as demonstrated at the end of the video at the URL below).
All attempts to re-flash, since, have included the additional step off adding the GApps zip (for ARM, Android 6.0) to the "ZIP Queue".
However, all attempts end the same way.
I've documented the process in the video @ the following URL: youtu.be/EZTwaURkRSs
Another strange behavior (that isn't apparent in the video) is that, immediately after being shown on the display, the "Welcome" screen looks fine for a few hundred milliseconds or so before the screen is drawn with a yellowish-hue. As if blue-light filtering kicks in (even when the system clock is mid-day).
I also tried to flash a different ROM (Oct-OS OCT-M-R3) on a few of the attempts, but again I observed the same exact behavior ("Welcome" screen's yellowish hue and lack of response to touch).
It doesn't seem to be a hardware issue, because touch does work, just not on the "Welcome" screen.
I'm fairly certain I've selected the correct ROM for the model.
So, what did I mess up?

I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again

andynoob said:
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
Click to expand...
Click to collapse
Do you mean that you were able to flash a ROM successfully, after flashing stock (4.4.2)?
Or, you were ONLY able to flash stock (4.4.2) successfully?
Thank you for the reply,
Gerald

I just restored my twrp backup of stock os .. Had urgent work so couldn't try to flash those ROMs again.. will try them next week

UPDATE:
So, I successfully restored my stock backup.
With the stock setup I experienced no problems.
Since my original post, I've alternated between restoring stock backup and flashing ROMs.
I tried flashing Oct-OS and Pac-ROM, again and again.
I also tried to install LineageOS, as well.
I am able to install CyanogenMod 12.1, but this doesn't meet my requirement of android version 6 or later.
Installation of any of the custom ROMs has resulted in the same behavior demonstrated in the video (youtu.be/EZTwaURkRSs):
- after boot, device fails to respond to touch input
- however, device does accept touch input on some UI objects. so, I don't think it's a screen/hardware issue
How can I debug further?
I'd like to try to capture some sort of boot log, but adb is "offline" during boot process.
And, since I can't make it past the "language selection/welcome" screen, I can't get to settings and enable USB debugging.

UPDATE:
I managed to enable ADB during boot, by using the ADB shell while the device was in recovery mode.
Code:
[email protected] ~ $ adb push ~/.android/adbkey.pub /data/misc/adb/
[email protected] ~ $ adb shell
~# cd /data/misc/adb/
/data/misc/adb# cat adbkey.pub > adb_keys
/data/misc/adb# cd /
~# mkdir /system2
~# mount -o rw /dev/block/mmcblk0p14 /system2 ## NOTE: for this command, had to figure out which partition was the system partition; here it was /dev/block/mmcblk0p14
~# echo "persist.service.adb.enable=1" >> default.prop
~# echo "persist.service.debuggable=1" >> default.prop
~# echo "persist.sys.usb.config=mtp,adb" >> default.prop
~# echo "persist.service.adb.enable=1" >> /system2/build.prop
~# echo "persist.service.debuggable=1" >> /system2/build.prop
~# echo "persist.sys.usb.config=mtp,adb" >> /system2/build.prop
~# ## now press Ctrl-D to exit the ADB shell
NOTE: thanks to @ErnestChia for the following post forum.xda-developers.com/showpost.php?p=63829295&postcount=27
So, I was able to get a logcat during the SetupWizard.
There were 3 lines, related to the SystemUI, that were repeated over and over.
Code:
W BroadcastQueue: Timeout of broadcast BroadcastRecord{51dfd23 u-1 android.intent.action.TIME_TICK} - [email protected], started 10010ms ago
W BroadcastQueue: Receiver during timeout: BroadcastFilter{a4079bf u0 ReceiverList{4b103de 730 com.android.systemui/10018/u0 remote:448f719}}
I ActivityManager: Skipping duplicate ANR: ProcessRecord{768d889 730:com.android.systemui/u0a18} Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
All I've gathered is that SystemUI isn't responding.
Which seems to have started during boot, with the following output.
Code:
W ActivityManager: Timeout executing service: ServiceRecord{dd2251a u0 com.android.systemui/.ImageWallpaper}
E ActivityManager: ANR in com.android.systemui
E ActivityManager: Reason: executing service com.android.systemui/.ImageWallpaper
E ActivityManager: 4.1% 730/com.android.systemui: 2.2% user + 1.8% kernel / faults: 1246 minor 2 major
SystemUI Stack Trace
Code:
Cmd line: com.android.systemui
Build fingerprint: 'samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys'
ABI: 'arm'
Build type: optimized
Zygote loaded classes=3986 post zygote classes=991
Intern table: 46441 strong; 62 weak
JNI: CheckJNI is off; globals=427 (plus 368 weak)
Libraries: /system/lib/libandroid.so /system/lib/libcompiler_rt.so /system/lib/libjavacrypto.so /system/lib/libjnigraphics.so /system/lib/libmedia_jni.so /system/lib/libsoundpool.so /system/lib/libwebviewchromium_loader.so libjavacore.so (8)
Heap: 5% free, 12MB/13MB; 84371 objects
Dumping cumulative Gc timings
Total number of allocations 84371
Total bytes allocated 12MB
Total bytes freed 0B
Free memory 813KB
Free memory until GC 813KB
Free memory until OOME 179MB
Total memory 13MB
Max memory 192MB
Zygote space size 1972KB
Total mutator paused time: 0
Total time waiting for GC to complete: 0
Total GC count: 0
Total GC time: 0
Total blocking GC count: 0
Total blocking GC time: 0
...
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x745992a0 self=0xb77f9b30
| sysTid=730 nice=0 cgrp=default sched=0/0 handle=0xb6efab44
| state=S schedstat=( 0 0 0 ) utm=64 stm=14 core=1 HZ=100
| stack=0xbe5d0000-0xbe5d2000 stackSize=8MB
| held mutexes=
native: #00 pc 0004290c /system/lib/libc.so (__ioctl+8)
native: #01 pc 00049391 /system/lib/libc.so (ioctl+14)
native: #02 pc 0001e8c9 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
native: #03 pc 0001eefb /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
native: #04 pc 0001f0b1 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
native: #05 pc 0001a0b3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
native: #06 pc 00089471 /system/lib/libandroid_runtime.so (???)
native: #07 pc 00db9189 /data/dalvik-cache/arm/[email protected]@boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative(Native method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:421)
at java.lang.reflect.Method.invoke!(Native method)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:80)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at android.hardware.ICameraService.getCameraCharacteristics(ICameraService.java:-2)
at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:635)
at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:99)
- locked <0x0da89d30> (a java.lang.Object)
at com.android.systemui.statusbar.policy.FlashlightController.getCameraId(FlashlightController.java:126)
at com.android.systemui.statusbar.policy.FlashlightController.<init>(FlashlightController.java:62)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1087)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3285)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3281)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:619)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:800)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:230)
at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java:-1)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke!(Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

i solved this issue by flashing the pac rom 6.0 from at&t . (Flash only the rom )

Do you have a copy of carbon ROM or Pac man for the d2tmo?