Database Develop

2.1 Hero Lock Screen

Got I Question....
Why the Hero doen't show the 2.1 Lock screen...
{
"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"
}
And instead it shows the default one...
Any App or something?

you gotta remove htc's lock screen first.
adb shell
rm /system/app/HtcLockScreen.apk
reboot

justinisyoung said:
you gotta remove htc's lock screen first.
adb shell
rm /system/app/HtcLockScreen.apk
reboot
Click to expand...
Click to collapse
Then what?

I'm Lost becuase I'm a Newbie, and I'm running 2.1 Sprint Update if I could explain step by step, I would be very grateful.

go into a command prompt
Cd C:\AndroidSDK\tools
adb remount
adb shell
adb rm /whereEverTheHellThatLockScreenFileIsPostedAbove
exit
adb reboot
check out the lock screen...it may not be rotary style, it may be slide...
If it isn't rotary, there is an update zip somewhere around here....
Check int he closet...third self, fifth box back...
damn beer....getting to me postings again.

I just rooted my phone and did what you told me and it says Permission denied
C:\android-sdk-windows\tools>adb shell
$ adb rm /system/app/HtcLockScreen.apk
adb rm /system/app/HtcLockScreen.apk
adb: permission denied
$ rm /system/app/HtcLockScreen.apk
rm /system/app/HtcLockScreen.apk
rm failed for /system/app/HtcLockScreen.apk, Permission denied

Got it, remove the HTC Lock Screen but i am having this problem
How do I Resolve this?
I think here is the answer but i don;t know what to do or how to install http://geekfor.me/fixes/vanilla-lockscreen

rockypr said:
Got it, remove the HTC Lock Screen but i am having this problem
How do I Resolve this?
I think here is the answer but i don;t know what to do or how to install http://geekfor.me/fixes/vanilla-lockscreen
Click to expand...
Click to collapse
try
adb remount
then ALL your commands. should work.

Got it, remove the HTC Lock Screen but i am having this problem
How d
Click to expand...
Click to collapse
try
adb remount
then ALL your commands. should work.
Click to expand...
Click to collapse
I removed the default lockscreen, but I am getting the error that shows on the screenshot

riggsandroid said:
try
adb remount
then ALL your commands. should work.
Click to expand...
Click to collapse
What are all the commands? Sorry I'm a noob.

[App][4.0+] CM App Installer

CM App Installer will pull the latest versions of the apps available that CyanogenMod exclusively develop, and give you the option to install them to your system either rooted or non-rooted. I cannot guarantee success with this, I don't develop the application, my job is simply to make it easier for you guys to get your favourite CyanogenMod apps on your own ROMs!
Use carefully! As ever, I do not take responsibilty for any damage done to your device as a result of this! The root features use the code specified in "code" in the options menu, or it's listed below. If you're paranoid, please give it a read
I have to emphasise, please try the non-root method first!. The root method is designed as a last ditch attempt to get it working, it does backup and restore your old versions but errors do happen, expect this as a possibility if you're rooted!
The list of apps available in the application are:
Apollo
Calculator
CM File Manager
Torch
Messaging
DSP Manager
Voice+
News and Weather Widget
Trebuchet Launcher
cLock Widget
Movie Studio
CM Wallpapers
Let me know if you have any more suggestions to add!
Code
This information is also available from within the application.
There are a number of commands that this application uses, it executes certain processes through the code to copy apps to the system directory.
These commands are ran as if they were ran inside the terminal emulator, and always consist of
process, remount to read-write, transfer/copy/rename, remount to read-only, close. (In this order).
I use a Process to get a SU Runtime instance
Code:
Process p = Runtime.getRuntime().exec("su");
And then I use a PrintStream to issue the commands listed below to it.
Remount the system partition as read-write
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Rename an app (use move command to move with a different extension - Creating backups)
Code:
mv /system/app/AppOfChoice.apk /system/app/AppOfChoice.bak
Copy an app from SD card to System directory
Code:
cat /sdcard/CMApps/AppOfChoice.apk > /system/app/AppOfChoice.apk
Remove an app from system partition
Code:
rm -r /system/app/AppOfChoice.apk
For permissions, I use chmod
Code:
chmod 644 /system/app/AppOfChoice.apk
Remount the system partition as read-only
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
And that is it. The process commands get pushed over the course of about two seconds, and should work. Again, I can't promise everything.
Credit also goes to the Reddit member /u/wchill, his code helped with the system code (shown in the Code section above)
Similarly, I do not take any responsibility if this app causes your phone to be bricked, corrupted, broken, or to encounter an unfortunate case of spontaneous combustion. Use at your own risk.
In the mean time, enjoy!
{
"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"
}
Source:
See this xda thread

