Develop Bugs

[DEPRECATED][GUIDE][ROOT] Smartwatch 3 KNX01V

I removed download link due to this method not working on lollipop.
This guide is deprecated, please use TWRP Recovery from this thread to install root
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
You have been warned!
Links:
Sony PC Companion
Download link removed while I will test for compatibility with 5.x, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"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"
}

reserved

How it works:
1. Each boot.img packs zImage (real kernel) and ramdisk (special files for kernel use)
2. This one has all modifications from LGGW rootboot by Justin Case:
a. Adds su binary, superuser.sh install script, modified install-recovery.sh and additional step into init.rc file to invoke superuser.sh install script. Also modifications to mount system as rw and some disabled security.
3. So basically it mount system as rw and does following (cut from superuser.sh install script):
Code:
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/sleep 2
/system/bin/cat /sbin/su > /system/xbin/su
/system/bin/cat /sbin/su > /system/xbin/daemonsu
/system/bin/cat /sbin/install-recovery.sh > /system/etc/install-recovery.sh
/system/bin/chown 0.0 /system/xbin/su
/system/bin/chown 0.0 /system/xbin/daemonsu
/system/bin/chown 0.0 /system/etc/install-recovery.sh
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu
/system/bin/chmod 755 /system/etc/install-recovery.sh
/system/bin/sync
/system/bin/sleep 3
/system/bin/reboot

I have dumped the rom from my debug/test version and was wondering if you were able to give me a guide on how i could try and flash it with a retail version? I presume this root guide probably won't work for me

Well, if hardware and partitions are the same - I do not see why it will not work. However, it will not help to flash.
I might try to compile twrp, but will have to carefully read its docs first.

thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?

iBuzman said:
thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?
Click to expand...
Click to collapse
Thanks for letting me know!
I reverse engineered changes in LGGW by unpacking and comparing ramdisks from both rootboot and original lg kernel and then applied the same changes to our kernel extracted from PC Companion files.

great thinking and good job ?
btw, that pic confirmed su access to watch over bluetooth debug connection ?

