Database Develop

[KERNEL] ★ HTC Incredible S ★ 2.6.35.9 Kernel Source Code ★

HTC has officially released the kernel source for the Incredible S
Just go right there to download:
http://dl4.htc.com/RomCode/Source_and_Binaries/vivo-2.6.35-g89aa373.tar.gz
From: http://developer.htc.com/

Amazing! Thanks for this, really good news and could really help with finding a method for root access. Even if it doesn't it's a bit of a win as HTC are notoriously bad at releasing sources, and this is the first .35 source they have released

I don't have any developing skills, so I can't help in that way but I figured I can post a mirror in case anyone needs it.
Enjoy,
http://www.fileserve.com/file/x29c4uR

i can't download it why?
please tell me why
I solve it
anyway thanks a lot!

anyone found something usefull so far in it?

Is there anyone who can post the config.gz file (located in your phone in /proc/ folder) ?
I would like to compare the config files from the Desire and the Incredible S.
Thanks a lot.

for you:
config.gz

Nvidia32 said:
for you:
config.gz
Click to expand...
Click to collapse
Merci beaucoup
Edit: Here is the head content of this file
Code:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.35.9
# Fri Feb 11 17:59:46 2011
#

How very generous on the HTC's part, providing the sources for the kernel that nobody would be able to run after it's built.

Fightspit said:
Is there anyone who can post the config.gz file (located in your phone in /proc/ folder) ?
I would like to compare the config files from the Desire and the Incredible S.
Thanks a lot.
Click to expand...
Click to collapse
Here is the latest config.gz from v2.12.981.2 built on the 1st of April:
config.gz
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.35.9
# Fri Apr 1 03:05:58 2011
#
Click to expand...
Click to collapse
Tell me if you're interested in building a custom kernel for this device. I can help testing it on my S-OFF one (et je suis français aussi )

Ginger bread wild
HTC Incredible S - GB MR - 2.6.35 release
http://developer.htc.com/
for devs

jul644 said:
HTC Incredible S - GB MR - 2.6.35 release
http://developer.htc.com/
for devs
Click to expand...
Click to collapse
At ****ing last!!!
Excuse my French, I've been waiting for this for a while...
Sent from my HTC Incredible S using Tapatalk

l0st.prophet said:
At ****ing last!!!
Excuse my French, I've been waiting for this for a while...
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
nothing new. not better than my work...

Your work has the camcorder delay bug. If you can fix it you could be right
Sent from my HTC Incredible S using XDA App

Can this kernel fix the problems for Vodafone nl users with no mobile internet connection?
Sent from my HTC Incredible S using XDA App

m-deejay said:
nothing new. not better than my work...
Click to expand...
Click to collapse
hi m-deejay, would you be rebaslining you V2 kernel with this one officialy for Increcible S?

m-deejay said:
nothing new. not better than my work...
Click to expand...
Click to collapse
It is new for everyone else. If I based a kernel off your work, it wouldn't be mine then would it? You may have had access to this for a while, but no one else has from what I can see, so it is new, and it is something I can work with.

will you be releasing your version soon?

Can anybody please have a look:
On MIUI and cyanogen ROMs the microphone stops working, when you make a call with a plugged in headphone.
Someone told me, it could be the kernel.
Is there something we can try on CM or MIUI?

[MOD][DEV]Native Screenshot For OTA Based Roms

1.Decompile android.policy.jar
2.\android.policy.jar.out\smali\com\android\internal\policy\impl\Phonewindowsmanager.smali
3.Open up phonewindowsmanager.smali
4.look for "com.htc.action.SCREEN_CAPTURE_BG"
5.Change "com.htc.action.SCREEN_CAPTURE_BG" to "android.intent.action.SCREENSHOT"
6.Save and recompile
7. Open up your build.prop and add
# Properties for supporting framework features
ro.htc.framework.screencapture = true
8. save
9. Add these files to your rom http://www.multiupload.com/V3UUU5B9RD
10. Open up your updater-script and add
set_perm(0, 0, 06755, "/system/bin/screenshot");
11.save
DONE...
Credits
-SKYRAIDER
-Cyanogen
-HTC