Access Chrome DevTools / Remote Debugging

Hi,
I'm interested in hacking some of the existing apps to see how they tick, since most of them are just HTML + CSS. I've been sleuthing around trying to find how to enable the remote debugging port of Chrome which is usually available (and even officially for apps that you actually register yourself). I've found
Code:
/data/chrome/.eureka.conf
contains a enable_remote_debugging flag which is currently set to false, is it as simple as modifying the file to say true? Does anyone know if this file is checksummed or have any other checking preventing me from modifying it? I normally would go right ahead but I don't want to brick the device, so I'm posting here for some reassurance/guidance.
Cheers,

Did it.
{
"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"
}
Posting it here in case someone is trying to achieve the same/similar things with their own Chromecast.
HOW TO: Add (any?) Chrome command-line argument to the Chromecast shell / Get the remote DevTools working.
Note: You will need root access to your Chromecast to perform these steps. This guide assumes you have busybox installed and on your PATH
SSH into your Chromecast, this is usually just ssh [email protected], although you may need to specify an IP address in place of Chromecast if your router does not automatically create a DNS entry for it.
Optional: once in your SSH session type busybox sh to get a terminal that supports history and tab completion.
Copy the process.json file somewhere you can modify it and make it readable for the 'chrome' user:
Code:
busybox cp /system/chrome/process.json /data/chrome/process.json
chown chrome:chrome /data/chrome/process.json
Modify the process.json file to add "enable-remote-debugging" and "remote-debugging-port" (or whatever other flags you want to use) to the cast_shell external_flags JSON array and save the file. The only editor I found on the device was busybox's vi, so you'll need to know the basics to modify that file, or use adb and modify it elsewhere.
Extract the environment variables from the running cast shell process
Code:
ps | grep cast_shell # take note of the PID
busybox xargs -0 busybox echo < /proc/1234/environ # where 1234 is the PID from the previous step
Copy that line for later, the output should something look like: (you can most likely copy this, but it may change depending on your firmware version)
Code:
LD_LIBRARY_PATH=/system/lib PLAYREADY_STORE_DIR=/data/netflix/AACS/ CAST_CLIENT_CERT=/factory/client.crt CAST_CLIENT_PRIVKEY=/factory/client.key.bin CAST_CLIENT_CERT_CHAIN=/system/etc/cert_chain.pem HOME=/data/chrome/
Switch to the 'chrome' user (the groups may be different for your firmware, check by reading /init.rc and looking under groups for cast_receiver service)
Code:
sudo -u chrome -g chrome:graphics:wifi:net_mgr:watchdog:log:panel:metrics /bin/busybox sh
Now paste that line on ENV vars and on the same line type:
Code:
/system/chrome/cast_cli stop cast
Your TV may turn off at this step. You can safely turn it back on.
Paste the line of ENV vars again and then again on the same line type:
Code:
/system/chrome/cast_cli --process-json-path=/data/chrome/process.json --enable-remote-debugging --remote-debugging-port=9222 start cast
If you are running adb logcat in another window, you should start to see cast_shell starting up. If it crashes, be sure to read the log to find out what's going wrong. It normally takes 10-30 seconds to show the backdrop again on the screen.
Now that the cast shell is running in debug mode, you should be able to navigate to http://chromecast:9222 and inspect your browser window remotely (or replace chromecast with your IP address).
Enjoy!

SU Binary files : not installed

When i check Root with Root Checker, in Stage 2 is Superuser Binary files : Not Installed. How repair this problem ?

Marek89 said:
When i check Root with Root Checker, in Stage 2 is Superuser Binary files : Not Installed. How repair this problem ?
Click to expand...
Click to collapse
Use magisk
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

i use magisk, but root checker not see binnary files.

any solution to my problem ?

