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
Related
Hey there,
Today I wanted to flash faux kernel - http://forum.xda-developers.com/showthread.php?t=1647993 over ARHD6 as I heard lots of good things about it.
I did:
[recovery mode]
10. Select recovery
11. go to /sdcard/download and select the downloaded zip file and let it run its script.
12. Once the script is done, select "reboot system now"
After I did that, my HTC one x was stuck on the boot screen, so I then downloaded and flashed the kernels in this thread - http://forum.xda-developers.com/showthread.php?t=1654982 I tried both Australian variants(since I got the phone in Australia) under "Faux123", and it was still stuck on boot screen. After that I wiped cache partition using clockwork mod, however this time when i rebooted, the phone just goes into a bootloop.
Okay no biggie (I thought), because I had 2 backups in clockwork. So I ran the 2 backups I had, guess what! Even after recovering, it still stuck on bootloop. Great. Now I've no idea what to do...
Any help would be greatly appreciated. Thanks!
Hi,
The Kernel is independent Form your backup.
What rom do you use?
You may need repacked kernels.
http://forum.xda-developers.com/showthread.php?t=1727567
.bootloader
Flash kernel
Erase cache
. Clockwork
Erase delvik
Erase cache (factory reset)
Flash rom
Flash kernel modules
.
When you flash your kernel and restore a backup it tries to use the original settings from stock kernel with your new kernel. This won't work.
Gesendet von meinem HTC One X mit Tapatalk 2
njensign said:
Hi,
The Kernel is independent Form your backup.
What rom do you use?
You may need repacked kernels.
http://forum.xda-developers.com/showthread.php?t=1727567
.bootloader
Flash kernel
Erase cache
. Clockwork
Erase delvik
Erase cache (factory reset)
Flash rom
Flash kernel modules
.
When you flash your kernel and restore a backup it tries to use the original settings from stock kernel with your new kernel. This won't work.
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I'm using Android Revolution HD 6. Should I still get a repacked kernel?
because we don't have s-off, you need to flash the boot.img (kernel) manually via fastboot with your pc. read fauxes kernel thread, it explains it all... good luck.
kemmo123 said:
because we don't have s-off, you need to flash the boot.img (kernel) manually via fastboot with your pc. read fauxes kernel thread, it explains it all... good luck.
Click to expand...
Click to collapse
Thanks!!! You're a life saver. So I flashed it in fastboot, then I ran the zip file in the recovery. After that it boots up fine! But everything I have is lost, so when I try to recover it by using my previous backup, it goes to another bootloop O_O. Any ideas on how to get back my apps and data back?
EDIT: All right! Got my data back!
1. Restored using clockwork
2. Goes into boot loop
3. Flash the kernel
4. Wallah!
Got one question tho, how do I know I'm using faux's kernel? When I look at kernel version in system info, it says:
(some numbers)
[email protected]#350
SMP PREEMPT
kazemagic said:
Thanks!!! You're a life saver. So I flashed it in fastboot, then I ran the zip file in the recovery. After that it boots up fine! But everything I have is lost, so when I try to recover it by using my previous backup, it goes to another bootloop O_O. Any ideas on how to get back my apps and data back?
Click to expand...
Click to collapse
Install the boot.img (that comes with your backup).
BenPope said:
Install the boot.img (that comes with your backup).
Click to expand...
Click to collapse
Thanks I reinstalled faux kernel, and it still says ubuntu in the kernel version in info lol so im probably running faux's kernel
My procedure in chronological order:
Flashed recovery TWRP 2.3
Wiped everything possible in the wipe-tab
Installed CM9/10 from zip on SD-card (zip contains META-INF, system and boot.img)
Flashed boot.img from the zip file CM9/10
Issued the command fastboot erase cache
Unplugged cable and reboot
What happens is that I am stuck at the HTC booting screen. I have been here for about 30-40 minutes. If I try any adb shell command I receive this error: - exec '/system/bin/sh' failed: No such file or directory (2) -. Clearly, something is not right here. I will not speculate because I lack the knowledge to do so. Any help is appreciated because I have been phone-less for a day now and it is getting irritating. Thanks!
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Sent from my HTC One X
TToivanen said:
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Click to expand...
Click to collapse
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
zettez said:
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
Click to expand...
Click to collapse
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
TToivanen said:
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
Click to expand...
Click to collapse
No, I have not. Maybe I should give it a try? Or is it not required? Should I not be able to start the phone without any gapps?
Do you by chance have any ROM you can recommend that works so I could try it out and exclude problems? Would very like to know if it is my phone or ROM that is buggy.
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Sent from my HTC One X
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
TToivanen said:
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Click to expand...
Click to collapse
Would you mind telling me which CM10 build you are using and which boot.img you flashed?
BenPope said:
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
Click to expand...
Click to collapse
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
zettez said:
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
Click to expand...
Click to collapse
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Sent from my HTC One X
TToivanen said:
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Click to expand...
Click to collapse
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
irundaia said:
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
Click to expand...
Click to collapse
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
zettez said:
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Click to expand...
Click to collapse
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
TToivanen said:
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
Click to expand...
Click to collapse
Will try again. I got the latest build from http://get.cm/?device=endeavoru. Will try cm-10-20121213-NIGHTLY-endeavoru.zip as it came out today.
zettez said:
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
Click to expand...
Click to collapse
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------
hmm the backup was useless... Off to the RUU it is....
irundaia said:
[/COLOR]hmm the backup was useless... Off to the RUU it is....
Click to expand...
Click to collapse
You flashed the stock boot.img before restoring?
irundaia said:
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
Click to expand...
Click to collapse
I see, then it is not only I who have this problem.
And a heads up, if the backup would go wrong, I currently use this ROM and it works pretty good if you want stock or cannot be arsed to get a root exploit for the stock ROM. http://forum.xda-developers.com/showthread.php?t=2035203.
Would be great if anyone has any ideas why irundaia and I cannot make CM10 work?
TToivanen said:
You flashed the stock boot.img before restoring?
Click to expand...
Click to collapse
You're right, I forgot to do that. I does boot now, still at a loss though. Can't we downgrade our Hboot to a version in which we know that CM can be flashed?
Kinda out of ideas here...
Can you confirm that the boot.img flashes ok? (should say OKAY)
Also confirm that you have endeavoru and not evita.
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"
Hi XDA,
I decided to install CM 11 on my HTC, and so I unlocked the bootloader, and I then rooted it. I also updated my HBOOT to 1.39. After this I installed CWM and backed up, and attempted to flash the latest CM for the One X. Firstly I had an issue with the status 7 error, but managed to overcome that by updating my CWM (Now running 6.0.4.7 Touch Recovery). At the moment I do not have an OS, and all attempts to flash a new ROM are successful, however when I reboot I am still stuck at a frozen boot screen. ("HTC. Quietly Brilliant"). Even restoring my backup doesn't work.
Any help would be much appreciated.
Apologies if this is in the wrong section.
Thank you
JamesNZ7 said:
Hi XDA,
I decided to install CM 11 on my HTC, and so I unlocked the bootloader, and I then rooted it. I also updated my HBOOT to 1.39. After this I installed CWM and backed up, and attempted to flash the latest CM for the One X. Firstly I had an issue with the status 7 error, but managed to overcome that by updating my CWM (Now running 6.0.4.7 Touch Recovery). At the moment I do not have an OS, and all attempts to flash a new ROM are successful, however when I reboot I am still stuck at a frozen boot screen. ("HTC. Quietly Brilliant"). Even restoring my backup doesn't work.
Any help would be much appreciated.
Apologies if this is in the wrong section.
Thank you
Click to expand...
Click to collapse
Have you flashed boot.img?
mr93 said:
Have you flashed boot.img?
Click to expand...
Click to collapse
I haven't, no. Is this unzipping the rom and then flashing the .img?
Yeah take out the boot.img indeed and flash it via fastboot
Mr Hofs said:
Yeah take out the boot.img indeed and flash it via fastboot
Click to expand...
Click to collapse
Aaaahhh THANK YOU SO MUCH !!! Working beautifully!!
Such a simple solution.
mr93 said:
Have you flashed boot.img?
Click to expand...
Click to collapse
Thanks a billion !!
Hi guys,
I'm new in this section because I had an HTC One SV, but today I receive One X. Now... I have a very serious problem: after I flashed a custom kernel, HTC doesn't seems to boot, but it it's stuck in the white screen with the green HTC word. I tried to flash another kernel and stock kernel too, but this doesn't seems to be useful... Please help me!!! (I'm not S-Off)
TheSura said:
Hi guys,
I'm new in this section because I had an HTC One SV, but today I receive One X. Now... I have a very serious problem: after I flashed a custom kernel, HTC doesn't seems to boot, but it it's stuck in the white screen with the green HTC word. I tried to flash another kernel and stock kernel too, but this doesn't seems to be useful... Please help me!!! (I'm not S-Off)
Click to expand...
Click to collapse
flash the boot.img via fastboot you must take it from modules archive and paste it on your fastboot folder then run from cmd fastboot flash boot boot.img and restart
Thant said:
flash the boot.img via fastboot you must take it from modules archive and paste it on your fastboot folder then run from cmd fastboot flash boot boot.img and restart
Click to expand...
Click to collapse
I tried many times and finally, my HTC booted until the lockscreen. If I tried to unlock, it returned that White screen, but my PC recognized it and I could copy Viper ROM inside it. So, I flashed the ROM and now it work. But if I want back to stock? I don't have any nandroid backup and; I don't know why, I can't do S-Off: using rumrunner, it does all the procedure, but it stucks on pouring: it arrives to pouring (8) and then it says me to reboot and retry. So, what can I do?
TheSura said:
I tried many times and finally, my HTC booted until the lockscreen. If I tried to unlock, it returned that White screen, but my PC recognized it and I could copy Viper ROM inside it. So, I flashed the ROM and now it work. But if I want back to stock? I don't have any nandroid backup and; I don't know why, I can't do S-Off: using rumrunner, it does all the procedure, but it stucks on pouring: it arrives to pouring (8) and then it says me to reboot and retry. So, what can I do?
Click to expand...
Click to collapse
No S-OFF for ONE X international Endeavoru, your only way is restore nandroid backup find it from somewhere
Thant said:
No S-OFF for ONE X international Endeavoru, your only way is restore nandroid backup find it from somewhere
Click to expand...
Click to collapse
Well, I understood. Thank you so much! I've found a nandroid yet, but I'm having problems with the process "HTC.opensense.social" or something similar because it stopped improperly. Sorry if I do so many questions, but I'm n00b <_< Thank you
TheSura said:
Well, I understood. Thank you so much! I've found a nandroid yet, but I'm having problems with the process "HTC.opensense.social" or something similar because it stopped improperly. Sorry if I do so many questions, but I'm n00b <_< Thank you
Click to expand...
Click to collapse
da a full wipe(system,data,cache and davlik cache) and don't forget to flash the boot.img from nandroid backup
Thant said:
da a full wipe(system,data,cache and davlik cache) and don't forget to flash the boot.img from nandroid backup
Click to expand...
Click to collapse
I did yet before restoring nandroid! But I didn't flash the boot.img because after restoring, I flashed a new kernel from recovery and from fastboot. The cause could be the custom kernel?
TheSura said:
I did yet before restoring nandroid! But I didn't flash the boot.img because after restoring, I flashed a new kernel from recovery and from fastboot. The cause could be the custom kernel?
Click to expand...
Click to collapse
are you flash the boot.img from the kernel?
Thant said:
are you flash the boot.img from the kernel?
Click to expand...
Click to collapse
Yes, I did
thesura said:
yes, i did
Click to expand...
Click to collapse
@TheSura
Sorry, Wich kernel do you try to flash
Thant said:
@TheSura
Sorry, Wich kernel do you try to flash
Click to expand...
Click to collapse
I flashed this kernel: http://forum.xda-developers.com/showthread.php?t=2586808
Now I want to try another because it has overclock to 1.7: http://forum.xda-developers.com/showthread.php?t=2138586
Is this good?
Ps: doesn't matter the error: I'm going to return to viper, so don't worry
TheSura said:
I flashed this kernel: http://forum.xda-developers.com/showthread.php?t=2586808
Now I want to try another because it has overclock to 1.7: http://forum.xda-developers.com/showthread.php?t=2138586
Is this good?
Ps: doesn't matter the error: I'm going to return to viper, so don't worry
Click to expand...
Click to collapse
in this aroma flasher have 6 kernels you must to flash the coerct boot.img from modules archive
Thant said:
in this aroma flasher have 6 kernels you must to flash the coerct boot.img from modules archive
Click to expand...
Click to collapse
Understood! Thank you very much!