Once you do this - how do you take a screenshot? Power+Home?
-xdadevelopers-user

xdadevelopers-user said:
Once you do this - how do you take a screenshot? Power+Home?
-xdadevelopers-user
Click to expand...
Click to collapse
yup
10chat

Doesn't work for me. Anyone else?
-xdadevelopers-user

xdadevelopers-user said:
Doesn't work for me. Anyone else?
-xdadevelopers-user
Click to expand...
Click to collapse
Anyone?
-xdadevelopers-user

xdadevelopers-user said:
Doesn't work for me. Anyone else?
-xdadevelopers-user
Click to expand...
Click to collapse
Hope I'm not necroposting too hard, but I just tried this. No luck.

what happens ?
10 char

When i try to take a screen shot i get a toast saying "error: /mnt/sdcard/tmpshot.bmp (no such file or directory)", and then another toast right after saying "screenshot is saved at null". I search my phones / directory with root explorer and find no .bmp files containing any screen shots. If i create a file named tmpshot.bmp on my sdcard then try to take a screen shot i get "error unable to save screenshot: java.language.nullpointer exception" and then "screenshot is saved at /mnt/sdcard/dcim/screenshots/******.bmp". Every time you create the tmpshot.bmp file and take a screen shot it also removes the file from the sdcard. So if you go to where it says it saved them the pic files are there but they have no thumb, and when you open it it is just a black screen with the little grey gallery error icon.

JoelZ9614 said:
what happens ?
10 char
Click to expand...
Click to collapse
Pwr+home brings up the power menu and takes me to the home screen. It is as if I haven't made the changes at all. I've double and triple checked and the changes are there.

I couldn't even find this line in the code:
com.htc.action.SCREEN_CAPTURE_BG

Working on Another Senseless ROM v2.0. For those having issues, you gave screenshot in /system/bin 06755 permissions correct? I did this using adb: adb shell - chmod 06755 /system/bin/screenshot.
Jermaine, which ROM are you looking for that in?

RMarkwald said:
Working on Another Senseless ROM v2.0. For those having issues, you gave screenshot in /system/bin 06755 permissions correct? I did this using adb: adb shell - chmod 06755 /system/bin/screenshot.
Jermaine, which ROM are you looking for that in?
Click to expand...
Click to collapse
I was looking in Insensitive.
***I'm mobile

jermaine151 said:
I was looking in Insensitive.
***I'm mobile
Click to expand...
Click to collapse
Found it in the method named: .method public interceptKeyBeforeDispatching(Landroid/view/WindowManagerPolicy$WindowState;IIIIIII)Z
Found it @ line # 5349 (that's the line #'s in Notepad++). Here's what's around it:
.line 1743
.local v14, intent:Landroid/content/Intent;
const-string v22, "android.intent.action.SCREENSHOT"
Obviously this is the modified line, from Another Senseless ROM v2.0 that is.

RMarkwald said:
Found it in the method named: .method public interceptKeyBeforeDispatching(Landroid/view/WindowManagerPolicy$WindowState;IIIIIII)Z
Found it @ line # 5349 (that's the line #'s in Notepad++). Here's what's around it:
.line 1743
.local v14, intent:Landroid/content/Intent;
const-string v22, "android.intent.action.SCREENSHOT"
Obviously this is the modified line, from Another Senseless ROM v2.0 that is.
Click to expand...
Click to collapse
Thanks Mark! I'll have to look at it again.

Hey Joel, just for grins I performed these instructions on my HTC Flyer's Honeycomb ROM named WestfireROM v2.0 (based off of the HC leak), works for that device too!
Is it okay to put up a post in the Flyer forums linking back to your OP? I suppose maybe wait until others can get this working maybe...?

RMarkwald said:
Found it in the method named: .method public interceptKeyBeforeDispatching(Landroid/view/WindowManagerPolicy$WindowState;IIIIIII)Z
Found it @ line # 5349 (that's the line #'s in Notepad++). Here's what's around it:
.line 1743
.local v14, intent:Landroid/content/Intent;
const-string v22, "android.intent.action.SCREENSHOT"
Obviously this is the modified line, from Another Senseless ROM v2.0 that is.
Click to expand...
Click to collapse
It must've been late when I tried before. LOL.I definitely see the line now. Thanks again. I'm going to test it out.
EDIT: Works perfectly!!! Thanks Joelz and RMark!!!

