Database Users

[Q] Nexus 4, USB Debugging with a cracked screen

Right I have UK Nexus 4, running 4.2.2, Developer Mode is enabled, but USB Debugging is not, it is not rooted.
How can I enable USB Debugging mode, without wiping everything on the phone as I need to use a program called MoboRobo before I wipe the phone (I need to backup messages, bookmarks and contacts)
I can't see anything on the screen at all, so if you are able to help and tell me I need to boot into Recovery mode, then pick an option I need to know how many times to press up or down, this is purely as I can't see a single thing on the screen at all.
I've been trying to follow this: http://forum.xda-developers.com/showthread.php?t=2177440
But I've no idea if that's correct for what I need to do (purely enable USB Debugging mode without wiping what's already on the phone)
Sorry if this has been covered, I've tried to search but the only thing that came close was a Nexus 7 where the user could still see the whole screen.

Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?

Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
1] No
2] No
3] No

JuicedToday said:
1] No
2] No
3] No
Click to expand...
Click to collapse
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Click to expand...
Click to collapse
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.

Johmama said:
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Click to expand...
Click to collapse
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture 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 use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.

JuicedToday said:
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
Click to expand...
Click to collapse
Ok, let's try eliminating possible reasons for your phone not showing up. Try re-entering recovery mode with the steps I provided above, in case it didn't work. I know this will sound stupid, but it's worked for me in the past: try switching which port on your computer that your USB cable is plugged in to. Try a different cable altogether if you have a spare. Oh, make sure you're using a USB 2.0 cable/plug. Sometimes MTP doesn't play nicely and you need to do weird things to get it working.
I've gathered a few database file locations that you might be interested in. I *think* they are correct anyway. I pulled them onto my computer but I can't try to view them right now, it'd have to be this weekend when I could get around to it, as I'm moving and I'd need to get settled first (Internet up and whatnot). I can still help you troubleshoot adb though.
SMS:
/data/data/com.android.providers.telephony/databases/mmssms.db
Click to expand...
Click to collapse
Contacts
/data/data/com.android.providers.contacts/databases/contacts2.db
Click to expand...
Click to collapse
Browser (I'm not exactly sure which browser)
/data/data/com.android.browser/databases/browser.db
Click to expand...
Click to collapse
Once adb is up and running, you'd use these commands to pull the .db file onto your computer:
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Code:
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
Code:
adb pull /data/data/com.android.browser/databases/browser.db
Those would pull the .db files onto your computer inside of the platform-tools folder. Again, I'm not sure about this, and can't confirm till later in the weekend, but I think to view those on your computer you can download SQLite from here. More importantly, I assume you can just put those .db files into the proper folders on your new phone to restore them. You'd have to figure out the correct folder location depending on your new device, as the manufacturer or carrier sometimes switches them.

Still getting nothing showing under adb devices even after trying several USB ports with a couple of various data cables.
Think it's a lost cause! Guess I'll just have to plump for the screen when I can afford it. Or swap the screen over on my insurance replacement enable USB Debugging then swap the screen back.
Other option would be to sell my replacement, buy the screen and still have a few quid left over.. Choices choices!
Thanks for taking the time and effort though, appreciate it.

Just thought I'd give this one last try. The data at this point isn't of any concern. I need to wipe everything that is on the phone, if that means the OS as well, then that's fine.
Is there a way I can remove my apps, data, messages etc via USB cable without USB Debugging being enabled?
Thank you for your time.:good:

cracked scereen, tried command, debugging alreadfy enabled. says devivce offline. is that because i have no SIM in it>?

Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.

ji_mestone said:
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
Click to expand...
Click to collapse
Looks like you're hijacking this thread, but just because I'm currently fighting a similar situation...
you can download the recovery image for CWM at http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-mako.img
and then reboot to bootloader, run "fastboot flash recovery cwm.img" (using the file you just downloaded, i usually just drag and drop onto cmd line)
That will get you the recovery installed that will be useful because you don't have to touch the screen.
After that, It's as simple as selecting wipe all. if you can't see the screen, then you'll have to do these steps (after installing CWM):
hold Vol- and Power until it turns off, then keep holding Vol- and push power again.
down, down, power - boots into recovery
down, down, power - gets you to wipe/factory reset page
down x 7, power - confirms wiping all data

Magisk root best bloat-removal option?

Hi
Almost just a week into my first Moto phone. Paid high for it and rejected a reasonable Huawei that was 25% cheaper because they stopped allowing boot unlocking.
Very impressed so far. Hardware is great although the sleek packaging, whilst feels nice, has me ****scared until the case I've coming in the mail (cannot buy accessories off the shelf in my area, much to my dismay) arrives.
I've seen the impressive 5-post articles by Explorer 4x4. They were a big factor in my choice to pay the extra cash for this phone.
Alas I'm a little nervously unsure of my next step.
Mainly I'd like to freeze / stop / possibly uninstall the bloatware I don't want.
What is the best full backup option, is it still Nandroid?
After that, is a Magisk root the safest / cleanest option to allow me to clean out that bloat I don't want?
Would appreciate any constructive advice.
Thanks

Yes well, you seem to have previous experience in routing and de-bloating, so
1) Backup all apps with titanium backup or similar (I use titanium)
2) remove bloatware with titanium, system app remover or sd maid or the method of your choice. SD maid is good with removing remnants too.
So, nothing special in regards to previous versions. If you're about to remove some system apps, please check XDA forums if something has changed in that aspect. I have removed the ones that I always remove.

