yashsingh1/xdaforums huggingface dataset:
[HTC One X] teemo:
FLAWLESS

This is sooo cool. No flaws, once you get to know the procedure.

1 Flash KL-ZeusBeta4.img ( yes, I renamed it - don't like spaces in my img names :D )

2 Boot to recovery

3 Wipe everything except SDCARD

4 Install (from TWRP 2.7)

5 Select aromafm (I have the aromafm...zip at /sdcard/!ROM/zeus/)

6 Navigate to your ROM (mine is at /sdcard/!ROM/Slim/)

7 Pick the ROM & Select /data & boot.img

8 Select "Yes" to flash full ROM. Select no to restore ROM later - Press "Done", Press OK, Menu-Exit

9 !!!!!! Wipe cache/dalvik !!!!!!

Finally, if you flashed full ROM, just hit Reboot System.

If you have ROM to restore, go back to main menu and restore. Hit Reboot.

I tried this a few times flashing between AICP/Slim/CM (boot.img not campatible). It reboots briefly to HTC logo, then reboot again to Android. No flaws!

Thank you a 1000 times!
[HTC One X] Thant:
ok I have one stupid question what will happend if I try to flash latest lyapota kernel #23 and inside have 9 boot.img??? and the flashing modules is with aroma??? Yes I want to flash only boot.img the modules will be flashed separately from recovery with aroma installer to choice the UV and other options?

Never maind I think to put all boot.img in one folder and to choice from this folder:) it must to work in this case
[HTC One X] Thunder07:
If you Try to flash a kernel with multiple boot. Img you'll be prompted to choose one boot.img in aromaFM KL..

And while I haven't tested this... In theory you don't need to flash aroma separately...

Just choose yes to flash the zip in recovery and aroma would start.

Send From My HTC One X
[HTC One X] teemo:
Yes, I know. I am way to slow :D But all the reports said it was not flawless, so I did not bother before now. Btw I did not use the app, since everything I need can be done from recovery.
[HTC One X] blackbuffalo:
I ve flash lyapota #23 with aromaKLFlasher.

When you choose lyapota #23, in AromaFM with appear 9 boot.img for you choose. I don't know why but when choose Flash Location is sdcard, my phone can't boot up, I must manual press power button three or five time it must boot. But choose /data it boot 2 time and work perfect.

Thanks [MENTION=618483]Thunder07[/MENTION] for aromaKLFlasher! So cool tool
[HTC One X] Thant:
I thing this evening will have time to try that and will report later. THANKS for the great Flasher

EDIT: Perfect Just PERFECT I don't have word to say thank you

EDIT2: [MENTION=618483]Thunder07[/MENTION] it is possible to have issue with mount like disk drive the sd card? Like MTP work perfect but when I select disk drive the computer want to format my sd card it is recognized like disk drive but when I press on disk drive the computer want to format the sd card I installed the kernel on data if it have some difference? Thank you in advance
[HTC One X] Thunder07:
Glad To Here,

That's probably a kernel thing...

if your kernel doesn't support Disk Drive it wont mount it, thus you can't assess it...

so the PC things it needs to format it 1st, in order to open.

As far as i know, KL shouldnt have any impact on the main kernel, i could be wrong.
[HTC One X] Thant:
Befor flash KL-Zeus Beta4.img i have working disk drive and rom

Ok what I do: flash the KL-Zeus Beta4.img and go to recovery wipe cache and dalvik and flashed the Lyapota kernel#23 from new AromaFM-KL.zip like when I have working disk drive and rom. After this restart the phone on second restart boot in the rom. Everything work like before to flash the KL-Zeus Beta4.img except disk drive. Now I must to try something else maybe to flash the boot.img from kernel and kernel from recovery and to see if disk drive will work again will report after few minutes

EDIT: [MENTION=618483]Thunder07[/MENTION] now what I tested flashed the boot.img from lyapota #23 kernel and after this from recovery flashed the modules and the disk drive work like a charm.

Now I will try to flash again KL-Zeus Beta4.img and after this with aroma the kernel but I will install and the modules separate from recovery again

EDIT2: after flashing KL-Zeus Beta4.img no matter wath I do the disk drive not working and I am not sure the disk drive is in the main kernel or not, but one is sure:

1. boot.img from kernel and modules = working disk drive

2. KL-Zeus Beta4.img and install from AromaFM-KL kernel = disk drive not working

Now I will go to sleep here is 1Am and tomorrow I am must to work again. Thanks again for the great work.
[HTC One X] Thunder07:
Thanks for testing,