xdadevelopers-user said:
Pwr+home brings up the power menu and takes me to the home screen. It is as if I haven't made the changes at all. I've double and triple checked and the changes are there.
Click to expand...
Click to collapse
+1. I can't get it to do anything, but the changes are definitely there. Does it matter where in the build.prop you put those additional lines?

Ok im an idiot. I was doing this late last night and i chmoded the screenshot file in /system/bin wrong. I gave it the correct permissions and now its working perfectly. I can finally ditch my screenshot app. Thanks guys.

godsmacked4653 said:
+1. I can't get it to do anything, but the changes are definitely there. Does it matter where in the build.prop you put those additional lines?
Click to expand...
Click to collapse
I put the changes at the very end, so it's the last two lines.

I just told xdadeveloper-user this same thing; if you want to post your android.policy.jar file and build.prop, I don't mind taking a look to make sure the changes were made right.

[MOD][SMALI] Enable Native AT&T / Tmobile WiFi Hotspot[MOD][SMALI]

Guide: Howto enable Native AT&T / Tmobile WiFi Hotspot​
Locate stock/unmoddified TetheringProvision.apk
This apk is located in /system/app folder from almost any Stock Samsung ROM
Or pull from your device.
connect your device to your PC
Make sure you have the appropriate USB drivers installed
make sure Android SDK Tools are installed
cd to the platform-tools folder in the SDK location
start a command prompt in the Platform-Tools folder
adb pull /system/app/TetheringProvision.apk
Using available tools to decompile and recompile the apk
I recommend either Virtuous Ten Studio or APK-Multi-Tool for this task as
either provide an easy to use interface for working with apk edits.
I'm not placing download links here for either just do a google search and
you will easily find either one.
Decompile the TetheringProvision.apk
Once you have the apk decompiled browse to the folder containing
all of the decompiled code (You will need to be in the smali folder).
locate and edit "TetheringProvisionActivity$TetheringPlanCheckTask.smali" (com/sec/tetheringprovision)
For AT&T WiFi Hotspot
search for "entitlement.mobile.att.net" and replace with "stacra.byethost7.com"
search for all instances of "http://entitlement.mobile.att.net/mhs1" and replace with "http://stacra.byethost7.com/tether/"
search for all instances of "http://entitlement.mobile.att.net/teth" and replace with "http://stacra.byethost7.com/tether/"
For Tmobile WiFi Hotspot
search for all instances of "http://selfhelp.geo.t-mobile.com/myaccountservice/selfhelp/hastetheringoption"
and replace with "http://stacra.byethost7.com/tether/"
See code snippet below for example (not complete code)
The lines you will be looking for are highlighted in blue.
Code:
.prologue
.line 1116
iput-object p1, p0, Lcom/sec/tetheringprovision/TetheringProvisionActivity$TetheringPlanCheckTask;->this$0:Lcom/sec/tetheringprovision/TetheringProvisionActivity;
invoke-direct {p0}, Landroid/os/AsyncTask;-><init>()V
.line 1117
const-string v0, [COLOR="Blue"]"http://selfhelp.geo.t-mobile.com/myaccountservice/selfhelp/hastetheringoption"[/COLOR]
iput-object v0, p0, Lcom/sec/tetheringprovision/TetheringProvisionActivity$TetheringPlanCheckTask;->TMobileTetheringPlanCheckURL:Ljava/lang/String;
.line 1118
const-string v0,[COLOR="Blue"] "http://entitlement.mobile.att.net/teth"[/COLOR]
iput-object v0, p0, Lcom/sec/tetheringprovision/TetheringProvisionActivity$TetheringPlanCheckTask;->ATTTetheringPlanCheckURL:Ljava/lang/String;
.line 1119
const-string v0,[COLOR="Blue"] "http://entitlement.mobile.att.net/mhs1"[/COLOR]
iput-object v0, p0, Lcom/sec/tetheringprovision/TetheringProvisionActivity$TetheringPlanCheckTask;->ATTMHSPlanCheckURL:Ljava
/lang/String;
...
...
...
Once you have located and replaced all the required lines in the smali save the file and recompile your apk following the instructions provided by whatever method you choose to work with
DO NOT SIGN THE APK LEAVE THE EXISTING SIGNATURE IN PLACE
Push the apk back to your device and reboot, test to verify working Hotspot.
Thanks
Thanks to @scrosler over at the LG forums for the original code of this patch
it has been changed and revised a few times since the original port by me over
in the HTC Forums.

