Develop Bugs

kernel, twrp and back to stock issues

hi,
im stuck in a circle of stupid mistakes
from the beginning:
my HOX was on stock ROM, but rooted.
i made the OTA to 3.18.401.1 (by using rootkeeper)
then i wanted to get back to stock without root by flashin a RUU.
there is no RUU for the 3.18.xx
the older RUUs are giving me an error 140 message
so i figured out that the only way to get back to stock now is by restoring a NAND backup
i haven't made a backup of my HOX because i already have it since few days
a kind user of this forum gave me his twrp backup of 3.18.401.1 to restore
so i flashed the twrp 2.4.3.0 to restore
but the touchscreen isnt working (same with twrp 2.4.0.0)
after reading a little on xda i now know that this is kernel related issue
i flashed the adviced kernel over CWM
flashed twrp 2.4.0.0
but touchscreen still isnt working.
:crying:
Now i dont know what to do.
im trying to fix this for 2 days now and i cant take it any longer
HOX CID HTC__102

AW: kernel, twrp and back to stock issues
Don't flash the kernel via cwm, flash it via fastboot
And the right section for this would have been Q&A
Gesendet von meinem One X mit Tapatalk 2

Flo95 said:
Don't flash the kernel via cwm, flash it via fastboot
And the right section for this would have been Q&A
Click to expand...
Click to collapse
Sorry, i thought this would be the right section...
How to flash the kernel with fastboot?
only unzip the boot.img and then fastboot flash boot boot.img ?

LaLey said:
Sorry, i thought this would be the right section...
How to flash the kernel with fastboot?
only unzip the boot.img and then fastboot flash boot boot.img ?
Click to expand...
Click to collapse
Flash cwr then twrp and no issues with touch after
Sent from my HTC One X using xda premium

matmar said:
Flash cwr then twrp and no issues with touch after
Click to expand...
Click to collapse
no, its not working. this is my problem

LaLey said:
no, its not working. this is my problem
Click to expand...
Click to collapse
Have you tried erasing cache in fastboot with fastboot erase cache. Maybe that will help

i had the wrong version of the twrp 2.4.0.0.
it has to be the openrecovery-twrp-2.4.0.0-endeavoru-JB.img
now touch is working
but how do i restore a backup?
my HTC_102-3.18.401.1 TWRP Backup.zip is on the root folder of sd.
whe i tap restore in twrp this backup is not shown...
EDIT:
ah ok, i need to create folder /twrp/backups/myIMEI/

Glad to see you got sorted

[Q] Kernel help

Maybe i missed the kernel lesson, but i can'd find it in this forum.
My problem is : when you install a new rom, first you flash the boot.img from rom. When you want to flash another kernel, you flash the kernel.img and if existe, the modules. Why am i getting no network or wifi ? ex: Viper x, and XM kernel.
flashed viperx bot img from rom zip, instaled 3.4.0, first boot, everything is ok. My battery drained like in 30 min, so i decided to flash another kernel. I've gone reading, and the XM looks the best in battery life, and see in other post that is compatible. I flashed XM, and now i have wifi error and no network.
Please help me.

SupremE MaDDoX said:
Maybe i missed the kernel lesson, but i can'd find it in this forum.
My problem is : when you install a new rom, first you flash the boot.img from rom. When you want to flash another kernel, you flash the kernel.img and if existe, the modules. Why am i getting no network or wifi ? ex: Viper x, and XM kernel.
flashed viperx bot img from rom zip, instaled 3.4.0, first boot, everything is ok. My battery drained like in 30 min, so i decided to flash another kernel. I've gone reading, and the XM looks the best in battery life, and see in other post that is compatible. I flashed XM, and now i have wifi error and no network.
Please help me.
Click to expand...
Click to collapse
Did you do the fastboot erase cache?
Which boot.img did you flash? The one from kernel.zip?
Please provide more details...

[email protected]|-|oR said:
Did you do the fastboot erase cache?
Which boot.img did you flash? The one from kernel.zip?
Please provide more details...
Click to expand...
Click to collapse
ok, i will write the steps
1. flashed boot.img from viper x (with viperx kernel flasher, that does fastboot erase cache)
2. flashed rom viper x 3.4.0
3. boot to see if is ok, is ok, all works, but the battery life is so poor
4. download xm kernel, and with the kernel flasher tool flashed it
5. no wifi and network signal

