yashsingh1/xdaforums huggingface dataset:
[HTC One X] teemo:
You mean that we can't control it properly?

If it works on Sense, then it's not hardware.
[HTC One X] vbaros:
That's what I can't remember [emoji4]

Do you have those problems on SlimKat?
[HTC One X] teemo:
Yes.

Photo sphere acts funny. Picture are moving even though you hold HOX still. Looks like a hardware issue, but then it should be the same on Sense.

Panorama works great. 360 degree with no problems.
[HTC One X] Thömy:
It could be that we're missing some sort of sensor calibration that compensates for the drift.

Some time ago I tried to figure out what Sense does. Because I remember that Sense ROMs have some kind of calibration functionality in the settings where you have to move your phone in an 8 pattern. What I could discover was that the /system/bin/bma150_usr binary is executed by the G-Sensor calibration GUI. It does some things. Reads and creates files. But the sensors behaved as bad as before. I probably missed something or the sensors on our device are just not accurate enough for Photosphere.
[HTC One X] teemo:
Some apps have gyro and accellerometer swapped as far as I can tell. Might be a clue, but how it can happen I don't know...

Or maybe its swapped in my understanding?
[HTC One X] milomak:
not sure why, but the gps was all over the place for me this weekend. losing gps. not being able to locate where my current position is (stating i am in another place).
[HTC One X] okle100:
Link not working

The link on the first page says folder not found on one.com

Can you please update/reupload ?
[HTC One X] teemo:
Thanks for notifying. My provider "updated" the links. I fixed it in the first post. Second post will be updated later.
[HTC One X] M@c|-|oR:
[MENTION=698346]teemo[/MENTION], do you have any insights how is Slim team doing with Lollipop?

Do you think it wold be possible porting it to HOX, as you are doing with KK?
[HTC One X] teemo:
I made a build 11 days ago. It works, but have the same problems as cm12. Main problems are no reliable internet or normal phone functionality.

Slim ROM is very basic and really no fun without internet. WiFi works though.

Lollipop is much more picky about getting ID data from the SIM card than previous releases. That is a problem for many old phones, that use a different method to read the SIM card.

I use Thömys sources. Its all his work :thumbup::thumbup::thumbup:

Edit: SlimLP status

https://plus.google.com/106433967005195000488/posts/ExeKkcDi2Fi
[HTC One X] yossi2010:
oh finally someone who starts this up.

it is not an hardware problem but a software one.

gyro recalibrates itself whenever there is a constant(almost constant) value on one of its axis.

so when you put your phone stable it will work perfectly fine but when you start moving around and you move in one direction for about 2 secs in the same speed(which is typical for photosphere gaming or VR) it will recalibrate and stop moving , once you stop moving it will move to the other direction at the same speed aka looking like it moves when the phone is still.

now if you continue working with the gyro you get an annoying drift but if you keep it still for 2-3 secs it will recalibrate again.

problem? recalibration everytime movement is constant(or zero).

solution: make an assisting app that will keep your phone in a constant callibration.

if someone does it he gets a thousand thanks.

---------- Post added at 07:59 AM ---------- Previous post was at 07:56 AM ----------

software.

---------- Post added at 08:04 AM ---------- Previous post was at 07:59 AM ----------

all you gotta do is stop the device from recalibrating everytime there is a constant movement(current behaviour)

to a more constant calibration method(put your device down on a table press calibrate and gyro knows its real zero)

this 8 figure calibration is for the compass i think(the iphone has it too)
[HTC One X] M@c|-|oR:
Update:

it looks like [MENTION=4865888]statmonkey[/MENTION] is about to solve his problem, and join the magic of SlimKAT :)

Good luck, mate!
[HTC One X] jefferson_uk:
Does anyone know if the speaker dock accessory works with slimkat? Dock mode works but no audio out on CM11. Not sure if its a CM issue or kernel/driver problem.
[HTC One X] statmonkey:
How I got here is all thanks to you. Really would have given up but for your advice. Unfortunately I think I have hit a MAJOR dead end. I got this device quite a while ago in Thailand and it since it was unbranded there doesn't seem to be anyway to upgrade the hboot or an OTA I can load. I have been looking all over the relavant info is this:

bootloader 0.95.000 (everything I have seen needs at least 1.54 with 1.12 the lowest I have seen even mentioned)

version-main 1.29.401.11 (this does not seem to be an issue)

realcid H_Y13

Model PJ4610000 (again everything I see is in the 80's at least)

This is related to slimkat in that without a higher bootloader the install process won't work. I had hoped that in the nandroid restore process my hboot would be updated. Alas no such luck. Anyone with any ideas?

Thanks, I was really looking forward to joining the slimkat community by the way :)
[HTC One X] teemo:
Okay, give it one more chance.

We don't have much action here in the KitKat threads, so let's write a few more posts to get you going.

First step, download the CWM recovery and my HTC__Y13 backup from here.

Unlock your HOX - make sure it say ****UNLOCKED **** on hboot/fastboot screen.

Go to hboot screen and enter FASTBOOT menu. I should say FASTBOOT USB

Check that fastboot is working, this will answer with serial number:

fastboot devices

Enter this from PC

fastboot flash recovery recovery-5840-hox.img

Make sure it does not give an error.

Disconnect usb cable. Use menu to get into recovery.

Go to Mounts and Storage and Mount USB Storage

Connect cable to PC again.

If Windows doesn't recognize the device, open windows Device Manager and Uninstall the problem driver (yellow triangle with "!"). If there is a google adb device, uninstall this as well (dont delete from drive).

Disconnect USB cable. Go to recovery advanced menu and reboot recovery. Connect USB cable and go to Mounts and Storage and Mount USB Storage again.

Wait at least one minute for Windows to find drivers for the usb drive.

Copy the HTC__Y13 nandroid to sdcard:\clockworkmod\backup\2013-01-01.00.00.00\

It should look like this:

boot.img

recovery.img

nandroid.md5

cache.ext4.tar

data.ext4.tar

system.ext4.tar

Now, reboot recovery. From the Mount menu: Format /system, /data and /cache.

Restore the backup. Reboot.

So far the above works for me. I am booted up with the superold firmware from HTC. And this is as far as I can go as the old touch driver does not work on a new HBOOT (1.72).

From this point, if you get this far, all you have to do is to let your HOX update to latest and greatest Sense for HOX.

Once you have the hboot up to 1.3X+ you can start over from post one.

Edit1: If your phone won't download the update, let's see if we can find it somewhere. It's just a file, I may have it on an old harddrive at home. Will check.

Edit2: Flash the recovery in the Nandroid after the Nandroid has been successfully flashed. Updates will only work with HTC recovery.

Edit3: There are RUUs, get RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
[HTC One X] statmonkey:
apologize for long post but ...

Great post thank you.

Did I sound pathetic or what in my last post? Didn't mean to, just tired and frustrated (no excuse I know)

Here are my notes. To save time I am at a place where I can boot but the way I did it my hboot is still at .95. It is downloading an OTA now and I will try to finish this way before trying the files you have suggested. I have them downloaded and since I have been in this far think I should try and finish. Having been through the process you describe starting over doesn't scare me anymore.

My process.

Stuck in boot loop. Device would not charge, would only when on usb go to hboot screen.

Step One - Install CWM 5.8.4.0

In terminal run:

fastboot erase cache

redid the unlock from HTC site just follow steps (it said unlocked but I had relocked it once before and wanted to make sure it was really done) it failed due to battery low so erased cache again and reran unlock

check battery with

fastboot getvar battery-voltage

unlock worked

downloaded 5.8.4.0 from http://xdaforums.com/show...5#post24738635

renamed it to something easy

fastboot flash recovery newname.img

presto. Am proceeding to next step.

Step 2 flash nandroid

downloaded the nandroid for Y13 from http://xdaforums.com/showthread.php?t=1975140 and unzipped it into a folder which I renamed Y13

ran

flashboot flash boot boot.img

it failed due to low battery. Moved the phone into recovery which seems to allow the battery to charge. Waited, moved to hboot - fastboot usb and ran again. Worked.

Opened recovery copied the folder I downloaded above into the clockwork/backups/ folder and renamed the folder to a shorter name.