reserved

Another Great Work Sir.... Awesome. Added Q16 on FAQ Thread. Thanks to my Favorite Dev @cstayton :good:
[SIZE=+1]Q16: How to Enable Native AT&T / T-Mobile WiFi Hotspot?[/SIZE]
Thanks to @cstayton [MOD][SMALI] Enable Native AT&T / Tmobile WiFi Hotspot[MOD][SMALI]​
☆Swyped From SFive SS Edition☆

Thank you for this!!!! Sweet. Great work man

Can u upload the modded tetherprovision.apk for the att version AND3 please
Im.askimg cause i dont have a pc to do modding anymore
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

carlospr21 said:
Can u upload the modded tetherprovision.apk for the att version AND3 please
Im.askimg cause i dont have a pc to do modding anymore
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
check post #2 Here

Look, I think you should improve the guide only works for at&t and tmobile.
I modified "TetheringProvision" in this guide and nothing, the same error: "Mobile data is not avaible or invalid SIM". Does not work with another carrier other than att or tmobile.
The only way that works for me is to replace the apk dirty "TetheringProvision" method Galaxy S4.
Corroborate if someone worked with different operator, for example, movistar latin america or other provider other country.

jm2k7 said:
Look, I think you should improve the guide only works for at&t and tmobile.
I modified "TetheringProvision" in this guide and nothing, the same error: "Mobile data is not avaible or invalid SIM". Does not work with another carrier other than att or tmobile.
The only way that works for me is to replace the apk dirty "TetheringProvision" method Galaxy S4.
Corroborate if someone worked with different operator, for example, movistar latin america or other provider other country.
Click to expand...
Click to collapse
obviously your carrier uses different methods to provision tethering, if you can tell me what methods they use i might be able to adjust for it
and P.S. if you can read you would see it says AT&T or Tmobile, i only offered as a hope that maybe other carriers used the same methods, so if you want me to look into it might try asking nicely.

cstayton said:
obviously your carrier uses different methods to provision tethering, if you can tell me what methods they use i might be able to adjust for it
and P.S. if you can read you would see it says AT&T or Tmobile, i only offered as a hope that maybe other carriers used the same methods, so if you want me to look into it might try asking nicely.
Click to expand...
Click to collapse
no problem, however the effort is appreciated.
do not know how could fix the code so that it works for another operator.
It should be something generic to accept any carrier.
Well for now the problem is solved just replace the apk: http://forum.xda-developers.com/att-galaxy-s5/themes-apps/mobile-hotsoit-carrier-t2801876
hello again. :fingers-crossed:

jm2k7 said:
no problem, however the effort is appreciated.
do not know how could fix the code so that it works for another operator.
It should be something generic to accept any carrier.
Well for now the problem is solved just replace the apk: http://forum.xda-developers.com/att-galaxy-s5/themes-apps/mobile-hotsoit-carrier-t2801876
hello again. :fingers-crossed:
Click to expand...
Click to collapse
i compared that apk to ours and it is not even close in code, not sure what kind of effect this will have in our devices as far as att and tmobile go
there where to many differences to sort through to determine what was needed. sorry

jm2k7 said:
no problem, however the effort is appreciated.
do not know how could fix the code so that it works for another operator.
It should be something generic to accept any carrier.
Well for now the problem is solved just replace the apk: http://forum.xda-developers.com/att-galaxy-s5/themes-apps/mobile-hotsoit-carrier-t2801876
hello again. :fingers-crossed:
Click to expand...
Click to collapse
I PM'd you a test patch let me know if it works please

