yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] S5Sickness:
I have tried But this is what i get when i run logcat from android studio..... (01-01 00:00:00.000 0-0/? E/Internal: device 'YFGV0815036703' not found) This is while the rom is installed and right after it boots into twrp.

---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------

We might have to wait we need a person that knows what the hell there doing... I do not and don't wanna keep wasting time until then...
[Miscellaneous Android Development] billyboy2316:
Quote:

Originally Posted by Unjustified Dev

First CM build is uploading unless your experienced with adb and familiar with unbricking your device I do not recommend testing.

File name when finished uploading

cm-12.1-20160106-UNOFFICIAL-NXA8QC116.zip

https://www.androidfilehost.com/?w=files&flid=47078

I'm definitely sure it won't boot that's why I built with adb on by default hopefully it makes it that far to debug the boot issue.

To send me a logcat if possible

adb logcat > log.txt

To grab a kernel message if possible

adb shell cat proc/kmsg > kmsg.txt

If it reboots you into recovery that's fine pull last_kmsg while in recovery and upload it

adb pull /proc/last_kmsg

When i tried to do adb logcat. It said it was waiting on device and never did anything. Even after I reinstalled the ROM. As far as the last two commands. It said error unauthorized device. I did each of these commands three times
[Miscellaneous Android Development] S5Sickness:
Here is what i got 3 logs i really hope it helps....http://www.filedropper.com/logs_3
[Miscellaneous Android Development] Unjustified Dev:
Do you get a bootanimation?
[Miscellaneous Android Development] S5Sickness:
No just flashes splash screen twice i get some words with symbols at the bottom and boots to twrp...
[Miscellaneous Android Development] Unjustified Dev:
You didn't pull a last_kmsg from recovery? I only got recovery log which doesn't help. I need to see what the cm ROM kernel said before it panicked and rebooted to recovery.
[Miscellaneous Android Development] S5Sickness:
Please tell me at what point do i get this? while in twrp?
[Miscellaneous Android Development] Unjustified Dev:
After you flashed cm and tried to boot it. You said it flashed and threw you into recovery. Once it does this pull the log. If you fail to pull the log at this point, it won't exist anymore.
[Miscellaneous Android Development] social-design-concepts:
try to snap a picture of the words at the bottom of the screen. that sounds like an error possibly from the efi bootloader.
[Miscellaneous Android Development] S5Sickness:
OK right after twrp boots to menu i will open fastboot cmd and run command (adb pull /proc/last_kmsg) right?
[Miscellaneous Android Development] Unjustified Dev:
adb commands but yes that's right.
[Miscellaneous Android Development] S5Sickness:
OK did it and this is what i got ... (error device unauthorized. please check confirmation dialog on your device) i'm in twrp i know this can't happen as the tab is in twrp..

This is what i did.. did i do something wrong?

Microsoft Windows [Version 10.0.10586]

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James>adb pull /proc/last_kmsg

adb server is out of date. killing...

* daemon started successfully *

error: device unauthorized.

This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

C:\Users\James>
[Miscellaneous Android Development] S5Sickness:
I tried but when i do the text is blurry....video or photo
[Miscellaneous Android Development] Rls4ever12:
A N D R O I D Shell@NXA8QC116 / $ (then a string of numbers 32._______ or 33.___________ it keeps changing) SysRy Emergency remount R/O

