yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] swTkepoe:
Quick question, i received the htc desire S yesterday and i instantly tried rooting it, since it still has the default htc sense rom android 2.3.5 .

The thing is i always get redirected to revolutionary.io but this site does not have the tool up anymore to root this device.

Does any of you have this tool and if possible can you share it? :)

Thanks in advance!
[HTC Desire S] kchaisu:
I had rooted my HTC Desire S for a long time ago using revolutionary.io. I guess you already have unlocked your device bootloader. Currently, there is Chainfire Systemless root (Beta SuperSU 2.67) which allows to root without modifying system and also Flashfire app to flash it. However, I have never tried them with the unroot device since my Saga have been rooted for a long time as mentioned earlier. You might google the items what I have mentioned; so might get some idea about rooting. Thanks.

I am sorry FlashFire by Chainfire is for Rooted device.
[HTC Desire S] kylon:
http://www.htcdev.com/bootloader

Here is the official unlock tool

Not sure what restrictions it has
[HTC Desire S] DynaMight:
If I remember correctly the biggest drawback from the official unlock method was needing to manually flash the boot.img through fastboot. As long as you extracted the boot.img from the update.zip file and flash manually it was fine.
[HTC Desire S] Mustaavalkosta:
Yep, you are correct. Before they fixed it for the newer devices unlocking via htcdev pretty much left you crippled with custom ROMs. Sadly, they never extended the better unlock support to older devices.

https://plus.google.com/u/0/103583939320326217147/posts/P1i8qzLfkTm

http://rootzwiki.com/news/no-need-for-s-off-htcdev-unlock-does-the-job-on-htc-one/
[HTC Desire S] TiceRex:
First of all: thank you very much for keeping my Saga alive!

A question: I've used cm-12.1 for some months, and now I tried to flash cm-13. However, after a (seeemingly) successful installation the phone still says it's cm-12.1.

What could be wrong? Could you please help me?

edit:

OK, after several attempts cm13 has booted up successfully. :)
[HTC Desire S] Sefy:
I Just did a wipe and re-install of the latest Sagaopt 22/02/2016 and i'm not sure if anyone else noticed but installations are MUCH quicker, the system itself responds much faster and i've experienced less Sluggish times compared to the previous build I was on (16/02/2016) and the only thing that I currently see that isn't working properly is the Bluetooth, whenever I try to connect to another device, it just turns off and then on again... and loops till I stop it manually...

Oh and still couldn't install SuperSU properly (even latest 2.67 beta).
[HTC Desire S] paradice55:
First of all i really appreciate what you guys are doing here but i had a few "bugs". First of all the system is not really smooth at some point. The second is that the AOSP error is constantly showing up. Besides that it is a really eyecandy rom and hope that you guys continue to make this nightlies a stable rom.

edit: I forgot to mention that i cannot get SU on my phone. I don't know it has to do with the rom or TWRP. Has anyone the same problem as me?
[HTC Desire S] ralfbergs:
What is "the AOSP error?" Can you please be a bit more specific?

Besides that it is a really eyecandy rom and hope that you guys continue to make this nightlies a stable rom.

You mean you cannot obtain root privileges? Did you enable "root" in the developer options? If not please tap seven times on build number...
[HTC Desire S] paradice55:
Thanks for the reply bro. By aosp error i mean the one with "Unfortunately, Android Keyboard(AOSP) has stopped". İts constantly showing up.

And with the rooting.. İ have found something on settings/developer options and then root access. Do i need to set that one to "apps and adb"?
[HTC Desire S] ralfbergs:
The fix for this seems to be to delete the following file (from "adb shell" or recovery):

root@sagaopt:/system/lib # ls -la /system/lib/libjni_latinime.so
-rw-r--r-- 1 root root 927328 2008-08-01 14:00 /system/lib/libjni_latinime.so

That depends on what you want to do. If you want to install apps that need "root," you need to obviously enable root (at least) for apps. If you want to use "root" on the command-line thru "adb shell," then you need to enable (at least) adb. You can also enable both if you want to use both methods.
[HTC Desire S] paradice55:
Alright i am in recovery now and looking in to file manager, in the system map.. But it is empty? Also looked in a map called "sbin" but that specific file wasn't there.

Did i do something wrong when installing or did i install the wrong rom?