Modified successful solution
THIS THREAD:
-----------------------------------------------------------------------
http://forum.xda-developers.com/att...t/mod-enable-native-att-tmobile-wifi-t2801442
MY PHONE:
-----------------------------------------------------------------------
Samsung Galaxy S5 from AT&T
Model number: SAMSUNG-SM-G900A
Android version: 4.4.2
Using Grand Fathered unlimited data plan
PREREQUISITES:
-----------------------------------------------------------------------
* Root Samsung Galaxy S5 using Towelroot.
- see MY PHONE above
* Download/Install "Virtuous Ten Studio" (VTS): a free tool used to decompile, edit, and recompile apk files.
* Use adb to pull TetheringProvision.apk from phone to PC
* Patch TetheringProvision.apk pulled from the phone using using the VTS tool
-- edited apk files per instructions in THIS THREAD.
-- for VTS settings use advanced, use original signature of apk, ...
* USING Root Explorer create /sdcard/myPatch1/
INSTALLATION PROCEDURE:
-----------------------------------------------------------------------
adb push myPatch1/TetheringProvision.apk /sdcard/myPatch1/
adb shell
su
mount -o rw,remount /system
cd /system/app
mv TetheringProvision.apk TetheringProvision.apk.bk20140719_stock_442
mv TetheringProvision.odex TetheringProvision.odex.bk20140719_stock_442
cd /sdcard/myPatch1
cp TetheringProvision.apk /system/app/TetheringProvision.apk
cd /system/app
cp TetheringProvision.apk TetheringProvision.apk.bk20140719_myPatch1
chmod 644 TetheringProvision*
ls -la | grep TetheringProvision.apk
mount -o ro,remount /system
reboot
NOTES:
-----------------------------------------------------------------------
* To make the above work, I added line
"mv TetheringProvision.odex TetheringProvision.odex.bk20140719_stock_442"
* The above procedure also worked using using a ALTERNATE PRE BUILT TetheringProvision.apk
downloaded from "TetheringProvision_Patch_V2.zip" link found at
http://forum.xda-developers.com/showthread.php?t=2795885
FYI: 7 zip was used to extract TetheringProvision.apk from downloaded zip - see *myPatch2 below
* Size of patched APK is almost 2x size of original; however, 7 Zip shows same contents are the same
ARTIFACTS(adb shell):
-----------------------------------------------------------------------
[email protected]:/system/app # ls -la | grep TetheringProvision
ls -la | grep TetheringProvision
-rw-r--r-- root root 475499 2014-07-19 02:26 TetheringProvision.apk
-rw-r--r-- root root 475499 2014-07-19 02:34 TetheringProvision.apk.bk20140719_myPatch1
-rw-r--r-- root root 432539 2014-07-19 01:50 TetheringProvision.apk.bk20140719_myPatch2
-rw-r--r-- root root 253215 2014-07-19 02:32 TetheringProvision.apk.bk20140719_stock_442
-rw-r--r-- root root 79528 2014-07-06 23:41 TetheringProvision.odex.bk20140719_stock_442
NOTES(artifact suffix):
-----------------------------------------------------------------------
* Original artifact backups suffixed with stock_442
* TetheringProvision.apk.bk20140719_myPatch1 - patched using VTS tool
* TetheringProvision.apk.bk20140719_myPatch2 - ALTERNATE PRE BUILT download

Why can't you just post the modified .apk for att and T-Mobile?

No modifications to my code without roper recognition
I'm normally a pretty easy going kind of guy, but sometimes I get a little testy when certain things happen, so I'm only going to say this once.
IF YOU USE MY WORK OR MODIFY IT IN ANY FASHION YOU MUST ASK MY PERMISSION FIRST, AND IN NO WAY OR FASHION ARE YOU ALLOWED TO REPOST YOUR MODIFICATIONS IN MY THREAD.
This includes creating patches for other systems, patches for same systems at request of other members etc.
If this happens again I will give proper warning and then I will close and delete the thread and that will be that.
This is an awesome community way beyond expectations however, I am a stickler for protocol, if you ask I'll will give permission 100% of the time as long as it is mine to give.