(also if I hit volume down it makes./ 126""x5 6"come up in this area)

The 126""x5 =five times
[Miscellaneous Android Development] S5Sickness:
Almost willing to buy one and send it to the dev trien to help use out....
[Miscellaneous Android Development] social-design-concepts:
[MENTION=4911249]Unjustified Dev[/MENTION] , what rom base are you working on?
[Miscellaneous Android Development] Unjustified Dev:
I'm building from source CyanogenMod

I posted my device trees if you want to see if you can pinpoint the issue

https://github.com/TeamRegular
[Miscellaneous Android Development] Rls4ever12:
Stock logcat

This is what you are looking for correct? But this is the stock logcat. I am not sure but could the tablet not being able to accept a pc fingerprint have something to do with not being able to get the log on the cm build
[Miscellaneous Android Development] S5Sickness:
While in twrp the tablet should be open to any command you throw at it without a security so i read...
[Miscellaneous Android Development] Rls4ever12:
Oh ok, correct me if I am wrong but when you had bricked your device and used the nandroid backup the tablet was giving you the same message we are getting now from the cm build the Android she'll message at the bottom of the screen
[Miscellaneous Android Development] Rls4ever12:
S5sickness I believe was bricked I saw it in the how to unbrick thread
[Miscellaneous Android Development] S5Sickness:
cm build will give error and info that stock build will not... Stock build gives totally different log...

cm gave the message stock didn't..
[Miscellaneous Android Development] Rls4ever12:
My mistake
[Miscellaneous Android Development] S5Sickness:
No biggy but lets find a way to get the log file from twrp... You must be in twrp right after you install cm build and it boots into twrp we need to pull the logcat from there..... problem is can't get log file while in twrp we need to figure out why ... i'm all over the net trying to figure this....

---------- Post added at 02:24 AM ---------- Previous post was at 02:16 AM ----------

Ok i have done everything i could... tried to get these file many ways even tried things just to see what would happen and i end up nowhere.. even when in stock i still can't get these files to pull...

BTW i installed cm build at least 20 times today...
[Miscellaneous Android Development] GrapeBandit:
Ok, so i have installed twrp, rooted, disabled encryption, installed memory leak fix, switched the cpu to ondemand/noop, removed all bloat/unwanted apps, and i am just as unimpressed with this device as i was when it stock. Its still slow and laggy as all hell, especially when browsing the internet(Boat HD).:eek:

Does anyone have any hard data or actual test results to prove that all this stuff we are going through to "improve this device" actually makes a difference, and not just placebo effect? :confused:

Is there anything else that could be done so it doesn't feel like im using a Motorola Backflip?

Edit: . . .and christ, is there anything that can be done to raise the volume on this shoddy speaker?
[Miscellaneous Android Development] S5Sickness:
Well we need a person to get logcat file from twrp while cm build is installed so the dev can figure why the cm build won't boot.. and maybe we can get a good rom for this device and fix your problems..
[Miscellaneous Android Development] Rls4ever12:
While in my stock rom the logcat is a piece of cake adb logcat and there it is. Cannot get no command to work in cm. Adb devices and it shows up but won't pull the logcat.
[Miscellaneous Android Development] Rls4ever12:
Also to get the logcat from adb in Stock when I get the waiting on device message I still have to go on the tablet and accept the fingerprint before it Starts or else it stays on the waiting message. So my question is while on cm in twrp how do i get past the waiting on device message?

---------- Post added at 12:24 PM ---------- Previous post was at 12:07 PM ----------

When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
[Miscellaneous Android Development] billyboy2316:
I tried that. If you look at the bottom of post 274 you will see i tried this three times and it still didnt work for me. IDKY?? I accepted the RSA key and still got nothing. I have been messing with this tab trying everything to no avail. I havent posted anything in the last couple of days because I cant get anything to work. Maybe its just me?;) I just tried to pull a log cat again. Didnt work. I restarted adb and this is what it said.

C:\Users\My 2\Desktop\ADB_Fastboot>adb devices

List of devices attached

0123456789ABCDEF unauthorized

IDK if that will help or not??

Are you getting this same error message when trying to pull last kmsg in recovery? ( C:\Users\My 2\Desktop\ADB_Fastboot>adb pull /proc/last_kmsg

error: device unauthorized. Please check the confirmation dialog on your device.
[Miscellaneous Android Development] Rls4ever12:
After using flashify to flash the cm this is the logcat that I got
[Miscellaneous Android Development] vampirefo:
Never mind
[Miscellaneous Android Development] S5Sickness:
This is the best we have got ... lets hope it's what he needs.. good job..... I got the same file.. Not sure if it's the same as yours...

---------- Post added at 03:25 PM ---------- Previous post was at 02:52 PM ----------

Does anyone know why we would get this when trying to get the logcat while in twrp after it reboots from install of cm?

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb logcat

error: device unauthorized. Please check the confirmation dialog on your device.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>?

- waiting for device -
[Miscellaneous Android Development] Rls4ever12:
It is the rsa key. On mine it says waiting on device on cm which it says the same in Stock then when I accept the key it starts logging. There is no way to accept the key in twrp but I am researching how to bypass this.

---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------

http://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb/120453#120453

---------- Post added at 03:40 PM ---------- Previous post was at 03:32 PM ----------

The check confirmation dialog is asking you to accept the key on your device
[Miscellaneous Android Development] S5Sickness:
same here.. playing with android studio... Now i get

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb logcat

adb server is out of date. killing...

* daemon started successfully *

- waiting for device -

---------- Post added at 03:46 PM ---------- Previous post was at 03:41 PM ----------

this is while i'm in cm rom can't accept it...
[Miscellaneous Android Development] Rls4ever12:
I have the same problem trying to figure out how to bypass it now
[Miscellaneous Android Development] Rls4ever12:
Here are the adb keys. Which are in the data/misc files on the tablet
[Miscellaneous Android Development] S5Sickness:
The site you posted said basically take working key from like say a stock rom and replace that with the cm rom key .. If that's what he means...
[Miscellaneous Android Development] Rls4ever12:
I think so. I am just trying everything thing. Away from cpu now but I am going to extract the cm. Then put my key in it.???? Then compress it back again when I get home. My key may not work for yours though after I thought about it. Noob learning from my mistakes.
[Miscellaneous Android Development] S5Sickness:
This is a lost cause .. ima buy me a samsung... seems to have more attention...
[Miscellaneous Android Development] billyboy2316:
Bro, I am willing to brick this device to help. I just don't know what else to do??
[Miscellaneous Android Development] S5Sickness:
it's not your fault.. you have done all that can be done without someone that knows this stuff to answer how the hell do we fix this error when in twrp...
[Miscellaneous Android Development] social-design-concepts:
I edited [MENTION=2472806]vampirefo[/MENTION] deafult.prop in the twrp to set ro.adb.secure=0 to disable the need to authorize adbd for the device in twrp . this should allow you to access the kmsg from adb when the device fails to boot the cm image.

View attachment ro.adb.secure.disabled.twrp.nextbook.zip
[Miscellaneous Android Development] Rls4ever12:
So flash this then flash the cm?
[Miscellaneous Android Development] social-design-concepts:
flash it the same way you flash the original twrp and make sure it boot into recovery and adb works as expected then flash cm.
[Miscellaneous Android Development] S5Sickness:
Did it and this is what i got... Am i doing something wrong?

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb pull /proc/last_kmsg

error: device unauthorized. Please check the confirmation dialog on your device.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>
[Miscellaneous Android Development] vampirefo:
This shouldn't be needed, what I believe is happening just from reading other's , (I guess I could just install the cm rom myself, but lack the desire to mess with my grandson's toy)

Either the rom or boot.img isn't compatible with the tablet, forcing tablet to try and boot from external device, the tablet boots Linux just fine by the way.

What they are seeing is tablet is waiting for keyboard input, without keyboard input tablet boots into recovery, in recovery it not authorized to connect to external device.

Why? Well for one none exist. Have you looked at the ROM? Is the rom Intel not arm? Is it complied for 64 bit?
[Miscellaneous Android Development] social-design-concepts:
if they wipe data after installing the ROM wouldn't the adb_key get wiped? if ro.adb.secure=1 the device shouldn't allow adb access as it can't copy adb_key from data to the root of the ram disk to authorize the pc for adb access?

ANDROID..... msg at the bottom comes from init, so the cm boot.img is loading but crashing early on which the efi bootloader boot logic is set to fail back to recovery if fail to boot boot.img
[Miscellaneous Android Development] vampirefo:
No recovery will allow adb even without an OS, they could wipe data and system and still have adb access.
[Miscellaneous Android Development] social-design-concepts:
from the adb unauthorized message that doesn't sound like the case.
[Miscellaneous Android Development] vampirefo:
They only received that message cause of cm, if they don't install cm use stock rom, boot into recovery wipe everything they will still have adb access, they lose adb access when they install cm and the BIOS forces the tablet to boot from external device.

Cm is forcing bios to choice another boot source none exist, recovery is still caught in same loop, so it ask for access to external device which doesn't exist.

The loop continues until a compatible os and or boot.img is installed.
[Miscellaneous Android Development] S5Sickness:
OK so after all the high tech lingo... Is this going to work? also can i rename this file to let's say twrp_recovery? i tried to use the file how it is now but i got this...

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb reboot bootloader

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot boot boot.img

downloading 'boot.img'...

OKAY [ 0.286s]

booting...

OKAY [ 0.034s]

finished. total time: 0.320s

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot flash recovery ro.adb.secure.disabled.twrp.nextbook.img

target reported max download size of 536870912 bytes

error: cannot load 'ro.adb.secure.disabled.twrp.nextbook.img': No error

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot flash ro.adb.secure.disabled.twrp.nextbook.img

unknown partition 'ro.adb.secure.disabled.twrp.nextbook.img'

error: cannot determine image filename for 'ro.adb.secure.disabled.twrp.nextbook.img'

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>
[Miscellaneous Android Development] social-design-concepts:
usb isn't in the logic of the efi bootloader maybe in the logic of the efi firmware but not the bootloader, from what i'm reading the bootloader is jumping to the kernel the kernel is calling init, init is failing somewhere and crashing forcing a reboot, the efilinux ( bootloader ) bootlogic is to fail back to recovery in the event of boot failure so the device boots to twrp.

the boot image should have no effect on twrp they are separate user space environments the only thing i know that cause adbd authorization error is adbd_key not being present in the data partition, when ro.adb.secure is enabled and ro.debuggable=1 twrp copies the adbd_key to the root of the ramdisk to allow adbd access.

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

fastboot flash recovery ro.adb.secure.disabled.twrp.nextbook.img

try to rename the file something shorter
[Miscellaneous Android Development] vampirefo:
I agree the boot.img most likely is fine, I think it's the cm rom it's self, something about it, isn't right.

adb keys in recovery aren't required, unless data partition is encrypted, if these guys refuse to decrypt their data partition? Oh well, LOL.
[Miscellaneous Android Development] S5Sickness:
OK flash had no error i renamed it to twrp_recovery, and flashed went to twrp first flashed then wiped. error then i wiped before flash no errors and this is what i got..

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot boot boot.img

downloading 'boot.img'...

OKAY [ 0.275s]

booting...

OKAY [ 0.035s]

finished. total time: 0.310s

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot flash recovery ro.adb.secure.disabled.twrp.nextbook.img

target reported max download size of 536870912 bytes

error: cannot load 'ro.adb.secure.disabled.twrp.nextbook.img': No error

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot boot boot.img

downloading 'boot.img'...

OKAY [ 0.274s]

booting...

OKAY [ 0.035s]

finished. total time: 0.310s

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>fastboot flash recovery twrp_recovery.img

target reported max download size of 536870912 bytes

sending 'recovery' (15558 KB)...

OKAY [ 0.393s]

writing 'recovery'...

OKAY [ 0.307s]

finished. total time: 0.700s

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb logcat

adb server is out of date. killing...

* daemon started successfully *

- waiting for device -

The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb shell cat proc/kmsg > kmsg.txt

error: device unauthorized. Please check the confirmation dialog on your device.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>

---------- Post added at 10:10 PM ---------- Previous post was at 09:49 PM ----------

How many times do we have to run the decrypt.img? i have no problem doing so but i have done it many times..
[Miscellaneous Android Development] social-design-concepts:
I think the problem is how your doing it, most intel devices don't fully support the fastboot boot command and im not seeing where your rebooting?

try it like this :

fastboot flash recovery twrp_recovery.img
fastboot reboot recovery

/* from twrp wipe data / factory reset the reboot recovery and test adb access then reboot into fastboot */

fastboot flash boot cm_boot.img
fastboot flash system cm_system.img

/* wipe data and cache just to be sure it is clean */
fastboot -w

/* reboot into android */
fastboot continue

if it fails to boot it should auto boot into twrp then :
adb devices

/* if it was properly authorized */
adb pull /proc/last_kmsg

alternatively you can use twrp file manager to copy /proc/last_kmg to the sdcard
[Miscellaneous Android Development] S5Sickness:
My tab is decrypted i'm looking at the setting asking me to turn it on.. Does this not mean that it is decrypted?

---------- Post added at 10:29 PM ---------- Previous post was at 10:20 PM ----------

ok where does the cm_boot.img come in? Ok these files should be installed when i flash cm rom right?
[Miscellaneous Android Development] social-design-concepts:
adb_keys and encryption are completely separate unrelated things. . .

adb_keys need to be hard coded into the recovery.img if the device is encrypted because twrp can't read /data because it's encrypted, if /data is not encrypted then twrp copies the adb_keys from /data, but if /data is formatted - wiped when twrp is booted then the adb_keys can't be copied because they don't exist in turn the device wont be authorized for adb access.
[Miscellaneous Android Development] vampirefo:
Ok , I just formatted data, system, cache, rebooted to recovery have full access to adb, which is exactly what I thought would happen, adb keys aren't needed.
[Miscellaneous Android Development] social-design-concepts:
that's so weird i just set ro.adb.secure=1 and get the un authorized message on my lenovo? is yours a eng , userdebug , or user build of twrp?
[Miscellaneous Android Development] S5Sickness:
The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb devices

List of devices attached

0123456789ABCDEF unauthoriz

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>adb pull /proc/last_kmsg

error: device unauthorized. Please check the confirmation dialog on your device.

C:\Users\James\Desktop\Nocturnal_ADB_Fastboot>
[Miscellaneous Android Development] social-design-concepts:
just uses twrp built in file manager to copy the file to the sdcard then. this adb auth thing is goofy
[Miscellaneous Android Development] S5Sickness:
are adb.exe different from others? i use Nocturnal_ADB_Fastboot and other people use different one's i guess there results are not that same as mine
[Miscellaneous Android Development] social-design-concepts:
vampirefo is using ones he compiled for linux, i use the ones included in the android sdk on windows and Ubuntu's ppa on my build box, the adb platform tools change with each version of android.

my current

C:\Android\sdk\platform-tools>adb version

Android Debug Bridge version 1.0.32

Revision eac51f2bb6a8-android
[Miscellaneous Android Development] vampirefo:
Well, now I am confused, I have 3 recoveries for this device, perhaps the one on my tablet is different from the ones I shared in this thread.

#!/usr/bin/env bash
make clobber
. build/envsetup.sh
lunch aosp_ares-userdebug
make -j4 recoveryimage

vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/nnn$ adb pull /proc/last_kmsg

remote object '/proc/last_kmsg' does not exist

vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop/nnn$ adb shell

~ #

adb logcat > log.txt

http://pastebin.com/1rPvCz3Z

adb shell cat proc/kmsg > kmsg.txt

http://pastebin.com/qR4r4vFL

Now to return the tablet to a 5 year old, that's tapping his foot.
[Miscellaneous Android Development] Rls4ever12:
Thanks
[Miscellaneous Android Development] social-design-concepts:
healthd is failing triggering the reboot recovery
[Miscellaneous Android Development] zerozed99:
Is [MENTION=4911249]Unjustified Dev[/MENTION] still working on porting CM or has the project been abandoned? Although I'd love a CM port, I'd settled for a ROM that was just deodexed and zipaligned.
[Miscellaneous Android Development] S5Sickness:
I think he got bored of waiting for the file he needed...