Ummmm... Not entirely sure what's to blame...

I'll try updating the kernel to use kitkat source (currently it's either JB or ICS :p) , hopefully that'll fix it.

Send From My HTC One X
[HTC One X] Thant:
Thanks I am on JB 4.2.2 but will be good to update the main img I will test when you release it :) and report.

The AromaFM-KL flasher work better then apk but this is my opinion:good:
[HTC One X] Thant:
[MENTION=618483]Thunder07[/MENTION] are you plan to update the KL-Zeus Beta4.img to latest sources any time soon?

Thanks in advance!
[HTC One X] Thunder07:
I finish exams a week from today,

Thats when Ill have a look at it.
[HTC One X] smeejaytee:
When you use this do you need kl.zeuz IMG of so which do I use for kitkat please this looks great
[HTC One X] Thunder07:
Its not magic... yet!!

you need to flash zeus for the 1st time.
[HTC One X] smeejaytee:
Thanks which boot.IMG do I need to flash for kk phrase

---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
[HTC One X] Thunder07:
One to rule them ALL!

I've only provided one which works with all of them.

I recommend you do a backup and read the instructions until they make sense.

And how did you manage to quote yourself into the same post :p

Send From My HTC One X
[HTC One X] smeejaytee:
No idea I thought i edited the post to say please

---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------

I get it now sorry but I used to use the app version such had different imgs for different versions of android it actually looks allot easier now
[HTC One X] kantry123:
Buddy whenever I flash boot img with modules

The phn boots but needed to be hard booted 3-5 times in a row

Any sol for that??

I know it's the prob that we needed to do fastboot erase cache

But how to fix this isue..as this cannot be performed on device

Also I tried wiping caches n dalvik in recovery

But all gave same results

Coz..my battery drains like 10-15% just for booting the phn..up bcz it gets. Stuck at HTC logo n we need to press the power button 10sec n then repeat until the phn boots second time

Any solution for that ??
[HTC One X] myheroduane:
+1
[HTC One X] paulh1978:
This is completely normal,it is a small price to pay to be able to flash a kernel outside of fastboot.
[HTC One X] kantry123:
I totally agree with u

But thunder007 said he might have found that issue..n can be fixed

So I asked him any sol

I don't wanna bother him much as he also does havee exams like mine r going on currently

Anywayz thanks for replying
[HTC One X] Thunder07:
I'm afraid bootloops and blackscreen are a separate issue.

bootloops (the phone boots until the htc screen and reboots in a loop) can be fixed by fastboot erase cache ... this one is potentially fixable.

Blackscreen (after the htc screen the screen goes black and stays like this) is fixed by few hard restarts... not entirely sure it can be fixed... but I will still have a look at the code and see what can be done, if any.
[HTC One X] Thant:
I I wait for the new release :fingers-crossed::o
[HTC One X] Thunder07:
Life has the tendency to go into overdrive after exams,

and I've got couple of things I need to sort out before I can resume working on this.
[HTC One X] Thant:
offcorse your life is more important. I just jouke I know you will do the job when you have time and I know this betther then others and I put a smiles in my previous post:silly::):good:
[HTC One X] teemo:
Kexec works great implemented in rom. Made a Kexec kernel for SlimKat. Boots directly to alternative kernel, without use of recovery.

There are two commits in my github.

https://github.com/teemodk/android_kernel_htc_endeavoru/commits/hbk

May/12 is the hardboot patch from Tasssadar (see OP). May/19 a small adjustment of memory.h

Kexec-tools compiled with files and patches from Tasssadars thread.

A simple script to launch a secondary kernel, based on Thunder07s script:

cmdline=$(cat /proc/cmdline)
kernel=$(cat /data/boot/kernel)
ramdisk=$(cat /data/boot/ramdisk)

cp kexec /data/local/tmp
cd /data/local/tmp/

echo KERNEL = $kernel > kexec.log
echo RAMDISK = $ramdisk >> kexec.log
echo ------------------ >> kexec.log
echo COMMAND LINE >> kexec.log
echo $cmdline >> kexec.log
echo . >> kexec.log
./kexec --load-hardboot "$kernel" --initrd="$ramdisk" --mem-min=0x82000000 --command-line="$cmdline"

echo ----------- start kexec for reboot ----------- >> kexec.log
./kexec -e

Still need ramdisk tuned with some logic to select the right kernel and copy/move modules. For now I can easily Kexec-boot to other kernel and get back to original with normal reboot. I start to smell multiboot [emoji1]
[HTC One X] Thunder07:
why did you use 0xBF200000 for the KEXEC_HB_PAGE_ADDR....