What is the vts tool? Thanks
Sent from my SM-G900T using XDA Free mobile app

xda23 said:
What is the vts tool? Thanks
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Virtuous Ten Studio you can find it HERE

WhiteWidows said:
Why can't you just post the modified .apk for att and T-Mobile?
Click to expand...
Click to collapse
lol i learned how to build roms before decompiling apks as i find it easier.. i guess youre suppose to be smart enough to pull the apk, decompile the apk, edit the apk, recompile the apk and possibly sign it afterwards in order to use this MOD! Good Luck! Without a pre modded apk I will hafta wait until the weekend to ask for permission to include in my ATT ROM
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
lol i learned how to build roms before decompiling apks as i find it easier.. i guess youre suppose to be smart enough to pull the apk, decompile the apk, edit the apk, recompile the apk and possibly sign it afterwards in order to use this MOD! Good Luck! Without a pre modded apk I will hafta wait until the weekend to ask for permission to include in my ATT ROM
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
really? Seriously? This is probably one of the easiest mods EVER, and since this mod can be adopted accross carriers posting a "premodded apk" would be time consuming as i would have to have the specific apk from every carrier.
THIS IS a thread on HowTo not a thread on Here you go have it...
P.S. if your building a ROM to post in the forums might be a good idea not to ruffle the feathers of the DEVS whose work you want to include.

cstayton said:
really? Seriously? This is probably one of the easiest mods EVER, and since this mod can be adopted accross carriers posting a "premodded apk" would be time consuming as i would have to have the specific apk from every carrier.
THIS IS a thread on HowTo not a thread on Here you go have it...
P.S. if your building a ROM to post in the forums might be a good idea not to ruffle the feathers of the DEVS whose work you want to include.
Click to expand...
Click to collapse
I do not own an ATT s5.. I have a vzw s5.. searching online you can find similar MOD for tethering that has been around for some time with the same exact edits as your MOD. Either way I am sorry if I offended you. I just feel it would be easier for ATT owners to have a modded apk that they can use for their ATT roms considering this is the ATT thread.. What youre implying is no one can take your mod edit (most likely found from someone else) and make an apk for others to use who do not have the ability to do it themselves. Android is about being open source and sharing with the community not providing a mod that is easily found throughout these forums and saying no one else can use it or post an apk without your permission or knowledge of how to make the edits in the first place.
Again, i am glad for what you do but a mod that has been around for some time isnt something one can claim as theres just because theyre first to post in a certain thread.
And all i was saying is why not post a modded apk or let someone else just with the att apk for att users in this thread? Not to go and make one for every device.. but hey, i will not add your mod to any rom I work on.. I will find one of the other devs MOD and give them the cred.
edit: here is the same mod from over a year ago:
http://forum.xda-developers.com/showthread.php?t=2278259
Of course you used a different server address but the mod is the same. You only need to direct the mod to a server that enables the hotspot to be turned on.
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
I do not own an ATT s5.. I have a vzw s5.. searching online you can find similar MOD for tethering that has been around for some time with the same exact edits as your MOD. Either way I am sorry if I offended you. I just feel it would be easier for ATT owners to have a modded apk that they can use for their ATT roms considering this is the ATT thread.. What youre implying is no one can take your mod edit (most likely found from someone else) and make an apk for others to use who do not have the ability to do it themselves. Android is about being open source and sharing with the community not providing a mod that is easily found throughout these forums and saying no one else can use it or post an apk without your permission or knowledge of how to make the edits in the first place.
Again, i am glad for what you do but a mod that has been around for some time isnt something one can claim as theres just because theyre first to post in a certain thread.
And all i was saying is why not post a modded apk or let someone else just with the att apk for att users in this thread? Not to go and make one for every device.. but hey, i will not add your mod to any rom I work on.. I will find one of the other devs MOD and give them the cred.
edit: here is the same mod from over a year ago:
http://forum.xda-developers.com/showthread.php?t=2278259
Of course you used a different server address but the mod is the same. You only need to direct the mod to a server that enables the hotspot to be turned on.
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
read the OP, it says where the mod came from scrossler over in the LG forums,(which by the way is the original mod this is based on) the design of this mod is different than his and has more edits. so yes this is based on his mod but is my work. i highly doubt you found lots of mods with the exact same edits as the edits in my mod point to my specific servers and are handled differently than others.
I am not posting a modded apk nor will I this thread is a guide on how to do it yourself.
nuff said thread closed.
AND P.S. THIS MOD IS ONLY FOR AT&T AND TMOBILE, NOT FOR VERIZON.

