yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] chota_shivaji:
Hi All,

- I followed the procedure mentioned here to port HTC Official Desire 2.3.3 ROM to Nexus One.

- I dumped the original Desire 2.3.3 ROM. Then used this ROM http://xdaforums.com/showthread.php?t=995445 as source which is already ported to Nexus One.

- With this I am able to boot up till boot-animation after which the phone boot loops with following exception:

D/AK8973 ( 189): Compass Start

I/ActivityManager( 251): Sending system update to: ComponentInfo{com.android.providers.calendar/com.android.providers.calendar.CalendarUpgradeReceiver}

I/ActivityManager( 251): Sending system update to: ComponentInfo{com.google.android.gsf/com.google.android.gsf.loginservice.MigrateToAccountManagerBroadcastReceiver}

I/ActivityManager( 251): Sending system update to: ComponentInfo{com.android.providers.contacts/com.android.providers.contacts.ContactsUpgradeReceiver}

E/AndroidRuntime( 251): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy

E/AndroidRuntime( 251): java.lang.RuntimeException: Failed to register input channel. Check logs for details.

E/AndroidRuntime( 251):	at com.android.server.InputManager.nativeRegisterInputChannel(Native Method)

E/AndroidRuntime( 251):	at com.android.server.InputManager.registerInputChannel(InputManager.java:258)

E/AndroidRuntime( 251):	at com.android.server.WindowManagerService.addWindow(WindowManagerService.java:2028)

E/AndroidRuntime( 251):	at com.android.server.WindowManagerService$Session.add(WindowManagerService.java:6062)

E/AndroidRuntime( 251):	at android.view.ViewRoot.setView(ViewRoot.java:527)

E/AndroidRuntime( 251):	at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:177)

E/AndroidRuntime( 251):	at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:91)

E/AndroidRuntime( 251):	at com.android.internal.policy.impl.KeyguardViewManager.show(KeyguardViewManager.java:186)

E/AndroidRuntime( 251):	at com.android.internal.policy.impl.KeyguardViewMediator.handleShow(KeyguardViewMediator.java:1194)

E/AndroidRuntime( 251):	at com.android.internal.policy.impl.KeyguardViewMediator.access$700(KeyguardViewMediator.java:106)

E/AndroidRuntime( 251):	at com.android.internal.policy.impl.KeyguardViewMediator$2.handleMessage(KeyguardViewMediator.java:1054)

E/AndroidRuntime( 251):	at android.os.Handler.dispatchMessage(Handler.java:99)

E/AndroidRuntime( 251):	at android.os.Looper.loop(Looper.java:143)

E/AndroidRuntime( 251):	at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:647)

E/LightsService( 251): [LedErr] setLight_native light=8 fail, NULL pointer

E/LightsService( 251): [LedErr] setLight_native light=8 fail, NULL pointer

Full Logcat output can be seen @ http://pastebin.com/gQ4DC337.

- This thread http://xdaforums.com/showthread.php?p=13059602 talks about similar error. However, it is due to absense of com.htc.commonctrl.jar in BOOTCLASSPATH (basically boot.img not compliant with Sense). However, I dumped the boot.img I am using. Its init.rc has this .jar added into BOOTCLASSPATH. So I am stuck now regarding how to proceed.

Does anyone have clues for me to check?
[Android Software/Hacking General [Developers Only]] rjmohit:
Bootloop

Even I had the same problem. I am pretty sure I used the correct boot.img, actually I tried each one from a different source. Could you suggest some solution. My phone doesn't boot. It remains indefinitely on the splash screen. Nexus One.
[Android Software/Hacking General [Developers Only]] Jurellz:
What Will Your Base Be ? I noticed that you have two seperate roms, did you start with a rom and dump ? . . .
[Android Software/Hacking General [Developers Only]] fshami:
Anyone here who was successful in porting using this guide?
[Android Software/Hacking General [Developers Only]] romified:
Somewhat successful, but had to modify the procedure for some of the framework files. Of course this is because we're talking the Thunderbolt (LTE) which is a whole different animal. You can get roms to boot, but getting them to "work" becomes the issue, and usually it's data/wifi/bluetooth related.

The Thunderbolt is breaking ground for LTE porting. It often requires editing and modifying files in addition to moving them around.

A heck of a phone to learn this on !!

