After many requests, I finally sat down and whipped up a UNIVERSAL MIUI installer for both CDMA and GSM versions of the Evo 3D.
The ROM itself is directly based on official weekly builds for CDMA and GSM editions. I have made a few changes to the filesystem (fixed HOSTS from blocking certain sites), added the original camera.apk that was included in initial releases of v5, and threw in a whole bunch of tweaks and extras.
Now, as CDMA is my native device, it will be a little more difficult to test and provide support for GSM. However, official releases have been rock-solid for quite a while now, so there shouldn't be any significant issues.
Below is the link to my CDMA thread. You will find weekly releases and changelogs here. If you require support, please post questions there. It's just easier for me.
Enjoy.
http://forum.xda-developers.com/showthread.php?t=2047911
Reserved
Super .. Good
Thanks.
Sent from my HTC EVO 3D X515m using xda premium
whoa thanks man! i'm definitely going to try your work :victory:
I tried to install this on my evo 3D gsm but it won't boot... I'm stuck in bootloader so I had to restore my old rom
Domac5 said:
I tried to install this on my evo 3D gsm but it won't boot... I'm stuck in bootloader so I had to restore my old rom
Click to expand...
Click to collapse
Hmmm...and herein lies the difficulty of porting for a device you don't have.
So, it's one of several things. On my end, I either borked one of the partitions somewhere (GSM and CDMA use different layouts) or I maybe missed a file difference.
It could also be a hboot/firmware issue. Again, I don't know much about the GSM stuff, but this is based on AOSP JB 4.1.2, so whatever hboot and firmware config works for that should work for this.
I apologize...I will go over the installer again and see if I missed something. If anybody else who's tried this could please report back with your results, it might help me in narrowing down the issue.
Edit: Also updated the OP info to reflect that this needs work yet.
I'll try this built in the morning .Love MIUI and this is big surprise
problem could be in aroma installer... at the end aroma should ask me do I want reboot but that part show about half second than just disappear and I have to manually reboot from 4ext recovery... I'm using hboot 1.49007 and I was on Yoda's rom before installing MIUI
After some updater-script hackery I got it booting,but every app force closes at the initial setup
Pc wouldn't see the device so didn't grab a logcat
So...is it too soon to download? Or will it boot?
B3!CrAZy said:
So...is it too soon to download? Or will it boot?
Click to expand...
Click to collapse
Yes it's too soon. It'll take you as far as bootloader only. Even if you make it past that, according to heli, apps fc's at initial setup. This is a WIP according to the op so we'll have to wait until he can fix the issue :good:
helicopter88 said:
After some updater-script hackery I got it booting,but every app force closes at the initial setup
Pc wouldn't see the device so didn't grab a logcat
Click to expand...
Click to collapse
What was the problem in updater-script? I just sat down at the computer today...gonna start going through it in a second here.
digitalhigh + helicopter88 = Perfect MIUI Jellybean
WellP, I just went over the files with a fine tooth comb (in this case, the comb being a 3-way folder compare utility), and found a few places where there were libs and configs either doubled up, or missing entirely. Sure this doesn't help with apps running.
Downloading Cool ICS GSM right now, gonna check out the updater-script/aroma in that and see if I can get some clues as to what I missed. I think between the file fixes and Aroma, this should be working shortly.
Okay, found three errors in the updater-script that definitely won't help. Fixed those, plus the changes to the filesystem(s). Uploading to goooooo now, will update this post and my OP in CDMA with the link when it's done uploading.
Waiting Waiting
digitalhigh said:
What was the problem in updater-script? I just sat down at the computer today...gonna start going through it in a second here.
Click to expand...
Click to collapse
I took META-INF from a random rom of mine,edited updater-script to flash also /data,and unpacked the contents of DH/gsm into system
helicopter88 said:
I took META-INF from a random rom of mine,edited updater-script to flash also /data,and unpacked the contents of DH/gsm into system
Click to expand...
Click to collapse
Well, I found two points where I had two calls to the FS optimizations one above the other, and I changed the partition number for the first line but didn't see it in the second. That prolly messed all kinds of stuff up. I also excluded the first part of the app selection menu, which was the cause of the customize.prop not being present. The new upload should be done in about 20 minutes...
http://goo.im/devs/digitalhigh/miuiv5/MIUI_3.6.29_SHOOTERS_DH.zip
If anybody would like to test-flash this and post results, I would appreciate it. Might be advisable to save the install log as well as grab a logcat...providing it installs fully and gets past bootloader. Thanks.
Related
Why oh why can I not get anything to boot on my gosh darn incredible? I've tried everything except making it all work.
I want so badly to get something to boot, but alas it never happens. Stuck at the white screen is as far as I ever get. I don't even get the satisfaction of seeing a bootloop, at least then I'd be seeing some sort of progress. Its disheartening. I've tried all kinds of roms and system dumps to no avail.
There must be something I'm doing wrong, what?
Sent from my ADR6300 using XDA Premium App
Do wipe data and cache before flashing?
Yeah. I did manage to get a boot loop with the huashan gingersense leak. So some progress.
Sent from my ADR6300 using XDA Premium App
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
gnarlyc said:
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
Click to expand...
Click to collapse
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Mr. Rager said:
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Personally, I wouldn't copy entire folders over. I also wouldn't copy the boot.img over. I'm not saying that it won't work in some cases. It might. I've always swapped the kernels inside the boot.img, and renamed the device specific init file. Then, I would compare the init files from an existing ROM for my device with the init files from the ROM that I'm trying to port and see if there are any lines that are device-specific. If the init file is trying to start up something that doesn't exist on my device, then it doesn't make sense to keep that line. On the other hand, there might be a line that changes something for that ROM that IS needed.
This same thing kind of goes with the libs and other files too. You might have one lib that relies on another lib being there. And it might need a particular build of that lib. And other files might call certain libs. This is one reason that building from source generally works better over the long run than trying to get one device's ROM to work on another.
You have device specific and ROM specific things going on at the same time, so wholesale copies tend to miss one or the other. Plus it's nice to dig in and get an idea about what's going on.
Also, if you can get adb access while it's booting, grab a logcat. It might give you an idea about what is failing.
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Mr. Rager said:
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Click to expand...
Click to collapse
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
dsixda said:
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
Click to expand...
Click to collapse
I've had a busy past couple of days, but I'll check into the recovery dump and see what's up. I did change the ro.board.
I was trying to abstain from your porting tools, no offense, only so I could do it manually. Just trying to gain more experience, I guess, and learn. Your kitchen is excellent. I use to set up my environment and deodex among other things. The porting tool, though greatly eases the pain and shorten the manual labor ( yes lazy America) , take the learning curve out, a bit. But I guess I could take a look at the script to see what's going on too. Lol.
EDIT#1 - So I just tried to flash my rom. However, it wouldn't, because for some reason my phone is very particular about how one copies files over to the sd card. For one, you have to have the phone booted up, MIUI GB latest in my case, and mount usb storage. If I mount it through recovery, it corrupts my sd card, too bad I wish I knew that earlier. It's a PITA really...Ubuntu...
But, as phone WAS:
Hboot - 0.92
Radio - 11.19
Ship S - OFF
I tried copying and flashing through recovery. Fail as usual. So, I was gonna boot up into MIUI and try to copy from there, and got the infamous 5-vibe and twinkle.
I tried several times to boot into MIUI, but after many battery pulls, I figured out something ODD. In the bootloader the first couple of times it skipped the scanning process, then it started scanning again. Upon further inspection:
Hboot - still 0.92
Radio - still 11.19
Ship S - ON <---NOT A TYPO
Why? I haven't a clue. I tether my phone, so I got it booted, yay, but to do it, my sd card has to be removed and my usb plugged in, then turn on. So, my next edit will be a progress update. AFTER I s-off again ( that sounds kinda dirty, lol ), and re-format my sd. Also, my phone thinks it's charging...ITS UNPLUGGED. Lol, infinite-charging batteries, it's the future...
Sent from my ADR6300 using XDA Premium App
So...Good news is I got another incredible with amoled screen
Bad news I got another incredible with nothing on it, or rooted :-( But I rooted it before I even activated it with *228
But, alas, I still have all of my work on my computer. I managed to back it up before my phone crapped out. Plus I kinda get to start from the beginning so I can be more observant, and particular.
So, back to work...will update tonight.
Edit 1 - So after some more tinkering I've managed to fix some issues, but others have popped up namely the HTC Sim card authentication, which I have no idea about, yet, bouncycastle.jar is being stubborn by not fiding its classes, and libaudioflinger.so is failing to link to libsystem_server.so which in turn fails the link to libandroid_servers.so. Same three problems as before it seems.
Here's a pastebin of the logcat.
http://pastebin.com/QYde7fuQ
I'll keep tinkering about and see what I can come up with. Hopefully I'm closer to getting this thing booted up than I think.
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
SummonerOfDeath said:
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
Click to expand...
Click to collapse
Pull me a recovery.log when you try installing the zip, and I'll have a look for you.
Sent from my HTC Hero using XDA Premium App
S.O.D. proudly presents.... recovery.log!
Here it is, i attached my own update.zip (rosie-signed.apk), maybe you could have a look at it as i don't know where the fault may be.
greets SOD
I would already be happy if you managed to solve the update.zip issue (would help me with other updates) but the main prob is adb noch really working, seems like some system part is blocking this?
my hero was originally a t-mobile google g2, created goldcard, rooted, custom recovery, new radio and custom rom.
a few details:
device HTC Hero (T-Mobile Google G2, the black one )
rom Salsasense RC2 (at the moment...)
recovery CWM 2.0.5.7 (think so, but im sure i got the latest)
sd 2gb
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
SummonerOfDeath said:
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
Click to expand...
Click to collapse
Fixed your update-script, new line for each command is needed
/facepalm
JieeHD said:
Fixed your update-script, new line for each command is needed
/facepalm
Click to expand...
Click to collapse
not serious no? /facepalm -.-" thanks will try that right now xD will give feedback if my device is still alive afterwards xDD
greets, S.O.D.
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
stroobach said:
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
brick after flashing modified rom.
push to /system/app didnt work.
flashing restarts recovery.
jieehd's tip of single lines for every command doesnt work, same as above.
error 0 = apk is not made for your device/rom, wont install.
error 7.. dunno, think its not matching binary or parsing error.
files from my thread? as post above says one is a log and the other is defect^^
i doubt weather will work as its eating HUGE amount of resources. if u want this lockscreen, maybe try salsasense, has got a 3.0 alike lock...
holidays now, wish good luck in coding would be happy if u found a solution
greets, SOD
were can i find HTCG2/hboot/PC10IMG.zip been looking all over for it and its no were to be find
Got some questions.
1. You want WHAT? And what is the purpose?
2. In how far is this related to this topic?
3. If u give us a path to this file, why do u ask where it is? Maybe try dowloAding some random rom (probably some ruu) and do extract & search..
4. Are you really willing to contribute to this topic? I dont see the point of posting this.
5. Obey forum rules. If u have got a question, post it directly in q&a section, not in some random topic or directly explain the connection to the actual topic.
Greets, s.o.d.
agnostic900rr said:
I dunno, no idea
Click to expand...
Click to collapse
what don't you know? may we help you? whats the purpose of all these posts?
i think i'll give it a last try next time wenn i got salsa sense installed and either find a solution instantly or give it up, as noone is willing to support me and i can't do much more with my poor coding skills.
seems like we have to admit that hero's dying and i have to wait for my contract to end so i get a new phone.
greets, s.o.d.
Hey Kids, I figured it was getting kind of boring around here so I'm releasing a little tool I've been using for a while now. It's just what it says, an "Auto Flasher". It will flash any rom, any kernel, backup data, restore data, fix permissions, etc. With full wipe function or just a cache and delvik wipe. All from the comforts of your pc. Just plug in your evo3d with usb debugging enabled and some room on your sdcard and off you go. Oh, almost forgot. This will also Odex all your system apk's if you like. It's on the menu. Even if you have some odexed, it will skip over those.
Things to do first:
1. Run the AF4.5setup.exe. Choose a location (I like the desktop) to run it from. It will create a folder called Auto Flasher V4.5.
1.a Run the 2.08setup.exe and the 2.17setup.exe *(these are just RUU 2.08 and RUU 2.17. Download them even if you already have them. The exe will install them to the proper folder.)
2. Open the Auto Flasher V4.5\Place-Files-Here\ROM folder and copy paste your rom of choice.
3. Open the Auto Flasher V4.5\Place-Files-Here\Kernel folder and copy paste your kernel of choice (if your flashing a kernel).
4. Make sure USB debugging is on and you have about 500 mb on your sdcard.
5. If you need HTC drivers, look in the \Drivers folder. (Install them first).
6. Run the Auto_Flasher_V4.5.bat.
7. Sit back with a brew and watch the show. (It will prompt you a couple of times for some yes and no questions).
NOTES:
I had to separate the .exe's because of file size limitations on DevHost. If your not doing a firmware change then you don't need them. But I recommend you download them.
When restoring data, run your rom first for a couple of minutes. I found everything takes nicer.
When running "11. Fastboot Radio/Wimax Flasher" Please make sure you don"t interrupt this. You won't like the results. If something goes wrong, you will have to flash your radio manually because you'll be in a nasty bootloop.
This is a beta release. Many improvements on the way.
Disclaimer:
If you say I bricked your phone. I will laugh. Nothing this does can't be undone with a nand restore. So for the love of god, DO A NAND BACKUP FIRST!!!
Download: New Links
http://dev-host.org/sFH - (Version 4.5)
http://dev-host.org/u2l - (2.08 setup)
http://dev-host.org/em1 - (2.17 setup)
Old:
http://dev-host.org/btB - (Version 4)
ChangeLog:
V4.5
- Added 12th Menu ---> Hboot 1.5 Flasher
- Same as V4 just with Hboot 1.5 Support.
- Still working on V5
V4
- Added 11th Menu
- Fastboot Radio/Wimax Flasher
- Added Date and time
- Fixed some bugs
- Realigned menu
- Added a lot more arguments (for less problems)
- 32x (bit) Compatibility
- New Icon
- Suprises coming in V5!!!
V3
- Initial release
Edit: For those who have downloaded V4 before 2/27/12, don't use the Auto_Flasher_V4.exe. There's some thing wrong with it. Instead, I've attached Auto_Flasher_V4.bat (unzip it of course). Place that in the \Auto Flasher V4\Auto Flasher V4 directory were adb.exe and all the other files are. Run that instead. Other wise redownload the whole thing again. New link is up.
Special thanks go out to to my son ZxZueSxS for helping me write this and the XDA family. You guys are great.
Big Thanks to all of the people that downloaded this.
If you like this please hit thanks on my page and ZxZueSxS page.
Will this work on hboot 1.5?
jdeoxys said:
Will this work on hboot 1.5?
Click to expand...
Click to collapse
Yes. the zipped folder has TWRP 1.1.1 in it, which works the same way, if you run it manually with ADB and Fastboot. The OP has made the process a little shorter and easier for you.
Thanks gonna give this a try later, so basically this acting like a Recovery in a way...
Sent from my PG8610000 using xda premium
gunfromsako said:
Thanks gonna give this a try later, so basically this acting like a Recovery in a way...
Sent from my PG8610000 using xda premium
Click to expand...
Click to collapse
Yes, it boots a recovery img.
just wanted to say thanks, gonna try this now. i see your in valpo too, that Indiana?
Yes it is
Sent from my PG86100 using XDA App
I'm currently working on a fastboot flasher add-on for radio's and wimax. Any request to make things easier?
Redownload
Sorry guys. I didn't have all the files in the zip. Please redownload. New link is up.
Although I have not yet tried this, I did just download it and feel like a kid at Christmas. I cannot wait to try this.
I'm on 1.5 as well; I'll give this a go and let you know how it goes!
Thanks a ton!
Sent from my Etch-A-Sketch using Tapatalk.
rpenrod23 said:
Although I have not yet tried this, I did just download it and feel like a kid at Christmas. I cannot wait to try this.
I'm on 1.5 as well; I'll give this a go and let you know how it goes!
Thanks a ton!
Sent from my Etch-A-Sketch using Tapatalk.
Click to expand...
Click to collapse
Thanks. Reply's are welcomed. I'm not sure how it does with 1.5. I'm on 1.4. But if you let me know, I can alter it as needed.
Macropoutsis said:
Thanks. Reply's are welcomed. I'm not sure how it does with 1.5. I'm on 1.4. But if you let me know, I can alter it as needed.
Click to expand...
Click to collapse
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
rpenrod23 said:
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
Click to expand...
Click to collapse
That's odd. I'm not sure. What OS are you running?
rpenrod23 said:
I have downloaded this on 2 different PCs with both IE and Firefox and am unable to run the Auto_Flasher_V3.exe.
I receive the good ol' "Auto_Flasher_V3.exe is not a valid Win32 application" error.
Thoughts? I find it hard to believe that I have downloaded multiple bad copies.
Click to expand...
Click to collapse
Sorry about that. I figured it out and have made changes in V4.
Update V4
Just put up V4. Many improvements. Give it a try.
the link in the first page says THERE IS NO FILE.
please be kind to upload your latest version.
thanks very much.
New Link
For those who have downloaded V4 before 2/27/12, don't use the Auto_Flasher_V4.exe. There's some thing wrong with it. Instead, I've attached Auto_Flasher_V4.bat (unzip it of course). Place that in the \Auto Flasher V4\Auto Flasher V4 directory were adb.exe and all the other files are. Run that instead. Other wise redownload the whole thing again. New link is up.
dralibak said:
the link in the first page says THERE IS NO FILE.
please be kind to upload your latest version.
thanks very much.
Click to expand...
Click to collapse
Link is up. Had to take it down. Sorry
Hey guys, I need someone with Hboot 1.50 to test this. I'm on 1.40. I believe you need to use the HTC Unlock Hboot 1.50 method first found here http://www.htcdev.com/bootloader . Then just use the tool. Thanks.
Will HBOOT 1.5 users be able to flash new radios/wimax with this without having to run the latest ruu? Thanks
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
Please read this carefully :
- BASE ROM by Kibuuka AOSP ICS 4.0.4
- PORT ROM from Mazda Team Dirt PARANOIDANDROID v0.2.1 for Supersonic aka HTC Evo 4G and Xylograph ParanoidAndroid for HD2
All the Credit and Donate go to :
1. Mazda [Team Dirt] (http://forum.xda-developers.com/showthread.php?t=1714415)
2. Molesarecoming aka PARANOIDANDROID (http://forum.xda-developers.com/showthread.php?t=1717079)
3. Xylograph
3. Kibuuka (you know where to find him)
4. Nop (you know where to find him)
5. TheManii (you know where to find him)
Please do me a favour, hit the THANKS button at least for above name list.
As usually, I take no credit at all for this rom because this is not my work, I'm not build this from the source, all I do is take the 2 rom, combine it, then try to make it boot on my device.
The rom from Mazda was made for running on HTC Supersonic, if running on DS5 sure it will have much problem and bugs.
All I can do just fix as much as I can, I'm not have experience in build rom, so do not expect too much on this rom.
I just want to share, not intend anything by making this, just have fun and feel excited when others ICS rom can running on my old device.
So lets have fun.
Not work
camera
Temporary work
wifi tether (use barnacle wifi tether from playstore)
headphone (use toggle headset2 from playstore, thanks to machbe 1984)
How to
Nandroid back up before flash.
Wipe cache and dalvik cache, factory reset from streakmod recovery
Flash rom
Factory reset from dell recovery
Be patience, phone need longer time to boot up, if it stuck on boot animation, press and hold power button untill phone shutdown and reboot again. This time will boot up.
Download link
http://www.mediafire.com/download/7eq27tblav0qdjt/ParanoidAndroid_Streak.zip
How to have tablet ui
HOW TO MAKE ANY ICS ROM HAVE TABLET UI
Thanks to Veisen for his awesome work, you can follow his thread
http://forum.xda-developers.com/showthread.php?t=1767955
Tools
- Winrar or 7zip
- dex2jar
- hex workshop
- services.jar from ICS rom
How to
- extract services.jar from ICS rom (system/framework)
- use winrar to extract classes.dex from services.jar
- use dex2jar to compile classes.dex [ d2j-dex2jar classes.dex ]
- the result "classes_dex2jar.jar", use winrar to open and extract WindowManagerService.class form classes_dex2jar.jar\com\android\server\wm
- open WindowsManagerService.class in hex workshop, choose replace icon from menu bar, fill the pop up with
Find : 8E0009000A000000821B9900781D36061C36072A2A2A2A1506
Replace : 930009000A000000871B99007D1D36061C36072A2A2A2A1506 8617046E8B
click ok, then choose replace all, after that choose replace icon from menu bar again, fill the pop up with
Find : B11C36061D3607A7FF8B
Replace : B11C36061D3607A7FF86
click ok, then choose replace all
- save WindowManagerService.class
- replace WindowManagerService.class by winrar in classes_dex2jar.jar without compression
- use jar2dex and create new dex file [ d2j-jar2dex classes-dex2jar.jar ]
- rename it to classes.dex
- use 7zip to replace your classes.dex in services.jar
- copy the mod service.jar back to your rom or phone
- in build.prop change density to 128 and reboot.
Now you have tablet phone
I have tested it and the result are
- dpi 128 [phone not work, data and wifi work well]
- dpi 240 [everythings work well]
Feel free to try use other phone.apk and post the result here.
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Try use streakmod?
Sent from my Dell Streak using Tapatalk 2
Anybody success flash it ? I'm afraid there is bad upload.
Sent from my PC36100 using Tapatalk 2
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
i have flashed it successfully by both StreakMod 0.3.2.8 and ClockworkMod 5.0.2.7
it has some interesting changes
i hope it will be better and better (such as camera and languages)
Yep, was able to flash it too. Preferred the CM9 ROM though! To each his own, I guess!
i always thought that this rom is nice... and ... it is nice..
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
nom051205 said:
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
streak 5 maybe old but it is still competitive hardware... and its large screen always beat others ( <5inch of course)
though i find it nowadays large screen is standard among south koreans...
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Hmm.. it seem that baseband ignorance patch is not working.. it gives blink to the light panel... lol... i am using 366bb to see how the call quality goes and it seems fine.. is there anyway to make the ignorance patch work? I pretty much like this rom and the lags is almost gone too..
TheManii said:
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Click to expand...
Click to collapse
You named it hackport was exactly what I did, honestly this is the first step of porting rom (make it can boot up then see how stable it run) after that there are others step more, I skipped it
I think when the base rom hit something like beta stage, there should be a lot of changes, on that time better to port from the beginning again to hv a better result
On supersonic, we used to put Papasmurfs script (found in HTC supersonic forum) then should hv good result, I hv tried it and rom show much better performance, but browser and gmail fc. (I choose I/O scheduler = SIO).
Sorry for the "Evo" things show up
I hv changed the strings.xml on values folder but always stuck when compile framework-res.apk.
Tried every method and apktool (apktool1.4.2/apktool1.4.3/apktool1.4.3.1/apkmanagers for ics/new aapt from android sdk) found on google still no go.
Sent from my PC36100 using Tapatalk 2
If you simply use pull the our AOSP build's drivers, I'd imagine that rebuilding shouldnt be too difficult as all the hard work is making the drivers work.
It would be similar to a hackport in that you dont build everything, but it means you dont have to worry about missing those strings
We'd lose device specific stuff like dock detection, but those dont work in the first place.
Kibuuka already has the device tree up on his git repo, you could prob just use that and it'd work with a couple changes at most (hopefully, and under the assumption that you can compile android in general)
AFAIK the 'official' apktool doesnt work on API15 apks, it only supports up to API14 (4.0.1-4.0.2).
Someone's supposedly made a mod to support API15, but I havnt tried it.
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
That's problem on every ics rom for dell streak
SULEY1 said:
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
Click to expand...
Click to collapse
use rootdim and select night mode #1 or #2 or #3 :good:
How to change at 160dpi?
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
Use LCD modder. But the dial stops working for me after sometime on that.
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
goto..
settings > paranoid settings > hybrid settings > global density
and change it to your preferrence...
disable hybrid mode in case the homescreen look big...
i am currently on 120dpi and i have no problem with the dial not working... all works so far...
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
ncik said:
Use LCD modder. But the dial stops working for me after sometime on that.
Click to expand...
Click to collapse
if you really use this rom.. dont use lcd modder.. use the built in dpi changer..