SupremE MaDDoX said:
ok, i will write the steps
1. flashed boot.img from viper x (with viperx kernel flasher, that does fastboot erase cache)
2. flashed rom viper x 3.4.0
3. boot to see if is ok, is ok, all works, but the battery life is so poor
4. download xm kernel, and with the kernel flasher tool flashed it
5. no wifi and network signal
Click to expand...
Click to collapse
From this steps I don't see that you flashed xm modules. that's why you don't have signal.
Sent from my HTC One X

NITRO_100 said:
From this steps I don't see that you flashed xm modules. that's why you don't have signal.
Sent from my HTC One X
Click to expand...
Click to collapse
i flashed xm kernel who has modules in zip.. tell me by stept so i can never ask stupid questions

SupremE MaDDoX said:
i flashed xm kernel who has modules in zip.. tell me by stept so i can never ask stupid questions
Click to expand...
Click to collapse
If you used One X One click, it should have flashed everything properly...
Still, here are the steps:
- place the kernel.zip to your sd card root
- place boot.img from kernel.zip to your fastboot folder on your pc
- reboot in bootloader
- fastboot erase cache
- fastboot flash boot boot.img
- fastboot erase cache
- reboot in recovery
- wipe cache/dalvik
- flash kernel.zip
- wipe cache/dalvik
- reboot
This works for me every time, even though I duplicate wiping (not necessary).

[email protected]|-|oR said:
If you used One X One click, it should have flashed everything properly...
Still, here are the steps:
- place the kernel.zip to your sd card root
- place boot.img from kernel.zip to your fastboot folder on your pc
- reboot in bootloader
- fastboot erase cache
- fastboot flash boot boot.img
- fastboot erase cache
- reboot in recovery
- wipe cache/dalvik
- flash kernel.zip
- wipe cache/dalvik
- reboot
This works for me every time, even though I duplicate wiping (not necessary).
Click to expand...
Click to collapse
Thank you, it was all i needed !

Ordroid 14.0 & XM-Kernel WiFi not working

Hi guys, i have a problem with Ordroid 14.0 & XM-Kernel #283, the WiFi not work, only put "authenticating", anyone know what could be wrong?
Thanks, and sorry my bad english

You flashed the boot.img, did you install the modules in the recovery ?

Yes, i follow the steps with says in the post
Install modules from recovery (Install the zip)
Wipe dalvik cache. Yes, it's important, the versions could have some binary level differencies (from different compiler options) which can lead to unknown behaviour with old dalvik code.
Erase fastboot cache
Flash kernel image with fastboot
If you have problems with some functions not working on your ROM, then repack. Otherwise it's not needed.
Click to expand...
Click to collapse

And did you used the repacked one that's posted in the thread ? If so i would try the pure one from the XM kernel thread

I tried with both, and tried with 4 versions, and not work :s

Try it once more the other way around, boot to the bootloader and flash the new xm boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Enter the recovery and install the modules.zip

The same, not work, I think I'll leave it with the stock kernel

Yeah i guess, if you tried the normal and the repacked one then there is not much to play around with anymore !
Did you try 274 too, i see that its been used without repacking ....

Yeah i think so, thanks very much for your help n.n

Link http://d-h.st/XfJ
You are using the sense based kernels right ?

Yes, i already test that version xD

Then im out of options !

[q] q. About maximus hd 20.0.0

Full wipe is obligatory
Installing Kernel via Kernel flasher is obligatory, otherwise your device won’t boot!
^^^
^^
^
in rom installation details written like this >>
THE QUESTION HERE !! FLASHING THE BOOT.IMG FOR ROM VIA CMD IS NOT ENOUGH ????

I haven't tried yet but I think the kernel flasher also flashes modules which may not be present in the Rom
Sent from my ViperX

command for boot.img work fine

Is available a FAQ post about MaximusHD 20 at this link
About it you must flash the given boot.img in the kernel flasher and perform a full wipe. Other kernels don't working on it. TWRP 2.6 is recommended because with other recoveries you may be stuck on 0% or 8% during the installation.
All is totally working with no bugs, if you have one you should retry a celan flash.
Good luck and enjoy :laugh:

frezd91 said:
Is available a FAQ post about MaximusHD 20 at this link
About it you must flash the given boot.img in the kernel flasher and perform a full wipe. Other kernels don't working on it. TWRP 2.6 is recommended because with other recoveries you may be stuck on 0% or 8% during the installation.
All is totally working with no bugs, if you have one you should retry a celan flash.
Good luck and enjoy :laugh:
Click to expand...
Click to collapse
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium

Whoareyou said:
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Which version of hotboot do you have? Have you clean dalvik via fastboot after flashing?

Whoareyou said:
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thats because you updated the phone to at least 3.17 software or higher (updated touch drivers !)
Indeed use twrp (repacked) or philz. Btw flashed it with philz myself, no issues
Sent from my HTC One X using XDA Premium 4 mobile app

@Mr Hofs
is clockwork recovery fine for installing this rom ?
or do u recommend philz recovery ??
If yes then how do i change from cwm to philz ?
Philz has a zip file whereas cwm is .img file
I installed cwm through cmdpromt
But how do i install philz through cmd ?

ronu said:
@Mr Hofs
is clockwork recovery fine for installing this rom ?
or do u recommend philz recovery ??
If yes then how do i change from cwm to philz ?
Philz has a zip file whereas cwm is .img file
I installed cwm through cmdpromt
But how do i install philz through cmd ?
Click to expand...
Click to collapse
hey mate,
1. +2. All recoverys should work. TWRP 2.6 is recommand. Some Philz users reported issues (stuck @ 0%, bootloop etc.).
3. Just flash it via fastboot.
4. Unzip it and you will find a .img file
5. fastboot flash recovery recovery.img
fastboot erase cache

ryman95 said:
hey mate,
1. +2. All recoverys should work. TWRP 2.6 is recommand. Some Philz users reported issues (stuck @ 0%, bootloop etc.).
3. Just flash it via fastboot.
4. Unzip it and you will find a .img file
5. fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks i will try this ! :good:

Guys official OTA is available in many countries. The new base is 4.18.401.2 but the Maximus is on 4.18.401.1. Also the hotboot is updated to 1.72.
I hope in a OTA update of Maxiums and not in another clean flash

I won't recommend any recovery. But philz has a fully functional one. Twrp is a good recovery but in the repacked version adb and ums does not work. And in philz it all does work. I use philz and flashed the sense 5 rom with succes. Just sharing my experience
Sent from my HTC One X using XDA Premium 4 mobile app

And as for the kernel, flashing it via fastboot is fine. the kernel flasher is a simple batch file to simplify things, but it doesn't appear to fastboot erase cache, so imo it is better to flash the boot image manually. I did and it's working flawlessly

MaximusHD 21 with base 4.18.401.2 is available, but on OTA you find the full rom, so 700MB.
I don't know if in the kernel flasher provided by football there is the wipe cache script, maybe the missing wipe can cause wifi issue.

frezd91 said:
MaximusHD 21 with base 4.18.401.2 is available, but on OTA you find the full rom, so 700MB.
I don't know if in the kernel flasher provided by football there is the wipe cache script, maybe the missing wipe can cause wifi issue.
Click to expand...
Click to collapse
kernel flasher only flash boot.img, no wipe of any kind.

wackywonderkid said:
kernel flasher only flash boot.img, no wipe of any kind.
Click to expand...
Click to collapse
An alternative is instead of rebooting your device from fastboot is to go back to hboot, load into recovery and manually wipe cache partition.

Tigerlight said:
An alternative is instead of rebooting your device from fastboot is to go back to hboot, load into recovery and manually wipe cache partition.
Click to expand...
Click to collapse
In any case if you select full wipe while installing the rom in the log you can read wiping cache so theoretically no problem. But a dev daid to me that is safer clean from fastboot

ar3na2012 said:
command for boot.img work fine
Click to expand...
Click to collapse
Yep, Flashing using cmd and erasing cache is working just fine.
See whats inside "Flash kernel.bat": nothing special but standard "fastboot flash boot boot.img"

[Q] Wifi & Bluetooth issues