why would you copy the modules using the ramdisk...

you're only adding more work to yourself with out any real added benefit.

whats are you trying to do like?

also since you compiled a kitkat kernel.. can you confirm this problem... no matter what ramdisk you use,

Kexec will always use the currently loaded ramdisk as a base for the new kernel.

NVM fixed that.

Edit:

@ Everyone

So i had some free time (well... from 12PM to 2PM :p)

using the new kernel rebase, i managed to boot Modded TWRP recovery from MultiROM menu...

why is this important??

because the modded recovery is 10mb large, which is bigger than the device recovery partition...

so you cant flash it instead of the current recovery...

and also, that recovery is needed to flash secondary ROMs for multiboot.

Anyways, right now both the recovery and multiROM use /data for holding /system & /data partition of secondary ROM,

but due to the size of the /data partition this is pretty much useless,

so ill work on this 2morrow night to hopefully allow flashing a 2nd ROM onto the sdcard.
[HTC One X] teemo:
My iomem is much different from yours.

Many people like to experiment with kernels, there is a lot going on now. With Kexec implemented in the standard kernel (all kernels), we can swap directly from the rom. For now we need to dual or triple boot plus use recovery.

It was a simple experiment, sorry if it did not fit your plans.

Best regards and thanks for your work on this, much appreciated.
[HTC One X] Thunder07:
ummm...

you dont need recovery.. but the reason i use it is, because it's a safer option, if android fails to boot you can go to recovery and fix things,

i also have an android app if you haven't noticed.

Kexec is generally not enabled is most kernels for some reasons... and using stand Kexec can cause alot of problem,

since the kernel has to deal with booted hardware instead of initializing it, as is most of it's implementation.

you're free to experiment how you like, but im still trying to understand what extra did you add.

also did you have a look at my ramdisk??

i've kexec in the ramdisk itself, to avoid the copy, paste, exec... also this guarantees kexec bin will always be available.

your current implementation assumes the user has kexec and that he didn't just format his data partition.
[HTC One X] teemo:
I never said I had a finished product for the public. Would never release an experiment.

The whole point of this is, that I can boot easily from inside the rom with one kernel to a different kernel, without going through a special kernel with one or more extra boots. It simply reboot one time - and you run a different kernel.

I do know your app, its brilliant, but I want to Kexec directly from the ROM to save the additional boot, that doesn't even work everytime.

Still need lots of work and of course everything should be in the right place without need to copy.

The ramdisk change is for the case, that you have a crash. Then the default kernel will boot and you need the correct modules.

I actually did this, because I dont know how to debug the Kexec kernel (zeus) and there is no way I could make it work after splitting and joining it.

The tools I use in linux always work, when I mess with ramdisk and join it again. For some reason not with zeus :D

Grrrr, out of battery.... thanks for listening :)
[HTC One X] Thunder07:
zeus uses an old sense ramdisk, so it wont work with aosp rom...

but the next release will be based on faux kernel and ramdisk...

anyway... so far it seems like it's booting from the 1st go with faux kernel... will know for sure once i release it.

also, you're using hardboot right...

that also means there will always have 2 reboots.

one when you boot the rom and the 2nd when you call kexec...

you dont notice yours because you wait for the rom to boot and you forget about it :p

also, i kind get what you want to do..

you want to have a slimkitkat kernel with kexec, so people can use it as is, a kernel...

but it will also work for kexec if they wanted it??

sure that works only if you build your own rom(which you do),

but since i dont, my way works better for me, as it's more universal.

about the modules, fair enough...

but that also means you'd need to copy the modules for the kexec kernel everytime, to make sure you're not using the main kernels modules on the kexec.
[HTC One X] kantry123:
[MENTION=618483]Thunder07[/MENTION]

i have a doubt bro..!

i'm unable to retore boot.img from nandroid backup.. even after using ur kl..recoveryaroma flasher beta3.

but the phn stuck in boot..

but if i flash the stock kernel manually

then i can boot probable

mine is 4.19.720.2 stock rom indian firmware

so mine kernel is bit different so i want that kernel only rather than having stock kernel of WWE europe kernel

can u tell me how to flash that boot.img using ur KL patch?

ive tried both KL app and aroma recovery too..phn gets stuck in bootloop

thanks and regards

kantry123
[HTC One X] teemo:
Just a thought, why not use CM kernel. Faux is not updated and I really doubt it will be for next Android release. It will most likely die, when ART becomes default.

