Develop Bugs

[DEV] Nemo Mobile - Alpha

This is non androd, non based on android ROM
This OS based on Meego.
I promised to publish a small guide how to boot Nemo Mobile on your phone instead of the default android. Here is a small guide how to do so. The process it self is quite simple and should be relatively safe as well, as you do not need to flash anything to try it out.
In this guide it is assumed that one has android tools, such as adb and fastboot installed, also Linux is assumed but it should work also on windows with minor modifications.
The phone used was unlocked/rooted before I tried this, so that might also be required for following these instructions.
First thing is to download all the needed files:
Downloads:
rootfs image: - http://sage.kapsi.fi/sagestechblog/gt-i9250/2012-04-26.1/nemo-handset-armv7l-gt-i9250.img.bz2
Kernel: - http://d-h.st/Ffw (also with this kernel you can boot arm linux)
Instruction:
Push the rootfs image to the /sdcard
# Uncompress
adb shell bzip2 -d /sdcard/nemo-handset-armv7l-gt-i9250.img.bz2
adb shell mv /sdcard/nemo-handset-armv7l-gt-i9250.img /sdcard/image.img
2. Download and flash kernel.elf
fastboot flash boot kernel.elf
fastboot reboot
Or with Flash Tools
3. Connect mouse via OTG
After this, the device should boot to the MTF based UX home screen.
What works:
USB OTG
USB Mouse/Keyboard
Display
Backlight
What no works:
Xorg starts with standard fbdev (no 3D acceleration)
Applications do not start as the software flag isn't forwarded properly
No window manager/application switcher (requires 3D)
No 3D acceleration
Touch screen
Sensors (Especially disabled)
No USB networking
No WLAN
No Bluetooth
No Sound
Touch keys
Hardware keys
...
Kernel sources:
https://github.com/XperiaNext/kernel_sony_msm8x60/tree/msm-3.0.67-fb

Changelog:
Alpha
- Added in kernel framebuffer support for booting this OS

Small preview:
Video:
Screenshots:
{
"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"
}

WOW，looks very powerful, but not for daily use.

Wow nice :good: keep going
waiting for better version with working touch . wifi etc....

[SCRIPT][DEV] All-In-One-ToolBox

Information for all:
This script is designed to house all my other scripts and other scripts from other people in a uniform way.
It is still under development, however i dont mind you guys trying it out, asking for etas, suggesting ideas or complaining that it covered you cat in gravy, im chill with that, and if you want to help go ahead. Just a little thing, if your commenting to help, please put all your text in bold so i can see the comment easier and reply and etc.
Script design:
The script has a busybox check and su check at the beginning, so you need both the latest complete busybox and its applets and the latest su installed.
The script then redirects you to a menu of selectable applets. I plan on making an applet input section where you can make your own applets and combine them into the menu (using greps and cats from files on sd), this idea has never been thought of in a script as far as i know, so for now its got a huge © symbol
There the script currently ends, since there is no redirect code for the script to go to when you select something.
How you can help?
Well if you have knowledge in bash or linux low level stuff like the kernel and vm and lmk, you can pm me suggestions or email me at [email protected] (preferred) or you can contribute code to the project over at github project page.
Or if you are a regular user you can run the script in smanager/a terminal emulator with root and attach a log of all the text from run-time of the script. This should help me debug the script even faster.
TL;DR: This is Pimp-My-ROM in a script. Enjoy!
XDA:DevDB Information
AIO-ToolBox, ROM for the Moto G 2014
Contributors
Pizza_Dox, luca020400, hoholee12
Source Code: https://github.com/Pizza-Dox/AIO
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Current Stable Version: ~WIP~
Stable Release Date: 2012-12-12
Current Beta Version: ~WIP~
Beta Release Date: 2012-12-12
Created 2015-02-27
Last Updated 2015-02-27

Changes: https://github.com/Pizza-Dox/AIO/commits/master

Screenshots:
{
"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"
}
Sent from my Moto G 2014

[SOLVED] ADB Devices Unauthorized

I am trying to get rid of this extremely buggy and heavy, Asus Zen software, on my ZE551ML, and replace it with something else, but I'm running into walls, everywhere I go. First, in ADB, I get
Code:
List of devices attached
F6AZFG14H361 unauthorized
I have tried clicking Revoke USB debugging authorizations, but that didn't help anything. I tried restarting ADB, didn't work. I know those are supposed to be the steps, but they aren't working, for me.
I am on ROM ww_2.20.40.174. Has anyone else had this problem?

Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
{
"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"
}