Nandroids will not work on pie due to encryption issues(for now) but Google backups will and you can backup and restore apps+data with TiBu too. Migrate is in beta stages but looks promising. Unlike TiBu it also backups app permissions.
Sent from my Moto G6 Plus using XDA Labs

https://forum.xda-developers.com/g6-plus/themes/debloated-os-t3861046

Xplorer4x4 said:
Nandroid will not work on Pie due to encryption issues (for now) but Google backups will and you can backup and restore apps+data with TiBu too. Migrate is in beta stages but looks promising. Unlike TiBu it also backups app permissions.
Click to expand...
Click to collapse
Thanks! Have never heard of TiBu. How do I find that as a search here and a Google search did not return useful results. Google Play?

weazie said:
Yes well, you seem to have previous experience in routing and de-bloating, so
1) Backup all apps with titanium backup or similar (I use titanium)
2) remove bloatware with titanium, system app remover or sd maid or the method of your choice. SD maid is good with removing remnants too.
So, nothing special in regards to previous versions. If you're about to remove some system apps, please check XDA forums if something has changed in that aspect. I have removed the ones that I always remove.
Click to expand...
Click to collapse
Thanks!
Unfortunately I've fallen at the first hurdle / attempt. I'm unable to unlock the bootloader, let alone get root:
Code:
fastboot oem get_unlock_data
... just hangs without returning anything despite having toggled 'OEM Unlock' in Developer options.

jandroidian said:
Thanks!
Unfortunately I've fallen at the first hurdle / attempt. I'm unable to unlock the bootloader, let alone get root:
Code:
fastboot oem get_unlock_data
... just hangs without returning anything despite having toggled 'OEM Unlock' in Developer options.
Click to expand...
Click to collapse
Are you able to boot into bootloader? Does 'fastboot devices' show your device? Hint: Don't paste your IMEI here.
---------- Post added at 17:51 ---------- Previous post was at 17:47 ----------
jandroidian said:
Thanks! Have never heard of TiBu. How do I find that as a search here and a Google search did not return useful results. Google Play?
Click to expand...
Click to collapse
TiBu = Titanium Backup

weazie said:
Are you able to boot into bootloader? Does 'fastboot devices' show your device? Hint: Don't paste your IMEI here.
---------- Post added at 17:51 ---------- Previous post was at 17:47 ----------
TiBu = Titanium Backup
Click to expand...
Click to collapse
Ah, had a suspicion it was a shortening for Titanium but it was too late at night for my brain to decode it
Yes, `fastboot devices` returns the device serial number and then the word fastboot.
I can also see the fastboot oem get_unlock_data command sent to the device via a line in the bootloader logs screen:
cmd: oem get_unlock_data
Click to expand...
Click to collapse
... however after several minutes, it's just hung. Tried the --verbose flag and still nothing :
{
"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"
}

jandroidian said:
I can also see the fastboot oem get_unlock_data command sent to the device via a line in the bootloader logs screen:
... however after several minutes, it's just hung. Tried the --verbose flag and still nothing :
Click to expand...
Click to collapse
- Do You have the Motorola Drivers installed?
- Are You running the cmd in administrator mode? Try also Windows Powershell.
Other than that, I can't think of anything right now. Many people seem to have had this problem in older moto phones, but I didn't find a solution. Some user mentioned in Youtube comments that "this problem can be solved by jtag software, replacing bootloader" altogether. But sounds like a drastic solution.

weazie said:
- Do You have the Motorola Drivers installed?
Click to expand...
Click to collapse
Yes. Installed them. Latest version I believe.
weazie said:
- Are You running the cmd in administrator mode?
Click to expand...
Click to collapse
Yes, originally probably not but I tried this on instinct but no difference, unfortunately.
weazie said:
Try also Windows Powershell.
Click to expand...
Click to collapse
Just tried this, unfortunately no difference.
weazie said:
Other than that, I can't think of anything right now. Many people seem to have had this problem in older moto phones, but I didn't find a solution. Some user mentioned in Youtube comments that "this problem can be solved by jtag software, replacing bootloader" altogether. But sounds like a drastic solution.
Click to expand...
Click to collapse
Thanks for scratching the old noggin for me.
Personally I'm unfamiliar with JTAG other than just seeing the acronym here and there. So would be an even more drastic solution for me ?
I was wondering if it would potentially have anything to do with me disabling some of the Moto apps. Doesn't seem likely given it's fastboot mode I'm writing in, rather than full blown Android.

jandroidian said:
I was wondering if it would potentially have anything to do with me disabling some of the Moto apps.
Click to expand...
Click to collapse
No, that doesn't affect the thing you're trying to do.

Thought I had a handle on a possible solution:
- Remove a universal ADB driver (clockworkmod) I had installed from way back in the day
- Remove a Google generic driver
- Reinstall (repair) Motorola drivers
- Reinstall ADB fastboot
- Reboot laptop
Nothing ??
Settings, System, Developer options, OEM unlocking (Allow the bootloader to be unlocked): On
Hmmmm
Is it possible this is something to do with the phone's regional designation? Maybe Motorola do not allow unlocking in my region.
Or perhaps it's something to do with the latest software. I did update the phone. Silly me, I still feel updates are often good for security and forget how often features get corrupted or removed these days.

