Database Users

KK 4.4 !! [Solved] Wifi Regional problem with sim card inserted

For 4.4 goto 2'nd post
This is for JB 4.3.1
If you like me have the problem of : ( wifi + sim_card ) = wifi not working
here is the fix : credits to HTCZ715E
http://forum.xda-developers.com/showthread.php?t=2368501
but just 1 more step , after making the new "telephony-common.jar" and adb push , and chmod 644
you HAVE TO wipe dalvik+cache
without wipe dalvik+cache it never worked for me.
HTC MyTouch 4G
[ROM] CM-10.2 | AOSP 4.3 Jellybean [KANG] [Oct-11]
cm-10.2-20131011-Albinoman887-glacier

Well heads up to the android 4.4
non of the previous solutions is not working :crying:
today i tried ROM Legacy Carbon 4.4
so i started to use my knowledge about cracking from the old MS-dos ages !!!!!!!!! and i cracked the bcmdhd.ko file
using IDA dissembler and HexEdit the bcmdhd.ko file.
Now wifi works again. :good:
The problem is that , in this method i cannot provide a universal file and you have to make your own cracked driver ".ko" file.
Or the developers of each Rom should use the working source code for the wifi driver which has the complete support for all languages.
refer to this post:
http://forum.xda-developers.com/showthread.php?t=1077329
and also here are some lines from logcat (i changed my mcc , mnc and country to XX ) with the cracked driver.
(i prefer to use cracking instead of patching because it was previously we called it)
Code:
D/Tethering( 1874): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
E/wpa_supplicant( 2047): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 1874): Failed to set country code XX
D/MccTable( 2051): updateMccMncConfiguration: mcc=XXX, mnc=XX
D/MccTable( 2051): getLocaleFromMcc to null_ir mcc=XXX
D/MccTable( 2051): getLocaleForLanguageCountry: skipping no language
D/MccTable( 2051): WIFI_COUNTRY_CODE set to ir
I/WifiService( 1874): WifiService trying to set country code to XX with persist set to true
D/MccTable( 2051): updateMccMncConfiguration updateConfig config={1.0 XXXmccXXmnc ?locale ?layoutDir ?swdp ?wdp ?hdp ?density ?lsize ?long ?orien ?uimode ?night ?touch ?keyb/?/? ?nav/? themeResource=null}
I/ActivityManager( 1874): Config changes=3 {1.0 XXXmccXXmnc en_US ldltr sw384dp w384dp h615dp 200dpi nrml long port finger -keyb/v/h tball/v s.6 themeResource=null}
The whole problem started from the "wldev_set_country" function in "C" code in a ".h" file of wifi driver.
i don't have the knowledge to manipulate the source code of the wifi driver and compile compile the ".ko" file.

This method is not for pplz who don't know about reverse engineering.
So i opened the "bcmdhd.ko" in IDA disassembler and select the ARM Architecture.
Then searched for the "wldev_set_country" function and in the disassembled code there is some Branches which should be re-routed.
for example: (these are the OP-Codes of ARM cpu)
BNE loc_206E4 in the hex view window "08-00-00-0A"
BNE = Branch if not Equal , (and must have to change to just Branch no matter what is the result of compare )
0A = BNE
EA = B (Branch)
AA = BGE (Branch if Greater or Equal)
..... and etc
The important thing is that in IDA hex-view for examaple it shows : 000206BC 08 00 00 1A
but at the bottom of window it shows: 000206F0 <= this is the address which u needs to find and change in your hex-ediotor
and in hex editor we will change that 1A to 0A
The whole process i re-route 4 branches to get success.
Also i've checked it , and there is no need to appliy the previous patch "telephony-common.jar"
Only the bcmdhd.ko driver needs to patch

I attached the cracked version of my bcmdhd.ko file.
you can try it , BUT IT MAY NOT FOR YOUR COUNTRY AND/OR YOUR SIM CARD and for sure it only works in some Roms
this is the driver version from dmesg
Dongle Host Driver, version 5.90.195.114
Compiled in drivers/net/wireless/bcmdhd on Nov 18 2013 at 17:0
Click to expand...
Click to collapse
i made the attachment for this Rom
[ROM][UNOFFICIAL] LegacyCarbon 4.4 \\ 18.11.2013 \\ Built From Source
you should unzip it and use "adb push" and "chmod 644 "
Code:
adb root
adb push bcmdhd.ko /system/lib/modules/
adb shell
su
cd /system/lib/modules/
chmod 644 bcmdhd.ko
and reboot
----------------------------------------------
HTC MyTouch 4G
[ROM][UNOFFICIAL] LegacyCarbon 4.4 \\ 18.11.2013 \\

I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:

BobZombiE said:
I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:
Click to expand...
Click to collapse
Did you use it? Bug important? I want to know some information. Thanks!

Sure , i'm using this patched driver almost on all Roms i'm testing and never had any wifi problems.
Sent from my myTouch 4G using xda app-developers app

BobZombiE said:
I test this file on [ROM][Official][4.4] Evervolv Nightlies
It's compatible And works 100% :good:
Click to expand...
Click to collapse
Camera, cam recording, and Browser? What any problem?
If I want back Rom 4.3 after install 4.4. Can I back?!
Thank so much your infomation!

hdhthed said:
Camera, cam recording, and Browser? What any problem?
If I want back Rom 4.3 after install 4.4. Can I back?!
Thank so much your infomation!
Click to expand...
Click to collapse
go to the related thread and take a look , or make a nandroid backup and try.
anyway:
Evervolv 4.0: at this moment: Camera does not work at all . but stock browser is ok :good:
Carbon 4.4 Rom : at this moment : Camera & Cam recording is ok. but stock browser does not work. u have to use other browsers like firefox

Yea! Make a nandroid backup ,after I can restore in Recovery. Have lost root?

hdhthed said:
Yea! Make a nandroid backup ,after I can restore in Recovery. Have lost root?
Click to expand...
Click to collapse
i don't think so

BobZombiE said:
i don't think so
Click to expand...
Click to collapse
Mean? You think lose root or cant restore a backup nandroid ?

hdhthed said:
Mean? You think lose root or cant restore a backup nandroid ?
Click to expand...
Click to collapse
i'm root and s=off , HBOOT 75
and flashed, backed up, restored my phone more than 100 times last week . and never lost root

This is my old phone... Fun to be back here.
I am asking about this modified driver. I need to find out first if my phone uses this driver (looks like a broadcom driver), but if it is, I am going to try it.
My question to the author is: do the changes you made make this driver location agnostic? Because you changed the BNE, to just branch, it seems that you are allowing it to function regardless of the country (in the MMC).
I have an HTC One running 4.4 and my issue is that I really need to use channel 13. My router is set to 13, but no matter what changes I make to the wi-fi region encoding (the region encoding change is successful), I still am limited to only channels 1 to 11.
So I just thought I'd ask to get your input on this...
Thanks,
Paul