This is why you mostly are seeing new ROMs lately for the Thunderbolt that are being ported are from the very telented team over at BAMF. Eris and Adrenalyne (and the rest of their team) make this look like child's play, but of course there is actually hours upon hours of coding and reviewing logcats to make it all happen.
[Android Software/Hacking General [Developers Only]] fshami:
Aside from framework modification, this procedure worked well?
[Android Software/Hacking General [Developers Only]] romified:
Yes, it got me to where I could at least boot into the rom and then use logcat to troubleshoot futher.
[Android Software/Hacking General [Developers Only]] Will972:
well i made the port but i'm suck on white screen and green htc .. i'm trying to port sense 3.5 from sensation to evo 3D ..

any ideas ??
[Android Software/Hacking General [Developers Only]] Mattix724:
I would like to try porting a sense rom from an older device, I have the Kyocera Zio M6000... yeah it probably won't even boot, but from what I've seen in the Zio source code it seems to built from some HTC sources. Is there any HTC sense phones with an ARMv6 msm7627 cpu with adreno200 gpu?
[Android Software/Hacking General [Developers Only]] Will972:
if someone know what file i must replace to fix the recording in camera :) ..

it's for evo 3D camera's
[Android Software/Hacking General [Developers Only]] fshami:
You got the ROM booted with steps from the first post?
[Android Software/Hacking General [Developers Only]] adakaya1994:
i did some ports desire hd to desire z but mobile network not working (no signal) any ideas?
[Android Software/Hacking General [Developers Only]] atoore:
Replace libhtc-ril.so and any libs that got ril on it to fix the data. As for recording, replace mediapeofiles.xml inside etc with your device's one and libomx*.so inside system/lib..

Hope that helps.
[Android Software/Hacking General [Developers Only]] fshami:
Followed every step & my DHD got stuck at splash screen..

Trying to Port Pyramid 2.3.4 for my DHD.

I've also attached dmseg & adb log
[Android Software/Hacking General [Developers Only]] adakaya1994:
Thanks i will try :)
[Android Software/Hacking General [Developers Only]] sharkie405:
I didn't look at your posted logs, but did you already try trimming the ROM down? In my noob experience, my ROMs wouldn't boot up until I trimmed them down. You could add "data/app" functionality to the ROM and try removing apps that you don't need. Zipaligning and deodexing your files may help as well.

I'm no expert though, these are just some thoughts from my own personal porting experiences. :)
[Android Software/Hacking General [Developers Only]] fshami:
Ahan so u were successful in porting ROMs by this guide. Nice...

Yes, i removed several apps to fit system partition, deoxded, zipaligned n all..

If you can look into the logs i attached in my last post & tell me ur expert opinion ;)

Thanks bud
[Android Software/Hacking General [Developers Only]] sharkie405:
Well F you then.
[Android Software/Hacking General [Developers Only]] rocky869:
plzzzz Someone tell me which sense rom should I try to port in ZTE blade???
[Android Software/Hacking General [Developers Only]] Will972:
yes but the rom have no sound :(.. .. and i try to made another port and this time sound work great but i'm stuck on bootloop (bootanimation).. someone got an idea ???
[Android Software/Hacking General [Developers Only]] felek73:
I made everything accordnig to tutorial but i have error:

minzip: incompatible "version made by" 0&0b .. (at 965) , so recovery wasn't even able to open archive ..I changed a little bit updater-script and also changed the structure of the archive ....

Any ideas what went wrong?
[Android Software/Hacking General [Developers Only]] punshkin:
how far do these instructions apply to other ROMs?

I want to port a stock/timescape rom from the Xperia X8 to the HTC Dream.

If these instructions dont work - is there a guide on how to port not-sense ROMs?
[Android Software/Hacking General [Developers Only]] justlovejoy:
so this is only fo r htc to htc not any other non sense devices like samsungs or lg's right?

! awesome guide by the way though thanks!
[Android Software/Hacking General [Developers Only]] Un1c0de:
Thanks for the awesome guide! Anyone know of any good resources (irc channels, etc) for getting help with porting issues this guide doesn't cover? (Mainly help in troubleshooting the logcats)

Thanks in advance :-)
[Android Software/Hacking General [Developers Only]] zelendel:
Yes as sense needs HTC framework and drivers to run sense. The want to have sense on a non HTC phone has been around for as long as sense has and it has never been done to my knowledge as the drivers only work on HTC devices
[Android Software/Hacking General [Developers Only]] DK174:
I have a HTC Merge on a deodexed sense 2.1 rom(2.3.4 android). Could I use this guide to port Runnymede to my device?

If so, which device would be best to start from?

Edit: Tried running this through with a Desire S Rom. Used a new SD card partitioned with ext in CWM. Used an Updater script from a rom I know works, yet it wont boot. I ported a sense 3.5 rom and I know I have at least 1 g in the ext partition, yet it wont get past the HTC screen. I'm looking to try it from a different rom, but anything I should look for? As in a specific phone I should focus on?
[Android Software/Hacking General [Developers Only]] Un1c0de:
Have you gotten a logcat and reviewed that?
[Android Software/Hacking General [Developers Only]] DK174:
Logcat wouldn't read my phone after I flashed the rom. Reads it fine now after I restored my phone. I'd like to give it another shot, I just didn't know which Sense 3.5 rom to start with.
[Android Software/Hacking General [Developers Only]] Un1c0de:
That's a good question. You might want to post that in the general section for your phone and get the advice from an experienced dev for your device. That's what I did and got some good feedback. Sorry I can't be more help.

Anyone know where to get help with logcats?
[Android Software/Hacking General [Developers Only]] DK174:
There aren't any experienced Dev's for the Merge other than 2Fast and he's pretty busy with some other things. I understand how to use Logcats, but believe that my issue is starting with the wrong Rom in the first place. I am looking for a good rom to start from.
[Android Software/Hacking General [Developers Only]] Un1c0de:
You could do desire s or hd, or even runny. For the runny you will probably have to trim down system to fit within the system partition of your phone.
[Android Software/Hacking General [Developers Only]] DK174:
Tried a Desire HD rom ported to the Merge. Still no Boot. Logcat also isn't connecting so I can't even see what's happening.
[Android Software/Hacking General [Developers Only]] Un1c0de:
Are you using a boot image compatible with your device?
[Android Software/Hacking General [Developers Only]] DK174:
Using the boot image pulled from the rom I am using now.
[Android Software/Hacking General [Developers Only]] Un1c0de:
I wish I could more help but I'm a noob to porting.

Sorry :-(
[Android Software/Hacking General [Developers Only]] jmz:
I can almost bet you system partition is filled up and the entire image isn't being flashed. try flashing it then going to advanced/view log in recovery and see what that says...
[Android Software/Hacking General [Developers Only]] DK174:
How do I increase that? Just partition the ext larger?
[Android Software/Hacking General [Developers Only]] Un1c0de:
Unfortunately you cannot change the size of your system partition. The Merge is the CDMA version of the Desire Z (I believe) which has a 535 MB partition size. I have the Incredible 2, which has a system partition size of 575 MB.

Before building your rom, check the size of your system partition and make sure it is less that 535 MB. To free up space, you can move some apps to /data/app.

Using dsixda's Android Kitchen, it's easy to take care of that.
[Android Software/Hacking General [Developers Only]] wildfire-s:
hi i have a wildfire s and would like to port a sense 3.5 rom from g2 will this work ??
[Android Software/Hacking General [Developers Only]] Un1c0de:
This will work for any sense ported to any sense. For the base you want to port from, the ported Rom looks better imo if you select a device that has the same graphics (wvga, etc) as your phone.
[Android Software/Hacking General [Developers Only]] Thekjp95:
Im porting a sensation 3.5 Rom to a dhd got it to boot but logcat is saying that there's something wrong with htcacoustic and hardware, both are in the system/lib folder and if I swap them from the target device I get stuck at splash screen
[Android Software/Hacking General [Developers Only]] :
Here's a tip!

Here's a tip!

Use 7zip instead of WinRAR. It's free. That way you'll never see "9 days remaining again" ! :D

Does pretty much the same thing.
[Android Software/Hacking General [Developers Only]] erfannorouzi:
tnx

for your great tip
[Android Software/Hacking General [Developers Only]] Octane70:
I was wandering if someone could point me in the right direction. This tutorial looks like it may work for my need.

I am trying to take an existing rom for my desire and trying to get it to fit on a different hboot.

For example, the rom I want to use is made for a cmr2 hboot with symlinks to the SD-EXT. What i would like to do is have it fit on a 387-10-40 hboot with a D2ext

script. Is it a simple as moving the files to the appropriate folders and update the updater script or is it more in depth?

Thanks
[Android Software/Hacking General [Developers Only]] come at me bro:
Can one try this with an ics Rom and the HTC vivid
[Android Software/Hacking General [Developers Only]] Will972:
for Porting Sensation rom to Evo 3D just need to change Firmware folder , some file in HW folder, all RIL file , Modules folder and boot.img :D .. also htcbatt from bin folder ..

this thing work for sense .. i really don't know if it work for ICS and seriously i don't think
[Android Software/Hacking General [Developers Only]] erfannorouzi:
you foget 3D engine for evo 3D
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
I am also receiving the same error with status 0. Did you or anyone else figure how to solve it?
[Android Software/Hacking General [Developers Only]] jmz:
Most likely you are overloading your /system partition. When it errors out run "adb pull /tmp/recovery.log" and see what it says at the bottom
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
I can't run the script exactly when it errors out but after it errors and I run it, it says "2248 KB/s (209544 bytes in 0.091s). BTW the error says E:Error in /tmp/sideload/package.zip (Status 0) and I'm trying to port a Sensation Sense 3.5 rom to the HTC Amaze
[Android Software/Hacking General [Developers Only]] jmz:
Maybe I should have been more clear. At some point after it errors out pull that log file and post
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
2033 KB/s (81207 bytes in 0.039s)
[Android Software/Hacking General [Developers Only]] jmz:
No. Where ever you ran that command there is now a file called recovery.log. no offense but if you don't know how to use the logs should you really be trying to port a rom?
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
You're probably right, I am younger than most on XDA, I just thought I could help the HTC Amaze community by posting a fully-working Sense 3.5 ROM because we don't have one. I will try what you said. :)

Edit: I found the recovery.log.
[Android Software/Hacking General [Developers Only]] jmz:
Attach the log to here and also your updater-script
[Android Software/Hacking General [Developers Only]] samuel2706:
heh heh thanks man but i need winrar for compression options ;)
[Android Software/Hacking General [Developers Only]] DEFINITIONOFREAL:
I'm also working on some ports for the amaze, I'm no dev, but if you want to team up maybe we can get something running
[Android Software/Hacking General [Developers Only]] jmz:
Also as a side note to this tutorial it might be good to look at the extract files script in cm7 source for your device. Might have additional files you might be missing
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
Well, I got a replacement Amaze because my other one had problems and I redid the steps and I think the mistake I made before was with the build.prop but I fixed it. I flashed it successfully but when I try to turn it on, it is stuck on the HTC splashscreen.

---------- Post added at 07:39 PM ---------- Previous post was at 07:09 PM ----------

That would be pretty cool, but I want to see if I can even jump in the world of porting. I just want to see if I can successfully port a rom now, and then I'll contact you.
[Android Software/Hacking General [Developers Only]] jmz:
Ok. When stuck at splash screen run this command "adb logcat > logcat.txt" then after about 10 secs hit ctrl+c. Then find the file logcat.txt file and post here
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
I attached a screenshot of the command prompt when I ran the logcat and the logcat.txt

Edit: Also in the rom I ported, the windowsmgr.max_events_per_sec=60 at build.prop was 60 but the target rom said windowsmgr.max_events_per_sec=150, should I have changed it to 150 or left it at 60?
[Android Software/Hacking General [Developers Only]] jmz:
Nvm. Tapatalk is being stupid
[Android Software/Hacking General [Developers Only]] jmz:
Ok sh is broken. In your device rom, what is in /system/bin? Sh or sh0? In your ported Rom delete sh and sh0 from /system/bin. If only one exists that's fine. Delete it. Now move the one from your original Rom to your ported Rom.

If the wrong one exists in bin it will cause the not found error like you are getting. If both exists, it will error out also because it gets confused. Do the same thing as before with pulling the log after you reflash
[Android Software/Hacking General [Developers Only]] sharkie405:
Based on this thread: http://xdaforums.com/showthread.php?t=1227269 that build.prop line is do with scrolling responsiveness and he suggests that 150 is ideal. It shouldn't have anything to do with your ROM not booting, if that's what you were thinking. Sorry, I've not been following this thread closely, so I may be misunderstanding. :)
[Android Software/Hacking General [Developers Only]] jmz:
Yeah that's true. It changes for different types of screens. I forgot to mention that
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
Same problem, I think because the target rom only had a sh0 file, so I only replaced the sh0 file to the ported rom and deleted the sh rom.
[Android Software/Hacking General [Developers Only]] jmz:
No its suppose to follow the kernel. So if you original had sh it should be sh in your ported Rom. Also you are 100% sure you copied the correct bin files over?
[Android Software/Hacking General [Developers Only]] jmz:
Actually something I didn't think of. Go flash again and before you reboot run this command.

Adb pull /tmp/recovery.log

Post it here
[Android Software/Hacking General [Developers Only]] 0utl4wZ:
First I've to thank you for this great thread.

But I've a question. I've tried to port the runnymede ruu for ace. For this I used

RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe

and

RUU_Runnymede_HTC_Europe_1.05.401.4_R2_Radio_20.5101.30.0822_3822.10.10.12_M_release_223366_signed.exe

My problem is that some files that exist in the runnymede ruu are'nt in the ace ruu. How I have to handle this? Should I delete the files in the runnymede ruu?

For e.g. when the name tells the truth this are files for beatsaudio that doesn't exist in the ace version. Will they work without problems or I've to port these for the ace device?

Thank you for your answers!
[Android Software/Hacking General [Developers Only]] jmz:
There are almost no files you need to delete out of a ported Rom. And def not the beats stuff because you will likely mess audio up pretty good. Unless you really know what are doing.
[Android Software/Hacking General [Developers Only]] 0utl4wZ:
Okay thank you for your answer. When I understand you, beatsaudio for example will work without any changes? But this combination of Rom is good when I want to use it in the Europe or is there a better one with sense 3.5?

What is with the csv files and others that that should be replaced but doesn't exist in the ace ruu but in the runnymede? Will this give any trouble at using it?

Sorry this is a totally new chapter for me. Normally I develop website's =)
[Android Software/Hacking General [Developers Only]] HuskyHamburger:
Okay, I tried porting a different rom using a different target rom, with the same results. In this case, both roms didn't have the sh0 lib, just the sh lib. Also, we can't flash kernels through recovery, we do it differently, so would that be an issue?

Edit: I had to upload the recovery.log in a separate text file because it wouldn't upload the original.
[Android Software/Hacking General [Developers Only]] sharkie405:
Quick question for you guys... It's not to do with only Sense but also with Android.

A quick set up, if I may... I was nearing completion of my ROM (for the EVO 4g) and was getting ready to release in the next couple of weeks probably. My ROM is an Android 2.3.3/Sense 2.1 Speedy port. They just released and OTA update for the EVO 4g that is now at Android 2.3.5/Sense 1.0. I can't release a ROM that's behind the stock version as in my ROM being 2.3.3 while stock is now at 2.3.5. So my question is...

I'd like to keep my base as (Sense 2.1) but upgrade the ROM to Android 2.3.5. I've tried using some of the files from the OTA update, but the ROMs haven't booted. So, I guess my question is, is this even possible or does the Sense version have to come from a stock ROM whos software was already at 2.3.5.

And, does anyone know what files exactly make up the Android part of the ROM? Is it everything that doesn't have an "Htc" in front of it? Not counting obvious stuff like the Gmail.apk and the like.

I realize the easiest way would be to port a stock ROM from a similar device that was already at 2.3.5 and Sense 2.1, but I can't find one. Does anyone know of one? I know there are lots of Sense 3.0 and 3.5 ROMs that have 2.3.5, but honestly, I prefer Sense 2.1.
[Android Software/Hacking General [Developers Only]] jmz:
First of all you need to change the mount commands in updater script. They need to match the first part of the recovery logfile. You are escentially installing Rom to /boot and /recovery with the way the script is setup now. Fix that then reflash. Are you going from sense 2.1 or 3.0 to 3.5? If you are you also need to change the bootclasspath in the kernel.

And just a side note so I don't have to keep asking, if you do something I suggest and it still doesn't work run the 2 commands I have asked before and post here
[Android Software/Hacking General [Developers Only]] jmz:
If one exists in the ported Rom and not in your original just ignore it. The only exception is sh as I have explained here
[Android Software/Hacking General [Developers Only]] sharkie405:
Just some advice to those asking about whether or not to add/delete files that are not naturally in both ROMs (port and stock)... What I've done is grab someone's ROM that I know works 100% and use it as a reference. Since I've been working on a 2.1/2.3.3 ROM, I've used MikG ROM as my go to. If I'm not sure whether I should add xxxxxxxx.lib then I look at Mik's ROM and see if he has added it or not and then I do the same. This is also a good way to learn how to write updatescripts and what not.