Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?
strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.
DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.
well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0
Related
I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
bringonblink said:
I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
Click to expand...
Click to collapse
When you load the kernel are you flashing the zimage manually or using a packaged update.zip that includes the wifi module for that kernel?
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
bringonblink said:
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
Click to expand...
Click to collapse
Are you building the kernel and boot image yourself or pulling them from somewhere?
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
bringonblink said:
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
Click to expand...
Click to collapse
Ah, indeed
So, that zip is meant to be applied via a custom recovery (CWM). It will flash not only the boot image, but also copy the newly build kernel modules, create a custom /etc/init.d and install busybox.
By flashing just the boot image you are missing the rebuilt modules and the custom init.d (which mounts /data with noauto_da_alloc, etc and sets windowsmgr.max_events_per_sec=72 for better scolling performance. As a result of not having the rebuilt kernel modules when the network module tries to load (bcm4329.ko) the version number won't match the kernel and it will fail to load. If you check dmesg you'll see it complaining
Flash this via a custom recovery and you should be fine (just place the entire zip on your device and then chose it from CWM).
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
bringonblink said:
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
Click to expand...
Click to collapse
When you reboot on a stock rom there is a script that checks recovery and if it is not stock it will reflash the stock recovery. This is an easy fix though. If you want to stay on stock you can flash CWM through fastboot, flash the SU binary and then rename/delete the script (/etc/install-recovery.sh or something like that).
If you want to just flash CM7 then just download the full zip and place it on the phone. Flash CWM through fastboot, boot into recovery and flash CM7 as desired (RC or nightlies). Then go ahead and apply the appropriate netarchy kernel - there's a separate version for CM IIRC. Make sure you do a full wipe before you flash CM7.
Ok so im downloading rom manager onto my phone, downloading CM7 on pc, then will transfer to phone (whole zip right?) then i just reboot in recovery, wipe and flash CM7, and THEN start on the kernel lol
Ok thanks ill keep ya updated really appreciate it
edit
Thanks a lot booted and rooted running CM7 and Netarchy
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.
downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.
ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.
hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.
2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.
why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit
okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...
Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar
Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app
tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Preston2291 said:
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Click to expand...
Click to collapse
Most kernels r flashed in recovery.
Tigerstown said:
Most kernels r flashed in recovery.
Click to expand...
Click to collapse
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Preston2291 said:
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Click to expand...
Click to collapse
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Tigerstown said:
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Click to expand...
Click to collapse
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick because I can't write to the system with a new rom
Preston2291 said:
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick
Click to expand...
Click to collapse
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Tigerstown said:
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Click to expand...
Click to collapse
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Preston2291 said:
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Click to expand...
Click to collapse
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Tigerstown said:
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Click to expand...
Click to collapse
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Preston2291 said:
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Click to expand...
Click to collapse
You should be able to just flash pretty much any sense based rom and have what you want. Write protection is removed in all of them, or, at least in all the ones I've tried.
That said, if you've already flashed a kernel that has write protection removed, you should be able to check it by just copying any file to the system folder. A text file, picture, anything. Then reboot the phone and check to see if the file you copied to the system folder is still there. If so, you're good to go. If not, write protection is still being enforced.