I've flashed every single compatible kernel there is for android 4.0.4 (I'm using the lastest ViperXL Rom) and it keeps returning to the original kernel that comes with the rom.
Is this a rom limitation or something wrong with my recovery?
acompres said:
I've flashed every single compatible kernel there is for android 4.0.4 (I'm using the lastest ViperXL Rom) and it keeps returning to the original kernel that comes with the rom.
Is this a rom limitation or something wrong with my recovery?
Click to expand...
Click to collapse
What's your hboot?
Are you flashing boot.img from fastboot first before you install the kernel, if you have 1.14?
Myrder said:
What's your hboot?
Are you flashing boot.img from fastboot first before you install the kernel, if you have 1.14?
Click to expand...
Click to collapse
I do have 1.14, although all the instructions on the kernels i've downloaded stated to just flash through twrp and enjoy?
acompres said:
I do have 1.14, although all the instructions on the kernels i've downloaded stated to just flash through twrp and enjoy?
Click to expand...
Click to collapse
fastboot flash boot boot.img
Or downgrade your hboot
Related
I dont know what went wrong, i just flash the 3.1.1 update in fastboot.
But still my DS is 3.1.0.
Is this because my DS is hboot 2.00.0002 and S-ON?
Is there a way to s-Off with this hboot?
leimrey said:
I dont know what went wrong, i just flash the 3.1.1 update in fastboot.
But still my DS is 3.1.0.
Is this because my DS is hboot 2.00.0002 and S-ON?
Is there a way to s-Off with this hboot?
Click to expand...
Click to collapse
What did u flash in fastboot?
The entire update?
The update needs to be flashed from CWM or 4EXT
The boot.img in the update needs to be flashed from fastboot for HTC dev users
suku_patel_22 said:
What did u flash in fastboot?
The entire update?
The update needs to be flashed from CWM or 4EXT
The boot.img in the update needs to be flashed from fastboot for HTC dev users
Click to expand...
Click to collapse
I only flash the boot.img of 3.1.1. because mine's from htcdev
I didn't flashed it in 4ext.
...
I need to flash them both? in recovery and in fastboot is that what you meant?
This is the thing i got confused
leimrey said:
I only flash the boot.img of 3.1.1. because mine's from htcdev
I didn't flashed it in 4ext.
...
I need to flash them both? in recovery and in fastboot is that what you meant?
This is the thing i got confused
Click to expand...
Click to collapse
Yes,
You need to flash the zip from 4EXT and then boot.img from fastboot
suku_patel_22 said:
Yes,
You need to flash the zip from 4EXT and then boot.img from fastboot
Click to expand...
Click to collapse
oh.. that's why. I thought i made a mistake in flashing. It's just my upgrading is not yet complete.
*Sigh* too much work for htcdev users. lol!
THANK YOU SO MUCH!
Now i'm relieved.
*i noticed your still not in fallout 3.1.0?, in your sig.
Hi, I flashed rom, but wifi is not working.
If someone could assist me with hboot and radio?
With other roms I had no trouble with anything, so some assist with hboot and radio would be needed to get this rom working.
ViperSAGA 2.1.1 with all otas
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
stock kernel, Amibuddha btb and patched
with either wifi not working... :/
AW: ViperSAGA 2.1.1 Wifi not working
I don't think this can have anything to do with radio or hboot. I assume you flashed the boot.img after flashing the Rom and after every kernel installation (the boot.img from the kernel you flashed)?
teadrinker said:
I don't think this can have anything to do with radio or hboot. I assume you flashed the boot.img after flashing the Rom and after every kernel installation (the boot.img from the kernel you flashed)?
Click to expand...
Click to collapse
Well, I havent flashed boot.img separately. I tried yesterday other roms also, (desire xs and sabsa) . Aroma should flash correct boot.img? i assume.
AW: ViperSAGA 2.1.1 Wifi not working
You are htcdev unlocked, still s-on. This means you can't write to the /boot partition from recovery, only through fastboot. So after flashing a new Rom or kernel, you have to extract the boot.img and flash it manually in cmd.
Puntti said:
Well, I havent flashed boot.img separately. I tried yesterday other roms also, (desire xs and sabsa) . Aroma should flash correct boot.img? i assume.
Click to expand...
Click to collapse
After installing the rom you have to flash the boot.img
this is the guide that i used to flash custom roms.
http://forum.xda-developers.com/showthread.php?t=1525100
Device: HTC Desire S (S-ON HTCDEV unlocked)
ROM: Desire XS Version 1.1
Recovery: 4EXTRecovery.
HBOOT 2.00.2002
Installing MIUI rom from here http://forum.xda-developers.com/showthread.php?t=2034030
JB 3.1.25,
- wiped cache/dalvik cache
- wiped data/factory reset
Stuck on boot animation, wont boot..waited for 30 min and still..
Coming from ViperXL, S-ON
Any solutions? Anyone experienced?
doc_v15 said:
Installing MIUI rom from here http://forum.xda-developers.com/showthread.php?t=2034030
JB 3.1.25,
- wiped cache/dalvik cache
- wiped data/factory reset
Stuck on boot animation, wont boot..waited for 30 min and still..
Coming from ViperXL, S-ON
Any solutions? Anyone experienced?
Click to expand...
Click to collapse
I think it not work with JB 4.1.2
Metoo
Did you fastboot flash the boot.img
Sent from my HTC One X using Tapatalk 2
jerrycoffman45 said:
Did you fastboot flash the boot.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
No I did not..It said in the instructions and also i read it somewhere that we dont need to flash the boot.img
Do I have too?
Problem solved, flashed boot.img
If you are s-on you do if your hboot is 1.14 or higher s-off fixs that and it is easy to do
Sent from my HTC One X using Tapatalk 2
doc_v15 said:
No I did not..It said in the instructions and also i read it somewhere that we dont need to flash the boot.img
Click to expand...
Click to collapse
I know you got it booted. But just to clarify:
Maybe I'm missing it, but I don't see in the MIUI instructions where it says you don't need to flash boot.img seperately. It makes no mention of boot.img either way, which is not the same as it saying its not needed.
If you are hboot 1.14 or higher, and S-on, you should assume that you need to flash boot.img separately with fastboot, unless the instructions explicitly say otherwise.
AFAIK, ViperXL is the only current ROM that will flash boot.img in AROMA (plus older builds of CleanROM, but not the current CR6). Even with ViperXL, it doesn't work for everyone, and some folks have had to flash it from fastboot.
redpoint73 said:
I know you got it booted. But just to clarify:
Maybe I'm missing it, but I don't see in the MIUI instructions where it says you don't need to flash boot.img seperately. It makes no mention of boot.img either way, which is not the same as it saying its not needed.
If you are hboot 1.14 or higher, and S-on, you should assume that you need to flash boot.img separately with fastboot, unless the instructions explicitly say otherwise.
AFAIK, ViperXL is the only current ROM that will flash boot.img in AROMA (plus older builds of CleanROM, but not the current CR6). Even with ViperXL, it doesn't work for everyone, and some folks have had to flash it from fastboot.
Click to expand...
Click to collapse
Thanks, It was not mention on the instructions, but there was people who asked in the thread whether they need to flash boot.img for the rom, it was answered no . So i was assuming.
But then, it worked right away after I flashed the boot.img
Thanks again
Sent from my One X
The colors are all messed up as well when i boot in and its not just this rom but cyanogen mod as well but whats odd is if i use older versions of both cyanogen and this everything is fine its just versions that are from oct 15ish and later.
Are you using a custom kernel? What are your bootloader details?
Sent from my Evita
timmaaa said:
Are you using a custom kernel? What are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
Evita Put Ship S-On rl
Hboot-2.14.0000
Radio-0,24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC- boot
Im pretty sure im on the stock kernel
Ok, are you flashing the boot.img with fastboot each time you change ROMs?
Sent from my Evita
timmaaa said:
Ok, are you flashing the boot.img with fastboot each time you change ROMs?
Sent from my Evita
Click to expand...
Click to collapse
No i haven't't i have just been flashing them but the rom still works its just the colors are all messed up.
XSoloDolo said:
No i haven't't i have just been flashing them but the rom still works its just the colors are all messed up.
Click to expand...
Click to collapse
You need to extract boot.img and flash it manually in fastboot every time you flash a new ROM. What you are experiencing is likely due to a kernel mismatched with the ROM.
Sometimes a kernal mismatch will result in the ROM not booting. Other times, it causes random bugs like this.
redpoint73 said:
You need to extract boot.img and flash it manually in fastboot every time you flash a new ROM. What you are experiencing is likely due to a kernel mismatched with the ROM.
Sometimes a kernal mismatch will result in the ROM not booting. Other times, it causes random bugs like this.
Click to expand...
Click to collapse
Wow that worked thanks man! I should have thought of that earlier too.
As Redpoint said, you need to extract the boot.img and flash it each time you change ROMs. The reason you were having problems was because you still had the boot.img from a previous ROM installed. It turns out that it was kinda compatible (letting the ROM boot), but kinda incompatible (strange visual glitches). If you get s-off you don't have to worry about flashing the boot.img manually anymore.
Sent from my Evita
Please can people help here?
I was trying to restore my sensation back to stock(orange it has hboot1.27) all was going well but then it would not boot and stuck in loop to the android recovery.
So far I managed to get 4ext back on and re unlocked the boot, tried reflash in 4ext different custom roms but non will boot after it installs them and say done it just reboots to the stock android recovery always.
I was thinking do I need to flash with a stock orange ruu? but also cant find one with hboot 1.27.
ahhhhhh this is a pain.
any help would be great.
thank you
jakk1981 said:
Please can people help here?
I was trying to restore my sensation back to stock(orange it has hboot1.27) all was going well but then it would not boot and stuck in loop to the android recovery.
So far I managed to get 4ext back on and re unlocked the boot, tried reflash in 4ext different custom roms but non will boot after it installs them and say done it just reboots to the stock android recovery always.
I was thinking do I need to flash with a stock orange ruu? but also cant find one with hboot 1.27.
ahhhhhh this is a pain.
any help would be great.
thank you
Click to expand...
Click to collapse
are you on S-ON?
if yes then flash the boot.img after flashing the custom rom via fastboot command
the command is fastboot flash boot boot.img
rzr86 said:
are you on S-ON?
if yes then flash the boot.img after flashing the custom rom via fastboot command
the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi thanks,
yes s-on
were is the boot.img is it in the custom roms?
sorry bit of a noob
jakk1981 said:
Hi thanks,
yes s-on
were is the boot.img is it in the custom roms?
sorry bit of a noob
Click to expand...
Click to collapse
yes extract it from the rom.zip
rzr86 said:
yes extract it from the rom.zip
Click to expand...
Click to collapse
thanks I will give it a go does it need to be a stock rom or can I still use a custom rom like vipers
jakk1981 said:
thanks I will give it a go does it need to be a stock rom or can I still use a custom rom like vipers
Click to expand...
Click to collapse
whatever rom you are going to use, use the boot.img from the specific rom after
rzr86 said:
whatever rom you are going to use, use the boot.img from the specific rom after
Click to expand...
Click to collapse
EXCELLENT in the end that did the job, THANKS FOR YOUR HELP - TOP MARKS
I tried ParanoidAndroid first but no good it didnt work,
Then tried ViperS 5.2.1 and that did work the the command you gave me.
If I did want this back to stock rom as factory set,
is there away? as this is how I got in this mess in the first place
jakk1981 said:
EIf I did want this back to stock rom as factory set,
is there away? as this is how I got in this mess in the first place
Click to expand...
Click to collapse
do you mean using a ruu.exe?
if yes i don't know if it exists an ics for orange
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
do you mean using a ruu.exe?
if yes i don't know if it exists an ics for orange
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Anyway at all to get it back to a pure stock orange rom.exe
I dont think there is ics orange ruu,
I have hboot 1.27 too