jandroidian said:
Thought I had a handle on a possible solution:
- Remove a universal ADB driver (clockworkmod) I had installed from way back in the day
- Remove a Google generic driver
- Reinstall (repair) Motorola drivers
- Reinstall ADB fastboot
- Reboot laptop
Nothing ??
Click to expand...
Click to collapse
You are on the right track here. Clean out everything from device manager that could possibly conflict, begin from a clean slate (including SDK, adb, fastboot installation) and follow @Xplorer4x4's instructions to the letter. I know it's frustrating, but if that doesn't helplet's think of other solutions. By the way, there are two methods to install the Moto Drivers. One seems to install just the driver (v.6.40 for me) and the other the Moto Device Manager (2.5.4). I did install just the driver.

weazie said:
You are on the right track here. Clean out everything from device manager that could possibly conflict, begin from a clean slate (including SDK, adb, fastboot installation) and follow @Xplorer4x4's instructions to the letter. I know it's frustrating, but if that doesn't helplet's think of other solutions. By the way, there are two methods to install the Moto Drivers. One seems to install just the driver (v.6.40 for me) and the other the Moto Device Manager (2.5.4). I did install just the driver.
Click to expand...
Click to collapse
Thanks for your support. Again, thought I might have had a handle on it: USB debugging was off. Enabled it, no difference.
Back to the history a little (not in chronological order):
- Removed Universal ADB driver:
- Drivers came from here:
https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
I used the 64 bit version, not the 32.
- ADB and fastboot installer from here:
https://raw.githubusercontent.com/h...ster/versions/adb_fastboot_installer-1.2s.exe
When I installed / ran Motorola Device Manager, I expected some visible GUI software but I guess I must have had the wrong expectations because all it has ever done is run one single dialog that checks for newer software for the phone and fails. I posted that in a different thread.
Aside from not starting from a clean Windows install, I think I did follow Explorer's method. But I'm not perfect though neither is Motorola, seemingly
I guess I'll uninstall the Motorola stuff and try to start from a cleaner Windows install. Hell, maybe even starting in Safe Mode might be easier.

jandroidian said:
I guess I'll uninstall the Motorola stuff and try to start from a cleaner Windows install. Hell, maybe even starting in Safe Mode might be easier.
Click to expand...
Click to collapse
Yes You're doing it exactly like I was. Hmm.

weazie said:
Yes You're doing it exactly like I was. Hmm.
Click to expand...
Click to collapse
Well, the plot sickens, it seems.
Yet again, thought I was possibly on to a solution. Found these:
Previous / temporary phones there. Uninstall those devices and surely I'm right? Nope.
Then, re-installed the 64 bit drivers. Surely that will take care of these:
Nope
Now I'm in this exact situation that the uninstalling of Motorola Device Manager 2.5.4 warned me about:
So it would see that perhaps the Motorola Device Manager, which I have not re-installed, is actually needed for drivers. I'm not even convinced the files in this zip:
https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
are actually legit at all. I decompressed the 64 bit MSI file and it doesn't look like any driver files I've seen before. No .inf files for one thing.

jandroidian said:
So it would see that perhaps the Motorola Device Manager, which I have not re-installed, is actually needed for drivers.
Click to expand...
Click to collapse
I think it is not needed as I don't have it installed. What's peculiar is that I probably did the same installation as you, but my device tree looks like this:
And I don't remember ever installing LeEco device drivers? Now I'm just confusing You more.

weazie said:
I think it is not needed as I don't have it installed. What's peculiar is that I probably did the same installation as you, but my device tree looks like this:
And I don't remember ever installing LeEco device drivers? Now I'm just confusing You more.
Click to expand...
Click to collapse
Well, it seemed to take an reboot, and installing the Motorola Device Manager (not the other drivers) but I appear to have gone another 2 steps forward and one back.
Now have that but still fastboot oem get_unlock_data hangs
Need to head to bed now (forgot to post, just previewed, last night!). Maybe I will have better luck tomorrow.
Thanks for your kind assistance!

Not sure if it's lacking drivers (and perhaps a reboot) but I've gone from three "Moto g(6) plus" devices listed in Other devices, with yellow exclamation symbols, to the same with question mark symbols.
In both cases the phone is not accessible during general windows use
Will have to keep researching about 4 to 6 hours from now.
UPDATE: re-installing Motorola Device Manager fixed the lack of files access.

I am a bit confused at what your problem is. Not sure fastboot has a verbose switch. I've never had a reason to try.
If everything works now leave as is. If you ha e issues start off by removing all drivers for Moto, and remove adb and fastboot too. Then reboot computer. Install just moto dtivers(moto manager is for older phones and Usless to us other than the drivers) and adb/fastboot. Reboot computer. Now connect phone. Then do what you need to do.
Sent from my Moto G6 Plus using XDA Labs

Klyde KD-1280 tesla Headunit

This is the motherboard and coreboard from Klyde KD-1280 Tesla headunit in case someone wants to know.
{
"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"
}
Anyone has any information on how to root this unit, please let me know.