I all, I've recently been having issues with my HTC One X and the Wifi and Bluetooth connectivity/range.
I've found that my wireless headphone need to be almost on top of the phone to connect, and the wifi drops to only just connected whilst other phones can sit just beside with full signal.
This has not always been the case, it may have been related to flashing the XM Kernal, but cannot be certain.
Since I have flashed CM10.2 nightly and understand it flashes it's own kernal, but I'm still experiencing these issues.
Can someone help?
Thanks, Joss.

Crazynutt said:
I all, I've recently been having issues with my HTC One X and the Wifi and Bluetooth connectivity/range.
I've found that my wireless headphone need to be almost on top of the phone to connect, and the wifi drops to only just connected whilst other phones can sit just beside with full signal.
This has not always been the case, it may have been related to flashing the XM Kernal, but cannot be certain.
Since I have flashed CM10.2 nightly and understand it flashes it's own kernal, but I'm still experiencing these issues.
Can someone help?
Thanks, Joss.
Click to expand...
Click to collapse
did you flash the modules to go with the kernel?

nogotaclue said:
did you flash the modules to go with the kernel?
Click to expand...
Click to collapse
Ahh, I assume no because I'm not sure that modules are.
I assumed I would simply need to flash the rom file and boot.img & it would do the rest.

Crazynutt said:
Ahh, I assume no because I'm not sure that modules are.
I assumed I would simply need to flash the rom file and boot.img & it would do the rest.
Click to expand...
Click to collapse
I made the same mistake when I first flashed a custom kernel. copy the zip file, that you extracted the boot image from, to your sdcard and install it via recovery

nogotaclue said:
I made the same mistake when I first flashed a custom kernel. copy the zip file, that you extracted the boot image from, to your sdcard and install it via recovery
Click to expand...
Click to collapse
The steps I've taken so far is to flash the boot.img via fastboot.
Installed the CM10.2 .zip via CWM Recovery.
And the appropriate clearing of cache and data etc.
The rom is booting just fine and works a treat, except for the low quality wifi and bluetooth.
Have I missed something else?

Crazynutt said:
The steps I've taken so far is to flash the boot.img via fastboot.
Installed the CM10.2 .zip via CWM Recovery.
And the appropriate clearing of cache and data etc.
The rom is booting just fine and works a treat, except for the low quality wifi and bluetooth.
Have I missed something else?
Click to expand...
Click to collapse
Yes you missed something, as I said above, the zip file that you downloaded from xm, the one you got the boot image from, needs to be installed in recovery as well as the rom zip
Where are the cakes?

nogotaclue said:
Yes you missed something, as I said above, the zip file that you downloaded from xm, the one you got the boot image from, needs to be installed in recovery as well as the rom zip
Where are the cakes?
Click to expand...
Click to collapse
I had XM installed, I thought by flashing CM though I would go back to it's default kernel.
I assume that would be a better setup...doesn't it automatically override XM when I flash the CM rom?
My current kernel version is 3.1.10-cyanogenmod+ [email protected] #1 Wed Aug 21 00:21:13 PDT 2013

Is your one x s-off ?
Where are the cakes?
---------- Post added at 09:47 AM ---------- Previous post was at 09:27 AM ----------
ok I'll assume your phone is s-off. either way do this:- if you have the rom installed already, flash the XM boot.img via fastboot, then reboot into recovery and mount usb storage and copy the entire original XM zip file(not just the boot .img) onto your card. now install the XM zip while in recovery and reboot

nogotaclue said:
Is your one x s-off ?
Where are the cakes?
---------- Post added at 09:47 AM ---------- Previous post was at 09:27 AM ----------
ok I'll assume your phone is s-off. either way do this:- if you have the rom installed already, flash the XM boot.img via fastboot, then reboot into recovery and mount usb storage and copy the entire original XM zip file(not just the boot .img) onto your card. now install the XM zip while in recovery and reboot
Click to expand...
Click to collapse
Phone is s-on...not sure what you mean by cakes.
Can I do the above with s-on or do I need to get s-off first?

Crazynutt said:
Phone is s-on...not sure what you mean by cakes.
Can I do the above with s-on or do I need to get s-off first?
Click to expand...
Click to collapse
sorry it took a while to reply I couldn't type properly for laughing, don't be offended but "where are the cakes" is my signature lol. and yes you can do that with s-on also, although if you are s-on and flash the xm boot image via fastboot installing the rom afterwards should not overwrite the xm boot.img. anyway do what i said, with installed rom, flash xm boot, then install modules in recovery(the xm zip file)

