So, what exactly is keeping us from flashing kernel's from the HTC One X, or for that matter a ROM made for the One X? I thought that the insides were basically the same, so isn't the software basically identical? Sorry if this sounds noobish, And could anyone clarify as to why this may or may not be possible?
Thank you for your time!
i believe (but not totally positive) not having S-OFF is what is keeping us for now..
butterbuns said:
i believe (but not totally positive) not having S-OFF is what is keeping us for now..
Click to expand...
Click to collapse
no its not that cause if u have a recovery u can flash a kernel... i do kno that
There isn't any source released yet
Not Sent
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
jkt97401 said:
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
Click to expand...
Click to collapse
Flashing kernels from a close relative device is usually not a good idea. Even though you would be able to recover your device from recovery or the bootloader when it bricks. Why don't you try?
Sent from my EVO 4G LTE
jkt97401 said:
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
Click to expand...
Click to collapse
No you cant flash them its a completely different phone. The kernel is made specifically for that phone, if you try ot you WILL BRICK YOU EVO trust me on that. Same with if you try to flash a one x rom. Please dont be that guy.
Sent from my EVO using xda premium
I will try it as soon as I am able.
I have been waiting to flash anything until I can get into the Google Wallet app and reset the settings to protect my NFC.
Needless to say, it's been having issues even getting into the app haha
david279 said:
Flashing kernels from a close relative device is usually not a good idea. Even though you would be able to recover your device from recovery or the bootloader when it bricks. Why don't you try?
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
I think it would be a hard brick right? So no getting into anything incliding recovery. Do not try it. But if you want a 700 dollar paperweight go ahead.
Sent from my EVO using xda premium
Why would it be a hard brick?? A kernel is part of the OS. It's not a firmware or a radio. If a kernel doesn't take, at worst, the phone will lock up. Use the battery pull equivalent to reboot the phone back into recovery and restore a previous image.
In pc terms, a kernel is not the bios. It's just part of the OS that lets the OS communicate with the hardware layer of the machine/device.
gpz1100 said:
Why would it be a hard brick?? A kernel is part of the OS. It's not a firmware or a radio. If a kernel doesn't take, at worst, the phone will lock up. Use the battery pull equivalent to reboot the phone back into recovery and restore a previous image.
In pc terms, a kernel is not the bios. It's just part of the OS that lets the OS communicate with the hardware layer of the machine/device.
Click to expand...
Click to collapse
I always thought a bad kernel would hard brick a phone. My bad. I stand corrected.
Sent from my EVO using xda premium
So any luck with that kernel?
Sent from my EVO using xda premium
Related
I'm planning on getting this device shortly & was wondering if the stock kernel will work with most of the roms developed here? I'm just trying to do my homework so I can be ready when I have it in hand. I'm so ready to ditch the g2x.
Sent from my LG-P999 using xda premium
TBH I haven't seen a stock kernel NOT work with a Custom ROM. The only thing is some of the features i.e. Wifi Calling may not work. So it's always best to flash the recommended to avoid boot loops or bugs.
I just looked at four of the most popular ROMs, and in less than five minutes read that only one of them said stock kernel was ok. The other three say to flash either faux's kernel, xboarder's newest kernel, or the included boot.img in the download.
But yes the stock kernel will work but like just mentioned it will have limited functionality. In my opinion, read what the dev says in their OP and throughout their thread, but a whole thread on this isn't necessary.
I don't mean to be rude, just saying it like it is. Welcome!
Sent from my HTC_Amaze_4G using XDA App
Thanks for ur replys guy's. I have always used the stock kernel with every rom on every device I've used. I'm new to flashing kernels & every time I tried flashing a kernel I've always had issues. Thanks again for ur answers.
Sent from my LG-P999 using xda premium
I wonder how this thread's topic relates to development...
Okay let me clarify the whole kernel thing.
We have three types kernels to chose from.
The stock OTA kernel. That's what your phone comes with. It is secured which means it will not allow scripts to auto-start (which means that init.d is worthless) and does not default with superuser access from adb or terminal. You can still get root access but you always need to do "su" command.
The unsecured kernel. This is the kernel that comes with your rom. This is commonly found in the zip file of the custom rom that you download. The custom rom DOES NOT (which also means DOESN'T, WON'T, WILL NOT, CAN'T and CAN NOT) update the kernel by recovery like almost all the other phones do. We believe this is because we have bootloaders with S-ON. When or IF we get s-off we may be capable of flashing a kernel by recovery.
Faux123's kernel.
Refer to [Kernel]HTC Stock[2.6.35.13](v0.0.7)OC~1.73/UV/CIFS+UTF-8[Dec-30]
Q&A
But can't we flash Faux's kernel by recovery?
Yes and no. I developed a workaround to make that work however it doesn't directly flash the kernel from the recovery. It flashes the kernel after the phone has already booted which is why a second reboot is required.
Well... why not? I don't understand.
Unfortunately since the phone MUST come to a complete boot from a kernel that initiats init.d scripts (unsecured kernel as described above), we cannot use the above method going from a pure rooted OTA rom or when going from SenseUI 3.0 to SenseUI 3.5 or ICS roms. Let me know if you're confused by this.
Alright... so can you tell me more about Faux's kernel?
Well since I'm not Faux123 I'll try to answer this.
It's a slightly modified version of the unsecured kernel (capable of executing init.d scripts) that has been tweaked to allow slight over clocking and control over the voltage going to the CPU and RAM of the phone. This can help you or hurt you. You can push your processor harder and faster to increase performance but you may lose stability and drain your battery faster. Alternatively you can reduce the voltage and preserve battery life. At this time the kernel is NOT complete due to HTC not releasing the full source of their TI drivers. It would appear that since it is not technically their drivers, they don't have to release it.
So... what's the problem making the kernel?
Faux123 tried to make the kernel from source, unfortunately without the full source attempting to do so will lose wifi and wireless tethering abilities. Again... blame HTC for that. Until they release the full source we're stuck with this limitation.
So all this talking about kernels you still haven't explain how to flash it?
This part is easy.
Use this: [Guide][Tool] Kernel Flasher 2 Step/Kernel Restore Tool||Noob Proof||V3 released || or whatever directions are included with the ROM or kernel that you're interested in flashing. If you're skilled enough you can just use the fastboot commands.
From bootloader:
fastboot flash boot c:\directorytoboot\boot.img
(replace c:\directorytoboot with actual directory)
So in conclusion... as soon as HTC releases s-off for our devices as well as the full kernel source code we can have some really kick @$$ phones! Until then... we have to [email protected]$$ everything such as fastboot flashing our half-a$$ modified kernels. It's not the rom or kernel developers fault... it's HTC's.
Felinos11 said:
I wonder how this thread's topic relates to development...
Click to expand...
Click to collapse
Yeah yeah... I'll move it.
Thank you binary for your excellent explanation. I posted it here because the people with the knowledge frequent this board & hope they would see it. I apologize if I posted this in the wrong place.
Sent from my LG-P999 using xda premium
Binary100100 said:
Yeah yeah... I'll move it.
Click to expand...
Click to collapse
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Stock kernel works fine.
seansk said:
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Click to expand...
Click to collapse
Go choke on some nitrous.
Binary100100 said:
Go choke on some nitrous.
Click to expand...
Click to collapse
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
seansk said:
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
Click to expand...
Click to collapse
I'll try it while at the range. The range masters should love that.
Binary100100 said:
I'll try it while at the range. The range masters should love that.
Click to expand...
Click to collapse
Hmm...I don't know if those two will mix well!!!
Hi Everyone I Want To Test ROM's Before Flash ON My PC So Please Help Me
You can't....
Sent from my GT-I9300 using XDA Premium HD app
Most roms have a video by TotallyDubbed
Sent from my GT-I9300 using xda premium
Hi,
Just made a Nandroid backup of your current rom then flash the new rom you want and if something is wrong or you don't like it... just restore your backup...
You can do that for all the rom you want to test, it is much simpler
That way you can really test on your phone... Even if it were possible on a PC, you can imagine that if you could test it on your pc it would not be comparable to test on your phone.
I Read That Triangle Away Is Very Dangerous Is There Another Way To Reset Flash Counter? I Heard That USB Jig Is Not Working For GS3
I Heard That USB Jig Is Not Working For GS3
Click to expand...
Click to collapse
It does work, in the way it was intended to do and does across all Galaxy devices; to revive a semi-hardbricked phone by making it enter Download mode.
I Read That Triangle Away Is Very Dangerous
Click to expand...
Click to collapse
Everything that flashes ROM's or works on the formatting of the device's internal storage is dangerous. I have yet to see someone who caused his device to hardbrick by using the app according to it's description.
It only modifies a value in the NAND, nothing much that can really go wrong. A risk always exists with all changes and updates.
Is There Another Way To Reset Flash Counter?
Click to expand...
Click to collapse
Nope
THE.W!ZARD said:
I Read That Triangle Away Is Very Dangerous Is There Another Way To Reset Flash Counter? I Heard That USB Jig Is Not Working For GS3
Click to expand...
Click to collapse
If you're that worried about bricking or avoiding the flash counter... why are you even trying to flash custom roms?
This is a development forum, I'll be the first to admit I have no idea how to develop anything apart from a deep hatred towards in-your-face vegetarians but at least I have a vague idea of what I'm doing, what I can do, and what I really shouldn't even think of doing. I got that from many hours lurking and searching these forums, try it some time.
Sent from my tricked out AOKP GT-I9300
spamcakes said:
If you're that worried about bricking or avoiding the flash counter... why are you even trying to flash custom roms?
This is a development forum, I'll be the first to admit I have no idea how to develop anything apart from a deep hatred towards in-your-face vegetarians but at least I have a vague idea of what I'm doing, what I can do, and what I really shouldn't even think of doing. I got that from many hours lurking and searching these forums, try it some time.
Sent from my tricked out AOKP GT-I9300
Click to expand...
Click to collapse
Because Some ROM's Have Better Performance, Fixing Some Bugs And Bringing Early Updates
d4fseeker said:
It does work, in the way it was intended to do and does across all Galaxy devices; to revive a semi-hardbricked phone by making it enter Download mode.
Click to expand...
Click to collapse
So To Avoid Risk I Should Buy Jig
THE.W!ZARD said:
Because Some ROM's Have Better Performance, Fixing Some Bugs And Bringing Early Updates
Click to expand...
Click to collapse
And you would test all this on a pc how?
It's so ridiculously easy to flash roms these days just flash some and try them out, if nothing bugs you about it tadaa, daily driver.
THE.W!ZARD said:
So To Avoid Risk I Should Buy Jig
Click to expand...
Click to collapse
If you do things right you shouldn't need one, I'd say don't buy it till you need it.
THE.W!ZARD said:
So To Avoid Risk I Should Buy Jig
Click to expand...
Click to collapse
I would, for 2 bucks you might as well, and then if anything goes wrong you don't have to wait to sort it. Having said that in 2 years of flashing and beta testing I have never needed one.Your choice, but flashing this device is simple if you do the necessary reading and follow the guides
Sent from the asylum
It's About If I Want To Reset The Flash Counter To Avoid Warranty Lose That's It. I Flash Omega ROM Before And Flashed Stock ROM Again And Reset Flash Counter Using Triangle Away But I Update The Mobile So It's Not To Use.
How To Restore Stock Kernel?
THE.W!ZARD said:
How To Restore Stock Kernel?
Click to expand...
Click to collapse
Reflash your rom without wiping data.
Sent from my tricked out AOKP GT-I9300
I Really Appreciated Your Help @spamcakes @slaphead20
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
NATO556 said:
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
This is not that it can't be done, but it the case of ics for the 4.0, it's a bug in the kernel that force us to flash a kernel from heimdall. If this bug was not here, the rom would be simply flashed with cwm. So the answer is it's not because dev don't want to do it like this, it's because they can't.
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
NATO556 said:
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
ti-pich said:
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
Click to expand...
Click to collapse
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
ti-pich said:
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
Click to expand...
Click to collapse
Well, that's part of it too. I think on the 4.0, the problem may be more complicated than that, due to it's storage layout, (I have the 5.0) but rest assured the devs are working on it.
Please let me know when they fix this bug what I need to do from there.
Sent from my YP-G1 using xda app-developers app
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
There's this but mostly because we change the partition (we completely ditch the j4fs support). Also the bootloaders expect to run BML/STL partitions so the bootmode isn't cleared. The thing that teamhackung made is that they created a partition named reservoir that would handle all the bad blocks. This partition is used to flash the boot partition which is the kernel one. This is still an undergoing experimentation for me but I'll try to compile a CM9 with this new type of flashing. An example of the partition layout is here:
https://github.com/CyanogenMod/andr...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
I may miss some things too but this is the things simplified.
Also NATO I do know how you feel about it and I'm trying to do my best (with han and oisis gone) to solve everything as soon as I can. (Don't forget that I have school too )
Sent from my Nexus 7 using Tapatalk HD
Actually most of the GB ROMs for the 4.0 are CWM flashable zips,
http://forum.xda-developers.com/showthread.php?t=1834375
http://forum.xda-developers.com/showthread.php?t=1718339 (older versions)
http://forum.xda-developers.com/showthread.php?t=1821860
http://forum.xda-developers.com/showthread.php?t=1895629
http://forum.xda-developers.com/showthread.php?t=1884557
http://forum.xda-developers.com/showthread.php?t=1719685
http://forum.xda-developers.com/showthread.php?t=1759949 (several ROMs)
http://forum.xda-developers.com/showthread.php?t=1825281
there are 2 or 3 more ROMs that are CWM zips but there based on the OLD CM7 port and with no deep sleep there not worth the time IMO (not the Porting DEVs fault, it was a known issue of the CM7 base).
NOT ENOUGH FOR YOU?
The ones that aren't are because of data corruption issues.
As for ICS, well thats been covered.
Thank you guys for all you do. I really am thankfull to have a website like this one to turn to for help.
Sent from my YP-G1 using xda app-developers app
As soon as the glitch is fixed please let me know. Another question, will there ever be an official CWM release on the player? And will Tardis_Balor update the Terra Silent Kernel once the glitch is corrected?
Sent from my YP-G1 using xda app-developers app
Also, why is hanthesolo's ethereal tomorrow not on this list?
Sent from my YP-G1 using xda app-developers app
rom*
Sent from my YP-G1 using xda app-developers app
BTW, the link for v2.0 of Icy Fusion is dead.
Sent from my YP-G1 using xda app-developers app
Hi,
Was wondering...is there a stock rom thats floating around for AT&T US....im new to the rom, kernel scene...and im wondering how I get a complete backup of my device if I want to go back to the stock rom that came with the US version of the HTC one...I keep hearing about a nandroid backup..will that work...and if i backup..and go back to stock rom...do i void my warranty..also..i see a rom called the clean rom which i think would fit my needs...but there is also a kernel out there called bulletproof...is the kernel and the rom two seperate things..im confused..always thought they were one in the same..sorry for the stupid question...can i use bulletproof kernel with the clean rom? and how would i go about getting that kernel on there..if so..thanks..for your time...
Kernel and rom are different. Imagine the kernel as the engine of the car and the rom is the body. Read around the dev section for different rom features to find the one that suits your needs. Be confident in what your doing before getting flash happy so ya dont mess up yur device
Sent from my HTC One using xda premium
Bladerunner1825us said:
Kernel and rom are different. Imagine the kernel as the engine of the car and the rom is the body. Read around the dev section for different rom features to find the one that suits your needs. Be confident in what your doing before getting flash happy so ya dont mess up yur device
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks bladerunner....i am taking it extremely slow...i dont need a device that doesnt work...lol...i just wanted to know if there was somewhere on
the web that had stock rom's used by AT&T for the HTC one so if i messed up...i could reinstall it...
abacus0101 said:
Thanks bladerunner....i am taking it extremely slow...i dont need a device that doesnt work...lol...i just wanted to know if there was somewhere on
the web that had stock rom's used by AT&T for the HTC one so if i messed up...i could reinstall it...
Click to expand...
Click to collapse
There are nandroid backups you can flash in recovery that will bring you back to stock. It's always a good idea to make your own backup before flashing anything.
Sent from my HTC One using xda app-developers app
Long story short, I hard bricked a Nexus 4 flashing a bad ROM. So now I have a new one, and I want to know if there is a way to check if a ROM is bad for my phone before I flash it. If a thread on xda says, this ROM is for HTC one, does that meadoit is only safe for THAT phone, or is anything that is JB 4.2.2 and up safe for my nexus 4? Just want to make sure before I start flashing ROMs again. Thanks.
Bro answer is a big No!!
You cannot directly flash a rom of a device on other one.
Coz every device have different hardware configurations and a rom contains different things to control hardware like bootloader and kernel that are chipset specific and using the one on other device can/will lead to a hard brick!!!
Though u can use files from different roms system partitions and try them on your device!!
Hope this helped....
Sent from my C1904 using xda app-developers app
Droidlover123 said:
Bro answer is a big No!!
You cannot directly flash a rom of a device on other one.
Coz every device have different hardware configurations and a rom contains different things to control hardware like bootloader and kernel that are chipset specific and using the one on other device can/will lead to a hard brick!!!
Though u can use files from different roms system partitions and try them on your device!!
Hope this helped....
Sent from my C1904 using xda app-developers app
Click to expand...
Click to collapse
Thanks man, really appreciate it.
Just search for roms specifically made for your phone, make a nandroid back-up, wipe it and than flash the rom. Normally there shouldn't be as many problems then.
Have fun!
sinndissension said:
Long story short, I hard bricked a Nexus 4 flashing a bad ROM. So now I have a new one, and I want to know if there is a way to check if a ROM is bad for my phone before I flash it. If a thread on xda says, this ROM is for HTC one, does that meadoit is only safe for THAT phone, or is anything that is JB 4.2.2 and up safe for my nexus 4? Just want to make sure before I start flashing ROMs again. Thanks.
Click to expand...
Click to collapse
You cant flash ROM to your device as it is made for other device . You can find many custom ROMS for your device. just google it and dont flash before reading its review.
also check MD5 checksum before you plan to flash that downloaded ROM