Does anyone know what are these connectors for?

Hello,
can you also take a photo without a heat sink?

The heat sink was glued down, so I did not want to take the risk to remove it.
Toto1365 said:
Hello,
can you also take a photo without a heat sink?
Click to expand...
Click to collapse

Took mine apart
Toto1365 said:
Hello,
can you also take a photo without a heat sink?
Click to expand...
Click to collapse
The heat sink lifted off easily. Its an RK3399 as suspected.
imgshare.io/image/img-20191224-130838.0lp04
The unit is not being detected when plugged in to a laptop with rk3399 drivers installed. No SDcard slot. No USB on the board.
I have a TWRP.img for rk3399, how would I go about flashing it?
The unit does accept a USB flash drive with a px6_update.zip file.
Anyone knows a way to convert .img to a .zip? Tried making one, fails on zip verification. Not sure how to sign the zip properly. Thanks!

Recovery info
Also I've been able to get into recovery using ADB Shellkit app from the play store.
imgshare.io/image/0lvZS
imgshare.io/image/0lWzj
Trying to flash TWRP for rk3399, so far no luck
Because there is no SDcard slot, cannot apply update from SD.
Cannot apply from ADB either as the unit is not being detected from all 3 usb ports for some reason.
Going to try a different laptop and cable now.

Thanks. Right now I'm trying to find out what those connectors are for on the coreboard. Wonder if they enable other features for the head unit.

Connectors
After some research and in comparison to other rk3399 boards I would guess they would be either camera, sdcard, or usb OTG - ribbon expansion board connections. The bigger (longer) one is possibly a video bus.
I will bluntly ask KLYDE if they can sell me the expansion boards. I've had some luck dealing with them in the past... I am very curious too, but in the end I am just interested in rooting it and possibly designing a custom ROM afterwards.

Dr0idFanatic said:
After some research and in comparison to other rk3399 boards I would guess they would be either camera, sdcard, or usb OTG - ribbon expansion board connections. The bigger (longer) one is possibly a video bus.
I will bluntly ask KLYDE if they can sell me the expansion boards. I've had some luck dealing with them in the past... I am very curious too, but in the end I am just interested in rooting it and possibly designing a custom ROM afterwards.
Click to expand...
Click to collapse
Yep I'm guessing the same thing. They have option to add HDMI out for less than $10, so I think one of those connection will enable that.
Also, I got the PX6.zip update from Klyde, and it worked. If you want it to take a look at how they sign the zip file, let me know. I will upload, so you can download it.

JohnnyMHo said:
Does anyone know what are these connectors for?
Click to expand...
Click to collapse
I can help: the connector on your right picture is used for the HDMI connection:
And if somebody needs an additional USB connection: there are -2- USB connections located on the mainboard. I noticed it while comparing your picture with mine. So I found that the USB connection (on your board) is different like on my board. After a small research I learned that the USB port has -4- connections to offer. So I soldered an old USB cable to that connector and now I have an "internal" ssd connected. I'm worried about the total power consumption when I use all 4 connections so I would like to ask: perhaps it's better to "install" a self powered (12V) USB port on that connection???
What do you think?

Confirmed working
I've soldered on the extra USB and connected to my phone, then ran Android Auto through that port. Works. Very good idea to use the port for an "internal SSD".
I also was hoping ADB would connect through it, but no go.
---------- Post added at 08:55 PM ---------- Previous post was at 08:13 PM ----------
Also had lots of time to mess around with the unit.
-ADB through USB is broken, not seeing device.
-Fastboot works but flashing is locked. "Fastboot OEM unlock" returns OKAY, but tried flashing twrp_rk3399.img file and says locked.
-Got the rockchip firmware update windows app to work, however the partition tables are different.
-Finally got root access via ADB over WIFI !!!
-Also backed up recovery partition using dd, then tried writing twrp_rk3399.img with dd only to get a boot loop on booting into recovery. Restored original recovery with dd without an issue. I am guessing either I'm doing something wrong, or more likely TWRP_rk3309_3.0.2 does not work for this unit, as it came from a tv box with the same chip...
-Now that I know I can backup all the partitions, I will try loading supersu.

Sounds promising...
That would be cool if you are able to get a working root on the device! Looking forward for any (positive) development...

Success rooting the thing
Syncronisator said:
That would be cool if you are able to get a working root on the device! Looking forward for any (positive) development...
Click to expand...
Click to collapse
-After a few more hours of mocking around I've rooted it. (Credit goes to someone else as I followed a guide for a different unit with some slight variation).
-I will write up a step by step guide when I have some spare time again.
-Shortly after I bootlooped it by updating the SU binary, I know how to fix it luckily. Root works though, just an annoying "update su binary" every time you open the superuser app.
One step forward, two steps back. Progress never the less.

Super SU...
is perhaps a door opener.
Unfortunately the last version is 2.82 and no more development.
Wouldn't it better to use Magisk Manager instead? ( I'm no programming guy so this is a simple qestion from a noob)
The two additional connectors I would say (after researching in specs and data sheets of other RK3399) are MIPI connectors/interfaces???