Thats good news

Yep

Not sure I follow you there: I call kexec FROM the ROM (see video)

When I get bored and want to use, test or whatever another kernel, I just boot to the next kernel.

Exactly :D

I use it, and it works normally for me - so far. Could be issues, but I wonder exacly what issues ?

Ultimately all the custom kernels should have kexec, then people can change very easy :) Maybe Im just dreaming.... but at least Im having fun and learn a lot.

https://www.youtube.com/watch?v=TmHI9IV1R7w
[HTC One X] Thunder07:
i could do that.. but how stable is stock CM??

using faux, atleast i know when he's building the kernel, he's making sure it works for HOX and not for 200+ devices...

I'm not entirely sure how is CM updates are maintained form that point of view, devices per device bases...

with that said, my kernel would probably never need to be updated,

as once i get a properly working kernel, it's version independent.

yes, i see what you're doing...

techincally you double booted (1st boot you booted default kernel, 2nd boot when you called kexec).

mine is more obvious since they happen one after the other,

anyway... there is no need to aruge about this point, because there are 2 (somewhat different) reasons to our kernels.

mine is made only to boot a 2nd kernel, yours is made to boot by itself.

is the kernel you're trying to flash stock image??

stock kernels dont have the magic letters, so unpackers dont unpack it, thus you can't install it,

ill have a look at the unpacker attached and look for one that supports stock kernels for next release.
[HTC One X] Thunder07:
-- KL Zeus Beta5, http://d-h.st/Hsr

- Rebased onto Faux Kernel (kitkat)

-Seems to fix black screens freeze,

now instead of it freezing it will reboot by itself (no need for hard reboot)

and it seems to boot more often than fail.

I'm also working on Multirom and it's driving me crazy...

It's so close yet so far way from booting but it just refuses for some reason.

[MENTION=2528998]Thant[/MENTION],

I dont know if this fixed mass storage issue,

as the way i mount my sd prevents me from using it as mass,

do please report back.

Edit:

YOU MUST BE JOKING!!

Multirom just decided to work!!
[HTC One X] ljjehl:
@Thunder07, I used your newest Zeus update along with aromaFM flasher. I was able to install my XenonHD kitkat rom using this, and flashing the boot.img via the aromaFM . (had to clean cache afterwards in recovery before booting) It takes 4-5 times to get it booting up initially. after a reboot, it's down to 2-3 times. When I didn't initially clean cache, I had to reset the boot after 5 times, since it stopped rebooting.

I will test a little more with different roms. Thanks for continuing your work!! This is the best invention/innovation for "s-off" since sliced bread!! :P
[HTC One X] humzaahmed155:
Sliced bread was an innovative S-OFF solution?! :silly:
[HTC One X] Thant:
Thank you so much I will test this days if I have time and will report later. Thanks again.

EDIT: I hope soon we will see multi rom:)
[HTC One X] Thant:
[MENTION=618483]Thunder07[/MENTION] now Mass storage work perfect everything is ok with the latest Beta5.Just :good::)Perfect
[HTC One X] humzaahmed155:
Works perfectly right now, though after installing it didn't automatically reboot after failing to boot the first time. Though after that it seems to work just fine.

So far, the phone has only rebooted once, though I fear that's because i'm using a pretty unstable kernel (next 10.2 intelli)
[HTC One X] cappuccina:
THANKS for the update Thunder.

Haven't installed a new rom yet but rebooted a couple of times, also from recovery and haven't had one freeze.

I somehow have the feeling it's booting faster now. But might be just a feeling. ;)

Great job.

I'm also curious about this multirom thing. ;p

Have no experience with it from other phones.

Looking forward to it. :)

sent from my carbonated Kitty Kat
[HTC One X] Thunder07:
That's Great!!

I've also though it was... so it wasn't just me after all!!

As for MultiROM,

Ill post that later tonight,

but only to those who are welling to test it 1st,

As i nuked my sdcard twice.

So those who want to test it,

Please backup your roms & sdcard onto your computer 1st...

you dont want to lose all 1500 pictures you collected over the past 2 years :crying:

with that said, that problem should be under control...

but that's why i'm only giving it to few to test it 1st.

http://xdaforums.com/showthread.php?t=2761149
[HTC One X] Thant:
This work only with TWRP or with any recovery this is my question at this moment. It is not a problem to test it if I have time to backup my sd card and have time to flash it and test it with second rom. How many roms you can install with MultiROM?