Used recovery to flash this backup and it failed due to md5 mismatch issue.

Followed these steps:

Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:

adb shell

this will get you to the phone's terminal

if you have # at the end of the line, you are good to go, if not, then type su

The syntaxes needed:

Quote:

cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data

md5sum *img > nandroid.md5

This will make an md5 image with the name that cwm acknowledges.

From this thread http://xdaforums.com/showthread.php?t=1835914

Reran restore in recovery and it worked. Now I have a working device at least.

Now booted into normal phone. Ran manual update and waiting. Battery low again so will wait an hour and try again. Will post results on whether this works or moving to your method shortly.

Again, thanks for the support and sorry for my ineptitude.
[HTC One X] teemo:
I found two old ota updates on my old disk. Just let me know if you want it.

The HTC__Y13 I uploaded to the nandroid thread gives a checksum error because one file is missing. I think it can be flashed if using advanced restore from cwm. Anyway, I fixed it and uploaded it in my previous post here ^^
[HTC One X] statmonkey:
Thanks I may need the OTA's. As I said I went ahead and tried with the way I was going and kept getting the assert error on the OTA I downloaded. Despite my fiddling with the update script as suggested elsewhere it continues to fail. I think that there is little diff between your path and the one I was on but .... I switched to yours, started over and am now downloading the update for that setup. I will try again when it completes. If it fails I will probably post back in here for suggestions or help if that is alright. Hard to believe how I have mucked this all up but after all this work would really like to see it through. Keep repeating ... the journey is half the fun, the journey is half the fun, the journey ....:cool:

OK both the stuff you have given me and the way I was going lead to the same place. That is the OTA upgrade failing by assert error status 7. I followed the steps here http://xdaforums.com/showthread.php?t=1632662&page=5

Which results in just a simple "installation aborted" after it says installing update. Hboot remains stubbornly on .95 So close and yet so far.

Any ideas out there? I am looking for an in between OTA since I just want to get to first at this point and will work my way past the next hurdle when I get to it.
[HTC One X] teemo:
Lol sounds like you have lots of fun. The link you found will only flash system. You need a new hboot, but that will not be updated.

One important thing. When you update you must use HTC recovery.

Do you get the update from HTC when Sense is installed ? If so, there is no need to mess with custom stuff. Just go to software updates in settings and let it update. I will find the correct recovery for you and update this post when I get near a pc. Don't mess with custom stuff, not needed.

Edit: Link to htc-recovery added.

BTW, this recovery will WIPE YOUR SDCARD :P I just lost mine lol. Thank god I had a backup from yesterday :D
[HTC One X] Thant:
Why you just don't run the RUU 1.29.401.11 or try to run RUU 1.29.401.12. Are your phone say Edeavoru PVT or Endeavoru XE. Dont forget to reloack bootloader before run the RUU and charge your phone to full before run the RRU. After the RRU you will be complete stock and you will update your phone to latest base
[HTC One X] teemo:
Cool, I was waiting for you to drop by :D, it is too long since I did any of this. I just let the system update by itself. No need to do anything fancy.

Can the later RUU 4.5 or 5 be used or does he need to to go all the way back to ics?

He is on nordic Y13, same as mine.
[HTC One X] statmonkey:
Yep, the Nordic. I should have mentioned before I am a 'nix guy so running the RUU is a bit problematic I think those are built for Win. I do have access to a Win box hmmm. The things we do for phones. LOL

Thanks for taking the time guys, appreciate the help. Teemo, that is what I am doing. I don't care about the stuff on the phone this is a backup device that I really just use for when I am overseas. To be clear all I did once I got the phone back up was download the software update manually and try to install it using recovery. This fails with the assert error described above. I have to believe that there is some way to get that to work and remain convinced that the issue has to do with jumping from hboot .95 to what it wants to install which is OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985n1wwcwzs385c0bvz FWIW yes this is PVT with S On. I think I am going to do some more research on the assert error, look a little more for an in between OTA and if that fails try to set up a win box and see if I can get the RUU to work. I haven't looked at Windows since 3.1 so that should be an experience.

Again, thanks for the help and consideration. I am open to any and all suggestions. I dread the Windows Experience!
[HTC One X] teemo:
Well if you can't do the RUU, then your best shot will by HTC auto update. That is, revert to ICS and Flash the HTC-Recovery. Ask Sense 4 to do the update, either by downloading or by placing an OTA on sdcard. I don't remember where to place it and how it works, there are guides for that :P

Have fun!
[HTC One X] statmonkey:
Thanks hadnt really understood what you meant before. Lots of ways to skin the cat i guess. Will try that one next.
[HTC One X] Thant:
No the same or the next one or will give error because on some hboot update want exactly and specific hboot. He can scipe some but not on ICS. But for 2 hours will update the phone complete over wi-fi

---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------

have something specific for hboot 0.95 but I don't remember where I read for this
[HTC One X] statmonkey:
That is what i remember too, I think I mentioned that way back when (11./22 I think) but sure can find nothing referencing hboot .95 anywhere. So are you saying that even trying the RUU method won't work? Sounds grim.
[HTC One X] teemo:
Can you paste your vars here, just to check if something is wrong or superspecial (just delete emei and serial). Here is mine:

tomas@P150HM:~ > [B]fastboot getvar all[/B]
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.401.2
(bootloader) serialno: HT23EWSECRET
(bootloader) imei: 35918804SECRET9
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) devpower: 84
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.870s
tomas@P150HM:~ >

There are many threads on 0.95 - just google HBOOT 0.95

Here is one.
[HTC One X] statmonkey:
---------- Post added at 07:29 AM ---------- Previous post was at 06:36 AM ----------

[/COLOR]

Maybe I am just looking for the wrong thing. I have been reading through many things on HBOOT .95 but apparently not found the one that works. Ill keep at it.

Aha, but that is a mistruth. I have been searching on HBOOT 0.95 but always as part of something like HBOOT 0.95 blah blah. Just started a search on just HBOOT 0.95 - well duh, lots of stuff there. Good tip, even though obvious. Never forget I am an idiot, always making it more complicated than it needs to be.

here as requested:

fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: None
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 4061mV
(bootloader) devpower: 93
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
[HTC One X] Thant:
the RUU method will work 100% but if you are with linux you need winbox
[HTC One X] statmonkey:
Good to know thank you.

Here at eureka.Iamadummy.com teemo has shone a light in my eyes and I think I can get around using windows. After slapping my forehead a few times I did a search on just HBOOT 0.95 and of course the first thread I saw was one that failed back when my phone was in the boot loop and the battery was too low. Following that process correctly this time I was able to get my HBOOT to 1.72! Big ups and thanks to all for taking the time (I will keep the RUU method in my back pocket) and am moving to re-installing recovery and then I believe I should be able to follow the steps on page 1 of this thread. I will update and have kept track of all the steps that I can post if anyone thinks its of value. Regardless I have a hop in my step today, I am hopeful my next post will be about how wonderful slimkat is. :laugh:
[HTC One X] Thant:
The RUU method will not work anymore for you you are on latest hboot and HTC not released RUU for this base. I hope you to not have problem with the tuch panel because in one of the hboot /I think 1.39/ have tp.img for update the tuch panel firmware:good:
[HTC One X] statmonkey:
Thank you to all who keep XDA alive and especially those who work to keep the HOX going. Specifically thanks to those in this thread who put up with me:

M@c|-|oR

teemo

Thant

You guys are awesome. No problems with the recovery or install.

A beautiful ROM is now running happily on my HTC One X. I can't stress enough how much help you have all been. All that was remaining was to reinstall the CWM recovery I had before and then follow the excellent first post in this thread. A bit anti-climatic after all the issues but happily so. If there is anyone who helped I have forgotten my apologies. Also as I said I have documented the whole process (leaving out of course my own misguided attempts) if it has value I can add it here. I think I will now go play with my new ROM. Long live SlimKat!
[HTC One X] M@c|-|oR:
[MENTION=4865888]statmonkey[/MENTION], you are welcome, mate. It is always a pleasure seeing someone with that much persistence and devotion :)

I hope you are equally devoted in other areas of your life (work, family) ;)