Syncronisator said:
is perhaps a door opener.
Unfortunately the last version is 2.82 and no more development.
Wouldn't it better to use Magisk Manager instead? ( I'm no programming guy so this is a simple qestion from a noob)
The two additional connectors I would say (after researching in specs and data sheets of other RK3399) are MIPI connectors/interfaces???
Click to expand...
Click to collapse
I've tried magisk. Does not work, gives "unknown boot partition" error while installing. What worked is supersu 2.82B. The rooting method I will post in the next few days. Just dont update the supersu binary after, it will bootloop. It will nag every time you open the the supersu app, but otherwise will work.
-----------------------------------------------------------------
So when I messed up and updated the super su binary it bootlooped on me. Then I had a problem updating it with px6_format.zip, the update process did not want to start. I was pretty desparate at that point and did some research on how to get my unit working again. Then I messed up further by erasing the loader entirely. At that point just had a blank screen.
So I figured out how to reflash the loader, and get the px6_format.zip loading again.
In the process of recovering my unit I figured out a few hardware things as well:
1. I've soldered two wires to key down points on the board, when held on boot takes you to the unit recovery.
2. I've removed the OTG resistor in hopes of getting ADB to work via a USB cable, but that did not change anything. ADB & Fastboot still does not work. No need to remove the resistor.
3. The original recovery that came with the unit is useless as nothing worked in it. However after installing the latest px6_format.zip it finally has a useful "Apply update from USB card" function

Started a new thread with rooting instructions:
https://forum.xda-developers.com/an...to-root-klyde-kd-1280-tesla-headunit-t4035039
Good luck, have fun and DO NOT update the SuperSU binarý afterwards.

Dr0idFanatic said:
Started a new thread with rooting instructions:
https://forum.xda-developers.com/an...to-root-klyde-kd-1280-tesla-headunit-t4035039
Good luck, have fun and DO NOT update the SuperSU binarý afterwards.
Click to expand...
Click to collapse
I will try my best but this have to wait 2 weeks when I will be at home... I will report instantly

That is exactly what I think. The problem is you have to get that expansion HDMI board. I cannot find it any where.
Trying to talk to Klyde support to see if I can buy it from them. Still waiting for them to reply.
Syncronisator said:
I can help: the connector on your right picture is used for the HDMI connection:
And if somebody needs an additional USB connection: there are -2- USB connections located on the mainboard. I noticed it while comparing your picture with mine. So I found that the USB connection (on your board) is different like on my board. After a small research I learned that the USB port has -4- connections to offer. So I soldered an old USB cable to that connector and now I have an "internal" ssd connected. I'm worried about the total power consumption when I use all 4 connections so I would like to ask: perhaps it's better to "install" a self powered (12V) USB port on that connection???
What do you think?
Click to expand...
Click to collapse

Hello. I appeal to the owners of the device. Help me figure out the standby mode in the radio. Found only a short dream in the settings. But there is no full-fledged standby mode. Maybe I didn’t just see. In the previous MTCE PX5 device, the sleep settings were 10min, 30min, 2 hours and Auto. If someone figured out write how to configure?
---------- Post added at 05:23 PM ---------- Previous post was at 05:07 PM ----------
If anyone needs it, here is an update for the system. Received recently from the seller.
https://drive.google.com/file/d/1gXU13McO7XdTEMxOncy5pyW-5-OI1bF0/view?usp=sharing
To update, copy the file to the USB flash drive, the default format is Fat32. Insert the flash drive into any of the USB inputs and reboot the device. The update will start automatically. After the update is completed, you will be prompted to remove the USB; After removing the USB flash drive, the update is completed.

There is no option for that with the current ROM for the device. Hope we can see some custom ROM soon for this device, since someone already found the way to root it.
sun.valeo said:
Hello. I appeal to the owners of the device. Help me figure out the standby mode in the radio. Found only a short dream in the settings. But there is no full-fledged standby mode. Maybe I didn’t just see. In the previous MTCE PX5 device, the sleep settings were 10min, 30min, 2 hours and Auto. If someone figured out write how to configure?
---------- Post added at 05:23 PM ---------- Previous post was at 05:07 PM ----------
If anyone needs it, here is an update for the system. Received recently from the seller.
https://drive.google.com/file/d/1gXU13McO7XdTEMxOncy5pyW-5-OI1bF0/view?usp=sharing
To update, copy the file to the USB flash drive, the default format is Fat32. Insert the flash drive into any of the USB inputs and reboot the device. The update will start automatically. After the update is completed, you will be prompted to remove the USB; After removing the USB flash drive, the update is completed.
Click to expand...
Click to collapse

Trying to revive a Nook Glowlight 3