Superuser Binary Files : Not Installed
black_file said:
Use magisk
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Click to expand...
Click to collapse
Rooted my phone by flashing Magisk 19.3. Root Checker verifies- the device is rooted but it also states :
Stage 2 - Superuser Binary
Files: Not Installed
Standard System Location
Command: Is -I /system/bin/su
Result: Is: /system/bin/su. No
such file or directory
Analysis: File /system/bin/su
does not exist.
Standard System Location
Command: Is -I /system/xbin/su
Result: Is: /system/xbin/su: No
such file or directory
Analysis. File /system/xbin/su
does not exist.
Standard System-less Location
Command: Is -I /su/bin/su
Result: Is: /su/bin/su: No such file
or directory
Analysis: File /su/bin/su does not
exist.
Alternative Location
Command; Is -I /sbin/su
Result: Irwxrwxrwx 1 root root
12 1970-03-26 00:23 /sbin/su -> /
sbin/magisk
Analysis:
Alternative Location
Command: Is -I /system/sbin/su
Result: Is; /system/sbin/su: No
such file or directory
Analysis: File/system/sbin/su
does not exist.
Alternative Location
Command: Is -I /system/xbin/
sudo
Result: Is: /system/xbin/sudo: No
such file or directory
Analysis: File/system/xbin/sudo
does not exist.
Should I be worried about this ? Should I install Supersu and update the binaries OR should the message be ignored.
I read on the forum that Magisk is an alternative to Supersu so am confused.Please enlighten :angel: a newbie.
Root Checker screenshot :
{
"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"
}

@GOD-TheSupreme
The root checker used doesn't recognise Magisk. It finds it:
Code:
Alternative Location
Command; Is -I /sbin/su
Result: Irwxrwxrwx 1 root root
12 1970-03-26 00:23 /sbin/su -> /
sbin/magisk
But, it doesn't know what it's looking at. It's probably not been updated in a long time and still think that SuperSU is the way to go...
Root checkers feel like quite an outdated thing though. If you have root, you'll see it in the Magisk Manager.
And by the way, superuser is not the same thing as SuperSU...

Binary files not installed
Have root on kindle fire with kingroot but su binary files not installed

Hi, im noob in rooting And i install magisk new version And root with SuperSU root Is compleate but "stage 2 supersu binary files not found" And my 128gb Samsung Galaxy S10 convert to 32gb when i put original firmware all Its ok but i want root And 32gb Its low And moduls in magisk noting do can't change my ui design or any in system anyone help please

Fresz

[GUIDE] Not registered on network fix - EFS failed to mount - NO IMEI or Zero IMEI

Today i got an issue for my N960F after flashing a custom ROM. I'm not sure till now what've gone wrong, but after rebooting my device i faced an issue that my SIM card can not register on network.
Cellular network signal is full, but can not make any calls and can not connect to data.
Tried to restore through TWRP with a nand backup, but always fails as EFS partition can not be mounted. Eventually I managed to restore my EFS partition after following the hereunder steps.
I'll just leave it here if anyone faced the same in the future.
Disclaimer: You are doing this at your own risk. I shall not be held liable for any losses or bricked devices ( They already are )
Pre requisites:
- ADB on your PC, latest SDK is preferred.
- Custom recovery ( with ADB enabled )
- Better to have a previous EFS backup
Steps:
- Reboot into recovery and enable ADB ( in TWRP, ADB is enabled by default )
- Attach your device to your PC. and open your terminal or command prompt as an admin.
- Type the following commands:
- Navigate to your ADB folder ( in my case it is C:/ADB )
cd C:/ADB
- Ensure that your phone is readable in ADB mode
c:\ADB>adb devices[ATTACH type="full"]5610649[/ATTACH]
c:\ADB>adb shell
Your terminal handle should change into root ~ #
~ # cd /dev/block
/dev/block # ls
you should get an output like this
{
"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"
}
/dev/block # cd by-name
/dev/block/by-name # ls -la
you should see device partitions listed as this .. EFS partition is highlighted in yellow and is on sda3 as below
/dev/block/by-name # mke2fs /dev/block/sda3
and you should be prompted by a message to proceed or not. Press y then enter
Finally,
/dev/block/by-name # mount -w -t ext4 /dev/block/sda3
We successfully formatted and mounted EFS partition and now either to restore your old EFS backup or flash stock firmware through ODIN.
Resources: