THIS SOURCE WILL WORK ON ALL CURRENT HTC EVO'S!!!
i found the board files for the EVO a while back but wanted to wait til we at least had the release RUU to release it. now the actual kernel itself isnt a EVO kernel. its actually an Incredible kernel source with the EVO board files in it. that said i had to mod the board files a little to get it to compile. anyhow link below and remember to fork as it helps github and everyone. thanx
GoDmOdE-EVO
Commit log:
Sat May 22, 2010 - First-commit-0_o = first commit
Sat Jun 19, 2010 - Fix the wimax LED, capella prox sensor. Add epson panel support for supersonic
(panel_type=0), which is present on
hardware revision 3. Implement 9bit spi. - by Joe Hansche (maejrep)
Sun Jun 20, 2010 - Add some more epson vs novatec fixes - by Joe Hansche (maejrep)
Mon Jun 21, 2010 - Fix proximity sensor and Implement wimax LED control. These commits also fixed issues with all other sensors, and enabling them to all work!!! - by Joe Hansche (maejrep)
THIS IS A UPDATE.ZIP THAT CAN BE USED WITH FRESH ROM, TO BOOT THIS KERNEL WITHOUT WIPING. PLEEEEEESE DO A NANDROID BACKUP BEFORE FLASHING THIS UPDATE.ZIP. SO U CAN JUST NANDROID RESTORE UR DEVICE BACK TO NORMAL AFTER UR DONE PLAYING . ANYHOW CAMERA IS NOT WORKING AND THERE SEEM TO BE WHATS THOUGHT TO BE VSYNC ISSUES. ANYHOW ENJOY!!!
http://link.geekfor.me/godmodefreshhh
of course dont turn this thread into a this is broke can u please fix it thread.
IF U WOULD LIKE TO HELP OUT OR BUILD UR OWN KERNEL FROM THIS SOURCE, PLEASE FORK. THIS IS ADVISED BY GITHUB AND ALSO BY ME. AS IT MAKE PULLING CHANGES TO AND FROM BRANCHES MUCH EASIER. THIS IS A GOOD THING FOR U AND ME. IF I MAKE A COMMIT U WANNA ADD U CAN EASILY SYNC UP WITH ME AND VICE VERSA. WORKS OUT GREAT FOR EVERYONE AND KEEPS US COMPLETELY OPEN, AFTER ALL WERE ALL ON THE SAME TEAM.
ToAsTcFh For MOD!!!! This is genius
Im a little too buzzed atm. What exactly is this and what does it mean for us? explain and ill understand it in the A.M.
Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it
chuckhriczko said:
Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it
Click to expand...
Click to collapse
how're you getting your evo today??
so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.
justinisyoung said:
how're you getting your evo today??
Click to expand...
Click to collapse
Ebay? Craglist?
ppl from the google i/o event selling them
YoungAceAtlanta said:
Ebay? Craglist?
ppl from the google i/o event selling them
Click to expand...
Click to collapse
Yep. eBay. It's a Google I/O device. Paid a HEFTY premium for it but it's worth it to get it two weeks early for me.
toastcfh said:
so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.
Click to expand...
Click to collapse
Awesome. Who else that you know of? I know I stopped devving for the Hero but I can't wait to start devving for this thing. This community is going to be epic!
Right on toast, this is awesome.
fantastic toast
can this kernel be loaded onto one of the google I/O event EVOs to test?
The device isn't root yet
toastcfh said:
The device isn't root yet
Click to expand...
Click to collapse
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?
joeykrim said:
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?
Click to expand...
Click to collapse
No. You can't flash anything worthwhile until the phone is rooted. Once this happens expect this forum to explode.
No we need root and the ability. To flash a custom recovery. Basically. The catch 22 is we need root before we can do anything custom
By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?
Shidell said:
By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?
Click to expand...
Click to collapse
we're thinking alike here. some of this terminology is new to me and some isnt. hopefully this makes sense. im gonna reword but ask the same question as above (at least i think same question) plus another question. im doing a lot of research and tryin to word things correctly...
this might be the same question as above, are we able to trick the supersonic RUU released here into loading our own rom.zip file (NBH)? (we were able to do this with the samsung moment)
if not, are we able to use the fastboot-bootloader mode (samsung moment doesnt have this) to install a custom recovery? if so, we are then waiting on a custom recovery to be developed?
I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)
Shidell said:
I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)
Click to expand...
Click to collapse
ok.. the bootloader isnt gonna let us flash anything that isnt for the phone that ive heard of at least. the bootloader is only gonna let us flash rom.zips signed by htc unless we have a engineering spl. if we had that we could fastboot whatever we want. but it is also my understanding that the new engineering spls will not let us flash to certain major partitions (ie rocovery, and boot) anyhow this i think was an issue for the desire that modaco rooted and he found a way around it. we need a recovery for sure. as starting a new with no backups and such would be nothing more then a pain. we should focus i think on obtaining a engineering SPL from someone nice who wants to hook us up or a exploit of some sort. we need to gain read/write access to system, boot and recovery partitions. we do that and we can do what we want with the device. were not gonna be able to just flash a kernel, boot.img, system, or update.zip thats not official without the ability to gain access to the recovery partition.
in an exploit we would have root user status and we would have write perms on system at that point we could possible add flash_image to bin, chmod it and use that to flash a new recovery. write access is all we need. if ur idea was possible all we would need to do is flash a distro with root access and then flash the recovery partition with a custom recovery. a custome recovery will give us the ability to flash, backup and restore whatever we want. so long story short we need root user status in any event so we can gain access to recovery partition.
Let me start by saying I am not completely new at this now and have unlocked, rooted, and installed some custom firmware (or is rom the preferred term?) on a few other more popular brand devices. Being as they were popular that made it super easy to find information, tutorials, and files. While I understand the basics of all the things I was doing and have learned a lot about using ADB and fastboot for instance I am still a bit lost on a couple key items.
So I recently however bought an iRulu V1 phone off of Amazon. While I was able to resolve how to root the device, which I can post about if anyone is interested, I can't seem to find enough information about custom recovery and roms. So here are some basic questions I have, which again I guess I should know since I dove in head first on my other devices, but I am still not sure when it comes to these things and really should understand them
1) Do I need a version of CWM or TWRP made for this device specifically or is there some generic that works for any device?
My device came with KitKat 4.4.2 no upgrade available form manufacturer currently to 4.4.4 or any update for Lollipop. I would love to install the latest version I can of course.
2) Similar to question #1, Is a custom rom needed to get any higher version of Android or can some generic version be installed?
3) On both question above, where does one begin to locate these generic or standard versions?
4) If there are generic versions of the recovery and/or Android rom, What are some of the caveats I might run into using them? More meaning what features might simply just not work?
5) I cannot find an image of the rom included with my phone from the manufacturer, What application or process could I use to be sure I have a complete backup I could restore should I do something stupid?
I tried an ADB backup and the image it created seemed way off in size even though I was using what I thought were proper parameters to get everything including the system.
I really have these questions as I still think of Android like one would of Linux for instance. If I have a computer Linux can run on, I can usually find a very generic ISO to get the OS installed and customize from there. I guess that is really what I am trying to do here, get as updated a version of Android as I can and then make everything work by loading modules or drivers as needed. I guess finally, Is that not really how it works with the Android OS ?
thanks so much for any answers or insight. I have thus far like many others found the info here invaluable while playing around with my various Android devices I have. I hope too that my post is falling into the proper format requested by this section, apologies if not.
LT
Hi, thank you for using XDA Assist. You're right, there is no information about your device on XDA. In general, only flash recoveries or roms that are specific to your device. There are no general ones. Flashing something that is not specific can brick your device. Your best bet is to ask specific questions about your device here, http://forum.xda-developers.com/android/help and hope someone else with your device can help.
Sorry I can't be of more help.
Thread closed.
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
CamShirayuki said:
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
Click to expand...
Click to collapse
The model number seems to be the AT&T version of that phone.
When you say that you can't get it booted, what do you mean exactly? What is the device doing when you try to boot it?
Have you tried holding volume up+power(let go when you see the splash screen) to boot into recovery, then factory reset and wipe cache partition?
Some devices have to hold volume down+power, then at the bootloader menu, choose the recovery option.
Sent from my LGL84VL using Tapatalk
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
CamShirayuki said:
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
Click to expand...
Click to collapse
I think you need to do some research to get familiar with how android devices actually work. Android devices are not like PC, you can't just install whatever OS you want, android devices are not "generic" like that. Operating systems for android devices have to be built specifically based on the hardware in the device, down to the kernel level, the kernel has to be specific to the device. You need to do some reading about how android stock recovery and custom recovery actually work , you also need to research how android stock firmware and custom operating systems are flashed on android devices.
It is "possible" to remove android and install Linux on an android device, but only certain devices can do it, depending on the security built-in to the bootloader that is installed on the device. There isn't a universal way to install Linux on android.
It is also possible to install Linux on top of android in a sort of emulator/VM then use a VNC to .
There are some apps to install linux on top of android, such as:
1) Linux Deploy
2) Complete Linux installer
3) UserLAnd
I installed and tested UserLAnd last night. Try this and see what you think.
https://github.com/CypherpunkArmory/UserLAnd
View the README.md for instuctions to set it up.
Sent from my LGL84VL using Tapatalk
Ok, so I've successfully built Android 8.1 and my devices kernel from Samsung open source.
My issue is, previously, I've only built AOSP for my Nexus. Flashing on a google device is simple because of fastboot, but Samsungs use Odin or Heimdal. I've used Odin/Heimdal to flash Samsungs before, but the roms come packaged in a tar.gz or other format.
I tried using Heimdall to pack up the .imgs, but it hasn't gone to plan yet.
Any help would be appreciated, I've had this android build sitting in a VM for like a month now, lol. It'd be nice to clear out that 150 or so gigs, lol.
which device you have
do you have twrp for your device
It's a 2016 Tab A with s pen. SM-P580. And yes, TWRP is already in the device.
Can I flash the system.img from TWRP? Didn't think of that till now.
Also, I know I can package the kernel and flash it there, but not 100% sure how to.
I'm interested in building an updated, de-googled, de-bloated, ROM for a TCL A30 , model TCL5102D, mt6762/6765. First off was whether to post in tha Alcatel Section. My understanding is that Alcaltel is no more and those phones are now marketed as TCL. Prior Alcaltel posts may be helpful - perhaps the moderators could rename the section "Alcaltel/TCL" rather than adding a New TCL section.
I fouund mtkclient in the forum and it works on my device. I have not TWRP rooted it yet but have pulled boot.img, vbmeta.img and the entire system image. I have also found the TCL source code site, downloaded an earlier device with Mediatek Helio 22P chips and adb pulled /proc/config.gz. GPL source for my specific device has yet to be published by TCL.
I've yet to pull the vendor blobs and have only found guides in the Lineagos documentaion. It's pulling from a zip'd image rather than a device and TCL does not have images for any of their current phone. Also could not find a dump for this particular phone.
My first challenge is trying to build the kernel. The TCL source code, kernel 4.19.127, is not structured like the AOSP kernel source and aarch64, gcc builds hang up on the lcdscreen driver. The screen driver was backported in later 4.19.x versions which built with the config.gz and upstream kernel.org source.
What I'd like to do is to do is update the TCL source to the latest stable 4.19 code base but my web searches have not come up with any examples on how to do this. Could also build with the AOSP 4.19-stable source with the pulled config.gz - chances that it would work?
If I can prebuild the kernel, then make a decision in regards to a LineageOS build vs a GSI build. Maybe even build within GrapheneOS (uses prebuild kernels).
Where, in the forum, should I start the line of questions? Can anybody point me to a guide on howto build an kernel with an up-to-date source?
hi, your best place to go would be here and here
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
danvep5014 said:
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
Click to expand...
Click to collapse
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
971shep said:
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm working on how to get the device to be recognized in mtkclient. Regardless of what button combination I use, the device fails to be recognized. Any specific way it needs to be done on the TCL A30?
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
danvep5014 said:
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
Click to expand...
Click to collapse
I start mtkclient with the phone connected via usb but powered off. Mtkclient messages that it is trying to establish a connection. Then just power up with the power key only. You should get messages that you connected in brom mode.
I was finally able to get it. Had to use adb reboot edl. Did the trick. Now I'm trying to build a rom with oxygen os but i keep getting stuck in a boot loop.
Boot loops can have many causes.. In the case of a custom rom, it is often that boot verification of the file systems fails, ie a file system checksum is different. In the thread I linked above, the way around this was to overwrite the three different vbmeta.* files with a blank file..