nogotaclue said:
sorry it took a while to reply I couldn't type properly for laughing, don't be offended but "where are the cakes" is my signature lol. and yes you can do that with s-on also, although if you are s-on and flash the xm boot image via fastboot installing the rom afterwards should not overwrite the xm boot.img. anyway do what i said, with installed rom, flash xm boot, then install modules in recovery(the xm zip file)
Click to expand...
Click to collapse
How is that your signature...it's only on some of your replies?
Anyway, I'm pretty sure I followed your instructions correctly, but now CM won't boot...whenever this happened previously, it was because I had not re-flashed the CM boot.img.
Should I have done this, or are you trying to leave the XM boot.img there?

Did u flashed the cm version of xm kernel or the sense version?
Sent from my HTC One X using xda premium

Crazynutt said:
How is that your signature...it's only on some of your replies?
Anyway, I'm pretty sure I followed your instructions correctly, but now CM won't boot...whenever this happened previously, it was because I had not re-flashed the CM boot.img.
Should I have done this, or are you trying to leave the XM boot.img there?
Click to expand...
Click to collapse
its only my sig on phone but not pc.
yes you have to leave the xm, that is the point of flashing the custom kernel, it replaces the cm one. and convictmoody asked a relevant question, did you get the correct xm kernel, the aosp one?

convict_moody said:
Did u flashed the cm version of xm kernel or the sense version?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This time I did the CM version - previously I've had sense on it.
nogotaclue said:
its only my sig on phone but not pc.
yes you have to leave the xm, that is the point of flashing the custom kernel, it replaces the cm one. and convictmoody asked a relevant question, did you get the correct xm kernel, the aosp one?
Click to expand...
Click to collapse
Okay, got it now
And...I'm still stuck - not passing the CM boot screen.

Crazynutt said:
This time I did the CM version - previously I've had sense on it.
Okay, got it now
And...I'm still stuck - not passing the CM boot screen.
Click to expand...
Click to collapse
ok what recovery are you using?

ClockworkMod Recovery v5.8.4.0

Crazynutt said:
ClockworkMod Recovery v5.8.4.0
Click to expand...
Click to collapse
ok from the beginning, download Xm kernel aosp version, copy the boot image from the downloaded zip into your fastboot folder.
next go into recovery and format these four, system, data, cache and sdcard.
now mount usb storage and copy the the cm rom.zip onto sdcard and then the whole xm zip file that you downloaded.
now boot into boot loader and do these exactly without the quotes, and when you press enter after each command make sure it says "okay" so you know it actually worked. "fastboot erase cache" then "fastboot flash boot boot.img" then again "fastboot erase cache".
now reboot recovery and install the rom but DO NOT REBOOT.
now clear dalvik
next, while still in recovery, install the xm zip file that you copied over with the rom.
again clear dalvik and then reboot.

nogotaclue said:
ok from the beginning, download Xm kernel aosp version, copy the boot image from the downloaded zip into your fastboot folder.
next go into recovery and format these four, system, data, cache and sdcard.
now mount usb storage and copy the the cm rom.zip onto sdcard and then the whole xm zip file that you downloaded.
now boot into boot loader and do these exactly without the quotes, and when you press enter after each command make sure it says "okay" so you know it actually worked. "fastboot erase cache" then "fastboot flash boot boot.img" then again "fastboot erase cache".
now reboot recovery and install the rom but DO NOT REBOOT.
now clear dalvik
next, while still in recovery, install the xm zip file that you copied over with the rom.
again clear dalvik and then reboot.
Click to expand...
Click to collapse
Alright, did all that...word for word.
Still stuck on CM boot screen.

Crazynutt said:
Alright, did all that...word for word.
Still stuck on CM boot screen.
Click to expand...
Click to collapse
you do know it takes a few minutes on first boot, sometimes 5 or 6 minutes?

nogotaclue said:
you do know it takes a few minutes on first boot, sometimes 5 or 6 minutes?
Click to expand...
Click to collapse
Okay, I've been waiting about 5 mins, but I'll wait patiently for a bit more
Thanks for your help by the way.