[DEVS][Safestrap][How-To] Reboot To Safestrap Recovery Via Power Menu

So First; we must thank @Hashcode for hos wonderful Safestrap Recovery That allows us to flash custom ROMs even though we have a locked Bootloader
In this Guide I will show you how to edit your power menu to change the reboot recovery from going to the recovery partition to going to Safestrap
This is independent of the safestrap app, IF AND ONLY IF the safestrap image is on the phone already
This is only for devs who want to incorporate this into their rom and I will not be answering questions on how to do this as even a beginner dev can manage this
I only ask that credit be given to @Hashcode, @Goldie @RErick and AllianceROM and that the supplied script not be changed or modified in anyway,
This is being shared freeley and a little thanks goes a long way
First thing is first
You will need to Decompile android,policy,jar
Look for globalactions$99$1.smali
Inside this smali file you will need to find
.method public onClick(Landroid/content/DialogInterface;I)V
and then look for this set of lines its at the very top
Code:
const/4 v2, 0x1
const/4 v3, 0x0
sget v0, Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;->rebootMode:I
const/4 v1, -0x1
if-le v0, v1, :cond_0
sget v0, Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;->rebootMode:I
Directly underneath that last line above add these lines
Code:
const/4 v1, 0x3
if-eq v0, v1, :cond_4
Now, at the very bottom of the same method, directly above the line that says
Code:
goto :goto_1
You will add these lines
Code:
goto :goto_1
:cond_4
const-string v1, "su -c /system/bin/recrbt.sh"
invoke-static {}, Ljava/lang/Runtime;->getRuntime()Ljava/lang/Runtime;
move-result-object v2
invoke-virtual {v2, v1}, Ljava/lang/Runtime;->exec(Ljava/lang/String;)Ljava/lang/Process;
Thats it for the jar file. Save and recompile and then I have attached a zip with the needed script inside that needs to be placed in
/system/bin and permissions set to 0755
Or if on a clean flash, dont worry about permissions.
:good:

RErick said:
So First; we must thank @Hashcode for hos wonderful Safestrap Recovery That allows us to flash custom ROMs even though we have a locked Bootloader
In this Guide I will show you how to edit your power menu to change the reboot recovery from going to the recovery partition to going to Safestrap
This is independent of the safestrap app, IF AND ONLY IF the safestrap image is on the phone already
This is only for devs who want to incorporate this into their rom and I will not be answering questions on how to do this as even a beginner dev can manage this
I only ask that credit be given to @Hashcode, @Goldie @RErick and AllianceROM and that the supplied script not be changed or modified in anyway,
This is being shared freeley and a little thanks goes a long way
First thing is first
You will need to Decompile android,policy,jar
Look for globalactions$99$1.smali
Inside this smali file you will need to find
.method public onClick(Landroid/content/DialogInterface;I)V
Thats it for the jar file. Save and recompile and then I have attached a zip with the needed script inside that needs to be placed in
/system/bin and permissions set to 0755
Or if on a clean flash, dont worry about permissions.
:good:
Click to expand...
Click to collapse
Ha, Freakin awesome you just made the day of nearly every dev here in the S5 forums. Great job and thank you very much.

Good job

@RErick
Great job Sir....this is what I called development.
☆ Swyped From SFour Flying Color CCC Theme ☆

Is there gonna be a zip to flash
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

ozz200127 said:
Is there gonna be a zip to flash
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doubtful, you need to ask your Rom dev to incorporate into their rom. With proper credit of course. [emoji5]

@bri315317 go to this thread and read post 2415 http://forum.xda-developers.com/showthread.php?t=2616221 make sure you have power menu options turned of in wanam and gravity box. It is for s4.
M&M AND Kitkat