help me solve my wifi issue
BobZombiE said:
For 4.4 goto 2'nd post
This is for JB 4.3.1
If you like me have the problem of : ( wifi + sim_card ) = wifi not working
here is the fix : credits to HTCZ715E
http://forum.xda-developers.com/showthread.php?t=2368501
but just 1 more step , after making the new "telephony-common.jar" and adb push , and chmod 644
you HAVE TO wipe dalvik+cache
without wipe dalvik+cache it never worked for me.
HTC MyTouch 4G
[ROM] CM-10.2 | AOSP 4.3 Jellybean [KANG] [Oct-11]
cm-10.2-20131011-Albinoman887-glacier
Click to expand...
Click to collapse
Hey guys ... I'am a normal user having sony xperia ion Lt28h .... I've just flashed CM11 unofficial rom but I have a wifi problem ..... can you teach me how to solve my regional wifi issue as I am in syria and have faced this problem earlier so i know it's a regional problem ..... thx for help

[Q&A] [ROM][29Jan][GNU/Linux] Sailfish OS (community port)

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
[ROM][29Jan][GNU/Linux] Sailfish OS (community port)
Click link here>> To jump to Development thread <<Click link here[/COLOR]
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
-----------------------------------------------------------------------------------------------
Hi guys,
i've started a general Q&A thread for n4 and others. Everything related to sailfish and of course n4 can be posted here.
1. Which HW components are working?
A: take a look at the spreadsheet libhybris: https://wiki.merproject.org/wiki/Adaptations/libhybris
2. Can I run my android apps?
A: atm = no. due to licensing issues the dalvik runtime is not included in android ports. Join community efforts in this XDA thread. The jolla phone run android apps.
3. What about playing videos and music
A: new ports with gstreamer1.0 (Nexus 5) play MP3, MP4, H264 out-of-box.
Install gstreamer1.0-libav for more codecs.
For old gst0.10 ports:
MP3: install gst-fluendo-mp3-0.10.23-1.armv7hl.rpm via rpm -i fluendo
Video: Install gst streamer plugins and ultimate codec support. detailed instructions: http://forum.xda-developers.com/showpost.php?p=53552092&postcount=424
4. I'm able to install apps?
A: On Nexus 4 and Nexus 5 yes. But expect glitches because Jolla Store is going under maintenance until Tablet comes out. Known issues:
* "Essential Apps from Jolla" is not visible. Find them one by one via Seach
* Newly added apps might not show up for SFE devices
Alternatively, try Warehouse (openrepos.net):
* Navigate via your phone's browser to https://openrepos.net/content/basil/warehouse-sailfishos
* Download latest RPM
* Either run devel-su pkcon refresh in terminal, or download at least one app from Jolla Store
* Ensure Settings->System->Untrusted software is allowed
* Go to Settings->System->Transfers, click on downloaded file, and it will be installed
5. whatsapp?
A: Beware of WhatsApp temporary banning 3rd party app users. You can try WhatsUp: http://forum.xda-developers.com/showpost.php?p=60264278&postcount=137
Next Mitäkuuluu version is rumoured to be unbannable, lets all wayt
6. How to access the device?
A: Via ssh or sftp. Take a look on @Daycrawler thread: http://forum.xda-developers.com/jolla-sailfish/general/sailfish-android-devices-release-t2696409. He released the ea mail where everything is described.
7. How to install sailfish on my device (other than n4)?
A: You will be able to install when an image is available. Check "Downloadable Image" column in https://wiki.merproject.org/wiki/Adaptations/libhybris .
Porting Sailfish OS by yourself is possible via following the HADK: https://sailfishos.org/hadk
For Nokia N9: http://wiki.maemo.org/Sailfish#Sailfish_Images
9. What about multirom?
A: MultiROM is supported on Nexus 4, Nexus 5, and OnePlus One (possible Nexus 7 too): Follow up: http://forum.xda-developers.com/jolla-sailfish/general/09-06-sailfishos-multirom-how-to-set-t2869096
10. Why I have to flash so much to get sailfish on my device?
mmmmmhhhh. Answer question by yourself and try
E.g. for Nexus 4 please do all steps you'll find in: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823 . It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't.
11. How to take a screenshot?
A: Install screenshot app by lbt, from Jolla Store.
A1: This can be done on the phone via terminal and also on a remote SSH PC client.
su-devel grabscreen /home/nemo/Pictures/Test.png
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
The picture can be accessed in the Gallery or via Filetug.
12. How to get files from/to device, because USB Mass Storage mode and SD card are not available ?
A1: ssh + scp combo (windows[putty] & linux)
This combo is a set of linux standard tools. You can connect to the phone via secure socket shell from your pc and transfer files to your phone and vice versa.
A2: sftp + filezilla (windows & linux)
You can access the files via filezilla. You can transfer files like you're doing with an ftp server.
A3: Gnome Desktop Environment
The gnome filemanager nautilus has an build in option for accessing sftp / ssh servers or devices easily.
A4: WinSCP (windows)
To connect via these methods, enable developer mode, set a new password and take a look what ip you've get. Behind the wlan symbol. Then choose one of the above methods:
username = nemo
password = the one you entered in developer mode section
[ssh]= ssh [email protected]_ip
[filezilla] = sftp://device_ip
[nautilus] = select: Connect to server (on the left side) and enter: ssh://device_ip
13. How can I use the Backup app when there's no (working) SD Card?
A: Launch Settings->System->Backup to save all the settings you want to preserve
Perform
Code:
tar cf $HOME/backup.tar -C $HOME .vault
scp backup.tar onto your PC (other ways of how pull files, see FAQ #12 above)
Install new Sailfish OS.zip, put the tarball back onto device (say at $HOME), then perform:
HTML:
cd $HOME && tar xpf backup.tar
Go to Settings->System->Backup and restore your content from a chosen backup
14. How can I provide another radio.img only for Sailfish OS?
Put radio.img onto Sailfish OS rootfs somewhere safe.
Edit /lib/systemd/system/firmware.mount and replace "What=/dev/mmcblk0p1" with "What=/path/to/firmware.img"
Be careful with that and always do backup (i.e. comment the first What out )
15. How can I skip tutorial?
On first screen, tap on corners in sequence: top-left, top-right, bottom-right, bottom-left
16. How can I mount android's virual sdcard partition (Nexus4,5) with all my goodies?
Try:
Code:
devel-su
mkdir /android
mount /dev/mmcblk0p28 /android
# User data is then available in /android/media/0/
# You can update your fstab file by adding the following line at the end:
/dev/mmcblk0p28 /android ext4 rw,relatime,data 0 0
# And for media to be tracked:
ln -s /android/media/0 /home/nemo/android_sdcard
17. Filemanager?
Install File Browser by Kari from Jolla Store.
For root access add on https://openrepos.net/content/schturman/startasroot-file-browser (See question #4 on how to access openrepos via Warehouse app)
This thread should be a collection for sailfish on devices and I will update frequently if news or tipps & tricks are available.
-----------------------------------------------------------------------------------------------
{
"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"
}
Please keep discussion focused, on the topic described in the OP

Arabic Keyboard
Is there a way to enable Arabic keyboard layout in SailfishOS?

Upgrade Sailfish
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al jolla-camera jolla-camera-settings sensorfw-qt5 qt5-qtsensors-plugin-sensorfw
[Fix problem with adaptation0 after upgrade]
[[email protected] ~]$ devel-su zypper al ssu ssu-network-proxy-plugin ssu-vendor-data-jolla
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Your Nexus 4 should now run Sailfish 1.1.2.16!]

Niyoru said:
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al qt5-qtmultimedia-plugin-mediaservice-gstcamerabin jolla-camera jolla-camera-settings nemo-qtmultimedia-plugins-gstvideotexturebackend sensorfw-qt5
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Disable repository adaptation0]
[[email protected] ~]$ devel-su ssu dr adaptation0
[Refreshing package list]
[[email protected] ~]$ devel-su zypper refresh
[Your Nexus 4 should now run Sailfish 1.1.2.16!]
Click to expand...
Click to collapse
Thank you for your instruction.. I just have one problem...
I get the below error message when trying to refresh the repositories. Even after doing "zypper clean -a".
"Retrieving repository 'adaptation0' metadata ---------------------------------------------------------------------------------[-]
Timeout exceeded when accessing 'http ://repo.merproject.org/ obs/sailfishos: /testing: /hw:/mako/sailfish_latest_armv7hl/repodata /repomd.xml'."
I'm running sailfish OS with Multirom.
I hope you can help me.
Kind regards,
Edit: I know what the problem is. I have to authenticate but I don't have any credentials. Is there a way how I can register for that repository? Many thanks

That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.

Niyoru said:
That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.
Click to expand...
Click to collapse
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works

btrdossantos said:
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works
Click to expand...
Click to collapse
This will not look like Sailfish 2.0, becouse this is not Sailfish 2.0. This is Sailfish 1.1.2.16, you can read more about that release on Sailfish Website. (Sorry for no links, but I can't put any into post, becouse I have less than 10 posts :c)

sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)

dimon2242 said:
sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)
Click to expand...
Click to collapse
If you upgraded Sailfish to 1.1.2.16, you can use command "devel-su zypper install sailfish-weather".
This work for me

Niyoru said:
If you upgraded your Sailfish to 1.1.2.16, you can use just "devel-su zypper install sailfish-weather".
This work for me
Click to expand...
Click to collapse
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(

dimon2242 said:
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(
Click to expand...
Click to collapse
In my phone this one work well: d-h.st/nkS8

Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi

carepack said:
Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi
Click to expand...
Click to collapse
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4

Browser is closed if i play online music or youtube video!
Hope, what this will be fixed in next update!)

Niyoru said:
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4
Click to expand...
Click to collapse
We're doin' our best :fingers-crossed:! Hope you enjoy the beloved sailfishos and thank you for sharing the information about quarters or not!
ahoi

Bug - Untrusted software installation
I am now running on v1.1.2.16 based on the tutorial provided in the thread (thanks Niyoru) and would like to report a bug.
I went into Setting -> System -> Untrusted software
and enabled "Allow untrusted software" option in there. However, I can't install any .rpm files. When I go back into settings, the setting is disabled. Not sure if this is caused by the upgrade or is also a problem in v1.1.1.27 as well in the Nexus 4 port.
The workaround was to go into terminal, do a devel-su and typing in:
zypper in package.rpm
Hope this helps...
PS. Looking forward to this build having the "Sailfish OS Updates" working instead of a manual upgrade process. Happy sailing! :fingers-crossed:

Installing sailfish via multirom with over kitkat primary rom
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?

Updated to v1.1.4.28 and all seems fine thus far...
Looks like latest update is screen resolution aware.
Sent from my Note 2 using Tapatalk...

mikerog said:
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?
Click to expand...
Click to collapse
You got to use cm10.1.3 as primary ROM, too.
ajack2001my said:
Updated to v1.1.4.28 and all seems and fine thus far...
Looks like latest update is screen resolution aware.
Click to expand...
Click to collapse
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards

keenofhiphop said:
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards
Click to expand...
Click to collapse
Yes, I update OTA using a combination of ssu and zypper commands... I guess it also helps that my account allows me to use early release software.

[TOOL] [WINDOWS] URET Android Reverser Toolkit v1.2 [UPDATED]

URET Android Reverser Toolkit v1.2 [UPDATED]
{
"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"
}
Overview :-
URET Android Reverser Toolkit Has Been Built With The Idea Of Providing The Easy Work With Android Reversing To End User, It Is Fast, Stable, Smooth And NOOB FRIENDLY..!!
This is a GUI program Which Helps You To Do Tasks With Just Clicking Options,No Need To Write Codes Or Commands, It Handles Everything With Itself.It Is Intended To Make Your Work Easy,
Features :-
- Decompile/Compile APK Or JAR File.
- Sign The Apk.
- Ziplign The Apk.
- Dex2Jar.
- Jar2Dex.
- Oat2Dex.
- Odex2Dex.
- Uncompress Xz Odex Of Samsung Roms.
- ADB One Click Commands.
- Include JDGui In It.
- Beautiful Theme
- Noob Friendly
- Much Faster And Clean,No Need To Put Commands Does Everything Automatically And Fixes Parameters Automatically When Required.
How Does It Work :-
- Drag And Drop/Browse APK/JAR/DEX/ODEX/XZ File To Required Place.
- Select Parameters When Required.
- Options Are Self Explanatory Read HELP For Every Actions.
- Error Box Only Shows Error When Found,If There Are No Error Shown You Will Get Desired Output.
- Logs Box Shows Logs Of Right Panel.
- Open JDGui Option Open Java Decompiler Bundled With It.
- Clear Input File Option Clears The Present Input File Location From The Box.
HELP IS GIVEN FOR EVERY SINGLE ACTION
I Released Dex Manager Which Used To Work Only With Classes.dex Year Back :- http://forum.xda-developers.com/android/software/tool-dex-manager-v1-0-designed-to-play-t2988532
Then Released APK Signer Here :- http://forum.xda-developers.com/android/software/apk-signer-v1-0-simple-clean-t3223909
Now I decided To Keep Up With This Tool To Keep Updated When Required And Keep All In One !!
Download :-
v1.2
Direct
Mirror :-
Zippyshare
Changelog :-
v1.2 (Released On 26/Feb/2016)
// It Is Recommended To Extract Toolkit On Desktop For Your Work,So It Works Reliable,As Putting It In Logical Drives Like D,E Etc Will Cause Permission Denied Problems,Or Run As Admin. //
// In Case Of Java Error,Make Sure You Add JAVA_HOME Environment In Your PC. //
- Added ADB Commands Like Push,Pull,Install,Uninstall,Backup,Restore,Reboot Device,Reboot Bootloader,Reboot Recovery,Clear Logcat Buffer,Take Logcat,Run Shell Etc With One Click.
- Added Oat2Dex,Odex2Dex.
- Added Uncompress XZ Of Odex In Samsung Firmwares.
- Added Logs Box For The Output Of Right Side Panel.
- Detailed HELP Button For Every Single Task.
- Fixed Symbols "'!^&" In Apk And Jar Name Causing Problems Being Recognized.
- Fix Some Delete Actions.
- On Start It Shows If Java Is Installed Or Not In Logs Box.
- Refactor Bit Of Code.
v1.1 (Released On 23/Feb/2016)
- Fix Dragging/Loading Files From Root Directory Of Toolkit Leading To Errors,Now You Can Load File From Anywhere From PC.
- Fix The Issue With The File Having Spaces In Name Leading To Errors,Now You Can Load Any Files With Any Name Upto Windows Characters Limit.
- Fix Issues In Android JAR Processes Leading To "ACCESS Denied" When Direcotory Was Open.
- Removed Extra ApkTool.
- Cross Checked All The Validations And Fixed When Error Found.
- Fix Loading Speed,Only Takes Small Time On Very First Start To Extract Skin.
- Minor Other Bugs Fixed And Optimizations.
- Toolkit Is Fully Stable Now.
v1.0 (Released On 22/Feb/2016)
- Initial Release.
Requirements :-
-JRE
-Microsoft .Net Framework v4.0 And Above
License :-
Free
Credits :-
- Ben Gruver For Baksmali/Smali.
- Connor Tumbleson And Ryszard Wisniewski For Apktool.
- Emmanuel Dupuy For JDGui.
- Bob Pan For Dex2Jar.
- Softdx For Oat2Dex.
- Igor Pavlov For 7-Zip.
- Google For The Android Open Source Project
MESSAGE :-
Any Feedback,Requests Post Here!!
THANKS
VIDEO :-

Reserved !!

Updated to v1.1,changelog added in first post,stable release !

Video added how to use it
some nice features are on to do list when get time will update it

Updated to v1.2
Changelog :-
v1.2 (Released On 26/Feb/2016)
// It Is Recommended To Extract Toolkit On Desktop For Your Work,So It Works Reliable,As Putting It In Logical Drives Like D,E Etc Will Cause Permission Denied Problems,Or Run As Admin. //
// In Case Of Java Error,Make Sure You Add JAVA_HOME Environment In Your PC. //
- Added ADB Commands Like Push,Pull,Install,Uninstall,Backup,Restore,Reboot Device,Reboot Bootloader,Reboot Recovery,Clear Logcat Buffer,Take Logcat,Run Shell Etc With One Click.
- Added Oat2Dex,Odex2Dex.
- Added Uncompress XZ Of Odex In Samsung Firmwares.
- Added Logs Box For The Output Of Right Side Panel.
- Detailed HELP Button For Every Single Task.
- Fixed Symbols "'!^&" In Apk And Jar Name Causing Problems Being Recognized.
- Fix Some Delete Actions.
- On Start It Shows If Java Is Installed Or Not In Logs Box.
- Refactor Bit Of Code.

Interesting tool jasi going to give it a try ..

you wont regret brother

Jasi2169 said:
you wont regret brother
Click to expand...
Click to collapse
virus detected

Andoiiid said:
virus detected
Click to expand...
Click to collapse
It is packed/obfuscated with the obsidium packer before there were only 2 detections now it has shown many detections because of packer signatures the AV trigger it as virus.
I will try another packer next time,all packers i have are pirated and all pirated gets triggered easily by AV ,do not have enough to buy legitimate version of packer.
Anyway i have AVG free antivirus and hopefully it doesnot detecr it and i use this tool for my daily work.
Best Regards,
JASI

Tool is downloaded 9007 times from zippyshare alone but people aint giving feedbacks :/

Jasi2169 said:
Tool is downloaded 9007 times from zippyshare alone but people aint giving feedbacks :/
Click to expand...
Click to collapse
As long as anti viruses are going to flag it you won't have anyone really using it... :/

Newyork! said:
As long as anti viruses are going to flag it you won't have anyone really using it... :/
Click to expand...
Click to collapse
This was not flagged when i released it now ot is flagged by half of antiviruses because company forwarded it that the packer used to pack is pirated copy ,if you are a research analyst you would know how these antiviruses comapnies sometimes pressurize developers to pay to them so they can keep it clean
Anyway patches and cracks / packers always result in antiviruses triggers
Except you have legitimate copy of packers
I have all kind of packers/obfuscators in my HDD and most of them are triggered as virus because it is pirated copy/cracked packers without licenses
Anyway i use it for myself and hopefully AVG free antivirus i use didnot triggered it yet so i have no problem ,once it trigger then i will think about it

Hey Jasi2169,
I tried to use your tool.
But every Time i try to decompile an APK I get the following Error:
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:186)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:156)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:113)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:78)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:47)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibResources.java:622)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.java:73)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.java:65)
at brut.androlib.Androlib.getResTable(Androlib.java:63)
at brut.androlib.ApkDecoder.setTargetSdkVersion(ApkDecoder.java:209)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:92)
at brut.apktool.Main.cmdDecode(Main.java:165)
at brut.apktool.Main.main(Main.java:81)
Could you help me?
Thanks in Advance,
Eric

com.googlecode.d2j.DexException: not support version.
at com.googlecode.d2j.reader.DexFileReader.<init>(DexFileReader.java:148)
at com.googlecode.d2j.reader.DexFileReader.<init>(DexFileReader.java:208)
at com.googlecode.d2j.reader.MultiDexFileReader.open(MultiDexFileReader.java:36)
at com.googlecode.dex2jar.tools.Dex2jarCmd.doCommandLine(Dex2jarCmd.java:105)
at com.googlecode.dex2jar.tools.BaseCmd.doMain(BaseCmd.java:290)
at com.googlecode.dex2jar.tools.Dex2jarCmd.main(Dex2jarCmd.java:33)

Download links are dead.

Download link dosnt work and file Does not exist

https://drive.google.com/file/d/0BzpeJB3N_dYQMEhHN2pFSkJRNEU/view?usp=drive_web
UART v1.6 is available here

Hi Jasi,
Would you consider open-sourcing your tool at some point? It would be much harder to take down, plus people could contribute to it.

Download link was dead. drive google link so

BytesReverser said:
https://drive.google.com/file/d/0BzpeJB3N_dYQMEhHN2pFSkJRNEU/view?usp=drive_web
UART v1.6 is available here
Click to expand...
Click to collapse
Link is dead.

Need help building a SM-T555 (gt510lte) LineageOS ROM

Dear all,
I am trying to build a LineageOS 17.1 ROM for the Galaxy Tab A 9.7 (gt510lte) SM-T555.
Using the repos of @retiredtab and aala27's repos I managed to build a config that resulted in a buildable LineageOS that I could install and that shows the Lineage boot animation but crashes/reboots after a while.
Fyi, my forks for the GT510LTE (SM-T555) I currently maintain here: https://github.com/blizzard4591?tab=repositories
Questions to @retiredtab:
- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".
- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.
- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?
Sadly, I am a total noob in the area of building Lineage, so I might miss some obvious things!
I am willing to put in some time and effort to make this work, but I just do not know enough to do it efficiently.
If you can spare the time for a few hints, I believe I can make some progress!
Cheers
Update 1:
My image is working, i.e. it boots and gives a stable system.
Problem: Bluetooth does not work and crashes a lot, I have no clue what the problem is.
Problem: Audio is not working, I see a lot of "audio_route: unable to find path 'low-latency-playback speaker'
The system settings dialog is missing the "Android Patchlevel" information - is this expected? I am building using "repo sync, breakfast gt510lte, brunch gt510lte" - is this correct? I am just an idiot.
Update 2:
Bluetooth and Audio are working, SELinux is not, so permissive it is for now.
Builds available on request.

RandomAndroidTinkerer said:
- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".
Click to expand...
Click to collapse
It was there before, but I think after the switch to Xenforo on Dec 1, 2020, it might have gotten lost. It's there now and what I use to generate 17.1 for T550.
RandomAndroidTinkerer said:
- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.
Click to expand...
Click to collapse
No, I just used what's in at https://github.com/Galaxy-MSM8916. Having said that, I found that for the SM-T350, it was missing some very important files so I grabbed those from stock.
RandomAndroidTinkerer said:
- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?
Click to expand...
Click to collapse
gt5note10wifi is for the P550, not T550. You shouldn't be using that as the *.mk files won't copy the correct blobs for your device.
RandomAndroidTinkerer said:
Update 1:
My image is working, i.e. it boots and gives a stable system.
Problem: Bluetooth does not work and crashes a lot, I have no clue what the problem is.
The system settings dialog is missing the "Android Patchlevel" information - is this expected? I am building using "repo sync, breakfast gt510lte, brunch gt510lte" - is this correct?
Click to expand...
Click to collapse
Congrats on getting a bootable stable system. For bluetooth, you are probably missing a bluetooth blob. Look in your adb logcat (see below) for red messages that are bluetooth related. It might say something like "missing libbt-nv.so".
Missing Android Patchlevel means you don't have a property declared in your *.mk file. Right now, I can' t remember what it is, but I will look for it.
Instead of brunch, I do
Code:
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon
This makes an engineering build that starts adb logcat immediately. That way, you can see all the messages as soon as the device boots. It helps a lot in troubleshooting stuck at boot animation problems.
The -j2 indicates how many CPU cores I have. If you have more, say 4, then -j4.
Once you solved all your problems and if you want to share your ROM, then do a brunch which is userdebug by default (for me, I just do a make -j2 bacon).
For adb logcat, I find
Code:
adb logcat -C | nl
helpful. It color codes the log so anything in red (error) needs attention. Nl numbers the log so it's easier to remember where you error messages are vs a timestamp.

For the Android patch level, show me a screenshot so I exactly what you mean.

RandomAndroidTinkerer said:
Problem: Audio is not working, I see a lot of "audio_route: unable to find path 'low-latency-playback speaker'
Click to expand...
Click to collapse
Try not to edit your initial post because I didnt' see the audio problem. Just make a new one so that I see new responses.
The audio problem is likely you don't have the correct definition in mixer_paths.xml. aala27 had the exact same problem. It's likely this
[UNOFFICIAL][ROM] LineageOS 17.1 for Galaxy Tab A 9.7[SM-P550]
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM. I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a...
forum.xda-developers.com
For SM-T550, the line inside mixer_paths.xml looks like
Code:
<path name="low-latency-playback speaker">
<ctl name="QUAT_MI2S_RX Audio Mixer MultiMedia5" value="1" />
</path>
You can see above, I have a path name that matches 'low-latency-playback speaker' exactly. Your mixer_paths.xml probably doesn't have this defined so you get no audio.

BTW, all the info I'm giving wasn't available via search engine when I first started. It's extremely frustrating to troubleshoot when I first started. Even now, I have problems with audio over bluetooth and stuttering audio over bluetooth for two platforms that both worked perfectly on the previous last major revision on Android.

Thank you so much; I know how hard this kind of initial research is!
Regarding the audio issues:
I tried that already, as you can see in https://github.com/blizzard4591/android_device_samsung_gt510lte/tree/lineage-17.1/configs/audio I used the config files from my stock image (I had assumed they would work, but they do not - why?) and then added said speaker there, but no luck, it still has the same error message. What am I misunderstanding?
Regarding Bluetooth:
Thanks to you tip, I added the libbt-nv.so module, but this did not change the situation.
I am now building a debug/eng build, but in the log I still see no messages of missing drivers/firmware/SOs. You can find my Logcat attached - could you take a look and tell me whether I am missing something? Should there be messages?
How did you find out that you were missing BLOBs?

RandomAndroidTinkerer said:
I tried that already, as you can see in https://github.com/blizzard4591/android_device_samsung_gt510lte/tree/lineage-17.1/configs/audio I used the config files from my stock image (I had assumed they would work, but they do not - why?) and then added said speaker there, but no luck, it still has the same error message. What am I misunderstanding?
Click to expand...
Click to collapse
You need to check the actual rom image to see if the mixer_paths.xml is correct. Do
Code:
adb pull /system/vendor/etc/mixer_paths.xml
and compare if the two are the same.
RandomAndroidTinkerer said:
Regarding Bluetooth:
Thanks to you tip, I added the libbt-nv.so module, but this did not change the situation.
Click to expand...
Click to collapse
I only guessed at what might be missing. The logs will tell who what's missing.
RandomAndroidTinkerer said:
You can find my Logcat attached - could you take a look and tell me whether I am missing something?
Click to expand...
Click to collapse
I see no log attached. Zip the log and then attach it.

You need to check the actual rom image to see if the mixer_paths.xml is correct. Do
Code:
adb pull /system/vendor/etc/mixer_paths.xml
and compare if the two are the same.
Click to expand...
Click to collapse
Yes, the file was incorrect, I guess the path
Code:
$(LOCAL_PATH)/configs/audio/mixer_paths.xml:$(TARGET_COPY_OUT_VENDOR)/etc/mixer_paths.xml
did not resolve to where it should, I changed that, once the build is done I will check.
I see no log attached. Zip the log and then attach it.
Click to expand...
Click to collapse
Interesting, I can see it, but I attached it as ZIP!

The log you attached is missing all the bootup sequence. You need to start adb logcat as soon as the device boots.
Audio
=====
Your mixer_paths.xml should be in /vendor/etc. /system/vendor is usually a link to /vendor. From my P550.
Code:
$ adb shell
gt5note10wifi:/ # ls -al vendor
lrw-r--r-- 1 root root 14 2008-12-31 17:00 vendor -> /system/vendor
If you are using the 17.1 msm8916-common repo, see lines 80 to 83
android_device_samsung_msm8916-common/msm8916.mk at lineage-17.1 · Galaxy-MSM8916/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to Galaxy-MSM8916/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
may be overwriting your stock mixer_paths. I would comment out lines 80 to 83 as a test.
Bluetooth
=========
You have tons of errors with your bluetooth. If you view your logcat in color, these are all in red.
Code:
04-01 13:19:22.910 1212 1212 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-01 13:19:22.911 1212 1212 F DEBUG : LineageOS Version: '17.1-20210401-UNOFFICIAL-gt510lte'
04-01 13:19:22.911 1212 1212 F DEBUG : Build fingerprint: 'samsung/gt510ltexx/gt510lte:7.1.1/NMF26X/T555XXU1CQI8:user/release-keys'
04-01 13:19:22.911 1212 1212 F DEBUG : Revision: '8'
04-01 13:19:22.911 1212 1212 F DEBUG : ABI: 'arm'
04-01 13:19:22.912 1212 1212 F DEBUG : Timestamp: 2021-04-01 13:19:22+0200
04-01 13:19:22.912 1212 1212 F DEBUG : pid: 866, tid: 1203, name: bt_hci_thread >>> com.android.bluetooth <<<
04-01 13:19:22.912 1212 1212 F DEBUG : uid: 1002
04-01 13:19:22.912 1212 1212 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
04-01 13:19:22.912 1212 1212 F DEBUG : Abort message: '[0401/131922.772914:FATAL:hci_layer_android.cc(119)] Check failed: btHci != nullptr.
When it crashes hard like above, there's no way bluetooth will work.
Again, if you are using the 17.1 msm8916-common repo, it's missing the bluetooth entries for manifest.xml and msm8916.mk.
For the manifest.xml you need something like
Code:
<hal format="hidl">
<name>android.hardware.bluetooth</name>
<transport arch="32+64">passthrough</transport>
<version>1.0</version>
<interface>
<name>IBluetoothHci</name>
<instance>default</instance>
</interface>
</hal>
For msm8916.mk, you need
Code:
# Bluetooth
PRODUCT_PACKAGES += \
[email protected]

[Sorry for the delay]
Okay, I think I ironed out most of the issues.
What is confirmed working:
- WLAN
- Bluetooth
- Audio
- GPS (though the initial fix took 30min+...)
What does not work
- SELinux
WLAN:
I see a messages like
wificond: No Offload Service available
wificond: Offload HAL not supported
wificond: Failed to get NL80211_ATTR_EXT_FEATURES
Click to expand...
Click to collapse
Is that an issue? I don't know...
I see a lot of messages from the PowerHAL:
QTI PowerHAL: Failed to acquire lock.
Click to expand...
Click to collapse
I already tried https://review.statixos.com/c/android_device_essential_mata/+/1626/1 but that apparently was not enough.
SELInux:
I added the policies by https://github.com/VirsysElectron/android_device_samsung_gt510wifi and made them work, but it seems they are not really working.
Example:
I/init ( 233): type=1400 audit(0.0:4): avc: denied { mounton } for path="/firmware-modem" dev="mmcblk0p25" ino=27 scontext=u:r:init:s0 tcontext=ubject_r:tmp_root_mount_file:s0 tclass=dir permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:5): avc: denied { read } for name="mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:6): avc: denied { open } for path="/dev/block/mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:7): avc: denied { write } for name="mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:8): avc: denied { ioctl } for path="/dev/block/mmcblk0p13" dev="tmpfs" ino=7580 ioctlcmd=127c scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/init ( 1): type=1400 audit(0.0:9): avc: denied { relabelfrom } for name="rmt_storage" dev="debugfs" ino=6571 scontext=u:r:init:s0 tcontext=ubject_r:debugfs_rmt:s0 tclass=dir permissive=1
I/init ( 1): type=1400 audit(0.0:10): avc: denied { relabelfrom } for name="rmts" dev="debugfs" ino=6574 scontext=u:r:init:s0 tcontext=ubject_r:debugfs_rmt:s0 tclass=file permissive=1
Click to expand...
Click to collapse
I declare
/firmware-modem(/.*)? ubject_r:tmp_root_mount_file:s0
Click to expand...
Click to collapse
in device/samsung/gt510lte/sepolicy/file_contexts, but it is not applied:
dr-xr-x--- 3 system drmrpc ubject_r:vfat:s0 16384 1970-01-01 01:00 firmware-modem
Click to expand...
Click to collapse
And I really do not know enough about SELinux to effectively engage this.
@retiredtab: How did you solve SELinux in your builds for the T550?

RandomAndroidTinkerer said:
- GPS (though the initial fix took 30min+...)
Click to expand...
Click to collapse
That seems like a really long time. Did you go outside to do the GPS reading? Sometimes it makes a difference if you are in or outside. You should do an adb logcat while testing out GPS. It might show some clues as to why it takes so long.
With the P550 and using GPStest from
GPSTest | F-Droid - Free and Open Source Android App Repository
An app for testing GPS and GNSS capabilities of a device
f-droid.org
I get a lock in 48 seconds by the window.
RandomAndroidTinkerer said:
What does not work
- SELinux
Click to expand...
Click to collapse
You need to read posts 202 and beyond at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
I list the tools that you can use to help build selinux policies. As I wrote in the other thread, do you blindly trust the policies generated by the tools? I'm not an expert so I don't know and it's highly dependent on each hardware device.
I built an image with selinux enforcing as a test sometime in March and while it works, I'm not confident and ready to release that. In addition, each device will require it's own set of selinux policies. What might work for the P550 may not work on the T555 due to differences in hardware (LTE, S-pen).
Building the correct selinux policies is an iterative exercise. Wipe everything on your device, format data. Install the ROM only. You grant the initial batch of policies, reboot, look at logs, grant some more and repeat until they are gone. You should do this with the ROM only. Don't load gapps, games, apps, etc and then run selinux.
RandomAndroidTinkerer said:
Is that an issue? I don't know...
Click to expand...
Click to collapse
I see them in my own builds and so far there's been no problem.
RandomAndroidTinkerer said:
I see a lot of messages from the PowerHAL:
Click to expand...
Click to collapse
Same as above.
RandomAndroidTinkerer said:
I already tried https://review.statixos.com/c/android_device_essential_mata/+/1626/1 but that apparently was not enough.
Click to expand...
Click to collapse
You will find through experience and more building that what works for one platform may not work for another. It's highly dependent on the device and code specific to that device.
RandomAndroidTinkerer said:
SELInux:
I added the policies by https://github.com/VirsysElectron/android_device_samsung_gt510wifi and made them work, but it seems they are not really working.
Click to expand...
Click to collapse
In order to boot selinux enforcing, you need to remove line 140 from
android_device_samsung_msm8916-common/BoardConfigCommon.mk at lineage-17.1 · blizzard4591/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to blizzard4591/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
Also, I'm not an expert in selinux, but I don't know why you would permit untrusted_app.te, untrusted_app_25.te and untrusted_app_27.te?

retiredtab said:
That seems like a really long time. Did you go outside to do the GPS reading? Sometimes it makes a difference if you are in or outside. You should do an adb logcat while testing out GPS. It might show some clues as to why it takes so long.
With the P550 and using GPStest from
GPSTest | F-Droid - Free and Open Source Android App Repository
An app for testing GPS and GNSS capabilities of a device
f-droid.org
I get a lock in 48 seconds by the window.
Click to expand...
Click to collapse
I think it was just the initial, first fix, and yes, I was not in the best position. Now that it knows where and when it is, a new fix even inside takes a couple of seconds. I used the same tool, also from F-Droid
retiredtab said:
You need to read posts 202 and beyond at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
I list the tools that you can use to help build selinux policies. As I wrote in the other thread, do you blindly trust the policies generated by the tools? I'm not an expert so I don't know and it's highly dependent on each hardware device.
I built an image with selinux enforcing as a test sometime in March and while it works, I'm not confident and ready to release that. In addition, each device will require it's own set of selinux policies. What might work for the P550 may not work on the T555 due to differences in hardware (LTE, S-pen).
Building the correct selinux policies is an iterative exercise. Wipe everything on your device, format data. Install the ROM only. You grant the initial batch of policies, reboot, look at logs, grant some more and repeat until they are gone. You should do this with the ROM only. Don't load gapps, games, apps, etc and then run selinux.
Click to expand...
Click to collapse
I had to load Magisk and LiveBoot to even get the early-boot log. Using ADB logcat I was unable to get a log from "system start" - the adb process would hang and wait for the device to be fully booted. Even afterwards, no messages from boot. I had USB debugging enabled, default USB conf "file transfer", etc.
Any ideas what I am doing wrong?
retiredtab said:
I see them in my own builds and so far there's been no problem.
Same as above.
You will find through experience and more building that what works for one platform may not work for another. It's highly dependent on the device and code specific to that device.
In order to boot selinux enforcing, you need to remove line 140 from
android_device_samsung_msm8916-common/BoardConfigCommon.mk at lineage-17.1 · blizzard4591/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to blizzard4591/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
Also, I'm not an expert in selinux, but I don't know why you would permit untrusted_app.te, untrusted_app_25.te and untrusted_app_27.te?
Click to expand...
Click to collapse
Good catch - I simply copied the policies from VirsysElectron to start, but since they do not really work, I don't think I will continue much on this path. I share your opinion on old drivers and the greater picture. I had hoped the old policies would work for most of the basics, but they do not.

RandomAndroidTinkerer said:
I had to load Magisk and LiveBoot to even get the early-boot log.
Click to expand...
Click to collapse
For an eng build, there's no need for Magisk and LiveBoot to get an adb logcat. Part of the eng parameters is that it enables adb right away.
For developing selinux policies, you leave it in permissive first, develop the policies as I stated and then when you think you are done, then enable selinux enforcing. More at
Validating SELinux | Android Open Source Project
source.android.com
RandomAndroidTinkerer said:
Good catch - I simply copied the policies from VirsysElectron to start,
Click to expand...
Click to collapse
And that's the problem right there. It's so easy to kang or copy someone else's work today (legal or illegal) that some don't bother to check if it's right in the first place. I'm not saying VirsysElectron code is wrong, he may have a good reason why those files are generated.
I also fall into that boat. I use the public open source repos, but there's no way that I have the expertise or time to check everything in the repo for errors, security vulnerabilities, code correctness, etc.

retiredtab said:
For an eng build, there's no need for Magisk and LiveBoot to get an adb logcat. Part of the eng parameters is that it enables adb right away.
Click to expand...
Click to collapse
No, that is the problem - it did not. I am using eng-builds and, as I described, adb did not work, and I have no clue why.
retiredtab said:
For developing selinux policies, you leave it in permissive first, develop the policies as I stated and then when you think you are done, then enable selinux enforcing. More at
Validating SELinux | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
I read that and some other introductions to SELinux, I get the general idea and concept - but as shown in my example, the labeling rule
/firmware-modem(/.*)? u: object_r :tmp_root_mount_file:s0
Click to expand...
Click to collapse
is not applied, I did not find anything that would tell me why or how to debug such an issue.
retiredtab said:
And that's the problem right there. It's so easy to kang or copy someone else's work today (legal or illegal) that some don't bother to check if it's right in the first place. I'm not saying VirsysElectron code is wrong, he may have a good reason why those files are generated.
Click to expand...
Click to collapse
I started writing my own policies from scratch (its somewhere in the repo history), but I first wanted to get my bearings, see how things work - ideally from a known, working starting point - which was a good idea, as otherwise the issue mentioned above regarding the labeling rule that does not get applied would have cost me much more sanity than just questioning someone else's code

Hello RandomAndroidTinkerer
I also own a T555, currently with TWRP 3.3.1 and LineageOS 16.0 from Virsys( 20191231). It's very stable, except the SIM didn't work.
Am of course interested in your image and would like to test it out. Which TWRP version do you use ?
Friendly greetings
Schaagi

Hallo RandomAndroidTinkerer,
thank you very much for your work and of course thanks for retiredtab and the others for their work This is my first post here and I you are the only one I found who builded an actual image. I'm very interested in testing your build. Could you send me an link, please? Thank you and bye bye.

Hi, I applied for an uploader account at AndroidFileHost, once this is granted I will upload a current build.

Current engineering build is up: https://www.androidfilehost.com/?w=files&flid=324776
I am using TWRP 3.1.0 from here.
Be kind on the feedback

RandomAndroidTinkerer said:
Current engineering build is up: https://www.androidfilehost.com/?w=files&flid=324776
I am using TWRP 3.1.0 from here.
Click to expand...
Click to collapse
For fun, I tried it on the P550 and not surprisingly, it doesn't boot. It doesn't even out adb logcat.
LineageOS also builds it's own recovery.img as another recovery option to TWRP. It's not as user friendly and lacks some features, but it's functional.

Thank you so much for your image - I am very excited to test it. Feedback follows in the next days.

[Beta] [11] ProjectSakura-x86 for PC's [OFFICIAL]

{
"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"
}
Project Sakura is a custom ROM based on Lineage OS, It tries to remain true to it while also providing some more functionality and UI changes. Its sole purpose is to provide a platform which is powered by Lineage and is more customisable than Lineage.
This is an unofficial port of Project Sakura for PCs running x86 CPUs by using patches provided by Android-Generic project.
Made with Android-Generic v2.0 - Android for PCs & GSI devices
More detail : https://android-generic.github.io/
Code:
* Your warranty is now..... I don't know this is PCs ¯\_(ツ)_/¯
* It's very important to read the instructions and understand what you are doing. So please, READ !
* I am not responsible if you accidentally wiped your data on your hard drives or making your main OS like Windows unable to boot.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration."
Currently the best method I recommend to use is to dual-boot with a Linux distro, using its Grub2 bootloader to load the OS.You can check out BlissOS wiki or SupremeGamers wiki for the instruction.
Manual Install on Linux - Documentation
docs.blissos.org
Linux
Android-x86 is just a highly modified Linux. As a result, it has lot of similarities with Linux.
wiki.supreme-gamers.com
Alternatively, If you want to install using Windows
Advanced Android-x86 Installer - Knowledgebase
knowledgebase.blissos.org
Windows
Due to how Android-x86 is structured, it can be installed in any system.
wiki.supreme-gamers.com
For .rpm
Howto install Android X86 RPM images
I DON'T RECOMMEND TO FLASH ISO ON USB BECAUSE THE BOOTABLE INSTALLER IS HAVING PROBLEM.
Click Here
-Android-x86 Project
-BlissLabs (with works like BlissOS and Android-Generic)
-Lineage OS
-AOSP
-Superior OS
-AOSiP
-DerpFest
-Pixel Experience
-Extended UI
-Havoc OS
-CrDroid ROM
Project Sakura Source
The kernel source which I use for the build : https://github.com/hmtheboy154/Darkmatter-kernel
ProjectSakura-x86 Source which include all the changes for x86 will be available soon
ProjectSakura-x86 source : https://github.com/supremegamers/android/tree/sakura/11-x86/
Project Sakura's Telegram Group (if you want to feedback about the ROM)
BlissOS/ AG (x86/ x86_64) Telegram Group (if you need help installing or feedback about the PC builds)​
​This is a x86_64 build so please make sure your CPU support 64bit and SSE4.2
About bugs : Unlike Custom ROMs on phones where people can just put "You tell me", PC builds do have problem..... a lot.
- Not all the hardware will work perfectly or even supported (*cough Nvidia GPUs ).
- Screen Recording is not working yet (gbm_gralloc limitation)
- FaceUnlock is not working (and don't even hope it work)
- Bluetooth might not working yet.
- SwiftShader is broken so you can't boot with Software Rendering.
- For user using AMD GPUs (or APUs), there's graphic bugs when you have to choose default apps like for default launcher or default browser. Here's an explanation by Mauro Rossi - one of the member of Android-x86 Project :
A long standing issue is "the tiling artifacts" happening with gbm_gralloc at ResoverActivity window when SW write buffer used, one example is the launcher selector at first boot and another is visible with Chicken Invaders advertisements windows on SW write buffer
Intel i915 and i965 were not affected, while r300, r600, radeonsi and nouveau are all affected,
iris and crocus expected to not be affected, but I need to check.
Click to expand...
Click to collapse
So if you are seeing this (or worse) then it's the one I'm talking about.
(Iris and crocus actually not affected btw)
Update : Iris got reported to be affected, and there are some cases of crocus too. So I will mark this as a bug for both AMDGPUs and Intel iGPUs in general. If you want to read more about the bug, you can read this post by Mauro for more info
Project Sakura-x86 for PCs
Maintainer: HMTheBoy154
Build Type: Unofficial
ROM OS Version: 11.0 r40
ROM Kernel: Linux 5.10.61
ROM Firmware Required: Included in the build
Based On: LineageOS 18.1
Version Information
Status: Alpha
Current Stable Version: 5.R
SELinux Status : Permissive
Release Date: 2021-09-06

This is the first initial build which include FOSS pack from BlissOS. FOSS pack provide some FOSS application and also microG as the GMS replacement. Also here's what I put into the build :
- Mesa 21.2.1, libdrm 2.4.107 and LLVM12.0.1
- alsa-utils and alsa-lib are on version 1.2.5.1 with alsamixer tool
- My customized Kernel 5.10.61 which include patches from GoogleLTS (kernel/common android13-5.10 branch), xanmod and Android-x86 (More detail)
- AOSP SystemWebView got replaced with Bromite SystemWebView (big thanks to them for providing x86_64 builds)
- Using FakeStore 0.1.0 instead of 0.0.2 provided by FOSS package.
- Adding Open Camera since the stock Camera app is broken.
Here are some screenshot :

where is the famous xda bugs description " bugs ? You tell me "

Ni8 said:
where is the famous xda bugs description " bugs ? You tell me "
Click to expand...
Click to collapse

Pro :3

For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'

I installed it in my realme c2 and its working very fine.

New builds have been uploaded, here are the new changes :
- Upstream to September Security patch
- Update Mesa to 21.2.2
- Fixed broken Bluetooth (require restarting bluetooth app)
- Adding thermal-daemon from Project Celadon
- Adding Thermal HAL from Project Celadon
- Pull houdini and Widevine from ChromeOS 92 recovery file for hatch
- Now comes with both GMS and FOSS build
For bluetooth, just restart `com.android.bluetooth` by using `pm disable` then `pm enable` and then it will work if your card already recognized by Android-x86 before. I tested with a fake CSR card and it's running as expected.
By the way, I applied for ProjectSakura maintainer, both for PCs and Oneplus Nord So expect a new OFFICIAL build soon.

cjeu100 said:
For anyone looking how to fix "serial console enabled, performance will be impacted" warning in notifications, here is how i fixed it.
Open termux, type following commands.
Bash:
su
nano /default.prop
Then edit ro.debuggable=1 to ro.debuggable=0 and press ctrl + x, save and exit.
alternatively,
Bash:
su -c 'sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop'
Click to expand...
Click to collapse
NOPE! even with root is a read only filesys.
And the SED command returns formatting error as well.
Pleas share proper in depth steps if you might. thanks

joshyakadamien said:
NOPE! even with root is a read only filesys.
Click to expand...
Click to collapse
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop

cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?

joshyakadamien said:
Thanks, one Q though, if i installed the system as R/W then again i need to mount it as R/W?
Click to expand...
Click to collapse
Only in Android 11, you need to mount as r/w again, ro by default unlike previous versions of Android x86.

Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.

Veselchak787 said:
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Click to expand...
Click to collapse
Hello my Russian friend from 4pda.
We are also waiting for the update

One more question: how I can download files using build in this rom internet browser?

Veselchak787 said:
Hello! I use now the rom ProjectSakura-5.2-OpenGapps-pico-20210922-1750--UNOFFICIAL.iso
I'd like to use browser Google Chrome with bookmarks sync, but it crushed every time after 5-10 seconds after start.
Is anybody can help me?
I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I just tested from the latest beta build I have here (haven't release it yet) and I do have the same problem, still don't know why, maybe I will take a look at it soon
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.

kamazok said:
Hello my Russian friend from 4pda.
We are also waiting for the update
Click to expand...
Click to collapse
I'm still planning for the new update tho, aiming for BoringDroid in the next version so we might have 4 Desktop Mode to choose. So I am waiting for utzcoz to fix it on newer security patch.
by the way, this thing is on 4PDA ???

We
HMTheBoy154 said:
this thing is on 4PDA ???
Click to expand...
Click to collapse
We are disсuss differen variants of Android x86.
Android OS на x86 - 4PDA
Android OS на x86, [androidPC]
4pda.to

I have notebook: HP 15s-eq1116ur, CPU - AMD Athlon Gold 3150U, video integrated - Radeon RX Vega 3, wifi and BT - Realtek RTL8821CE.
Click to expand...
Click to collapse
I'm rocking this on a HP Elitepad 1000 G2 with nice batt times
But in the meantime, please try other Browsers that are not having any GMS-relation like Bromite or Firefox. I know that without sync will have some tough time to you, but those browsers are working well so far.
Click to expand...
Click to collapse
Brave is stable for. ex.

cjeu100 said:
That means you need to remount /system as read/write. Install gearlock to do it automatically, or
extract system.img from system.sfs in the folder/ partition in which Android is installed, and in android terminal run
su
mount -o remount,rw /
For the sed error run su first and then type
sed -i "s|ro.debuggable=.*|ro.debuggable=0|g" /default.prop
Click to expand...
Click to collapse
Thanks, did the trick.