Edit: i installed the "cm-13.0-20160222-UNOFFİCİAL-sagaopt.zip" and "open-gapps-arm-6.0-micro-20160222.zip
[HTC Desire S] ralfbergs:
You need to mount /system first -- in the menu root there is a button "Mount" where you can mount /system, make sure you allow read/write there as well...
[HTC Desire S] paradice55:
Thanks m8 i found the file and deleted it but i still get the same error message of AOSP. Do you know something else i could try?
[HTC Desire S] ralfbergs:
you could try to install Google Keyboard.
[HTC Desire S] paradice55:
Tried the 23 februari rom but still get the aosp error
[HTC Desire S] kchaisu:
I am wondering if you have made the installation correctly. There are two posts on how to install CM-13 and Gapps on post #25 and Post #30 on this forum. You might be interested in taking a look at them. This might be possibly solved your problem. I am sorry, I do not know how to post the link. Thanks.
[HTC Desire S] Lapyyyyyy:
Guys, hi!

Only I have two bugs in this awesome ROM?.. 1. Photo doesn't save; 2. Can't download anything.

Cheers
[HTC Desire S] kchaisu:
Actually, I also have problem with stock browser on downloading. However, when the first download fail, just delete it and repeat it. Then the second time, the downloading will be successful. It is funny though. Thanks.
[HTC Desire S] paradice55:
I followed the install instruction on the homescreen. I tried the instruction on #25 and finally i don't get any error messages. Thanks m8
[HTC Desire S] paradice55:
Does it take long to get a stable rom?
[HTC Desire S] i23098:
Soon... http://www.xda-developers.com/xda-external-link/first-cm13-snapshots-coming-soon/

And after CM13 itself is stable, it doesn't mean that it is stable on unsupported devices. A little longer then... but from the comments, shouldn't be too long :)
[HTC Desire S] mithe:
Just flashed from 20160222 to 20160226 and the ROM runs very fast for the old device.

Camera starts more stabel from lock screen.

There is still flickering 1/4 to 2/3 of the screen, especially on lock screen. I got the feeling it is caused by the keyboard.

The calendar app runs much more reliable. I did not experience the bugs from one month ago.

The Phone app takes a moment to start. Also when I get called.

As expected from the changelogs there is still no change in bluetooth, it crashes everytime while establishing a connection.

Great work! I cannot keep up with all the nightly versions.
[HTC Desire S] Sefy:
Just flashed build 0228 over 0224, everything seems to be a bit faster which is nice, but i found something strange with the battery charging.

I left it to charge all night from 0% and in the morning (7 hours later) it says 10 more hours and charge was just about 33%

After rebooting the phone, it went up to 95%

Is this a known issue?
[HTC Desire S] ralfbergs:
Sounds as if there was a process hogging the CPU, and reboot cleared it. Observe it, maybe there's something wrong with your setup. You could install Better Battery Stats (free to download here from these forums, google it!) to see what's wrong...
[HTC Desire S] Mustaavalkosta:
Sounds like typical dying battery to me unless you have brand new high quality battery.
[HTC Desire S] Sefy:
While the battery certainly is far from new, i've not seen this issue occur before now...
[HTC Desire S] ralfbergs:
SELinux "permissive"

Hi [MENTION=3382363]Mustaavalkosta[/MENTION], [MENTION=3334728]kylon[/MENTION].

Is there any plans to work on switching to "strict" SELinux mode?

Don't get me wrong, it is amazing what you guys did to bring the latest, greatest Android to our good ole' Saga, but this would be what we call in German "the dot on the 'i'", i. e. the last missing thing that makes something perfect.

Best,

Ralf
[HTC Desire S] Mustaavalkosta:
Yeah, it has been on the to-do list since 12.0 but not on very high priority. I don't currently know anything about writing SELinux policies and without a working set of those we can't really enforce SELinux without breaking everything that doesn't work based on generic policies. I suppose for kylon (if he knows his way around writing SE policies) this is a bit difficult to fix too because he doesn't have a device to see SELinux denials. It might be doable with craploads of community help and logs but still it's a kind of dreadful way of fixing the SELinux situation.

All in all, might happen, might not happen. It depends how many other critical issues pop up before I manage to get to figuring out how SE policies work. Currently I'm trying to find a way to get my car back 400km away from home where it broke down while returning from visiting family. No brain cycles available for ODP problems until that situation is dealt with. :(
[HTC Desire S] ralfbergs:
Minor issue w/ internal flash?

Hi [MENTION=3382363]Mustaavalkosta[/MENTION].

Can you please have a look at this kernel log snippet? This was taken on 2016-03-02.