Kid_Ding said:
Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
Click to expand...
Click to collapse
It never gives me this popup. It "sees" the device, but never asks to add the fingerprint.
All of this assumes your Zenfone 2 is being recognized by the computer, running the command:
Code:
lsusb
Bus 003 Device 015: ID 0b05:5601 ASUSTek Computer, Inc.
If it is not, you have another problem. If it is being recognized, continue.
[SOLUTION BELOW]
Ubuntu 14:
Kill the ADB server.
Code:
adb kill-server
In the user's profile, look for a folder called .android. The folder may be hidden or owned by root. If the folder is owned by root, run these commands with the sudo prefix or sudo -s to promote to the root user.
Code:
ls -la
drwxr-x--- 2 root root 4096 Mar 21 10:24 [COLOR="Blue"].android[/COLOR]
Rename the folder to .android.old.
Code:
mv .android .android.old
Remove the USB debugging authorizations, on your phone, in developer options.
Restart the ADB server
Code:
adb start-server
If your usb is still plugged in, it should pop up the dialog to add the RSA fingerprint. Do so.
Check to see if the phone is recognized.
Code:
adb devices
List of devices attached
F6AZFG14H361 device
Thanks for the help.

help
excuse me, i am in the same situation, but my phone is stuck on recovery screen , i need a code to authorize it through adb only (( , any help???

[TOOL] [Linux] [8.1.0/9.0/10.0] Stock-Rom Flash Tool Nokia 6.1 Plus [DRG_sprout]

Note - I'am Not Responsible for bricked devices
this tool is a Linux port of Raghu varma's tool
{
"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"
}
-= Usage =-
Note - Make sure your phone bootloader is unlocked
1. Download qNokiaTool.zip & extract it, or just download the binary file
Note: if the binary didn't work download and compile the source code from below
2. Download latest HOME BREW Stock ROM And extract in one directory
3. Copy qNokiaTool.bin into the ROM directory
4. Now connect phone to PC
5. Go to download mode
6. Open that directory in terminal and run qNokiaTool.bin as root i.e. sudo ./qNokiaTool.bin
7. Make sure to press ok on every flashing step
8. Now select Button according to your Phone code
9. Example I'm Using Nokia 6.2 Plus & My phone code SLD & so I will choose [DDV SLD] same option for 7.2 for 6.1 , 7.1 & 7+ users choose [ DRG B2N CTL PL2 ]
10. I will click on [DDV SLD] According to my phone as i explained in point #9
11. wait for 10 min Tool will flash the rom & your phone reboots to system.
12. So finally this is what the exact standard method to flash stock rom on Your devices
Download Binary file
Download Stock ROMS​
XDA Dev DB Information:
Stock-Rom Flash Tool Nokia 6.2 ported for Linux
Contributors:
@baraa-almasri
Credits:
Raghu Varma for allowing me to port his program
Source Code:
https://github.com/baraa-almasri/qNokiaTool
Version Information
Status: Alpha 0.2
Current Stable Version: Alpha 0.2
Stable Release Date Alpha 0.2
Created 2020-04-14
Last Updated 2020-04-16

Wrong section

PaperPlane217 said:
Wrong section
Click to expand...
Click to collapse
I know, but I can't post in development

Question Debug Over Wifi Option Missing from Developer Settings

I have been trying to enable ADB debugging over WiFi on my Pixel Watch, although the option to debug over WiFi seems to be missing from the developer settings on my device. I have tried connecting to two different networks, restarting my watch, and verifying that my watch is running the latest software, yet the result is the same. I have also tried enabling "wireless debugging" on its own. When I run adb connect <ip_address> or adb connect <ip_address:port>, the message "No connection could be made because the target machine actively refused it" always shows. I would appreciate any help that I could get with this issue, as I would like to run faces that I create with Watch Face Studio on my Pixel Watch, and I do not believe that I have any other way to do so.
{
"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 have now tried resetting the Pixel Watch, and the issue persists as described in the original post.

Probably you need to pair, follow the steps here, and you will be able to.
[TOOL] All-in-One tool for Windows. Wear OS Tools v9.0
All-in-One tool for Windows. Wear OS Tools v9.0 It's a tool for use with any Wear OS watch. I am releasing today an improved and optimized version with several new features. What does it do? It is an All-in-One tool for Windows that makes it...
forum.xda-developers.com

bernarbernuli said:
Probably you need to pair, follow the steps here, and you will be able to.
[TOOL] All-in-One tool for Windows. Wear OS Tools v9.0
All-in-One tool for Windows. Wear OS Tools v9.0 It's a tool for use with any Wear OS watch. I am releasing today an improved and optimized version with several new features. What does it do? It is an All-in-One tool for Windows that makes it...
forum.xda-developers.com
Click to expand...
Click to collapse
I assume that you are referring to the instructions given in the section "Clarification on the new pairing procedure in Pixel Watch," but please correct me if I am wrong. Once I obtain a pairing code, IP address, and port number, how do I enter this information on another device without first enabling debugging over WiFi? I am using a laptop running the latest version of Windows 11 and a Pixel 7 running the latest version of Android 13. Alternatively, is there another way that I can use the tool to pair my watch without having debugging over WiFi enabled?

Actually, I was able to connect my watch properly by running the tool, entering the IP address and port and following the instructions from there. Thank you for sharing!