Hello,
A long time ago I was using a Nook Glowlight 3. I had rooted it, installed relaunchX and a bunch of readers. Later I switched to Boox Air (for size) and did not use the Nook for a long time.
Recently my son showed interest in reading books from a tablet, and I thought Nook would be suitable for him. However, since it was rooted, it was a bit complicated for him to navigate, so I decided to return it to its original state. Here is what I did to end up where I am now. I will be happy to elaborate on any of these, but I do not want to make my initial post too long, so people will be less likely to skip it.
1. I did a factory reset (by pressing home button during reboot), but this somehow erased the Nook launcher (or maybe I had erased it before, I am almost it was working before). After this reset, upon a boot, I would get past basic setup (timezones and wi-fi) and then get a blank screen.
2. Then using 5taps L-R trick, I turned on USB debugging again and rooted it again.
3. I installed relaunchX and Renate's launcher, but I could not tie them to the home button. I did not know how (I still do not know). I could launch them with adb shell and monkey command though.
4. I tried to get into recovery mode or fastbook through adb (by using things like "adb reboot recovery"), but did not succeed.
5. I downloaded and put the update.zip for this Nook and put it on / as well as /sdcard/ directories. Put Nook to sleep and waited a long time, but no success there either.
6. I was getting frustrated at this point and finally did something really stupid: I unzipped update to a directory under sdcard, remounted various partitions rw and tried to copy all the files coming from update.zip via a cp command. After a short while this command ran, I received an error message, something like "/bin/sh permission denied" (I guess it was referring to execute permissions not being present, and got kicked out of adb shell.
7. Now, the machine is going into factory reset upon boot and after the factory reset it reboots and goes into factory reset again. I tried interrupting the reboot multiple times, pressed various button combinations during reboot, but there are only two outcomes: power off or going into factory reset.
Is there anything I can do? If you can think of a software solution, I'd love to hear it.
I am not good with hardware, and I don't have any equipment (in particular I do not have a UART) but I am faculty member in a physics department in a university, so I can probably access any reasonable electronics equipment. I am willing to do some hardware tinkering, or perhaps to call on a favor or two from some of my experimental colleagues.
I am willing to try pretty much anything since my son is asking if I repaired the Nook almost everyday, and I would like to be able to honestly say I tried everything.
Thanks in advance for any help you may provide.
cheers,
ato

Manually installing an update.zip is not difficult, but that's not how to do it.
If it's really in a loop that you can't break and there's no ADB then you'll have to get more drastic.
One way is to use a UART and interrupt u-boot while it's booting and going to fastboot. From there you can flash a recovery and go to it, do a manual update, maybe fix something that's broken.
Another way is to defeat the flash memory on boot so that it goes to the ROM bootloader. From there you can use my imxlink.exe to load a modified bootloader that will go directly to fastboot,
Either of those two ways requires you opening the case. The Glow3 is not as bad as the Glow2, it doesn't use tape.

Thank you for your response. I can definitely open the case. I found some instructions here:
Barnes And Noble Nook Glowlight 3 Disassembly
This is a disassembly Guide For the nook...
www.ifixit.com
that looks doable.
It sounds like your second suggestion does not require additional equipment (except to open the case). Did you describe elsewhere on this forum how to defeat the flash memory on boot? I have read so many of your postings here in the last few weeks (and I am very grateful for those). I am guessing this might be something you already described before.

I can also order a UART. Will a CP2102 unit w/ 3.3 and 5V be adequate? I just think having a serial connection is so cool that I need to try it.

Yeah, any USB UART will do.
OTOH, I'm a bit more of a fan of the FTDI than the CP2102. I did have problems with a driver years ago but haven't touched them since.
If you fall in love with UARTs and want to use them on something modern, you might need 1.8V
I think that these are pretty cool in having selectable logic level.
https://www.amazon.com/DSD-TECH-SH-U09C5-Converter-Support/dp/B07WX2DSVB/
OTOH, anything will work for now.

I live in Turkey and that FTDI does not seem to be available here. I will keep your recommendation in mind though, thank you!
I ordered a CP2102. They had links to a driver on the order page, hopefully I will not have big problems. It should arrive in a few days.

I will try and open my glow3. Do I need to do anything special about the power? It is almost fully charged, so it would take a long time to drain the battery, but I can certainly try.

OK. I took a leap of faith and opened it up (I have a small window when my kids are sleeping), hopefully did not blow up anything.
Here is a photo in case it might help with someone looking to replace their nook glowlight 3 battery:
{
"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"
}
If I need to tinker with J11, J12 or J13, I can tell that they are way beyond my soldering capabilities. Do I need to get some connectors?
Would more detailed pictures help?
cheers,
atakan

No, you don't need to solder unless you want to make it permanent.
Usually just sticking wires in holes and adding a bit of sideways pressure is enough to make good contact.
If you have those 0.025" gold pins (like on cable ends) they are a close fit to the hole and work great.
Do you have any resistors on hand? Maybe 100 ohms or so?
We can try to get you going before the UART arrives.

I do not have any resistors on hand, but I can pick some up in about an hour. I will do so.
Unfortunately I do not have any gold pins either, but i think I can find some 0.5mm cables, which are probably actually 0.025''.

I found some resistors including 100 ohms (but also 47, 1000 etc). I also found some cables that measure 3/128 inches, quite close to 0.025. I got my avometer and optician's screwdriver set
How should I proceed?
While waiting your reply, I will install the WinUSB driver from zadig, I am guessing I will need that.

Download from my sig imxlink.exe and nnglow3.img (Neo Noogie).
Get the attached ub3fb.img
Code:
C:\>imxlink.exe ub3fb.img nnglow3.img
Now connect from TP23 to your 100 ohm resistor to a ground on the board.
While doing that LONG press the power button.
As soon as Windows "bongs" or imxlink.exe reacts disconnect the resistor and sit back.
You might have to try it a few times. Windows might be slow the first time that it sees 15a2/0063 on USB.

Wow! Something happened. iMX Link is working and now saying waiting for Fastboot or ADB.
Before that, the red led for Bootloader was on briefly.
The screen is showing the nook image that it shows while starting to boot.

Mmm, do you have the drivers for fastboot already loaded?
Are you sure that it isn't in fastboot?
When you pull the USB cable and reinsert it does it go "bong"?
Check in devmgmt.msc with "Show all devices". Look for 18d1/d00d
Make sure that it has a driver.
It really should go Red - Yellow - Green.
If not, try doing it again.

I do not know what the drivers for fastboot are. How I check for them?
When I pull the cable it goes "bong", but not when I reinsert it, not upon further pulls.
I'll try again.

Well, if you never saw yellow, you don't have drivers or something.
Did you ever have fastboot working on your desktop?
It's the same "Google drivers" as for ADB.
If you see something with an exclamation mark in Device Manager (devmgmt.msc) that's it.
I know this stuff works because on my Glow3 I intentionally erased u-boot so that I could always reboot using imxlink.exe and get a direct choice of boot image.

No, I always used ADB on Linux before, and not on Windows, which it what I am using now.
It is trying to install i.mx6sl driver from windows update and failing.
I will look for this "Google drivers" for ADB

I installed the Google drivers. It now went to red, then yellow but not green.
It is now saying
Waiting for disconnect...
Waiting for ADB...

Quote the text please, I don't know what's going on.
What's the screen doing?
You probably need to install the drivers for ADB.
If your Linux system has ADB you should be able to plug it in now.

I am sorry, I am really a noob w/ Windows, I cannot even take a screenshot (I tried PrtSc button).
Here is the output:
C:\Users\ato\Downloads\renate>imxlink.exe ub3fb.img nnglow3.img
Waiting for bootloader or Fastboot or ADB...
Found iMX6SL
Load addr 87800400, DCD offset 002c, DCD size 0220
67 DCD ops processed
Write, addr 87800400, size 00039270
********************************************************************************
********************************************************************************
*********************************************************************
Jumping to 87800400
Device disconnected correctly
Waiting for Fastboot or ADB...
product i.mx6sl NTX Smart Device
version 0.5
Sending boot image, 6043648 bytes... ok
Waiting for disconnect...
Waiting for ADB...
I installed Google ADB drivers.
When I try to run ADB from Windows, for "adb devices -l" I get an empty list.
Should reboot into linux and try?

Hisense 43A6H Google tv rootable?

I'm about to buy this TV is it rootable?
Hisense 43A6H Google tv rootable?

Technically speaking anything that runs on android can achieve root access. But I think you’re asking if there’s active development. I recently bought a Hisense 65” U6h myself, and there is no development that I have found . If all you need is root, try to get your hands on the stock boot.img from the factory rom. If there’s any updates for your model download it on the computer extract the boot.img and then copy it to a usb drive plug the drive into your tv install magisk apk and use the boot.img on the flash drive to do the patch. Would you mind if I ask what you are trying to accomplish with root access?

well I'm actually trying to remove system apps the easy way by using Mi Explorer and improve system performance and free up some internal storage space so I have enough room to play morrowind by the way sorry for the no spaces I'm not really sure how to use this remote control microphone on my Hisense 43a6h Google TV. honestly there's a lot more stuff I want to do with it as well though like using Viper for Android and among other things like my God VPN repeater hotspot. thanks
{
"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"
}

So I contacted Hisense and they sent me the firmware but its a .pkg apple archive and i cannot extract it. Can you help me so I can patch the boot.img and recompile and flash it so I have root access? Thanks
43A6H_43A53FUA(0012)_M0721.zip
drive.google.com
Dear Hisense Customer
Fri 2/3/2023 6:03 PM
Thank you for contacting Hisense.
Please follow the below instructions to update your TVs Firmware.
Download the ZIP file from the above link.
1. Follow the link above and download the zip file. The file is compressed, use a built-in or downloaded (i.e. Winzip) unzipping software to view the zip file contents.
a. Locate the .pkg file inside the .zip.
b. Copy the file xxxx.pkg to the root level of a USB stick formatted as FAT32.
c. Safely Eject the USB from your PC.
2. With TV powered on, Insert the USB stick into the TVs USB port. If the TV has both white and blue USB ports, use one of the white USB 2.0 ones.
3. If the TV displays the USB Media Device prompt after sensing the USB is inserted, just cancel or lose the box.
4. Enter the TV menu and navigate along this menu path [MENU button] > Settings > System > About > Upgrade > Upgrade by USB
5. The TV will respond confirming that an update file is found, and provides 2 options. Select Reboot.
6. The TV will take a few minutes to apply the update and will reboot once the update is complete.
7. Once rebooted, you can remove the USB stick and complete the setup of the TV.
If you have any questions or concerns in the meantime, give me a call at 1-888-935-8880 and please reference your First and Last Name or Telephone Number.
Thank you again and have a great day!

chris1892006 said:
So I contacted Hisense and they sent me the firmware but its a .pkg apple archive and i cannot extract it. Can you help me so I can patch the boot.img and recompile and flash it so I have root access? Thanks
43A6H_43A53FUA(0012)_M0721.zip
drive.google.com
Dear Hisense Customer
Fri 2/3/2023 6:03 PM
Thank you for contacting Hisense.
Please follow the below instructions to update your TVs Firmware.
Download the ZIP file from the above link.
1. Follow the link above and download the zip file. The file is compressed, use a built-in or downloaded (i.e. Winzip) unzipping software to view the zip file contents.
a. Locate the .pkg file inside the .zip.
b. Copy the file xxxx.pkg to the root level of a USB stick formatted as FAT32.
c. Safely Eject the USB from your PC.
2. With TV powered on, Insert the USB stick into the TVs USB port. If the TV has both white and blue USB ports, use one of the white USB 2.0 ones.
3. If the TV displays the USB Media Device prompt after sensing the USB is inserted, just cancel or lose the box.
4. Enter the TV menu and navigate along this menu path [MENU button] > Settings > System > About > Upgrade > Upgrade by USB
5. The TV will respond confirming that an update file is found, and provides 2 options. Select Reboot.
6. The TV will take a few minutes to apply the update and will reboot once the update is complete.
7. Once rebooted, you can remove the USB stick and complete the setup of the TV.
If you have any questions or concerns in the meantime, give me a call at 1-888-935-8880 and please reference your First and Last Name or Telephone Number.
Thank you again and have a great day!
Click to expand...
Click to collapse
Hey. I’m so sorry about the delayed reply I haven’t been on the forum too often lately. I’m not too familiar with the pkg compression personally. If you were able to pull that boot.img you should be able to just use that in magisk as the boot image to patch. I’ll log in my computer soon and try to download it and see what happens on my Linux system. How did you get that firmware file from them, what did you ask? I might just end up doing the same lol. I have been using adb to remove things such as google tv home launcher replaced with premium projectivy

talksickisil said:
Hey. I’m so sorry about the delayed reply I haven’t been on the forum too often lately. I’m not too familiar with the pkg compression personally. If you were able to pull that boot.img you should be able to just use that in magisk as the boot image to patch. I’ll log in my computer soon and try to download it and see what happens on my Linux system. How did you get that firmware file from them, what did you ask? I might just end up doing the same lol. I have been using adb to remove things such as google tv home launcher replaced with premium projectivy
Click to expand...
Click to collapse
Called them but now i need to learn how to downgrade firmware and bypass recovery no command how to extract pkg to root? Ill try bootloader unlock. So do u own this tv?

chris1892006 said:
Called them but now i need to learn how to downgrade firmware and bypass recovery no command how to extract pkg to root? Ill try bootloader unlock. So do u own this tv?
Click to expand...
Click to collapse
Mine is the U6h but is essentially the same. For these purposes at least. The main difference between the two is a different type of panel .

I wonder if you have the blinking power light issue like I do after using adb to fully remove google home launcher. I took a sharp knife and one of those square rubber feet for furniture and cut it down to size and put it on top of that light. I’d rather do that than have the stock launcher even having a chance of re installing itself

Wow cool which launcher are you using? Whats the stock launcher filename? I'm going to try to unlock the bootloader soon then I guess I'll learn how to dump the whole os and dump the boot.img I guess idk what im doing but ive done this before with mtk devices just not a tv.

chris1892006 said:
Wow cool which launcher are you using? Whats the stock launcher filename? I'm going to try to unlock the bootloader soon then I guess I'll learn how to dump the whole os and dump the boot.img I guess idk what im doing but ive done this before with mtk devices just not a tv.
Click to expand...
Click to collapse
yeah dumping/compiling is above my skill set. The launcher I use is Projectivy. I paid for the premium version to support the dev because I really like it, but the only feature premium adds is being able to choose a wallpaper from storage. Also the package name is going to always be listed below the name of the app when you are in settings>apps> highlighted app...... google tv launcher I removed with adb shell and command adb shell pm uninstall -k --user 0 com.google.android.apps.tv.launcherx if you end up disabling the google launcher I highly recommend also disabling set up wizard afterwards. Otherwise, the app will re-download and you will be playing whack a mole.

I just tried disabling the launcherx and it disabled the SETTINGS button on the remote which is a deal breaker. How do I fix this? I like using Nova Launcher instead of the stock launcher.

Hello good sir.

@TheMadScientist Hello good day mate. ;p So do u know how to get this working on google tv? I disabled the launcherx and it disabled the settings menu as well.
Thanks

chris1892006 said:
@TheMadScientist Hello good day mate. ;p So do u know how to get this working on google tv? I disabled the launcherx and it disabled the settings menu as well.
Thanks
Click to expand...
Click to collapse
Not really. When I looked into them was when they really started hitting the market. I had one of the 55 inch. But got rid of it pretty quick once I got my samsung

@TheMadScientist I plugged in my male to male usb and it never got detected plus sp flash tool i had isnt compatible with MT9612 MEDIATEK CHIP. Can u give some android 11 usb adb google tv advice? Is the mt9612 emmc or nand?

I got the bootloader unlocked but no root yet.

chris1892006 said:
I got the bootloader unlocked but no root yet.
Click to expand...
Click to collapse
Can you link the guise or a quick how.tl on that? Netws hst for magisk and cI oukd likely figure out su binary over UART or termux + su exec trjcns