Really Sorry for that you loses your data:( Try to mount like mass storage from recovery and use some programs for recovery deleted data maybe you will have the luck to restore most of them:(
[HTC One X] vaykossil:
I flashed beta5 and followed the instruction in op , but I'm stuck at htc screen, I'm on viperx so the question is can use this on sense ? Or maybe repack is needed ?
[HTC One X] Thunder07:
It will only work with TWRP,

However twrp will not replace your current recovery but it will be a 2nd recovery which will work along it.

However, the only way to manage a 2nd ROM is through TWRP,

That includes backup, flashes and even adding newer ROMs.

Each ROM between /system /data /cache partitions use 3gb of space...

An empty sdcard can hold almost 8 ROMs + the main ROM... So 9 ROMs in total.

As for my sdcard...

As I said earlier, with the way I use it I can't use it as an mass storage..

But I do have an idea now that I will try...

But anyways I already made peace with it :p

Send From My HTC One X
[HTC One X] Thant:
When you flash KL zeus boot.img you must to go after this in recovery to use KL flasher.zip and install some kernel when you start to install KL Flasher from recovery navigate to your new kernel open it choice the boot.img from the opened arhiv and then the script will continue and flash the modules and the restart the phone and everything will be OK
[HTC One X] Thunder07:
what kernel did you use before??

did you flash that same kernel through AromaFM??
[HTC One X] Thant:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
[HTC One X] vaykossil:
I did exactly what you're saying, will investigate more, thanks anyway

I'm was on ep7.7 from audahadi and yes, flashed same kernel through aromafm and couldn't pass htc screen, can I repack kesex kernal ?!
[HTC One X] Thunder07:
No, never repack Zeus!!

did you need to repack ep7.7 for it to work with Viper.. if so you'd need to repack it and flash it again through AromaFM KL.

I dont use Viper... but they usually need repack right??
[HTC One X] Thunder07:
Answered on MultiROM Thread.
[HTC One X] vaykossil:
Yes , ep 7.7 needs repack to boot on viperx, but I replaced the repacked one in the kernel zip and then flashed from aromafm, so it can't be the problem, maybe some other guys on sense can give it a try and help us out, will try again with another kernel and will report back.

Thanks.

---------- Post added at 02:55 AM ---------- Previous post was at 02:14 AM ----------

Finally, got it boot :)

There was something wrong with ep's ramdisk, bad repack maybe

Flashed lya's kernel and it booted just fine, then installed your app and flashed my desired ep through it, all its fine now

It's great, thank you thunder [emoji106][emoji122]
[HTC One X] Thunder07:
:good:

But there is no need to rezip..

The recovery flasher can flash boot.img as is,

When I get the time I'll add a repacker to AromaFM KL.

Send From My HTC One X
[HTC One X] ljjehl:
You know, there's sdcard recovery apps out there that can recover those pictures. Not sure if it's too late now, since when you re-write over the deleted partitions too many times, makes it more difficult for recovery. :\
[HTC One X] Thunder07:
ill say it's too late now...

I've been experimenting with MultiROM and filled my sdcard over twice!!

have you tried a simple reboot, users have reported better wifi/BT with beta 5 :/

My BT is also working fine like...

with that said... try beta6...

nothing much changed.. but you never know.

Also Anyone on beta5 update to beta6...

beta5 + multirom seems to be whats causing the sdcard wipes...

as you are, your safe.. just dont try them 2 together!!

Link is in the op.
[HTC One X] blackbuffalo:
Beta6 work fine. Boot 2 times and I don't need manual press and keep power button for hard reboot my HOX! Thanks so much
[HTC One X] Thant:
For me and the 5 and 6 BT/WiFi works bether then 4:)
[HTC One X] kantry123:
[MENTION=618483]Thunder07[/MENTION]

i've some problem with the latest one

on every reboot it takes almost 10 times every time i restart my device(normally it was 2-3 )

draining my battery like 20-30% battery

any sol or do u where i'm missing something?

regards
[HTC One X] Thant:
No problem here boot from the first time even no need to reboot twice

EDIT: [MENTION=4644981]kantry123[/MENTION] are you using MULTIROM?
[HTC One X] kantry123:
Thanks for ur reply bud..

then i think my device can't bear it coz its getting overheated like hell while rebooting 10 times is like hell to me..!

so i think i'll be rolling back to fastboot method

NOPE i'm not using multirom

thn & regards

kantry123
[HTC One X] blackbuffalo:
Some time, my HOX get same problem with [MENTION=4644981]kantry123[/MENTION] too. Boot 4 or 6 time then boot operation, drain battery and very crazy