The i/o errors and "Emergency Remount" seem worrying...

Also, why does it seem to try to mount /system r/w? I thought it should be mounted r/o right away from the beginning? But the r/o status here seems to be only due to the emergency r/o remount?

Kind regards,

Ralf

PS: The strange screen flickering in the lower half of the screen that someone mentioned is still present.
[HTC Desire S] Mustaavalkosta:
There's no erase function (they have even removed the code inside it instead of commenting it out or returning early) in HTC's kernel and I suppose only HTC knows why. It does exist in CAF kernel. Sadly that leaks out as I/O error because erase operation can't be performed.

https://github.com/OpenDesireProjec...30/blob/cm-13.0/drivers/mmc/core/core.c#L1397

https://us.codeaurora.org/cgit/quic/la/kernel/msm/tree/drivers/mmc/core/core.c?h=ics_chocolate#n1430

I guess this cherry-pick can be reverted and the errors will be gone but I don't think much changes in terms of functionality.

https://github.com/OpenDesireProjec...mmit/168e221387f3640697d7dea247c03104dcfbd6af

I don't remember why I even picked it up. It probably came in as a batch with other cherry-picks.

I don't see any lines saying that partition is actually mounted as read-write in that log. That emergency remount can occur even if partition is already mounted as read-only, can't it? I don't know but that sounds very plausible to me. Our fstab certainly has it as read-only. :)

https://github.com/OpenDesireProject/android_device_htc_aceopt/blob/cm-13.0/rootdir/fstab.htc7x30#L8
[HTC Desire S] ralfbergs:
I'm not in a position to comment on whether this would be a risk to the integrity of the flash, but for sure I would appreciate any error messages to be gone, especially if they don't really constitute a problem and are even expected...

You're absolutely right. It was my interpretation, and I was wrong...

Thanks for looking into this and commenting...
[HTC Desire S] Mustaavalkosta:
Yeah, I agree that errors that shouldn't be there really shouldn't be there. I mainly meant to say that this is nothing that requires immediate action to prevent data corruption etc.. I'll likely revert that commit when I next time open the kernel source for something. I was aware of the missing erase functionality and actually also aware of those I/O errors too but since the errors didn't seem fatal and I had more pressing matters to deal with at that time I never connected these two things together until now so it's good that you asked about it.
[HTC Desire S] ralfbergs:
Thanks a lot. Good to know there's no risk of corruption...
[HTC Desire S] kchaisu:
Thanks Mustaavalkosta for your kind contribution. CM-13-20160304-sagaopt is the first build that provides smooth set up without any modification to make AOSP keyboard function normally.
[HTC Desire S] kchaisu:
Thanks Mustaavalkosta for your kind contribution to the DS community as well as DHD community. I am very appreciated your kind commitment. I hope you enjoy your new job. Currently, I am getting to the point of less interesting in Android ROM and apps development. Since I rooted my HTC Desire S three years ago, I have been participated in this community for most of the days. I have been decided that whenever my DS was broken I would buy a new phone. However, my phone is still looked new and has never betrayed me at all. Thanks for your time and hope your have good health and prosperity.
[HTC Desire S] kchaisu:
I flashed the latest CM-13-sagaopt build with two latest Gapps, Open Gapps and Delta Gapps and found out that while Open Gapps provides normal bootup and setup without deleting or renaming system/lib/libjni_latinimegoole.so file; on the other hand, Delta Gapps needs deleting or renaming system/lib/libjni_latinimegoole.so file for normal bootup and setup otherwise AOSP keyboard will be FC. That means AOSP keyboard FC is a Gapps issue. Thanks.
[HTC Desire S] paradice55:
Hey devs..

Is the 7 march update the final update? You have'nt updated it since then so i wanted to ask. Have'nt tried the last update tho
[HTC Desire S] Mustaavalkosta:
Nightlies are automated builds thus if upstream breaks something they will fail without anyone monitoring it. I have logs on the build server though. At least new maven requirement on host OS broke it and then they broke toybox compilation but I don't know what's still broken.
[HTC Desire S] TheArt:
Hi

I installed this rom, all fine but when I reset the phone appears Encryption unsuccessful and button Reset phone. What i do wrong and how fix it.
[HTC Desire S] Mustaavalkosta:
You have done the partition conversion to opt partition layout somehow wrong. Go through the instructions again.
[HTC Desire S] i23098:
New build is up :D 118k changelog

I'm still on 12.1 but maybe it starts to be time to move... People using 13.0, is this stable enough now for a daily usage :confused:

Thanks Mustaavalkosta and all other developers for the great work :highfive:
[HTC Desire S] paradice55:
Thx for the reminder m8. Gonna install it anytime soon.
[HTC Desire S] kchaisu:
Hi Mustaavalkosta,

I tried to flash CM-13-20160317- unofficial-sagaopt build without success. I did not boot up. I just got black screen. The test was based on clean installation both with and without gapps. Thanks for your kind contribution.
[HTC Desire S] dimeb:
I also tried to upgrade to CM-13-20160317- unofficial-sagaopt. I did not boot up. I just got black screen. logcat httр://logcat.scheffsblend. com/view?id=28719298
[HTC Desire S] Mustaavalkosta:
Thanks! You just solved the issue by providing a log.

03-18 23:31:04.853 E/libEGL ( 1659): load_driver(/vendor/lib/egl/libGLESv2_adreno.so): dlopen failed: library "libstlport.so" not found

Display driver won't load thus the black screen.

Edit: You can snatch libstlport.so from the earlier build and push it to /system/lib/libstlport.so and the recent builds should boot up. Or wait for the next build where it's likely fixed if I don't fall asleep before pushing a fix to github.
[HTC Desire S] kchaisu:
Thanks Mustaavalkosta for your kind support. According to your explanation that mean the booting is processing, but the display could not show up. I left the booting for half an hour but got only black screen. Thank you very much.
[HTC Desire S] Mustaavalkosta:
Well, when it can't load display drivers that leads to various other processes crashing and it won't go very far with the boot up process. That library loading error I mentioned was only the beginning of issues. Also you wouldn't get anything on the screen even if the boot up finished due to the part of the system that would take care of handling delivering any images to the screen being "broken". :)
[HTC Desire S] kchaisu:
Thank you very much Mustaavalkosta for the explanation. As you mentioned, I managed to get the system booted up now. It is just the file you have mentioned is missing. Just copy to the system/lib an all is working now. Again thank you very much.
[HTC Desire S] :
Why still in old ROM?

HI guys, I tried to follow the guide for first install what was kinda complicated due to the fact that I could not get any connection of my phone to Win10 (Error: Device Enumarator not working, device not recognized). So Altough I installed drivers, ADB and all stuff I founbd no luck via Fastboot.

Finally I manaded to exchange my 4ext recovery by a very new one, and could create a zip file with the TWRP2.8.7.1 that I could install from 4ext. So recovery (seems) to work now.

I did wipe chache, System, data, sdcard (I have no ext SD mounted altough i installd a µSD card, no chance to mount it. It's shown as sdcard in filemanager).

The I installed latest cm13.zip, latest gapps (open for arm 6.0). All shown as successful in TWRP.

After reboot, im back in my old PACMAN 4.2.2 ROM. ???? No CM13.

ANy idea what I forgot? I tried to reformat as mentioned in the OP (resp. on post 2) but not sure if that really worked. i also did not really understand the re-partitioning part, as I found no real hint on if and how to repartition.

Can anyone help?

Thanks, GeScha

Phone Data:

SAGA PVT SHIP S-ON RL

HBOOT-2.00.0002

Radio-3822.10.08.04_M

eMMC-boot

Aug 22 2011,15 15:22.13

TWRP v2.8.7.1
[HTC Desire S] paradice55:
Did you flash boot.img of the latest rom? If not, try that and reboot again. If you don't know the command etc. It is shown on the first page of this thread.
[HTC Desire S] :
Damn, thanks a lot, that's what I've overseen as I was reading throught the "first install" only.

Any idea how I can get fastboot working if my device is not recognized by Windows at all?

I know I did it once when installing 4ext and PACman ROM, but there I still was on Win7.

Any hint, I searched around google and xda quite some time, but could never fix the connection for fastboot. There for I was quite happy to find a way to install the TWRP via PG88IMG.zip.....
[HTC Desire S] ChristianFerrer:
I use win10. fastboot and adb works perfectly. Have you tried this? http://xdaforums.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
[HTC Desire S] :
You're the man, DB drivers now work. On Win10 actually only the registry entry needs to be inserted, the hotfix pakage from Microsoft is not needed at all.

Now I restart :) installing both zip files (CM13, gapps) from TWRP, then install the boot.img from cm13 zip file seperatly via fastboot. Fingers crossed....
[HTC Desire S] ChristianFerrer:
That was also the fix to my problem when I upgraded to win10. Im glad it worked.
[HTC Desire S] :
Problem now is, that I can connect, can flash via TWRP....I did flash the cm13&Gapps zip, flashed boot.img...now th following happens:

Phone boots up to the white splash screen with green htc logo. Then screen turns to black and - as fas as I can see - nothing happens any more. I also can't reboot, swithc on or off (actually I do not know if its on or off) no led (with or without cable) - nothing. Till I take out battery, then I can try swithc off again => splash screen - black (and nothing else)

or

Boot into recovery or bootloader.

What did I do wrong?
[HTC Desire S] ChristianFerrer:
What build are you trying to install? The 20160317 build has got some trouble. You need to download the latest build.
[HTC Desire S] :
SUCCESS!!!

Not sure if it was the 17th nightly, but now I installed the 19th nightly and SUCCESS, it boots.

Additionally I did redo all wipe and formated SDCARD from ext4 fo f2fs. And I skipped GApps install for first try, not it bootet. Wos MM on Desire S....

Thanks for all your help, really great!

Only thing left to try is reinstall with GApps....will report.
[HTC Desire S] :
Reinstalled both zips (cm13 & gapps) wipe cache & data. Now it really works. Thanks a loz!

Gesendet von meinem D5803 mit Tapatalk
[HTC Desire S] ChristianFerrer:
I am experiencing a problem with my Wi-Fi with the ROM. I am connected to the network but it keeps on disconnecting and connecting again. I dont know what seems to be the problem. I'm sure it's not my Wi-Fi because I can use it perfectly in my PC without any problem. Anyone?
[HTC Desire S] paradice55:
Do the proces for new installations on the first screen of this thread.
[HTC Desire S] ChristianFerrer:
I did. Still the same problem. I've tried factory resetting, flashing it again. Revert back to my 4.2 ROM and tried the process for this ROM again. I've searched around google and found that Im not the only one with that problem. I think it's a problem with my Radio. Anyone who uses the ROM, please tell me your BaseBand Version. Think it might be the problem because I've flashed custom Radio. Mine is 20.76.30 .0835U_3831.19.00.110
[HTC Desire S] kchaisu:
I have the same baseband as yours. I could not notice the problem.

Sometime when I used L Speed apps I face a problem with WiFi connection and found that it was a Busybox issue. So flashed [MENTION=1143630]osmosis[/MENTION] Busybox, the problem was gone but Stericson Busybox from play store the problem was still intermittently occurred. Thanks.

---------- Post added at 06:21 AM ---------- Previous post was at 06:16 AM ----------

As you might have learned that CM-13 applied Toybox, some apps still use Busybox BTW the transition and Toybox has not yet provided with full command applets.
[HTC Desire S] ChristianFerrer:
I have not fully set up the phone with this ROM. I have not signed google acct. yet because of the WiFi problem. I thought the problem was related to the BaseBand. I am still trying to figure out what the trouble really is. I like this ROM because of it's speed compared to CM12.1 .
[HTC Desire S] JerseyChewi:
Upgraded from CM12.1 yesterday. First impressions are great! I was doubtful about whether it could really be any faster but it definitely is, at least a little. I don't know for sure yet but it looks as though the irritating WebView bug has gone away, which is great news. Just one fly in the ointment…

I'm seeing the same issues with Bluetooth that others have been reporting. Unable to pair with my headphones, rapidly switches on and off, and crashes with Unfortunately, Bluetooth Share has stopped. I wish I'd known about this because it's a bit of a deal breaker for me. Downgrading doesn't bear thinking about either though. I'll see what I can find out but I'm not too hopeful. Here's the interesting part of the logcat.

---------- Post added at 10:06 PM ---------- Previous post was at 09:14 PM ----------

I've had a dig around. The error occurs in android_system_bt's controller.c. The last change to this file involved BLE and this change was probably made after CM12.1. If I had to guess, I'd say that this part of the change (from line 187 to 199) should have been put inside an #if (BLE_INCLUDED == TRUE) block. In fact, there's one just below. What do you think? I very rarely build Android and I don't want to have to waste all that bandwidth and CPU time just to find out that I'm wrong. Are you able to give it a try?
[HTC Desire S] Mustaavalkosta:
Yeah, it seems possible that BLE stuff is leaking due to missing ifdefs. We are not defining BLE_INCLUDED anywhere but I don't know on top of my head what's the default for it these days. I try to take a look into this ASAP. Work that pays bills has taken most of my time for the past weeks. :/