parkerj7uc said:
@bri315317 go to this thread and read post 2415 http://forum.xda-developers.com/showthread.php?t=2616221 make sure you have power menu options turned of in wanam and gravity box. It is for s4.
M&M AND Kitkat
Click to expand...
Click to collapse
I believe you mistaken me for the other person, but that's OK. Thanks for supplying it to those that need it. [emoji482]

Edit: disregard. Took me 5-6 hours of hunting around to decide to look in ext.jar.

LineageOS 17 for suzuran?

Does its existence for devices like the Z3C make it more or less likely for us to see on suzuran? Would love to see a LineageOS 17 ROM for this device. Makes me wish I was a dev. Thanks to all those who continue to grind hours into porting and developing ROMs for the platform.

beflythis said:
Would love to see a LineageOS 17 ROM for this device.
Click to expand...
Click to collapse
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why

Berni-0815 said:
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Click to expand...
Click to collapse
Are you making any kernel changes? If not, that's probably why. You can't use the LineageOS 15.1 kernel on the PIE. Correct me if I'm wrong but Pie requires linux kernel 4.4x and greater while, Android 10 requires 4.9 and greater.

Apart from fixing compile-errors, no.
But I don't think that the kernel version is important. This project uses kernel 3.x too, if I'm not wrong...
Sure, there have to be changes, but I can't do so...

I've tried another kernel (this one) and I changed/added some files to avoid compile errors. But the result is the same:
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
...and so on until end of battery...

Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.

Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place)
Click to expand...
Click to collapse
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
I've tried to build pie with this kernel. Nearly the same result.

Berni-0815 said:
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
I've tried to build pie with this kernel. Nearly the same result.
Click to expand...
Click to collapse
Weird, I ran into some issues building pie yesterday, but didn't have any time to fix it. I'll try again tonight and see how it goes. If I still have issues, I'll have to wait till the weekend.

Joel16 said:
Weird, I ran into some issues building pie yesterday
Click to expand...
Click to collapse
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold

Berni-0815 said:
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Click to expand...
Click to collapse
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.

Joel16 said:
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building
Click to expand...
Click to collapse
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Click to expand...
Click to collapse
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?

Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.

You can do It!!!

Joel16 said:
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
Click to expand...
Click to collapse
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
The z5c is based on Qualcomm Snapdragon 810 MSM8994, like:
SONY XPERIA Z5 PREMIUM | MOTOROLA DROID TURBO | MICROSOFT LUMIA 950 XL | NUBIA Z9 MAX
Is there any source of a pie build availible where we can get some hints how get a pie build to run?
Here are some kernel sources from the Nubia Z9 Max (nx510j):
https://github.com/nubia-development/android_kernel_nubia_msm8994

I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
I'll have a look at this. :good:

Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
For my self I try slowly become deeper into that topic: building a rom.
So I did a little bit of research in github and gitlab and I found some interesting repos from this user:
https://github.com/Cyborg2017?tab=repositories
I ask him if he could help us a little bit and the first result is this.
@Joel16 & @Berni-0815 Perhaps this is useful:
https://github.com/Cyborg2017/android_kernel_sony_msm8994/tree/sony_msm8994_p-upstream
I hope it help us to come closer to an LineageOS 17 for suzuran.

I_did_it_just_tmrrow said:
I ask him if he could help us a little bit and the first result is this.
Click to expand...
Click to collapse
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...

Berni-0815 said:
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Click to expand...
Click to collapse
Yep, just try his source. He told that it could be useful to test this kernel with building twrp first.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg

I_did_it_just_tmrrow said:
Yep, just try his source.
Click to expand...
Click to collapse
I'm actually building a rom with that kernel. I'll see later if it's working.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
Click to expand...
Click to collapse
Right
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
Click to expand...
Click to collapse
Ah! Nice. I'll try it later. Thank you very much! :good:

Berni-0815 said:
I'm actually building a rom with that kernel. I'll see later if it's working.
Right
Ah! Nice. I'll try it later. Thank you very much! :good:
Click to expand...
Click to collapse
Let me know how it goes, I'm more than certain kernel is what's preventing us from getting Pie/Q to boot up.