This will work for the S7 and S7 Edge. In fact it will work for all Android Devices on Jellybean and higher.
You can change DPI without root but will need to use adb on a computer.
As some of you may be aware, changing dpi in build.prop does not work, therefore I have also now included a method to change DPI with root, without the need of a computer. Scroll down to see how to do this.
Since the April update, Samsung have included a menu in the settings screen which allows you to change between 'Standard' (640 DPI) and 'Condensed' (560 DPI). If you have not had this update, you can still access this menu using this app.
(AT&T users have confirmed that this menu is not available in the display menu but still available via the the app route.)
If you would like a different DPI other than 640 or 560, please follow the instructions below:
Change DPI without root (Requires Computer):
This will NOT trip Knox.
To do this, follow the steps below.
The first thing you need to do is to install adb. The quickest way to do this is using the adb installer. You can download it from Here. If you follow the steps correctly in that thread, you should have no issues installing adb.
Now you will need to enable USB Debugging. [If you have 'My Knox' installed, you will not be able to do this so you will need to uninstall 'My Knox' First otherwise USB debuggin will be greyed out.]. Go into Settings > About Device > Software Info and keep tapping Build Number until Developer Options is enabled. Then go back into the Settings screen and go into Developer Options (located just above 'About Device'). You should see USB Debugging, turn the slider to on.
Connect your S7E to your computer. You will see a notification asking for you to Allow USB degugging for that computer, select 'OK'.
Now open Command Prompt (CMD) on your computer. (If you're not sure how to do this, Click Here to find out how).
First thing to check is if adb can detect the device, so type the following command in CMD and press enter...
Code:
adb devices
If this command shows the device (a line of random letters and numbers), then it has successfully detected your device. If nothing shows, then it cannot detect the device and you have either not enabled USB debugging, not allowed USB Debugging for this computer (as per the prompt when plugging it in)or the drivers have not been installed. (Most recent Windows will automatically install the Drivers, but if you are having Driver issues, then install Kies, connect the device to Kies to allow the drivers to install, then remove device from the computer, disable Kies then start again from Step 3).
If the device is detected in adb, go ahead and enter the following command to change your DPI. 560 is the most commen used but you can change this to anything you like (I find 520 to be the best).
Code:
adb shell wm density 560 && adb reboot
Your S7E should now reboot and the new DPI will be applied. To confirm this, install DPI Checker from the Play store. The prop file will still show the default DPI of 640 so ignore this.
If you want to revert back to the default DPI, enter the following command:
Code:
adb shell wm density 640 && adb reboot
Change DPI with root (No computer required):
1. Download a Terminal app (such as this one) and open the app.
2: Type the following:
Code:
su
Then tap enter. This will prompt root permission, make sure you allow permission
Code:
wm density 560 && reboot
Change 560 to your prefered DPI.
Then tap enter.
3. Your phone will reboot and when booted it will have the new set DPI.
4. To change back to stock DPI, use the following in Terminal:
Code:
wm density 640 && reboot
FAQ:
Will this affect Samsung Pay?
Yes. Users have reported that Samsung Pay will not with any DPI other than 560 or 640
Will this affect Android Pay?
No. A recent update to Android Pay means it now works with any DPI
Will this affect the scaling of Samsung apps?
Anything below 520 will affect the camera (in pro mode)
Other than this, I have not noticed any other scaling issues (see screenshots below).
Screenshots:
Camera:
{
"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"
}
Other Samsung Apps
If you have any issues or questions feel free to ask me and I will be happy to help.
If you notice any mistakes or know any ways this can be improved, please let me know and I will update the guide.
I suggest you don't. Samsung apps are notorious for not scaling with dpi changes, which is why Xposed App Settings is a brilliant companion app as you can set certain problem applications (like contacts and phone) to default DPI whilst having the overall system set to what you want.
Ye I had that with previous android devices but I can cope with that more than I can cope with the high DPI
Beefheart said:
I suggest you don't. Samsung apps are notorious for not scaling with dpi changes, which is why Xposed App Settings is a brilliant companion app as you can set certain problem applications (like contacts and phone) to default DPI whilst having the overall system set to what you want.
Click to expand...
Click to collapse
From another thread...apparently the only app that has scaling issues (so far) is the Camera.
A_N_D_R_E said:
From another thread...apparently the only app that has scaling issues (so far) is the Camera.
Click to expand...
Click to collapse
I put mine at 560 and 600 (from stock 640) and yes the, camera has a small black baro n the side, but everything else is 100% cosmetically. Functionality is 100% even with the camera.
entropism said:
I put mine at 560 and 600 (from stock 640) and yes the, camera has a small black baro n the side, but everything else is 100% cosmetically. Functionality is 100% even with the camera.
Click to expand...
Click to collapse
Did yours trip Knox?
nope.
entropism said:
nope.
Click to expand...
Click to collapse
Are you 100% sure? I don't want to take the risk without being certain.
CuBz90 said:
Are you 100% sure? I don't want to take the risk without being certain.
Click to expand...
Click to collapse
I mean, if you don't want to believe me, that's on you .
entropism said:
I mean, if you don't want to believe me, that's on you .
Click to expand...
Click to collapse
I do believe you, I just want to be sure.
Thanks. I'll do it later tonight.
Well, I changed it to 560 with no issues. All Samsung apps look fine, including the camera app so not sure why some are seeing a black bar. Strange
What's the default on this?
CuBz90 said:
Well, I changed it to 560 with no issues. All Samsung apps look fine, including the camera app so not sure why some are seeing a black bar. Strange
Click to expand...
Click to collapse
Can you please explain how you did it? I always thaught that root is required for changing dpi.
Beefheart said:
What's the default on this?
Click to expand...
Click to collapse
640 is the default dpi on the S7 Edge
masiegel said:
Can you please explain how you did it? I always thaught that root is required for changing dpi.
Click to expand...
Click to collapse
Enable USB debugging in developer options
Connect S7 to your computer with the USB cable
Then enter the following command (assuming you have adb installed - if not, click here to find out how to install adb)...
Code:
adb shell wm density 560 && adb reboot
(You can change the 560 to whatever DPI you want)
The device will then reboot and the new DPI will be set.
It would seem the contacts/phone app now scales. It didn't used to.
Beefheart said:
It would seem the contacts/phone app now scales. It didn't used to.
Click to expand...
Click to collapse
It was bad on my S4. So bad that I ended up using a 3rd party dialer. I'm glad they no longer have the issue.
I am confused as to why some people are seeing a black bar in the camera app after changing DPI to 560 when I am not. Strange.
Anyone know the default DPI for the S7? I've changed my DPI to 560 and it seems to have taken well. How far can I go?
Default is 640, as mentioned above...
Sent from my SM-N920V using Tapatalk
JasonJoel said:
Default is 640, as mentioned above...
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Sorry, I meant for the S7 (non-Edge).
Related
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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"
}
Note - Java is needed to Run SDK Manager - Install JAVA
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Reserve if needed
Thanks! Good stuff.. I just installed Windows 8 and totally forgot that I had to reinstall this... ( which originally took me 8 hours to figure out the first time! Lol ) this will definitely help future HTC people out...
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
wtoj34 said:
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am aware that USB 3.0 does cause issues with adb, mostly the longer running ones it hangs sometimes, I don't have an answer for that right now, I am running with 2.0 still and I have zero issues.
This is something that I came across that seemed to resolve a lot of adb issues
USB 3.0 Help with ADB
also
XDA Thread I found that in
cant launch sdk manager
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
bdorr1105 said:
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
Part 2. Verifying ADB is set up properly and Working
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Click to expand...
Click to collapse
davidmatt34 said:
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
Click to expand...
Click to collapse
Thanks for sharing that, I added that as note in the OP...Glad you are setup and good to go
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
jbarcus81 said:
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
Click to expand...
Click to collapse
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
bdorr1105 said:
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
Click to expand...
Click to collapse
Yeah.. the link just wasn't working at the time.. weird..
jbarcus81 said:
Yeah.. the link just wasn't working at the time.. weird..
Click to expand...
Click to collapse
Thanks for the update
Sent from my HTC6525LVW using Tapatalk
Also make sure you don't have drivers installed for another phone.. ADB couldn't find my M8 until I uninstalled my lg spectrums drivers on Win 8.1
Sent from my HTC6525LVW using XDA Free mobile app
Nice job.. Thanks for this. My first W8.1 machine.
Guys can someone help ,,
everything is installed and still getting the following error :
C:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH44FWM09049 device
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
i've been trying to fix this for the past 4 hours but no luck ,, anyone ??
I$ device in fastboot mode?
nvmd
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
technochatter said:
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
Click to expand...
Click to collapse
Yes.
Android SDK - Powerful tool and easy to set up for use with your Android Device
{
"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 am putting this together for some who may be confused on how to set this up. I love Android SDK, have been using it for ever and once it is setup, maintenance is extra easy. There are 100 ways to skin a cat with ADB tools and development tools. This is my personal choice, go about it how ever you want. This tool is well maintained and always updated so its a big reason I use it. Great support and a great and powerful tool
Click to expand...
Click to collapse
Part 1. Follow These Steps Below - (Preparation)
Download Links For Tools
1. Java SE Development Kit (JDK)
2. Android SDK Tools Only - Download Only, Do Not Install yet
If You Choose Windows for example
3. Universal ADB Drivers - Instructions Here
Click to expand...
Click to collapse
How to Install and Set-up
1. Install Java SE Development Kit (JDK) from Start Here section if you have not yet
2. Launch Android SDK installer you downloaded up above in Download Links
3. During install - Set Installation Path to
Code:
C:\Android\
4. After Installation is Complete, run SDK Manager.exe
5. Install 5.1.1 and 6.0 since these are the APIs for all current Devices. Should not really see anything less than 5.1.1
Note* - Just put a check box where you see the red circles in the picture. The reason I have Tools (Preview Channel) is because I updated to the 25.0.1 RC2 SDK Tools, however, that is not required. You can choose 24.4.1 and it will be fine. It will say installed where as mine does not in the picture because I chose to use 25.0.1 RC2
6. Let all updates install to completion - This could take a while depending on your internet connection
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
IMPORTANT - Make sure you have already enabled developer options and USB Debugging or you will not see the below results
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\platform-tools
2. In Command prompt type
Code:
adb devices
You Should get Prompted to Allow USB debugging - Ignore if You Already Have Done This
3. If your output shows your device attached like below, then you are good to go!!!
and
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type
Code:
sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
Windows 8
Windows 10
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\platform-tools
Windows 8
Windows 10
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
@Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
@[B]Snoop05[/B] - ADB Drivers and Fastboot
Reserve if Needed
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Peccoskaify said:
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Click to expand...
Click to collapse
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
bdorr1105 said:
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I've tried it many times.... i have enough space on my drive, but everytime i try to download this one and only part, prints out this error message....why do i always have so many problems with it
Peccoskaify said:
I've tried it many times.... i have enough space on mi drive, everytime i try to download this one and only part it prints out this error message....why do i always have to have so many problems with it
Click to expand...
Click to collapse
Lol you and me both bro, but you don't have to install that, that is optional, the rest looks good. You should be able to use it now
Edit: looks like a network issue or the repository is down... That will work itself out.. Right now, it is not required
Sent from my LG-H901 using Tapatalk
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Peccoskaify said:
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Click to expand...
Click to collapse
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
bdorr1105 said:
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
Click to expand...
Click to collapse
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Peccoskaify said:
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Click to expand...
Click to collapse
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
bdorr1105 said:
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
Click to expand...
Click to collapse
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Peccoskaify said:
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Click to expand...
Click to collapse
Have you had any luck?
Sent from my LG-H901 using Tapatalk
bdorr1105 said:
Have you had any luck?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Nope :/
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Yea I am looking into it the v10 is hard to find anything
Sent from my LG-H901 using Tapatalk
Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
bdorr1105 said:
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Did it, nothing changed, is this reason for refund?
Peccoskaify said:
Did it, nothing changed, is this reason for refund?
Click to expand...
Click to collapse
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
bdorr1105 said:
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
Click to expand...
Click to collapse
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Peccoskaify said:
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Click to expand...
Click to collapse
Thats not correct, su did not work, you should have a # symbol before the command, guess not being rooted doesn't help
edit: connect your phone to the computer and type the same command
I think strangely it is just recognizing adb reboot and omitting the bootloader, so try adb reboot-bootlader when connected to the computer
[GUIDE] How to enter developer mode on 2017 Honda Civic (and now root & install apps)
======================
Sticky
Honda has changed the password to enter the developer mode in new vehicle models so the old method described in this thread may not work any longer. If you have difficulty entering the developer mode or do not have a laptop, you may consider trying the new web based installation (paid service). The new method supports almost all Honda vehicles including Civic, CR-V, Accord, Pilot, Ridgeline and Clarity. For more information please refer to: xxxxxxx Mod Edit: Link removed.
======================
Updated 2020.10.02
Display compass and rich vehicle information in the instrument cluster. Display advanced turn-by-turn directions while using Waze. Try it now (for Civic and CR-V only): Mod Edit: Link removed.
{
"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"
}
======================
Updated 2020.03.08
Support playing FLAC lossless audio directly in the factory USB audio player (for Civic & CR-V only).
======================
Updated 2019.06.22
Open rear camera by one click.
Real-time monitoring of battery voltage with voice alarm.
Seat belt voice alarm.
Show CPU usage, battery voltage in the status bar.
======================
Updated 2018.09.14
New test version: display turn-by-turn navigation directions in the instrument cluster, in conjunction with Waze.
======================
Updated 2018.01.14
A totally new One Click Root tool (Windows GUI version) and Honda Hack app were released. With the help of Honda Hack app, we can install apps without a laptop. What's more, we can enable the steering wheel audio controls, save offline maps and songs to the external USB drive now.
======================
Updated 2017.09.27
Finally I solved the auto reboot problem while remounting the system partition. Enjoy it!!!
======================
Updated 2017.06.26
Now we can root the head unit and install apps. Below are the detailed steps, please use at your own risk.
Detailed steps:
1. Enter developer mode and enable USB debugging.
Go to HOME > Settings > System > Detail information.
In the Android Settings window, click About.
Click the Build Number seven times exactly.
Now you will see the Please enter a passcord prompt.
Click the top 4 items in order 1, 4, 2, 3 and you should unlock the developer mode.
Go into Android Settings > Developer options and enable USB debugging.
2. Change the USB role of the head unit from Host to Device.
Press the power, menu, and brightness button at once, and hold until you enter a new menu with two options.
Click the bottom option called Detail Information & Settings.
Now hold the MENU key to enter another menu.
Then Hold the HOME key to enter the last menu. You should first hear two consecutive beeps and then one final beep.
Lastly, change the role of USB Port from Host to Device.
Now connect your laptop to the front Android Auto/CarPlay Port using the USB A to A cable.
3. Run the One Click Root
Disable your anti-virus and/or anti-malware programs before continue.
Download the root tool: HondaHack.zip
Extract HondaHack.exe from the ZIP file.
Run HondaHack.exe and it should connect to the head unit automatically. Android ADB USB Driver should be installed automatically in the meanwhile.
Click the ROOT button and wait for the processing to complete.
After the head unit is rebooted, you should see Honda Installer in the app list. Honda Installer was installed as a system app so you will not lose it after a factory resetting.
Open Honda Hack and click Install an app to install apk files you saved in the internal sdcard or external USB drive.
4. You can also Install Honda Hack if you would like to have more powerful features including:
Install apps without a laptop.
Bypass parking brake.
Enable steering wheel controls for civic & accord.
Force landscape mode so apps such as Spotify will display properly.
Enable write access to the external USB storage (pro only).
Auto click the OK button at startup (pro only).
Auto run app at startup (pro only).
View attachment 4388157View attachment 4388158
5. Change the USB role of the head unit from Device to Host.
Do this just like the reverse action in step 2, otherwise the USB port will lose its charging capacity and CarPlay / Android Auto will stop working.
Download Honda Hack: HondaHack.apk
If you do not like the GUI version, you can still download the original command-line version from GitHub: https://github.com/codeage/root-honda
Some files and scripts were obtained from this thread: https://forum.xda-developers.com/android/general/guide-how-to-gain-root-shell-2016-honda-t3487644 and all credit goes to @jersacct.
Great job, I'm going to try this on my Honda CRV 2017 later today to see if it works!
I tried this this morning on my 2016 Civic and it works!
Port 5000 is open for adb on my Civic. Not sure if the port is different on a Pilot or not, but it's different than the standard adb port (5555). I found it by running an nmap scan of my headunit's IP.
Unfortunately even after I enabled Developer mode on my HU, my adb does the same thing it did before. That is, I can adb connect to port 5000 on my HU's IP, but when I do "adb devices", it shows the device there but "offline".
My expectation was that once Developer mode was enabled, connecting via adb would bring up a prompt on the HU asking if I wanted to authorize that remote device.
However, I was doing the adb connection from my PC inside my house, then running out to my garage to check the screen. So maybe I just didn't get there in time to see it. I'm going to try it again from my laptop sitting in my car tonight when I have more time to mess with it.
Works on my 2017 cr-v! Has anyone had a chance to try usb debugging?
josby said:
I tried this this morning on my 2016 Civic and it works!
Port 5000 is open for adb on my Civic. Not sure if the port is different on a Pilot or not, but it's different than the standard adb port (5500). I found it by running an nmap scan of my headunit's IP.
Unfortunately even after I enabled Developer mode on my HU, my adb does the same thing it did before. That is, I can adb connect to port 5000 on my HU's IP, but when I do "adb devices", it shows the device there but "offline".
My expectation was that once Developer mode was enabled, connecting via adb would bring up a prompt on the HU asking if I wanted to authorize that remote device.
However, I was doing the adb connection from my PC inside my house, then running out to my garage to check the screen. So maybe I just didn't get there in time to see it. I'm going to try it again from my laptop sitting in my car tonight when I have more time to mess with it.
Click to expand...
Click to collapse
Yes, same problem here. I think port 5000 is not for adb but some other service from Honda.
codeage said:
Yes, same problem here. I think port 5000 is not for adb but some other service from Honda.
Click to expand...
Click to collapse
I hadn't considered that. You might be right. I tried connecting adb on my PC to another computer of mine on a port number that I know for sure isn't an adb listener, and it gives that same behavior of just showing that device is "offline".
But, everything I've read indicates you can't connect with adb over wifi until you first connect with USB and authorize the instance of adb on that computer to connect to the device. So I think that could also be the reason we can't get anywhere on port 5000.
I don't have a TypeA-to-TypeA USB cable to try connecting to the car's USB ports with though.
https://forum.xda-developers.com/an...2016-honda-t3487644/post70868431#post70868431
try adb with the usb port on device mode
YurS0D1a0 said:
https://forum.xda-developers.com/an...2016-honda-t3487644/post70868431#post70868431
try adb with the usb port on device mode
Click to expand...
Click to collapse
Already tried this but does not work.
codeage said:
Already tried this but does not work.
View attachment 4184875
Click to expand...
Click to collapse
Hey just making sure before I end up trying the same thing. You tried connecting through the USB port right?
Edit: Turns out you can. I had a friend post about it since my account is new.
OldAmber said:
Hey just making sure before I end up trying the same thing. You tried connecting through the USB port right?
Click to expand...
Click to collapse
Yes, I tried connecting through the USB port.
thanks
nice information
Post for OldAmber since his account is new
I was able to establish an adb connection through usb by changing the role to Device. Here's a video just showing it off and a picture just to show I did have shell access.
https://www.youtube.com/watch?v=9nJuMShXW0o
and a pic just show I did have shell access.
http://imgur.com/a/8K8cy
His build number is 1.F186.69
I tried using the same root method but it looks like our Factory_reset.sh is not located in the same directory, all the files pushed through successfully though.
OldAmber said:
I tried using the same root method but it looks like our Factory_reset.sh is not located in the same directory, all the files pushed through successfully though.
Click to expand...
Click to collapse
can You get and post this file /data/system/whitelist.xml
mayby this method (psneuter): https://forum.xda-developers.com/showthread.php?t=2684210 ?
vraj1470 said:
Post for OldAmber since his account is new
I was able to establish an adb connection through usb by changing the role to Device. Here's a video just showing it off and a picture just to show I did have shell access.
https://www.youtube.com/watch?v=9nJuMShXW0o
and a pic just show I did have shell access.
http://imgur.com/a/8K8cy
His build number is 1.F186.69
Click to expand...
Click to collapse
Glad to know this. I've already tried this but does not work. Maybe I got a bad cable? I will try again later. :laugh:
Kurian8 said:
can You get and post this file /data/system/whitelist.xml
mayby this method (psneuter): https://forum.xda-developers.com/showthread.php?t=2684210 ?
Click to expand...
Click to collapse
I tried pulling that file, but it says it does not exist. This might be because I don't have root. And I have not yet tried the psneuter method, but I don't think that would work since I can't install apks as it is.
OldAmber said:
I tried pulling that file, but it says it does not exist. This might be because I don't have root. And I have not yet tried the psneuter method, but I don't think that would work since I can't install apks as it is.
Click to expand...
Click to collapse
I hope at end of week starting doing own tests. First iI'm going to try psneuter and dortyc0w. To test psneuter You don't need install any apks. Just put file to temp directory /data/local/tmp/, lunch shell (adb shell) and change rights to 777 and next try to execute it.
Kurian8 said:
I hope at end of week starting doing own tests. First iI'm going to try psneuter and dortyc0w. To test psneuter You don't need install any apks. Just put file to temp directory /data/local/tmp/, lunch shell (adb shell) and change rights to 777 and next try to execute it.
Click to expand...
Click to collapse
Just tried it out and had no luck. I got the following error
Code:
255|[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 777 psneuter
[email protected]:/data/local/tmp $ ./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
There's no file whitelist.xml in /data/system/, but I found another file named packages.xml there. I also found the shell script /system/custom/bin/auto_install.sh references to this xml file so I think it is the correct whitelist file. The file packages.xml is readable by root users only so I can not pull it now.
There's no file factory_reset.sh in /system/etc, so I tried to use dirtycow to overwrite another small shell script file /system/bin/mount_debugfs.sh and got the following output:
Code:
$ adb shell '/data/local/tmp/rootme/dirtycow /system/bin/mount_debugfs.sh /data/local/tmp/rootme/factory_reset_mod.sh'
But the file /system/bin/mount_debugfs.sh was not changed after the exploiting. Maybe the dirtycow vulnerability has been patched already in this kernel?
Very nice another steps ahead
Possible it's syntax mistake? Before second file name You missed trailing / in path
Can You try it again:
Code:
$ adb shell '/data/local/tmp/rootme/dirtycow /system/bin/mount_debugfs.sh [COLOR="Red"]/[/COLOR]data/local/tmp/rootme/factory_reset_mod.sh'
1-Download and install Nova and Twisted Home Manager from Google Playstore
2-open Twisted Home Manager and select Nova
3-if you power down phone you will have to reselect Nova in Twisted Home Manager
4-works with any third party launcher (Huawei Home Switcher is already on your phone, Twisted Home Manager enables it)
thanks for your guide
also possibly this
https://forum.xda-developers.com/showpost.php?p=78073547&postcount=15
Sebring5 said:
1-change phone settings to app drawer, enable third party installations and gesture navigation
2-set up Huawei id (country not important)
3-set up App Gallery ( select country China)
4-install Google Playstore if not already installed
5-download and install from App Gallery Nova and Huawei Home
6-set up Nova with gesture navigation (swipe up for app drawer)
7-download and install from Playstore Nova Prime and Twisted Home Manager
8-update Nova from Playstore
9-open Twisted Home Manager and set Huawei Home as default and select Nova
10-if you power down phone you will have to reselect Nova in Twisted Home Manager
Click to expand...
Click to collapse
This is was to drawn out.
You best bet is below.
adb shell
pm uninstall -k --user 0 com.huawei.android.launcher
After a factory reset it will return however. This is give you Nova with no problems. Except you might loose the gesture navigation. However you can use Nova for some of that.
I'm going to create a guide and possible a script to remove this and most bloatware.
Sebring5 said:
1-change phone settings to app drawer, enable third party installations and gesture navigation
2-set up Huawei id (country not important)
3-set up App Gallery ( select country China)
4-install Google Playstore if not already installed
5-download and install from App Gallery Nova and Huawei Home
6-set up Nova with gesture navigation (swipe up for app drawer)
7-download and install from Playstore Nova Prime and Twisted Home Manager
8-update Nova from Playstore
9-open Twisted Home Manager and set Huawei Home as default and select Nova
10-if you power down phone you will have to reselect Nova in Twisted Home Manager
Click to expand...
Click to collapse
This doesn't work ! Well .... it does for a bit but always goes back to stock launcher if you try to get the multi tasking window to work. In Nova, no matter what gesture you set up - once you do it to get the multi tasking list up, you select an app and then it reverts back to stock.
Does this happen to you or have you managed to get around this?
g_woodend said:
This doesn't work ! Well .... it does for a bit but always goes back to stock launcher if you try to get the multi tasking window to work. In Nova, no matter what gesture you set up - once you do it to get the multi tasking list up, you select an app and then it reverts back to stock.
Does this happen to you or have you managed to get around this?
Click to expand...
Click to collapse
I do not use multi tasking or split windows.
antiochasylum said:
This is was to drawn out.
You best bet is below.
adb shell
pm uninstall -k --user 0 com.huawei.android.launcher
After a factory reset it will return however. This is give you Nova with no problems. Except you might loose the gesture navigation. However you can use Nova for some of that.
I'm going to create a guide and possible a script to remove this and most bloatware.
Click to expand...
Click to collapse
Perfect!! Works like a charm - many thanks
g_woodend said:
Perfect!! Works like a charm - many thanks
Click to expand...
Click to collapse
Ditto & thanks.
Make sure USB is set to MTP and USB Debugging is actually on (it seems to have a life of its own). THANKS!
Was there a need to kill the huawei drive app also?
Rudolpht said:
Ditto & thanks.
Make sure USB is set to MTP and USB Debugging is actually on (it seems to have a life of its own). THANKS!
Was there a need to kill the huawei drive app also?
Click to expand...
Click to collapse
RedCriwx posted it here first thanks to him
https://forum.xda-developers.com/showpost.php?p=78073547&postcount=15
antiochasylum said:
This is was to drawn out.
You best bet is below.
adb shell
pm uninstall -k --user 0 com.huawei.android.launcher
After a factory reset it will return however. This is give you Nova with no problems. Except you might loose the gesture navigation. However you can use Nova for some of that.
I'm going to create a guide and possible a script to remove this and most bloatware.
Click to expand...
Click to collapse
With Nova can you still program all the gestures inside the Nova settings, do they all work? I am interested in doing this, but read "swipe up for home using gesture navigation doesn't work anymore". I don't use swipe up for home and as long as I can program swipe up still it's all good. If all the programmable gestures work, I would be willing to try your method although in all the years of unlocking phones, flashing ROM's, modems, kernels, ClockworkMod, TWRP, using Odin, etc, I've never used adb even once. And I'm looking forward to your debloating list. I'm afraid of removing too much and losing some features. I only removed the apps that were completely Chinese so far.
antiochasylum said:
This is was to drawn out.
You best bet is below.
adb shell
pm uninstall -k --user 0 com.huawei.android.launcher
After a factory reset it will return however. This is give you Nova with no problems. Except you might loose the gesture navigation. However you can use Nova for some of that.
I'm going to create a guide and possible a script to remove this and most bloatware.
Click to expand...
Click to collapse
I would appreciate a guide, as I am not very familiar with using ADB.
DavidMT909 said:
With Nova can you still program all the gestures inside the Nova settings, do they all work? I am interested in doing this, but read "swipe up for home using gesture navigation doesn't work anymore". I don't use swipe up for home and as long as I can program swipe up still it's all good. If all the programmable gestures work, I would be willing to try your method although in all the years of unlocking phones, flashing ROM's, modems, kernels, ClockworkMod, TWRP, using Odin, etc, I've never used adb even once. And I'm looking forward to your debloating list. I'm afraid of removing too much and losing some features. I only removed the apps that were completely Chinese so far.
Click to expand...
Click to collapse
jeradjohnso said:
I would appreciate a guide, as I am not very familiar with using ADB.
Click to expand...
Click to collapse
adb is easy. Most think its hard, but its really simple. I'm going to try and compile a list tonight and get this updated.
I've got my L29 setup and I have remove a few things. I'm going to try the launcher route tonight, and I an using Evie launcher till I can get to my PC and configure it.
Swipe up will still work on the homescreen. As I use that for the app drawer. I do not think swipe up will work to go back home, like a system based gesture.
antiochasylum said:
adb is easy. Most think its hard, but its really simple. I'm going to try and compile a list tonight and get this updated.
I've got my L29 setup and I have remove a few things. I'm going to try the launcher route tonight, and I an using Evie launcher till I can get to my PC and configure it.
Swipe up will still work on the homescreen. As I use that for the app drawer. I do not think swipe up will work to go back home, like a system based gesture.
Click to expand...
Click to collapse
That's great! I use swipe up for the app drawer as well.
jeradjohnso said:
I would appreciate a guide, as I am not very familiar with using ADB.
Click to expand...
Click to collapse
While we wait for antiochasylum to develope a much detailed guide this is how I got this done:
1) Install HiSuite (https://consumer.huawei.com/minisite/HiSuite_en/) to ensure you have the correct drivers (I know this is mostly bloatware, but is either this or risk to install an "alternative" driver)
2) Download and extract ADB (I use platform tools: http://mirrors.zzu.edu.cn/android/repository/platform-tools_r28.0.1-windows.zip)
3) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
4) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
5) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
6) Open a command line and go to the directory you extracted "Platform Tools" to.
7) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
8) Run "adb shell"
9) Run "pm uninstall -k --user 0 com.huawei.android.launcher". It should show "success".
You are done!
Hope it is usefull.
RedCriwx said:
While we wait for antiochasylum to develope a much detailed guide this is how I got this done:
1) Install HiSuite (https://consumer.huawei.com/minisite/HiSuite_en/) to ensure you have the correct drivers (I know this is mostly bloatware, but is either this or risk to install an "alternative" driver)
2) Download and extract ADB (I use platform tools: http://mirrors.zzu.edu.cn/android/repository/platform-tools_r28.0.1-windows.zip)
3) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
4) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
5) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
6) Open a command line and go to the directory you extracted "Platform Tools" to.
7) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
8) Run "adb shell"
9) Run "pm uninstall -k --user 0 com.huawei.android.launcher". It should show "success".
You are done!
Hope it is usefull.
Click to expand...
Click to collapse
:highfive:
Thank you! :victory:
RedCriwx said:
While we wait for antiochasylum to develope a much detailed guide this is how I got this done:
1) Install HiSuite (https://consumer.huawei.com/minisite/HiSuite_en/) to ensure you have the correct drivers (I know this is mostly bloatware, but is either this or risk to install an "alternative" driver)
2) Download and extract ADB (I use platform tools: http://mirrors.zzu.edu.cn/android/repository/platform-tools_r28.0.1-windows.zip)
3) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
4) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
5) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
6) Open a command line and go to the directory you extracted "Platform Tools" to.
7) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
8) Run "adb shell"
9) Run "pm uninstall -k --user 0 com.huawei.android.launcher". It should show "success".
You are done!
Hope it is usefull.
Click to expand...
Click to collapse
I LOVE YOU!!! I did it and one problem gone! Thank you!
DavidMT909 said:
I LOVE YOU!!! I did it and one problem gone! Thank you!
Click to expand...
Click to collapse
You dont even need the hisuite drivers really. Just platform tools from google.
Hows Nova working out with the launcher gone? Better?
antiochasylum said:
You dont even need the hisuite drivers really. Just platform tools from google.
Hows Nova working out with the launcher gone? Better?
Click to expand...
Click to collapse
OMG! So much better! I was getting tired of things randomly making it go back to stock launcher. One app wouldn't let me place a widget, it kept going back to stock when I tried to place it, then I'd have to start Nova again. As soon as I did this, it let me set the widget first try, like it's supposed to. Imagine that. Running much smoother now. Now that the launcher problem is fixed, I just need to get all my notification badges working, and figure out a good way to have some kind of light notification whether it's the little floating icons I seen someone post an app of, or the flashing light. I kinda like the floating icons on the screen idea if it works.
antiochasylum said:
I'm going to create a guide and possible a script to remove this and most bloatware.
Click to expand...
Click to collapse
Thanks, I'm not familiar with Huawei phones and what packages can be safely "removed".
RedCriwx said:
While we wait for antiochasylum to develope a much detailed guide this is how I got this done:
1) Install HiSuite (https://consumer.huawei.com/minisite/HiSuite_en/) to ensure you have the correct drivers (I know this is mostly bloatware, but is either this or risk to install an "alternative" driver)
2) Download and extract ADB (I use platform tools: http://mirrors.zzu.edu.cn/android/repository/platform-tools_r28.0.1-windows.zip)
3) Go to Settings > System > About Phone and tap on "build number" about 8 times. You should see a message saing: "You are a developer now"
4) Back to the previous menu and you should see now a new item called "Developer options", go there, find and enable "USB debugging" (you may have to use a Huawei ID).
5) Now connect the phone to the PC via USB and select "Transfer files" on the phone.
6) Open a command line and go to the directory you extracted "Platform Tools" to.
7) Run the command "adb devices", your device should shown. If not, you need to check the drivers.
8) Run "adb shell"
9) Run "pm uninstall -k --user 0 com.huawei.android.launcher". It should show "success".
You are done!
Hope it is usefull.
Click to expand...
Click to collapse
Just some info for anyone... You can safely ignore step 1, and for step 2 just download the minimal adb fastboot package from here: https://forum.xda-developers.com/showthread.php?t=2317790
FYI
{
"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 uninstalled the launcher app in the method described, but now I am having issues using any launcher. In default apps, Launcher, all 3 installed launchers (incl. Nova) are greyed out so I cannot click on one. Any ideas on on to rectify.........No launcher at all.
Has anyone had much experience with the TiVo Stream 4K yet? I have 2 questions really. I would like to accomplish both without rooting the device.
1) Is there a way to skip the initial TiVo activation? I've tried powering off the device once it gets to that screen, but it starts right back up to the activation. I've tried hitting home, back, skip, everything I can think of, but it won't let me move on until the device is activated on a TiVo account. I want to help a buddy out by setting up his device for him, but I don't want the device to be locked to my TiVo account. I may be able to clear data on the TiVo app and remove it from my TiVo account manually (I haven't tried that yet), but I'd like to just skip the whole TiVo activation and let my friend do it all himself (set preferences, services to monitor, etc).
2) Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen? When you go into the Channel Customization, you can deselect all channels but the TiVo Suggestions Channel. I can't even get it to move down the list (all other channels you can go left on the channel and move or remove, but that option isn't available for the TiVo suggestions Channel). I've tried clearing data on the TiVo apps. I've even tried disabling the TiVo and Sling apps, but the channel remains (and if you click it when the apps are disabled, it just errors out loading the app).
The important thing with both of those is it must be done without Root. I want Google Play to remain genuine so Netflix and other streaming apps work properly.
From what I can tell, No and No unfortunately. If you disable the Tivo app as well, the block in the launcher remains and won't go away. If you click it, its magically working again and not disabled. I'm fairly certain they modified the launcher and worked the Tivo stuff is permanent as for the price. The hardware is made by another company, same one that makes their AirTV2 tuner for sling. So I would just setup the tivo stuff under your tivo email. If your friend isn't going to use Tivo services in any way, it won't be an issue for you.
https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.
USAMac said:
https://photos.app.goo.gl/pNcD361dJLsxTxMK9
I went through the original setup and configured it as it expected me to. Then I uninstalled most of the apps it comes bloated with. The ones I couldn't uninstall, I disabled at least visually. Then I installed Wolf Launcher and modified it to my liking. I then moddifed the remote to make the tivo button to open tivimate with a single click and vod apk with double click. I also made the Guide single click to open app history and double to open "Power off, Restart and Screenshot". Sometimes pressing tivo button would bring up the tivo guide and tivimate, so I disabled the tivo app, sling and most other crap entirely I didn't want running in the given app settings.
The only button I could not override was the Netflix button. You cannot uninstall Netflix either, but I believe you can disable it. My device runs incredibly smooth now and my display stays off when I use the power options above. Playback of vod does flicker sometimes, but I feel sure that will get resolved with a future update.
Click to expand...
Click to collapse
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Yea I've had issues with ethernet connection as well. I believe there will be an update soon to resolve alot of the issues. My anker and amazon after ethernet adapters don't work, but I've read ugreen works but some say its unstable.
Anyhow, I used ButtonMapper
siralsmooth said:
Which button remapper app did you use? Might want to do something similar.
Also, not sure if it's just the hub I bought, but the Aukey USB type c 4 port hub doesn't work on the stream, but it does on my Huawei. Strangely a generic type c otg with a USB Ethernet adapter works fine.
Click to expand...
Click to collapse
Hey sorry for the delay! I used ButtonMapper.. and yea, there are alot of externals not working.. hopefully, the pending update will resolve these issues as well!
Is there a way to install the Tivo app on this thing? Kind of ironic it doesn't come with it.
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
what is the point of debug version of the firmware? sorry just asking to clarify
chinkster said:
what is the point of debug version of the firmware? sorry just asking to clarify
Click to expand...
Click to collapse
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.
crackers8199 said:
i'm curious about this too. the new ts4k software is absolute trash, would love to be able to go backwards and keep it from doing updates if possible...but i need more clarity on what exactly this does.
Click to expand...
Click to collapse
I see the commands but do you know exactly how to implement them to flash the firmware? Just asking I've been watching this thread for a while
jmanley69 said:
Has anyone been able to remove the TiVo Suggestions Channel from the Android TV home screen?
Click to expand...
Click to collapse
Might be a year late and I'm sure everyone knows this already but.
If you go to apps system apps then disable the app I circled in this picture then restart your system it will let you freely customize everything on the homescreen. (Besides play next but that can be disabled)
{
"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"
}
ben1226 said:
there is a debug version of the firmware
TIVO - Google Drive
drive.google.com
adb shell reboot fastboot
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot reboot
adb disable-verity
adb reboot
adb root
adb remount
relook command is
fastboot flashing lock_critical
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV
jahrule said:
So, it is important not to have the erase button checked. I mistakenly had it checked and now the device is stuck in USB download mode showing GX-CHIP (instead of worldcup) that is password protected and the password.bin provided does not seem to unlock it. Any guidance would be helpful.
For others, I have successfully downloaded the ota and have flashable images for anyone interested. If you haven't updated you can flash from fastboot, if you haven't then follow what @ben1226 has in TiVo gdrive remember to uncheck erase and then you should be able to unlock flashing from fastboot. The Rom already has a su binary (in /xbin) which can be enabled (permissions are set off by default) for those interested if one wants root.
EDIT: Attached the unmodified OTA update.
ota-type=BLOCK
post-build=eSTREAM4K/SEI400TV/SEI400TV:9/PI/5614:user/release-keys
post-build-incremental=5614
post-sdk-level=28
post-security-patch-level=2021-04-05
post-timestamp=1622542764
pre-device=SEI400TV
Click to expand...
Click to collapse
Is there a guide to do this the links you gave me dont show anything . I'm about to buy one and attempt this but I need instructions I mainly want root .
@tokoam The tools etc are found here https://drive.google.com/drive/folders/18PWax4UPUBAdgAz1R9KnmCNFlt6a3fjA?usp=sharing where @ben1226 linked.
basically don't update it when you first get it. In a few days I will have more as m currently working on something for it.
If you are inpatient and have some know how then: flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options). Then chmod the `su` binary located in /xbin/ and you should have root and be good to go.
flash the update I provided above ... Then chmod the `su` binary located in /xbin/ and you should have root and be good to go
Click to expand...
Click to collapse
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
flash the update I provided above, but NOT the bootloader from there (the updated bootloader enables oem lock and so far have not found a way to expose the option in dev options)
Click to expand...
Click to collapse
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.
Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now
goapy said:
I installed the update that you attached above (in post #13) but there is not any su binary located in /xbin/, or anywhere else.
This seems to make sense, because you say in post #13:
EDIT: Attached the unmodified OTA update.
But I'm not sure why you suggested that the 'su' binary would be there, if the update attached to post #13 was installed.
I didn't flash the bootloader from the update (in post #13), but still the bootloader was locked after I installed the rest of the update. Even if I didn't update bootloader.img or boot.img, the bootloader still gets locked when installing the rest of the update attached to post #13. So, the update is locking the bootloader by other means, probably via system.
I could unlock the bootloader again only by re-flashing the userdebug verson via usb burning mode. But then, of course, I no longer have 5614.
Click to expand...
Click to collapse
jahrule said:
Right the bootloader lock happens only when you flash a system.IMG which is not a user debug version. The su binary is in the debug system img. I think if we can expose the allow OEM unlock option in Dev settings then we would be good to ho. My device bricked in gx-chip mode that apparently uses a different password then the one provided by Ben so im stuck there for now
Click to expand...
Click to collapse
Here is something that can be done:
if (!showEnableOemUnlockPreference()) {
removePreference(this.mEnableOemUnlock);
this.mEnableOemUnlock = null;
That needs to he removed from tvsettings.apk
doing that is the easy part.. but installing the custom apk is the hard part.
need bootloader unlocked so we make changes to system.
the above is decompiled from the userdebug build.
also:
private static boolean showEnableOemUnlockPreference() {
return !SystemProperties.get("ro.frp.pst").equals("");
}
private boolean isOemUnlockAllowed() {
return !this.mUm.hasUserRestriction("no_oem_unlock");
}
pretty much: ro.frp.pst = 1 or true should turn on OEM unlock in developer options.
BTW: user restrictions only means, you must be logged into box with correct username and all..
bypassing settings and logging on as guest or whatever will not show any developer options..
that is what it means about user restrictions..
The circuit board used in the tivo stream 4k has a place for a micro sd card socket. I'm going to install a socket and check if it works.
I read on reddit this morning that the android 10 update started on 3/17. No sign of it on my hardware yet.