Still, it was you who did all the job. Our role was much easier - just giving you some ideas what to try. I can imagine the frustration you had during the process, but now you can enjoy all the benefits of your hard work :cool:

Not for long, hopefully, as I am looking forward at Lollipop build for HOX :good:

P.S. As for the process explanation, it would be a great idea that you open a new thread in Q&A, and help others, too. In the PM you mentioned a locked HBOOT, so I am also interested what the hell was wrong with your phone :) :confused:
[HTC One X] statmonkey:
Oooh Lollipop that woudl be sweet!

I opened a new thread and threw it in here http://xdaforums.com/htc-one-x/help/fixing-hboot-95-stuck-bootloop-charging-t2974556

The issues in short summary were these. I needed to get 5.8.4.0 on the phone so I could boot into recovery and get the phone to charge. Relock the phone. Then I needed to add the firmware to upgrade HBOOT as suggested by teemo. Then unlock and put the recovery back on it. Once that was done install the ROM according to teemo's steps on the first page. Easy-peasy. Like all things on this forum, there is almost too much information out there and too many ways to get there.
[HTC One X] M@c|-|oR:
[MENTION=698346]teemo[/MENTION], I am getting into no-flash crisis. :silly: :silly: :silly: :eek: :eek: :eek:

8.20 :confused: :confused:
[HTC One X] teemo:
LoL - will probably not happen for SlimKat. Only if there are hox changes. None till now :D

Typed from my SlimLP pre-alpha :p
[HTC One X] p70shooter:
I think they should have called it SlimPops :D How you liking lollipop? Have tried SlimPops on my g3 and it was nice.
[HTC One X] cappuccina:
haha I remember last year when I saw your new signature for Kitkat and I desperatly wanted to try it. :D

after a really long time without Slimkat (for whatever reason, I don't know:) ) I am back and installed latest version and it is really nice.

Very smooth, fast and responsive. No crashes or other issues, that I recognize on other roms. But you all know that of course. :p

I installed HK Theme Manager because I really need a bit theming there, I think that was the main reason for not using Slim. :angel:

I am too much used to change the look every now and then. And all those nice new CM themes are not compatible with HKTM.

But time is precious and if I have a nice working rom, I can live with the same theme for weeks :good:

THANKS teemo for still working on our lovely HOX. :good: :)

I might change battery and try to fix my weak wifi and also stick with it for longer.
[HTC One X] teemo:
Well well welcome back :)

Yeah I like custom stuff too. Want to make it "mine". One of the reasons I will never touch anything starting with "i".

Really hope SlimTeam, CM, AICP, Omni etc find ways to customize and still make it fast and simple. They did in the past, so I have great confidence in the future. It starts now.
[HTC One X] mja:
Me too - [MENTION=698346]teemo[/MENTION] please give us a little hope!
[HTC One X] teemo:
All I'm saying is that there is nothing more to do for SlimKat. All updates from SlimTeam its for other devices. Development has stopped.

Let's just say: SlimKat is dead, long live SlimLP!

World is moving forward.
[HTC One X] mja:
You shurely don't mean my late lovely iPaq ?...
[HTC One X] teemo:
iPaq and all the other PADs were awesome. But that was long before the evil i-thingies began to multiply, spread and darken the world.
[HTC One X] winesh:
Does version 8.12.2 contain ls notifications and network speed?
[HTC One X] teemo:
Lockscreen Notifications - Yes.

Battery Bar - No.

Network Speed - No.
[HTC One X] winesh:
Ahh to bad for the network speed :p
[HTC One X] anto12:
[MENTION=698346]teemo[/MENTION]

when would you release your build of SlimLP :D

thanks,
[HTC One X] p70shooter:
When it's ready.
[HTC One X] teemo:
At current state it is very basic. No customization. Not even for the capacitive buttons. They will do Back, Home, Recents.

I fixed a video issue yesterday, until then I had no video.

USB file transfer is not working. Only adb.

Everything else should be working. I have not tested NFC yet though.

If there is interest, I can upload the alpha.

Thömys CM is more complete, you might want to check that out. Also, Eyosen have a working LP for AICP, but I don't know the status.