Related
I'm about to be coming over to the LG Optimus T world here in the next few days. I'm coming from a T-Mobile myTouch 3G 1.2 (the one with the headphone jack). I've been messing with rooting for about 8 months now and have put up two guides in the myTouch section of these forums as well as provide daily help. I've already got rooting and installing a custom recovery on this phone down by reading through the forum and will surely get flash happy with the ROM's over the next few weeks. My question is this: is there anything else I need to know? Such as, are there different radio/bootloader versions for these devices? The myTouch has around 12 different bootloader/radio combinations. Is this the only recovery available? I may have to see if I can get a guy from the myTouch forums to theme it out a little. Either rate. If there's nothing else that I need to know to do, is there anything that should never be done with this phone?
I think Clockwork works, but I haven't tried it yet. I'm afraid of bricking my phone, so I just stick to the recovery you linked to.
Miscellaneous stuff:
- "axis inversion" issues with the touchscreen
- touch screen cpu spike, but already fixed by mik_os (from 100% cpu usage to somewhere less than 30%)
- random sdcard unmounts: haven't had this issue in a long time. this used to be very much talked about a few weeks back.
- there's already a working gingerbread rom (cm7 port) but the gps and camera doesn't work yet. also, ui is a bit slow.
I'll update this when I realize I have forgotten something
is there anything that should never be done with this phone?
Click to expand...
Click to collapse
The only thing I know of is drellisdee's warning of not flashing a radio.img from the recovery
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
DonJuan692006 said:
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
Click to expand...
Click to collapse
ClockworkROm has been ported to P500 i have installed it but haven't created any backups or flashed some ROMS
Is there anything like Odin for HTC phones (Android) like the Thunderbolt (lets just say Desire HD)?
I'm thinking of switching because of the cheap plastic and because of the antenna on all 3 of my fascinates. Also, the only reason I got this phone is because of the unlocked bootloader.
Also, are there great developers that are going to work on the Thunderbolt (like we have here)?
Additional question: Assuming that the Thunderbolt is the same price on contract as the Fascinate, is it possible to replace the Fascinate with the Thunderbolt (with all of the problems I have)?
There's nothing like ODIN on the Thunderbolt, although the overall flashing and things on an HTC device should be easier than a Galaxy S. The likely of the Thunderbolt having a lot of devs is high, because I'm assuming that as the next Verizon HTC device, many Incredible devs will migrate to it.
What do you mean by replace?
TheSonicEmerald said:
There's nothing like ODIN on the Thunderbolt, although the overall flashing and things on an HTC device should be easier than a Galaxy S. The likely of the Thunderbolt having a lot of devs is high, because I'm assuming that as the next Verizon HTC device, many Incredible devs will migrate to it.
What do you mean by replace?
Click to expand...
Click to collapse
By replace, I mean trade in for a new device. I bought it at Best Buy if that matters.
EDIT: By Odin, I mean flashing completely to stock if anything goes wrong, or if I just want stock sense again.
If your on a contract, you can't just trade your device in for a new one. Though, Best Buy's Buy it Back program might let you if you applied for it, though I don't know the exact details. If you buy just the device for the full price, you can switch the phones on your contract by deactivating your Fascinate and activating your Thunderbolt.
HTC has a program called HTC Sync that flashes the RUU, or the stock firmware, onto your HTC device. Though, I don't think you will need to flash the RUU at all with the Thunderbolt unless you need to return to stock as it doesn't have Voodoo or the things that mostly cause brick problems for the GalaxyS devices and most of the things you can just flash the stock firmware rom zip to fix problems.
TheSonicEmerald said:
If your on a contract, you can't just trade your device in for a new one. Though, Best Buy's Buy it Back program might let you if you applied for it, though I don't know the exact details. If you buy just the device for the full price, you can switch the phones on your contract by deactivating your Fascinate and activating your Thunderbolt.
HTC has a program called HTC Sync that flashes the RUU, or the stock firmware, onto your HTC device. Though, I don't think you will need to flash the RUU at all with the Thunderbolt unless you need to return to stock as it doesn't have Voodoo or the things that mostly cause brick problems for the GalaxyS devices and most of the things you can just flash the stock firmware rom zip to fix problems.
Click to expand...
Click to collapse
I am not registered for the buy it back program. Also, does the RUU flash recovery, stock boot logo (param.lfs on Fascinate), boot loader, etc.?
HTC uses the RUU and it will update the device based on what is included with the RUU. It would be similar to odin packages for SGS phones, you can include everything or just one thing in the flash package. Most times though, I feel like you're going to want a full RUU package when you need it.
imnuts said:
HTC uses the RUU and it will update the device based on what is included with the RUU. It would be similar to odin packages for SGS phones, you can include everything or just one thing in the flash package. Most times though, I feel like you're going to want a full RUU package when you need it.
Click to expand...
Click to collapse
Can I open the RUU's in 7-Zip to see what's inside?
Is it possible to run Droid charge rom, modem and kernal on fascinate? I ask because I was a htc hd2 owner and they were able to install any htc rom on htc hd2 using maglrd. Since Droid Charge part of samsung family just inquiring if it's possible.
interpol909 said:
Is it possible to run Droid charge rom, modem and kernal on fascinate? I ask because I was a htc hd2 owner and they were able to install any htc rom on htc hd2 using maglrd. Since Droid Charge part of samsung family just inquiring if it's possible.
Click to expand...
Click to collapse
I don't actually know but every bit of my being says NO! Samsung's hardware is probably second to none. But, that's about the only thing Samsung is good for and that is also the reason I own a Samsung phone. But, as far as compatibility, support, or being developer friendly, Samsung sucks!!
Sent from my SCH-I500 using Tapatalk
You may be able to get the ROM to work, but that would be it, and it also wouldn't be a direct transfer, you'd need to change some stuff like they do to get Fascinate ROMs working on the Mesmerize. The kernel would only partially work, and I think the modem is different as well.
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
I wanna know too...
bump.
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
HMZX said:
I wanna know too...
bump.
Click to expand...
Click to collapse
I think you can definitely test w/o causing permanent damage. For the smoothest test experience, you'll want to be familar with a custom recovery and the backup/restore modes available along with the type of internal memory unlock used on the device (Revolutionary or HTC official method).
Once you're familar with the basics, it would be fairly simple to test. The combinations for testing, off the top of my head, would be:
1) Sensation kernel and EVO 3D ROM.
2) Sensation kernel and Sensation ROM.
3) EVO 3D kernel and Sensation ROM.
Speaking from experience, once you're familar with how to load kernels and ROMs, the process is fairly generic across devices once write access to the internal memory is obtained.
Again, I'll re-iterate the importance of making a proper backup and being familar with the restoration process.
There are only two main hazards which come to mind:
1) Make sure NOT to flash the radio, bootloader, or any other file. ONLY flash kernel/system partitions.
2) Before flashing kernel/system partitions ensure the partition sizes between devices are the same, or EVO 3D is larger. Not sure the device limits and stops partitions from overwriting each other as I know some older devices did not and this caused an unrecoverable damage.
I'm sure if I missed anything, somebody else will post up. Hope that helps provide some technical background and logic to the approach! Keep us updated!
Thanks for the reply. I'm already familiar with flashing kernels/roms and how to make a nandroid backup etc so that isn't a problem. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Yeah I have a GSM phone so that's why I said GSM. Also wouldn't porting to the GSM version be easier then to the CDMA version since the sensation is also GSM?
Anyways I'm kinda busy today but I will try to see if it boots on my phone tomorrow and post my results. I'll.also try to get the camera to work by copying libs like you suggested.
Sent from my HTC EVO 3D X515m using XDA App
vipirius said:
Thanks for the reply. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Click to expand...
Click to collapse
Answer to first question: partition sizes are generally mentioned in a handful of different locations depending on the device: /proc/partition(s), /proc/emmc or /proc/mtd off the top of my head. Since the devices are similar and others have already tried this approach, probably not a concern, but none the less never hurts to learn more!
Answer to second question: the cameras (2 of them for 3D) on this device, along with the 3D display are the two biggest difficulties in porting AOSP such as CM to this device, in my opinion. they use closed source proprietary code from HTC. this requires a bit of reverse engineering and kanging from other random sources in order to get a final working product. personally, i wouldnt invest the time/effort into it, but others might find it a beneficial endeavor for themselves. either way, you're guaranteed to learn a bit about cameras! as stated above, all android libraries are loaded in /system/lib.
For the camera, I view android as having essentially three components contributing to a fully functional camera.
1) Camera drivers in the kernel
2) Camera libraries in /system/lib
3) Camera application apk file for Android UI
These three need to work together to at least some degree in order for there to be some functionality in the camera.
Gumby63 said:
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
Click to expand...
Click to collapse
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
joeykrim said:
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
Click to expand...
Click to collapse
Well yeah it completely reboots back to the splash screen. During the bootanimation, I can't get a logcat and adb says there is no device connected. This isn't my first port but I've never had this happen lol. I'll look into what you said.
Sent from my HTC Flyer P510e using Tapatalk
Well, I successfully installed Android Revoltion HD 3.6.13, It boots, everything seems to work, however I didn't test GPS and BT yet. And the camera is well, half working I guess. The camera app opens, and i can see the controls etc but no image comes, and when I press the capture button the flash pops but the app FC's after that. I'm gonna try flashing [MOD] Camera from HTC Amaze 4G, v0.11 and see if it works. If it doesn't I'll copy over all the camera related libs I can find from my old ROM and see if it works then.
Edit: Hahahaha yessss it works I just flashed the Amaze camera app and now camera works only 2D of course but it's enough for me. I'll keep testing for a few days and of there aren't any serious bugs I can find I'll be using this as my daily driver from now on
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
vipirius said:
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
Click to expand...
Click to collapse
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
t3project said:
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
Click to expand...
Click to collapse
Yeah that's what I was going to do, but thanks anyways. I'll report back on my success.
Gumby63 said:
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Click to expand...
Click to collapse
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
im not sure what you read but IT WAS WRONG..........
while you can do some of this stuff from your phone, you can not do a complete port properly without a computer
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Gumby63 said:
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
vipirius said:
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
Click to expand...
Click to collapse
this is only patrialy the problem. flashing roms doesnt affect the radio so that wouldnt change but i there are some other libs that need to be moved that are associated with communication to the radio. cant remember which off the top of my head
Gumby63 said:
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Yeah I thought the article I read was Bull****! I wish I could remember where I read it to show you guys what it said but just can't remember for ****... Lol!
Well Thanks for Confirming guys...
Hello, since the Hox has much roms , and yes it's more supported, i was thinking , by searching with some guides here on xda , if porting a Hox rom on our Hox+ is possible?
clitoridys said:
Hello, since the Hox has much roms , and yes it's more supported, i was thinking , by searching with some guides here on xda , if porting a Hox rom on our Hox+ is possible?
Click to expand...
Click to collapse
no they have different processors so when installing the phone would crash causing a brick. brick is when the phone dosent turn on.
They are different devices , ask the dev to rewrite the rom for hox+ DDD
SomebodyEpic said:
no they have different processors so when installing the phone would crash causing a brick. brick is when the phone dosent turn on.
Click to expand...
Click to collapse
I tried this when I had my One V (I wanted Sense 4+ on it). This is complicated. I don't think you'll get any more than a boot screen (if that). Don't count on even this working though. Like the guy above said, the hardware is VERY different.
If you do port though, make sure you use Cyanogenmod as a base. But then again, why do it? It's much better to use a compiled ROM than a ported one.
hendrickson02 said:
I tried this when I had my One V (I wanted Sense 4+ on it). This is complicated. I don't think you'll get any more than a boot screen (if that). Don't count on even this working though. Like the guy above said, the hardware is VERY different.
If you do port though, make sure you use Cyanogenmod as a base. But then again, why do it? It's much better to use a compiled ROM than a ported one.
Click to expand...
Click to collapse
Sure but the Hox has more roms... i was thinkin that the devices was the same, except for the memory.
clitoridys said:
Sure but the Hox has more roms... i was thinkin that the devices was the same, except for the memory.
Click to expand...
Click to collapse
No totally I understand. Easy mistake to make. Still, you can try. Just use your version of HOX+'s CM 10 or 10.1 as a base for porting. Who knows, it might work. Beware of thus AT&T HOX+ though, as no one has gotten the call audio to work yet.
I mean the sense roms , not aosp/aokp
Inviato dal mio HTC Sensation XE with Beats Audio Z715e con Tapatalk 2
You misunderstand. If you want to port, you should use CM as a base. You put the X Rom on top of the CM layer.
Sent from my HTC One X+ using xda app-developers app
In addition to having different processors, the phones also have different modems I believe. The thread for Paranoid Android on the AT&T HTC One X+ has more details about why devs can't get voice to work in AOSP ROMs on the HOX+. For the One X as I understand it, devs could use the modem drivers from ICS builds to get them working in JB. But the HOX+ has never has ICS on it, and has a different modem than the International version to work on AT&T.