really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
how to benefit?
root apps of course!!
(sry for bad pic, unlocked bootloader z3 in low light [emoji12]

XorZone said:
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.
Click to expand...
Click to collapse
that's awesome man! will purchase mine next week, can't wait to root it. thanks for the answer.

Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.

cb22 said:
Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.
Click to expand...
Click to collapse
Yeah, I noticed the same about WiFi chip, it might be that they packed bcm43341 as part of the BCM23550 soc, like Invensense MPU9250 chip packs mpu6500 inside.
For the 43341 I'm finding it in the configs here: https://android.googlesource.com/kernel/tegra/+/bdde9f16131a5ac2039062d5ce22e3e153acbe68^!/
Looks like BCM43341 is BCM4334 + NFC chip, so we could try S3 I9300 files as per http://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9300Firmwares

how can i grant superuser permission to an app? i install es file explorer with sideload but i can't get superuser permission. the procedure is ok

Sorry admins for not putting in correct location....
Moved to Correct Area!

cdrshm said:
Sorry admins for not putting in correct location....
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Click to expand...
Click to collapse
As usual, check if adb enabled in settings-about-developer options, if there are no developer options - it is as usual 7 times click on build number in about screen.

And please use Q&A thread for such questions

I've confirmed root survives the Lollipop update

Wow, I was out whole weekend, will have to catch up with the update

[Rom][5.0.2]UNOFFICIAL FlymeOS 4.5.3.1

{
"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"
}
_________________​Hi XDA Developer
Here another port of flymeos from member:MROM
I saw it on Another website and want to share it with you
The new port has many improvements ....
IAM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS FROM YOUR PHONE
Thanks for topsecret78 for get rom source and change details
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Click to expand...
Click to collapse
Changelog
CHECK DOWNLOAD PAGE FOR CHANGELOG
here some pics
Another screenshots here
Click to expand...
Click to collapse
So we Reach the download part
Note : looks like flyme 5 is officially maintained by (machao) member on (gfan) forum and latest builds will be found HERE
flyme 4.5.4.3 beta Google Drive
Downloaded it?! Let's install it and taste flyme
First ensure your bootloader is unlocked
1. Put Zip file on your sdcard
2. Restart your phone into your favourite recovery
3. Backup your data
4. Wipe (System,Data,cache,dalvik cache) not important to wipe internal memory
5. Install Zip from sdcard
6.restart system
First start will take 5 up to 10 min so don't think it's bootloop
TESTED ON C6903
After start let it 2 min and restart to install Su
You can download it from official website or you can use kingroot or kingo to root

Please sent permission to download file rom.

You can download now
Hit thanks if you like it

abdo.war said:
You can download now
Hit thanks if you like it
Click to expand...
Click to collapse
Where are kernel sources? You can't post a rom without posting kernel sources. Also, could you post a link to rom sources too. Thanks.

I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me

abdo.war said:
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
Click to expand...
Click to collapse
Doesn't matter who the builder is: posting roms without kernel sources is not allowed. For your sake you should post kernel sources or the mods will close this thread.

Report thread to mods to close it
I am sorry but I am still new here

abdo.war said:
Report thread to mods to close it
I am sorry but I am still new here
Click to expand...
Click to collapse
I am not going to report you, but rules are rules. They are part of GPL license...

Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Translate from google
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone

hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..

markakash said:
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
Click to expand...
Click to collapse
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
fastboot flash boot boot.IMG
Then reboot
fastboot reboot
Click to expand...
Click to collapse
Then try to install it
I installed rom from flashfire but it's dangerous

link to download in fisrt post
https://drive.google.com/file/d/0B3yReeEdHxbWSkFrYmhXbjJRaE0/view
or
http://pan.baidu.com/s/1pJXPr8R
I tested and work xperia Z1 C6903
---------- Post added at 16:30 ---------- Previous post was at 16:21 ----------
Info from source
"According to the competition regulations to place the file and naming 2: According to the rules without built-root themselves into the brush to 3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart"
and
"Please read the complete message painted machine
ROM tested before release because of personal consequences Brush problems caused not bear
Built-in networking to promote the software, please support the author can then run reservations can also uninstall (as some promotion app requires placing it under the system needs to RE Manager Entering system / app Delete)
Prohibit secondary modified to personally thank all publication reproduced, please indicate support oil"

Since this is based on CM12 meaning android 5.0.2
Does this have any slow charging issues?

Rom update to Flyme 4.5.4.4R
Change details ========================== ======================
Update fixes
[Contact]
All models support SIM card contacts
【camera】
Repair photographs sound problems can not be closed
Added (some models) Set the option to save photos to SD card
【music】
Repair song not normally know the songs matching problem
【other】
Living repair service hotel category loading problems
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Link to download
http://pan.baidu.com/s/1jGYfpdG
1: According to the competition regulations to place the file and naming
2: According to the rules without built-root themselves into the brush to
3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart

What about C6902??

abdo.war said:
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
Then try to install it
I installed rom from flashfire but it's dangerous
Click to expand...
Click to collapse
whare boot.IMG??

msamsameemo said:
whare boot.IMG??
Click to expand...
Click to collapse
In the Zip file

Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875

topsecret78 said:
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
Click to expand...
Click to collapse
What's the password?

Abu Badr said:
What's the password?
Click to expand...
Click to collapse
you don't need this link i already uploaded it to google drive go to
download at first post under screenshots
i have uploaded too iuni os if you want i can post it
Click to expand...
Click to collapse

[DISCOVERY] Looking for info to try to support recovery on International honor 5X

If you're in the USA, TWRP and root are available for you here - but only if you have the KIW-L24 model:
[TWRP] for KIW-L24 USA (kiwi)
^^ That recovery is not recommended or tested for any version other than KIW-L24 as of February 10, 2016.
So here's the situation:
We may be able to support other versions for international users
We make no promises
We are providing a tool and instructions for you to give us the information we need about your version
We make no promises
You MUST give the information exactly as we request
No personal information is being gathered - none
We've made it as easy as possible, you don't have to be an expert
We may have to come back and ask you for more information
We make no promises
But we are willing to try if you want to help
Instructions:
Download the attached zip file and unzip it on your phone - ES File Explorer or equivalent is fine
Run the script: find-honor.sh
Copy the contents of /sdcard/found-honor.txt to http://hastebin.com
Post the link to your hastebin here in the thread
DO NOT post the output here - we're not going to manage to that - only post your hastebin.com link, ok
You may run the script however you like:
adb shell or Terminal Emulator
or just use SH Script Runner (instructions on that will come later in the thread)
Shell/terminal instructions:
cd to the folder where you unzipped the script
Execute the following command:
source find-honor.txt
How to upload:
Go to the found-honor.txt file in your file browser
/sdcard, /storage/emulated/0 and Internal Storage all mean the same thing on your phone
Open, select all, copy
Paste and save to hastebin.com
Pictures follow, in my example I use the built-in Files app
Go to the internal storage, tap on find-honor.txt
OK to open Just Once with HTMLViewer
Long press any word to get menu on bottom
Select all, then copy
Goto http://hastebin.com and paste
Find the disk image in the upper right corner to save
Post the link
Your output will look similar to http://hastebin.com/norufikubu.avrasm
{
"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"
}
SH Script Runner Instructions:
Load the file as shown in the pictures
Run it with the little run button next to the name in the top bar
Post results to hastebin using instructions above
DOWNLOAD SCRIPT HERE:
View attachment find-honor.sh.zip

If you're curious to see the how the information is being gathered:
Code:
#!/system/bin/sh
#
# Find honor 5X properties for recovery exploration
# EarlyMon 2016/02/08
TARG=/sdcard/found-honor.txt
getprop | grep -i ro.build.product > $TARG
echo "" >> $TARG
grep -i msm /system/build.prop >> $TARG
echo "" >> $TARG
cat /proc/meminfo | grep -i memtotal >> $TARG
echo "" >> $TARG
cat /proc/partitions >> $TARG
echo "" >> $TARG
cd /sys/dev/block
for i in 179:*
do
cat $i/uevent | grep NAME >> $TARG
echo "" >> $TARG
done
cd - > /dev/null
df >> $TARG 2> /dev/null
echo "" >> $TARG
cat /proc/self/mountinfo >> $TARG
echo "" >> $TARG
cat /system/build.prop >> $TARG
echo ""
echo "Copy the contents of"
echo ""
echo "$TARG"
echo ""
echo "to hastebin.com"
echo ""
echo "Post the hastebin.com link in the thread."
Remember -
ONLY POST YOUR DATA LINK, LIKE THIS:
http://hastebin.com/norufikubu.avrasm
You can see from my sample link that nothing personal is being gathered.

Happy to help
Hope this helps:
/eqokatoboh.md
If this is against the rules, then delete it.
Have a nice day
Widos

WidosFTW said:
Hope this helps:
/eqokatoboh.md
If this is against the rules, then delete it.
Have a nice day
Widos
Click to expand...
Click to collapse
http://hastebin.com/eqokatoboh.md
That works, thanks.
That's a 2/16 KIW-L21

Run Script with SH Script Runner
hastebin. com / ujotesawow.md
Im a new user so i cant post links

racing2410 said:
Run Script with SH Script Runner
hastebin. com / ujotesawow.md
Im a new user so i cant post links
Click to expand...
Click to collapse
Welcome to the forums.
http://hastebin.com/ujotesawow.md
Another 2/16 KIW-L21 - thanks!

@WidosFTW or @racing2410
Per suggestions from the team (shm and Ncypt3d) after reviewing your data, we've decided to update the script because we don't want to take the chance relying on the honor website specs.
Please refer to the following picture from the app CPU-X in the Play Store:
The top of yours ought to be similar and say MSM 8939 HUAWEI KIW-L21 (where mine says L23).
If there is any doubt, please erase the old find-honor.sh on your phone, get the new copy from the OP, and repeat the process for us.
Many thanks!

ok lets see
hastebin /ereyaronoh.avrasm

Done it @EarlyMon
/oqiqemojer.avrasm

http://hastebin.com/ereyaronoh.avrasm
http://hastebin.com/oqiqemojer.avrasm
Perfect, just what we expected, thanks!

I'm on the US version but still appreciate that you're working on our international brothers and sisters 5xs. So I must say....this sounds "very promising "! Sorry I couldn't help it.

WidosFTW said:
Done it @EarlyMon
/oqiqemojer.avrasm
Click to expand...
Click to collapse
racing2410 said:
ok lets see
hastebin /ereyaronoh.avrasm
Click to expand...
Click to collapse
From what i can tell from the info provided the L24 twrp recovery should work on L21.
Here is the official L24 twrp:
https://dl.twrp.me/kiwi/twrp-3.0.0-0-kiwi.img.html
Stock L21 recovery encase it does not work:
https://www.androidfilehost.com/?fid=24411628330025737
If there is a error please put as much info as you can get and pictures if possible. Also attach a recovery.log so we can double check everything is working.

ok i will try to flash the recovery after work. first i have to unlock my bootloader :angel:

deadman96385 said:
From what i can tell from the info provided the L24 twrp recovery should work on the L21.
If there is a error please put as much info as you can get and pictures if possible. Also attach a recovery.log so we can double check everything is working.
Click to expand...
Click to collapse
The installation works fine and it also starts the twrp but you cant use it properly because you get the touchscreen error, which was already described in the US Thread. I dont know where the recovery.log is so I cant post it here. I somehow managed to install root but I would consider this unusable.
Edit:
Found the log, it is in the attachments.

Can confirm. Installing TWRP was fine, but it can't be used (touchscreen does not recognize input)

LordKelsier said:
Can confirm. Installing TWRP was fine, but it can't be used (touchscreen does not recognize input)
Click to expand...
Click to collapse
You mentioned that you were able to use the debloat method on your KIW-L21.
Did something change on the touchscreen usability or can you elaborate for the benefit of us and others?

EarlyMon said:
You mentioned that you were able to use the debloat method on your KIW-L21.
Did something change on the touchscreen usability or can you elaborate for the benefit of us and others?
Click to expand...
Click to collapse
Someone in the main thread posted that you have to tap the screen extremely fast and that the issue is most likely a bug in the TWRP software (not waiting long enough for user input or something). It worked this way but is extremely luck based. Like I had to try and flash the zip file 10 times before I was able to slide the slider while not having the archive validation checkbox checked.
Selecting the "install" button and the archive itself also took a few minutes. Basically you'll have to hammer your screen at 5 touches per second or something for it recognize

Same with me it took me about an hour to get it working.

We've been discussing the touchscreen among ourselves and your feedback may help - thanks!
Sent from my KIW-L24 using XDA Free mobile app

Do you still need ppl to run the script for the L21?

[ZIP] [FLASHABLE] [ROOT] [04-28-2017] (Re)Enable Hotspot (Stock or Custom) [MM & N]

[ZIP] [FLASHABLE] [ROOT] [04-28-2017] (Re)Enable Hotspot (Stock or Custom) [MM & N]
Introduction
This flash fixes the telephony database (i.e., /data/data/com.android.providers.telephony/databases/telephony.db) and if necessary injects busybox and init.d support into ROMs. The purpose is to properly enable hotspot tether support. It fixes the hotspot support on each reboot so if you lose hotspot due to, for example, a factory data reset, this will repair the database at the next boot.
DISCLAIMER
Always read the DISCLAIMER file before committing to the use of this flashable mod.
What It Does NOT Do
The flash does not add the hotspot menu item to ROMs that do not otherwise have it. In other words, if you do not have a 'Hotspot' menu in your Settings or other toggle items, this flash will not add those. You need to talk to your ROM developer in order to get those.
What It Does
The flash does two basic things for ROMs WITH built in init.d support:
Installs a working sqlite3 executable at /system/xbin/sqlite3;
installs an init.d script at /system/etc/init.d/01-hotspot to correct telephone database settings;
installs an init.d script at /system/etc/init.d/02-hotspot to add a quick setting tile for hotspot;
sets global setting tether_dun_required to 0 (zero).
Most custom kernel flashes modify the init files to support calling on /system/xbin/run-parts to run the scripts in /system/etc/init.d -- check the boot image you are using.
The flash does quite a bit more for ROMs missing init.d support (e.g., stock):
Installs a working busybox (and all applets) at /system/xbin;
Installs a working sqlite3 executable at /system/xbin/sqlite3;
Injects init.d support into the boot image (boot.img);
installs an init.d script at /system/etc/init.d/01-hotspot to correct telephone database settings;
installs an init.d script at /system/etc/init.d/02-hotspot to add a quick setting tile for hotspot;
regularly checks and keeps global setting tether_dun_required at 0 (zero);
add build.prop setting to enable USB tethering.
The script at /system/etc/init.d/01-hotspot logs its operations to logcat so you can see what it did, if anything at all. Make sure you have logging enabled if you use a kernel that supports such changes (e.g., my SkyHigh port).
Hope this helps those who are having troubles with hotspots after wiping data before or after flashing ROMs.
Instructions for ROMS that DO HAVE init.d Support
Download the hotspot-v5.zip file from Android File Host (MD5 sum: 201820413864c9d60e971d06a59ac8ff)
Copy the hotspot.zip file to your phone, assume to /sdcard/hotspot-v5.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-v5.zip)
Reboot to system (Android)
Instructions for ROMS that DO NOT HAVE init.d Support Built-In
Download the hotspot-busybox-initd-v6.zip file from Android File Host (MD5 sum: 60f01ccdfe88a22673ef0efe6e390309)
Copy the hotspot-busybox-initd-v6.zip file to your phone, assume to /sdcard/hotspot-busybox-initd-v6.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-busybox-initd-v6.zip)
Reboot to system (Android)
Previous Versions:
Instructions for ROMS that DO HAVE init.d Support
Download the hotspot-v4.zip file from Android File Host (MD5 sum: 40082313f82c7cbe7b866d77e250f16e)
Copy the hotspot.zip file to your phone, assume to /sdcard/hotspot-v3.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-v4.zip)
Reboot to system (Android)
Instructions for ROMS that DO NOT HAVE init.d Support Built-In
Download the hotspot-busybox-initd-v4.zip file from Android File Host (MD5 sum: c495361fdd3cc72e52e868473fe5fb92)
Copy the hotspot-busybox-initd-v4.zip file to your phone, assume to /sdcard/hotspot-busybox-initd-v3.zip
Boot into TWRP Recovery
Install the zip (e.g, from /sdcard/hotspot-busybox-initd-v3.zip)
Reboot to system (Android)
Version 3 for ROMS that ALREADY HAVE init.d Support Built-In: Android File Host (MD5 sum: 77611280dac47c6ca328aff73d721d56)
Version 3 for ROMS that DO NOT HAVE init.d Support Built-In: Android File Host (MD5 sum: 48a3e3ba78892927a3b26e45b2052e30)
Version 2 hotspot-busybox-initd-v2.zip: Android File Host (MD5 sum: 5b978c9312f79f6d26f541811160350a)
Version 1 hotspot-busybox-initd.zip: Android File Host (MD5 sum: 45b8bea3e01fa74e443ea1ec9791561f)
ROMS Tested
TeamSPR ROM
Stock, rooted 6.0.1
Stock, rooted 5.1.1
Note: Some recent ROMS include this script in the init.d support already (e.g., TeamSPR v3).
If you verify on another, please let me know and I'll add it to this list.
Notices
The flash for ROMs not having init.d support includes:
The busybox program in binary form. Busybox is a GPLv2 licensed tool, which provides you the option to receive source code underlying the binary executable. That source code can be found here: http://git.busybox.net/busybox/. If you want that source code and cannot obtain, feel free to ask me and I will get you a copy by reasonable means, at your cost.
The sqlite3 program in binary form. SQLite is a public domain program. You can read its license here: https://www.sqlite.org/copyright.html.
The programs known as mkbootfs, mkbootimg and unpackbootimg. These are all licensed under the Apache 2.0 License. The sources may be found here: https://github.com/osm0sis/Android-Image-Kitchen/blob/master/authors.txt.

Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Change log
This post will keep up to date the various changes that occur from version to version of each flash in this thread.
hotspot-v5 and hotspot-busybox-initd-v5:
Updated to support Nougat.
hotspot-v3 and hotspot-busybox-initd-v3:
Now sets all APNs that have MMS type set to include DUN type as well (tethering). The belief is this should also fix many non-sprint carrier variants, but testing all those is not something possible for the author.
All init.d scripts log to logcat for all versions.
hotspot-busybox-initd-v2:
Now honors (and reinjects) SELINUX enforcement tag on the boot image to prevent the 'red text' folks were seeing on boot after flashing;
Now logs to logcat (Android system log) when it takes actions (every five minutes or so it verifies that the telephony database and system properties still are set for tether support.

This worked perfectly on the SPRrom , thank you. ?

i have galaxy s6 g920p (BOJ7)
in setting menu i cant see Mobile Hotspot!!
i flash this file and nothing happend.
please help me i need hotspot

mahdi72 said:
i have galaxy s6 g920p (BOJ7)
in setting menu i cant see Mobile Hotspot!!
i flash this file and nothing happend.
please help me i need hotspot
Click to expand...
Click to collapse
A little more info please. ROM? Recovery.log from TWRP? Hard to help flying blind.
Also, see where your telephony.db file exists.
Sent from my SM-G920P using Tapatalk

tdhite said:
A little more info please. ROM? Recovery.log from TWRP? Hard to help flying blind.
Also, see where your telephony.db file exists.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Stock Rom
Rooted
Software version : G920PVPU3BOJ7
Hardware version :G920P.02
Android : 5.1.1
Base Band : G920PVPU3BOJ7
Build Number :LMY47X. G920PVPU3BOJ7
Telephony.db = /data/data/com.android.providers.telephony/databases/telephony.db
/data/user/0/com.android.providers.telephony/databases/telephony.db
tnx

Updated -- Custom and Stock ROM Support
New flash supports ROMs missing init.d support. See the OP.

tdhite said:
New flash supports ROMs missing init.d support. See the OP.
Click to expand...
Click to collapse
Sprint S6 G920P, 6.0.1 stock root.
after flashing, nothing changes. i dont see the option to turn on/off hotspot.

yaibakt said:
Sprint S6 G920P, 6.0.1 stock root.
after flashing, nothing changes. i dont see the option to turn on/off hotspot.
Click to expand...
Click to collapse
Click on the Hotspot menu Item. It doesn't look like a menu item, but it opens the hotspot setup.
Sent from my SM-G920P using Tapatalk

could you please give me a screenshot of it?

yaibakt said:
could you please give me a screenshot of it?
Click to expand...
Click to collapse
{
"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"
}
Click that Hotspot item.
Sent from my SM-G920P using Tapatalk

silly me.
I dont have that hotspot and tethering setting either

yaibakt said:
silly me.
I dont have that hotspot and tethering setting either
Click to expand...
Click to collapse
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk

tdhite said:
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yes, my s6 is rooted, so that i could flash your zip via twrp...
I dont have that log file
Sent from my SM-G920P using Tapatalk

Do you have OEM Unlocking turned on in Developer's settings? What you show suggests the flash was not able to persistently rewrite the boot image.
Tell me that answer above and whether the file exists at /init.d.rc and if not, that tells me the flas is not in fact suceeding at persistently updating the boot image.
Sent from my SM-G920P using Tapatalk

tdhite said:
Please attach the file at /data/local/tmp/tdh-hotspot.log so I can see what is happening in the update.
Also, are you rooted?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Hi tdhite, my phone was rooted. And this is my tdh-hotspot.log. I also flashed your file but still don't get hotspot and tether Can u check for me ty
I also got the file init.d.rc in root and my OEM unlocking opened too

andyz0301 said:
Hi tdhite, my phone was rooted. And this is my tdh-hotspot.log. I also flashed your file but still don't get hotspot and tether Can u check for me ty
I also got the file init.d.rc in root and my OEM unlocking opened too
Click to expand...
Click to collapse
Ok, hang on folks, looks like I found (I think) the issue some are seeing. Long story -- a selinux permissions issue. Working on it.

@tdhite My offer is still on the table

Updated -- 03/18/2016
Does a couple *more* things now:
keeps tether_dun_required at 0 (there is a background process that sets it to 1)
sets up build.prop for usb tethering
See the original post, use the flash for ROMs lacking init.d support.
Let me know if if that helps with folks not getting the tether option at all, and for those working, you should not see provisioning requirements. IF you do, wait a minute or so and try again. There is a service that checks randomly between every 15 to 45 seconds for changes to the tether_dun_required global setting.

[Alpha][miatoll] Droidian (Debian Bookworm) for Xiaomi Redmi Note 9 Pro - 9 Pro Max - 9S - Poco M2 Pro

{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.
This is accomplished by using well-known technologies such as libhybris and Halium.​Carefully read the whole post before jumping to installation.​They are important to give you the best idea of the current state of the OS.​
What is working:​- Alarm Clock (bullseye/stable only. Doesn't work on bookworm/nightly)
- Manual brightness
- Vibration
- Carrier info, signal strength
- Data connection (read bugs section)
- Incoming, outgoing calls
- SMS in, out
- Change audio routing
- Voice in calls
- Volume control in calls
- Bluetooth
- WiFi
- Proximity
- Rotation
- Touchscreen
- Earphones
- Headphones
- Loudspeaker
- Microphone
- Volume control
- Pin unlock
- Waydroid
- Wireguard
What doesn't work:​- Most of the things not mentioned above.
Bugs:​- RIL gets broken after switching airplane mode or modem off/on. Fixed after a reboot.
- Mobile data stops working after making or receiving calls. Toggle mobile data on and off from the settings app.
- Mobile data doesn't work in the first 2-3 minutes after reboots. Toggle mobile data on and off from the settings app after waiting a while to get it working.
- Droidian has no power management yet so you're left with only the 5020mAh battery which can last up to 6 hours without heavy usage.
Installation:​
Make a backup now, as your device will be wiped.
Click to expand...
Click to collapse
Download the needed files and tools
Droidian rootfs (specific build required)
Android 10 (Q) stock firmware
Latest TWRP recovery
Adaptation (unofficial)
Device preparation
A USB 2.0 port/hub with an actual USB 2.0 controller is recommended (Using fastboot on a USB 3.0 port may cause errors with some Xiaomi devices)
Save your APN (Android)
The Access Point Name or APN can be found in the Settings menu of Android
Take a piece of paper or a text editor, and write down everything that you see on that screen
These are likely to include a URL (e. g., internet.carrier.net), a username, and possibly a password
Unlock the bootloader (Computer)
Refer to the instructions provided by the device manufacturer
Other useful sources include the LineageOS wiki and xda-developers
Boot into recovery (Computer)
Boot TWRP by running fastboot boot twrp-VERSION-miatoll.img
Wipe the device (TWRP)
Go to the Wipe menu
Select Advanced wipe
Tick the boxes called Dalvik / ART cache, Cache, System, Vendor, Data
Swipe to Wipe
Go back to the previous menu
Choose Format data and type yes
Go back to the main menu and select Reboot
Choose Bootloader
Boot TWRP again by running fastboot boot twrp-VERSION-miatoll.img
Copy the files to the device (Computer)
When TWRP is booted, open the device’s Internal storage from your computer
Copy all of the files you downloaded to this folder
Droidian installation (TWRP)
Install recovery
Install the file called twrp-VERSION-miatoll.img as an Image to the Recovery partition
Install Droidian rootfs
Install the file called droidian-rootfs-arm64_YYYYMMDD.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload droidian-rootfs-arm64_YYYYMMDD.zip
Installation is optional for stable releases, but it is recommended, because it helps with debugging
Finalizing the installation
Install adaptation package as a flashable zip (TWRP)
Install the file called adaptation-droidian-miatoll.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload adaptation-droidian-miatoll.zip
Boot your device
Go to the Reboot menu and choose System
TWRP might complain that there is no OS installed, but that’s fine
The first boot may take longer, and at least one spontaneous reboot is expected during the process
You should be greeted with the lock screen, the default password is 1234
Congratulations, if everything went well, now you should be running Droidian.
Notes:
Recovery
Use the recovery linked at the start of this page. The installation might fail with other recoveries that the one mentioned above.
Default password
The default password is 1234.
Apn
Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls
Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Broken calls
Switching airplane mode on and off or switching the mobile modem off and on from the Quick Settings or the Settings App will break calls. If that’s the case reboot the phone to fix it.
Out of storage
By default when flashing Droidian it allocates 8GB of memory to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
Status
Droidian GSIs are experimental! Bugs and missing features are expected.
SSH access
Connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications
You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
Credit:​Marcel Alexandru Nitan
Droidian Mobian UBports
You can ask for assistance specific to this device at Droidian for miatoll devices.
Sources:​- kernel
- adaptation package
Donate:​- PayPal
- Revolut

Announcement/Update ~ Droidian
Support for Droidian Bullseye has been discontinued. Droidian Bookworm has become more stable while the old Bullseye version hasn't received any updates from the devs since December 2021.
Users that are still on Bullseye are recommended to backup their data and install the Bookworm version for Droidian by following the new instructions located at https://devices.droidian.org/devices/miatoll/
For already Bookworm users:
Until now we've used the same ramdisk Ubuntu Touch uses because Droidian had no dynamic partition support. That has been changed on the previous days and a new adaptation package has been created to update the old ramdisk we used.
I've disabled the old miatoll ppa repository so the kernel won't get updated since it will "wipe" all the data and modifications.
To continue to receive kernel updates add the new miatoll ppa repository:
Your data and system changes will be cleared but will remain in /userdata/rootfs-overlay which will no longer be used after updating to the latest kernel as all the changes are now written into the Droidian rootfs.
Bash:
sudo curl -# --proto '=https' --tlsv1.2 -Sf https://miatoll-linux.github.io/repo/miatoll.gpg --output /usr/share/keyrings/miatoll.gpg && \
echo "deb [signed-by=/usr/share/keyrings/miatoll.gpg] https://miatoll-linux.github.io/repo/ bookworm main" > ~/miatoll.list && \
sudo mv ~/miatoll.list /etc/apt/sources.list.d/miatoll.list && \
sudo apt update
sudo apt upgrade

Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.

Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!

ProtoDeVNan0 said:
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
Click to expand...
Click to collapse
Not to go off topic but that's one of the reasons I stopped making Roms on XDA and instead keep them for myself lol.
Anyways OP, Amazing to see people working on Debian based Roms for our device. Will definitely be checking this out sometime this week!

[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Unfortunately I can't. The recoveries we have available for our phones are not able to mount the raw img file (rootfs.img) so sideloading the devtools and the adaptation package is not possible so we have to manually fix the mount via losetup and make the extraction of the packages above ourselves.
Probably everything will be fixed when we're going to get a fully working and stable recovery.

hi! what is it the current situation of battery drain, i really want to give a try

[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Installation steps reduced

[email protected] said:
hi! what is it the current situation of battery drain, i really want to give a try
Click to expand...
Click to collapse
Well it improved since the last time. Don't expect days of battery life but it's enough to get you through the day
*Waydroid can decrease the battery like a lot btw.

Hi, I really love your work @nitanmarcel
Thanks

How is this for daily use?
Mobile data problems fixed?