Database Info

[Discontinued][HTC One SV][ROM] Jelly Bean Stock Odexed k2_u & k2_ul (cwm flashable) - HTC One SV

[Discontinued][HTC One SV][ROM] Jelly Bean Stock Odexed k2_u & k2_ul (cwm flashable)
Hi guys, i have made some "Test ROMs" for you. As this are my first ROMs i make public, please fire not at me
That is the reason, why i call it "test" or "beta".
Please Notice: if you are already on Jelly Bean, this rom brings you nothing! Don't flash it in this case.
Its not tweaked, its not modded, completely stock!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
- to jmztaylor and Facepalm crew for getting S-Off and for his tips
- to bkcokota for a mostly working recovery
- dsixda for his kitchen
- Zamek for his cwm backup and testing
- Matlevo12 for latest k2_ul JB system dump
- marcelo117 (from android-hilfe) for k2_ul JB boot.img
- the community where it did a lot of research
- Picture from chip.de
Notice:
I tested this myself on a european non-lte phone (codename: k2_u) and it works. But as always bricks can happen and i am not responsible if your phone is dead afterwards.
Don't do this, if you are not experienced enough!
This files are for flashing in recovery.
As it is stock rom it has stock kernel. Kernel source code can be found at htcdev.com.
ChangeLog:
Code:
- 04/28/13 Initial release
- 05/08/13 LTE version added
- 05/12/13 Wiper fc fixed and readded
- 05/25/13 Bluetooth fixed
- 06/02/13 New base for k2u (Mobile data counter fc fixed)
- 06/04/13 New base for k2ul (Mobile data counter fc fixed)
Bugs:
- k2ul: You tell me
- k2u: You tell me
Download:
K2_u (Non-LTE): k2u_JB_2.14.401.107_stock_odexed_01_06_13.zip
Md5 Sum: 39BDAABAAF72C9AE9B80C50018D1CA4F
K2_ul (LTE): k2ul_JB_2.14.401.6_stock_odexed_03_06_13.zip
Md5 Sum: 5C3BDDBAD1690794925284AA2E11150B
How to install:
First of all: make a nand backup in recovery, so you can easily go back if you don't like it!!!
Download the zip file that match to your device and copy to sd card.
Wipe/format data/system/cache/dalvik cache, factory reset.
Flash the zip through recovery.
Htcdev.com unlocked users who are not S-Off have to extract boot.img from the zip file and flash it afterwards over fastboot with the command:
Code:
fastboot flash boot boot.img
Then reboot.
Some things also to mention:
- There is no superuser/su inside, if you wanna root, flash superuser from here.
I hope this will help somebody and have fun with it!!!

someone can do this with last ICS? becaus i think this is problem with updating from ICS to JB ( JB update signature ) so i think writing this JB on bricked ICS is reason why i can't use OTA
anyway Thanks for this rom
i checked on K2_UL and is working!

I have no system dump from k2_ul ics and i think there is already an ics build out there.

i think this is also JB
http://androidfiles.org/?developer=K2_UL&folder=Stock_Roms
anywas someone share dump of ics and jb, but i'm not sure is a good idea to using dump without md5.

When i look into build.prop i would say it is ics.

Wow !
How cool !
Thanks, old.splatterhand !
I'll try it as soon as I'm back home in 10 days.
A few questions : ... what exactly did you do to "create" those ? What did you start from, what did you mod, etc ?
Basically : what is this rom ?
Sorry but I'm having a hard time getting it, but I'll test it anyway !
Another thing :
Dabman said:
i think this is also JB
http://androidfiles.org/?developer=K2_UL&folder=Stock_Roms
anywas someone share dump of ics and jb, but i'm not sure is a good idea to using dump without md5.
Click to expand...
Click to collapse
Same thing here : what are those ?
Thanks !

This is thought for people who like it stock. There are no mods inside.
In germany there were people who deleted by accident their system partition.
To help people for that i made the one for k2_u and thought i'll do it for k2_ul too.
They are made from system dumps, but the k2_ul is not the most actually one (but better than nothing).
They are also for me a start, to see if it works. Then i maybe can try to build up on this my first custom rom. As i'm no dev and that all is new, i have to make small steps.
By the way: i think for those people who like it stock and only want to remove some things from system, they can try to remove it from the zip and see if flashing works (as long as we don't have a kernel without write protection) but only, if they know how to do without breaking something. But i'm not totally sure about this, so people have to test themselves.
That's why i called it "Test"-ROMs. To have something, we can play with. :laugh:
And for the builds on androidfiles.org it looks like ics for me. But maybe jmz can bring light into it.

Ok, cool !
Thx

By the way: if a k2_ul user with the latest software (should be, when a small 32mb update after the Jelly Bean updade came, 2.14.401.6) can do a system dump...

Hi.
1 . Tried to dl your rom to try it, it didn't work out. I tried it from 2 different computers/modems, it takes ages and stop at one point.... file is too big I guess.
2. I have the latest OTA installed on my K2_UL... what exactly do you want ? How do you do a system dump ?
Thanks !

Thanks for your reply, i'm already changing the filehoster cause i'm also not happy with it.
For the dump:
Phone should be in Android, Usb Debugging on, adb should be working, then type in command window of your adb folder:
adb pull /system
This will copy all system files into adb folder.

Okay, just did it. It's uploading on dropbox, I'll pm you the link.
I just did a factory reset before making it, in case you wonder.

Matlevo12 said:
Okay, just did it. It's uploading on dropbox, I'll pm you the link.
I just did a factory reset before making it, in case you wonder.
Click to expand...
Click to collapse
Fine! Factory reset would not be necessary i think, because system still has write protection.
Anyway thanks a lot for it. I will add now mirrors for the links in first post.
Its really hard (if you have no premium account) to upload a filesize more than 500 mb as free user.

Just tried it, it's working great, no problem (for now).
I'm going to start plating with it (removing a lot of stuff, even sense launcher or tings like that) to see how it goes.
I'll keep you posted.
Fyi, according to Sir Google, wiper.apk seem to be some kind of HTC background task manager. If battery life proves to be shorter, maybe that's the cause.

Matlevo12 said:
Just tried it, it's working great, no problem (for now).
Click to expand...
Click to collapse
Nice Thanks for testing!
Fyi, according to Sir Google, wiper.apk seem to be some kind of HTC background task manager. If battery life proves to be shorter, maybe that's the cause.
Click to expand...
Click to collapse
I have heard it should "help" to get quicker gps for Us people by network location, but who knows...?
We will see if it cause some problems.

I spent some time playing with it this afternoon.
I deleted a bunch of things to see how it'd go and got some things ****ed up, so I'll do it the other way around now (deleting slowly and checking everytime !).
Bloatware's gone, for a start, and that's cool.
Really happy not to see Google+ and Facebook in my apps list anymore
Wiper is still a problem, don't know why though. I tried to take the deodexed version from JMZ ics stock rom, but it didn't work out.
I'm thinking wiper.apk could be the power saving notification/switch, do you have it when you use your rom ? I don't...
If someone (maybe you, old. splatterhead) running stock JB and S-off could try to freeze wiper.apk to see if he still gets the notification afterwards, that'd be awesome.
I'll try to cook up something ultralight yet fully fonctionnal sometime soon.

I'm uploading your system dump as flashable zip. Will send you the link to test.
As for uploaded.net filehoster, this is from their twitter page
We are experiencing ddos attacks right now. We are working on it
Click to expand...
Click to collapse
It seems they have problems.
In case of wiper.apk you can read here.
But i have it for my k2u deodexed apps working (without crashing), so let's see if we can solve it that way.

old.splatterhand said:
I'm uploading your system dump as flashable zip. Will send you the link to test.
Click to expand...
Click to collapse
I already did one by just putting my system dump files in /system/ and the boot.img from a cwm backup (even if it probably is the same). It works as well as yours from what I've seen.
Careful there's superuser.apk in it, but it is useless.
By the way, would you have a topic or webpage in store for some basic knowledge about :
- what's in a ruu
- how one makes a cwm flashable zip
- different uses of cwm
Etc...
I didn't search yet (but I will), so if you don't have anything in mind don't sweat it !
Thanks.

Matlevo12 said:
I already did one by just putting my system dump files in /system/ and the boot.img from a cwm backup (even if it probably is the same). It works as well as yours from what I've seen.
Careful there's superuser.apk in it, but it is useless.
By the way, would you have a topic or webpage in store for some basic knowledge about :
- what's in a ruu
- how one makes a cwm flashable zip
- different uses of cwm
Etc...
I didn't search yet (but I will), so if you don't have anything in mind don't sweat it !
Thanks.
Click to expand...
Click to collapse
Maybe you can try my version too, to get sure it is ok, before i make it public. Will send you the link by pm.
You can use an existing zip and edit updater script in it or you can create them also with dsixas kitchen. As i'm writing from my phone i have actually no links but search for "edit updater script" and you will find a lot.

Added the link for k2_ul latest base.

Related

Well I'm kind of in the mood after getting some good feeback from my Defy ROM, so seen as though v1.08 has been released by Advent - I thought I would try and get a release based on this out - try and liven up the vega section on XDA!
As I've said before - I aint no Dev and don't profess to be. I know a fair bit about Android, but I don't compile, what I can do, is put things together that make it easy for others.
As you can see I've marked this as a release candidate, so I'm open to suggestions of what else could be included/improved on, although this is meant to be an unbloated blank canvas for people to build on.
ROM Includes:
Advent v1.08 base
Flash (You may need to reinstall by browsing to /system/etc/shuttle_priv and reinstalling the app in there)
Launcherpro
Gapps (No Gmail - I don't use the app - download from the market if you want it)
High Res Gallery
Moduleap screen calibration app
ES File manager
New for RC2:
Included small notification bar
Custom Boot screen
Modaco USB Switcher (Host/Slave)
Optional Clockworkmod Recovery
Added stock taskmanager back in (even though I think its fairly poor)
My favourite part of this is the installer - I don't think you can get much simpler than this. I'm sorry to Mac and Linux users, but this is a windows installer package, I've never owned a mac (and probably never will) and have limited linux experience.
Install process:
This assumes you have already have the Vega nvflash/adb drivers installed.
1) Download Higgsy_Modded_v1.08_Vega_RC2.exe here
2) Make a backup of your current ROM using clockworkmod recovery (If you use it).
3) I Also advise a backup of your apps/app data via Titanium Backup.
4) Boot into nvflash recovery using the following method:
Disconnect power cable if connected
Power the Vega off
Reconnect the power cable
Hold the back button for 2 seconds
Keeping the back button held down, press and hold the power button for 2 secs
You should hear a "bing bong" from the PC - if so release the buttons
If you don't get a bing bong, disconnect power for 10 secs then reconnect and try the process again.
5)Once you are in nvflash mode execute the Higgsy_Modded_Vega_v1.08_RC1.exe you downloaded, once complete hit enter when the DOS window prompts you.
6)Wait 10 secs and then power on the device as normal.
Installation for Clockworkmod Package:
1)Download the Clockworkmod_Install.exe from here
2)Make sure your Vega is connected to your PC and you have USB debugging enabled on the device
3)Double click the Clockworkmod_Install.exe program and let it do its bit
4)Once the DOS window disappears then it all done.
5)I recommend a standard shutdown/cold boot after install (prob don't need this, but I like to do it anyways.
I had previously posted earlier that clockworkmod was giving black screen, I can now confirm that installing via the above method, has stopped this for me- I have done 3 reflashes/install clockwork/boot into clockwork/flash a zip/reboot/cold boot and it hasn't black screened me, I was probably trying to be a bit clever trying to integrate things I didn't need to, and to be fair its better as an optional extra anyway.
Further note from me on clockwork mod after someone reported BSOD:
Clockworkmod is hit and miss, I spent best part of a day testing/reflashing and in the end I got it to work without any issues, i.e. the usual BSOD after first cold boot after using clockworkmod. What I found prevented it earlier was after using clockwork mod to backup/restore/flash zip etc, was to reboot back into clockworkmod straight away and then just hit reboot in clockworkmod as soon as it loaded up, then if you cold boot after this it loaded up ok. I think the key thing if you are going to use clockwork, is take a recovery straight after setting everything up, then its not so much of a biggy if it does black screen.
Enjoy the ROM
Thanks go to the following:
[email protected] for all my hosting
[email protected] for the Recovery.img/app for the vega. and USB switcher (And indeed kicking of the whole vega scene) At the end of the day Modaco got me into android and for that I'm grateful.
[email protected] for High Res Gallery3D
Fede Carnales for Launcherpro, that is included in the rom.
Estrongs team for a great file explorer.
Advent for making the technology available at an affordable price/original firmware.
Anyone else who thinks they should be thanked.
Please don't post this on other forums without asking me first
Screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Addons, Patches, apks:
SpareParts.apk
Original Gallery3D (If you are getting force closes)
2D Gallery (If like me you think Gallery3D is a load of rubbish lol)
I recommend Wallaby for setting high res wallpaper - its small, simple, free and integrate into android nicely (option when selecting "wallpaper) QR:

Changelog:
25/01/11:
RC2 Release
Added small notification bar as standard
Custom boot screen
Made Clockwork Mod an easy installer optional update
Added USB switcher for switching between USB Host/Slave mode
Added taskmanager.apk back in
Moved Moduleap.apk to /data
24/01/11:
Initial RC1 release

good job mate. will try it out tho. Hows the responsiveness and smoothness, any comment.

alphaola said:
good job mate. will try it out tho. Hows the responsiveness and smoothness, any comment.
Click to expand...
Click to collapse
in my opinion very nice, I will be completely honest - I have compared this and it is mostly advent adding the newer tegra drivers in, there are other differences and additions too though.
would like some feedback from others on the installer and if its working sweet for them (it is for me)

Higgsy said:
in my opinion very nice, I will be completely honest - I have compared this and it is mostly advent adding the newer tegra drivers in, there are other differences and additions too though.
would like some feedback from others on the installer and if its working sweet for them (it is for me)
Click to expand...
Click to collapse
I will like to try it and give feedback,but am having the best experience of my vega - Web_machines 1.07.5 + mcr 6.

alphaola said:
I will like to try it and give feedback,but am having the best experience of my vega - Web_machines 1.07.5 + mcr 6.
Click to expand...
Click to collapse
Well if the others working good for you then just stay with that, this is just another option

If this had a small notifications bar I would be flashing it now. I think I will wait (unless you can add this )

Lennyuk said:
If this had a small notifications bar I would be flashing it now. I think I will wait (unless you can add this )
Click to expand...
Click to collapse
I couldn't decide which way to go with that, I always used the small notification before, some like it some don't. I'll make an update.zip add on. easily done.
Edit: I want to compile it myself too (framework-res) and not use the other one thats available, gives me more experience if I do it myself.

Higgsy said:
I couldn't decide which way to go with that, I always used the small notification before, some like it some don't. I'll make an update.zip add on. easily done.
Click to expand...
Click to collapse
Genius, thanks (I could do it but am incredibly lazy tonight + lets you keep the credit for doing it )

Very nice indeed
Waiting for the small notification bar as well though

Oh and Higsy, please don't tell me you own an android phone and don't use Gmail???!!! if so why the hell not?

Higgsy said:
I couldn't decide which way to go with that, I always used the small notification before, some like it some don't. I'll make an update.zip add on. easily done.
Edit: I want to compile it myself too (framework-res) and not use the other one thats available, gives me more experience if I do it myself.
Click to expand...
Click to collapse
Thanks Higgsy, will give this a go tomorrow. If you are going to modify this yourself, would it be possible to have a semi-transparent small notification bar as an optional update.zip? Or if you know of a good n00b guide to do so, it would be appreciated.
Cheers

Hi Higgsy,
Thanks for making this easy for us that are not so well informed and those that can't be bothered
Mine crashed tonight, Nothing to do with your update, but would it be ok to use your update to bring it back to life
Steve

s.morris said:
Hi Higgsy,
Thanks for making this easy for use that are not so well informed and those that can't be bothered
Mine crashed tonight, Nothing to do with your update, but would it be ok to use your update to bring it back to life
Steve
Click to expand...
Click to collapse
Yep just flash like you were flashing the stock firmware by nvflash

Lennyuk said:
Oh and Higsy, please don't tell me you own an android phone and don't use Gmail???!!! if so why the hell not?
Click to expand...
Click to collapse
Nope don't use it never have, don't like it. If I had the choice I would include the motorola blur email app - coz I like that the best.

Great work Higgsy.
I would like to see button savior installed as default, its a must for the vega. Also would like the small taskbar. Also does this contain flash?
Thanks mate

Small notification bar patch added to the OP, changes something else too, spot the difference.

original_ganjaman said:
Great work Higgsy.
I would like to see button savior installed as default, its a must for the vega. Also would like the small taskbar. Also does this contain flash?
Thanks mate
Click to expand...
Click to collapse
Again button saviour is a must, I agree, my aim here was to provide a blank canvas with only the basics. To be honest there aint a great deal of space in /system. If people agree then I'll include it in the next release.
Flash included and works, you may need to reinstall it by going into /system/etc/shuttle_priv/selecting the app to install. I'll update the OP coz I forgot about that.

I notice in the screenshot that the kernel version is v1.06 is that a mistake. i have flashed the official firmware and it says v1.08.

original_ganjaman said:
I notice in the screenshot that the kernel version is v1.06 is that a mistake. i have flashed the official firmware and it says v1.08.
Click to expand...
Click to collapse
Yup and I know what I've done, won't cause any issues I don't thing but I will sort now and reupload

After seeing Calkulin's EViO ROM with his full-color notification bar icons, I've decided to make my own in a standalone format to be used with most** ROMs.
I made serious effort to match the icons with their larger counterparts found throughout the stock HTC ROM (I run SprintLovers and am OCD about everything matching...). This is a continuous work in progress, subscribe to this thread for future updates.
There's a LOT more icons changed than shown here, but this should give you an idea.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The attached zip files are to be used with MetaMorph (download it from the market if you're not familiar), DO NOT try to flash them through recovery. I've separated the the core system files (framework, resources, settings) to ensure stable and consistent operation. Just download them and run them one by one through MetaMorph, your phone will most likely reboot after each (if it doesn't, do it manually to ensure a fresh starting point for the next MetaMorph).
-- 2/23/2011 --
Framework | Download
MD5 | 8CFF3F555F1FDA52B7DBE0E450A193BA
Resources | Download
MD5 | 41C9BE18A386FB03977589F7E3827CA3
Settings | Download
MD5 | ABD9C1489C5BCD45077494F030B723E7
Apps (Gmail, HTC MMS, HTC Music, HTC Peep, Market) | Download
MD5 | BE50CDC39411B5888E08124A4A3B391E
-- The icons for Android Market may or may not work for you, I'm fixing this at this moment and will post an updated method later. If it doesn't work for you, it's not a critical problem, you just won't see the nice, new, pretty icons. The Market will still work just fine.​
For those that would like to use the icons in ROMs or at their own will, use this link below. DO NOT try to flash or MetaMorph this file, it's just a zip of all the icons I've made.
-- 2/23/2011 --
Master Archive | Download​
Any questions, specific requests, or recommendations; please let me know...enjoy!
Lawyer-Speak
**This is tested and works fine on SprintLovers, and other users have reported it also works fine with various other ROMs. However, I can't guarantee it will be the same for every individual combination of ROM/hacks/edits/etc. (there's just too many variables in most cases), so be smart and nandroid backup before you try it.​

Will try this when I get home today thank you
Sent from my PC36100 using Tapatalk

this theme sucks and the OP sucks
jk, nice work

I would LOVE to have the colored signal bars only. i think thatd be nice.
great work!

tailsthecat3 said:
I would LOVE to have the colored signal bars only. i think thatd be nice.
great work!
Click to expand...
Click to collapse
No problem...the signal bars are in the Resources file...just download it, open the zip, navigate to "com.htc.resources/res/drawable-hdpi" and delete whatever icons you don't want to change, then just run that modified zip file through MetaMorph

This is cool.. QUESTION: Does it require that I run each zip, or can I just run the ones I want to change? For example, can I only run the Colors Apps zip and be ok?
Thanks!

kenlperry said:
This is cool.. QUESTION: Does it require that I run each zip, or can I just run the ones I want to change? For example, can I only run the Colors Apps zip and be ok?
Thanks!
Click to expand...
Click to collapse
Yeah...each of the files are independent so run whichever ones you want to change...furthermore, follow my post above if you want to only change specific icons within one of the zip files.

schmittx said:
Yeah...each of the files are independent so run whichever ones you want to change...furthermore, follow my post above if you want to only change specific icons within one of the zip files.
Click to expand...
Click to collapse
Thanks bro! I apprecite the quick response. I'm gonna give it a try right now. I'll post how it turns out.

schmittx said:
No problem...the signal bars are in the Resources file...just download it, open the zip, navigate to "com.htc.resources/res/drawable-hdpi" and delete whatever icons you don't want to change, then just run that modified zip file through MetaMorph
Click to expand...
Click to collapse
thanks. worked perfectly.

tailsthecat3 said:
thanks. worked perfectly.
Click to expand...
Click to collapse
Are you guys using the free version of Metamorph? I just downloaded it and ran the coloredresources.zip. I applied all, and it said it was complete. It didn't auto-reboot, so I manually rebooted and nothing has changed. I then tried to run the coloredframework.zip and it's been about 5 minutes on the screen where the circle spins(showing activity) and it displays "Applying framework.res.apk theme 1 of 1... Any ideas why it's doing this?
If it helps, I'm running the latest Sprint Lovers ROM, HW003.
Thanks!

kenlperry said:
Are you guys using the free version of Metamorph? I just downloaded it and ran the coloredresources.zip. I applied all, and it said it was complete. It didn't auto-reboot, so I manually rebooted and nothing has changed. I then tried to run the coloredframework.zip and it's been about 5 minutes on the screen where the circle spins(showing activity) and it displays "Applying framework.res.apk theme 1 of 1... Any ideas why it's doing this?
If it helps, I'm running the latest Sprint Lovers ROM, HW003.
Thanks!
Click to expand...
Click to collapse
Strange...I'm running paid version of MetaMorph, but this ran fine on the free version as well...in the settings of MetaMorph, try setting the delay to 3000 (default), and then apply the zip again...it will take a while to apply Resources and Framework because there's a lot of icons to change and the more apps you've got running at the same time, the slower it will be...normal installation should only take a minute or 2 max...

Thanks again.. I didn't change anything(already had the default of 3000). I ran the Resources zip again and it auto-rebooted and the changes were successful. Same for the Colored Apps zip. I tried the Framework zip again and it still seemed to hang. I'll play around with it a few more times.

Awesome man. I'd like to include these in my rom possibly. I just don't want to include it until it's finished. When it's done, I'll definitely consider putting these in.

I am on Fresh 3.5.0.1 and the framework one put me into a bootloop.

Bielinsk said:
I am on Fresh 3.5.0.1 and the framework one put me into a bootloop.
Click to expand...
Click to collapse
Strange, sorry to hear that...I don't have any experience with Fresh so I don't know if Fresh's native framework is different enough than SprintLovers to cause this...only thing I could think of is that my framework also includes slightly modified icons for JsChiSurf's drop-down widget control (forgot to mention that in my original post) but I wouldn't think that'd cause a bootloop? (you'd just have extra unused icons in your framework)
Might also be a bad upload/download?...I can re-post tonight and add checksums so you can verify.
I'm still somewhat new to dev work, so maybe someone with more experience could chime in...

I think I change my battery icon a while back from stock Fresh.
I am not sure what is in the Framework, I may just rip up the zip and take a look. Other ones seemed to work fine.
It was weird, its not really a bootloop, it just keeps playing my start animation over and over and wont actually boot. Tried wiping cache and dalvic, didn't help.
Good thing I took a backup

Will this mod work on a stock rooted Evo?

Bielinsk said:
I think I change my battery icon a while back from stock Fresh.
I am not sure what is in the Framework, I may just rip up the zip and take a look. Other ones seemed to work fine.
It was weird, its not really a bootloop, it just keeps playing my start animation over and over and wont actually boot. Tried wiping cache and dalvic, didn't help.
Good thing I took a backup
Click to expand...
Click to collapse
Yeah, go ahead and hack away at the framework zip...maybe try deleting all but one icon or so and see if that will apply? Let me know if you find anything that I need to fix...I don't want to cause similar problems for everyone...
He123321 said:
Will this mod work on a stock rooted Evo?
Click to expand...
Click to collapse
I believe you need to be deodex'ed to use this, but I'm not an expert...either nandroid backup and try it or do some more research (maybe a more knowledgeable dev can chime in?)...sorry for a wishy-washy answer, just being straight with you.

He123321 said:
Will this mod work on a stock rooted Evo?
Click to expand...
Click to collapse
it worked for me.

Works good for me too...

I've made a few edits to jt1134's 06/20 build of fascinate CM7MTD (which has working GPS!!) to get it working on our radio (EE19 or EC10, your choice) and have uploaded this for others to use. I'm not going to create a release thread of any kind yet as jt is working on getting all 3 of our phones supported officially by CM after he finishes a painstaking process of rewriting sensor drivers (that will mean all hardware will be working, then mms will be looked at). And lmartin92/jt will be able to get us native builds after that happens.
Please visit this thread to make sure you click his thanks and/or throw jt a little money, if it weren't for him alone we would probably never see the merging into mainline CM7!
This release is as is and we're not needing any bug reports at this time.
Note: It will also say Verizon wireless as your service provider, but that's just because I didn't edit the eri.xml file within framework-res.apk
jt1134 said:
Here is a test build/preview of the 2.6.35 MTD CM7 port for Fascinate. It is built off the work of TeamHacksung, and is very different from earlier CM7 builds. At this point it is very functional, but still in very much of an ALPHA state.
Working:
Calls!!
Bluetooth!!
3G data
WiFi
SMS
Camera/Camcorder
USB mass storage / sdcard
Sensors (accelerometer / compass)
GPS!!
Not Working:
MMS
light and proximity sensors
Included in the package is the base ROM and kernel. GAPPS must be flashed separately. Link below. You may also use nemesis2all's kernel here : http://forum.xda-developers.com/showthread.php?t=1119169
When flashed the first time, your filesystems will be converted to MTD (yaffs2/ext4). Do not try to flash any other ROMs via cwm at that point, and do not try to get into recovery via the 3 button method. Use adb reboot recovery or the reboot recovery option from the power menu. To revert, and switch to another ROM, flash a full Odin/Heimdall package (like DL09).
Since your filesystems are being fully converted, there is no need for Voodoo or any other lagfix. DO NOT TRY TO INSTALL ANY KIND OF LAGFIX ON THIS ROM!!! Voodoo sound capability is however included in the kernel.
To install, boot into cwm recovery, wipe data, and flash the ROM. It will reboot and the do the actual install. If you are on a previous version, you can simply flash it over your curren install. If you have problems, try wiping data first. The ROM will work whether you are on rfs or ext4.
*** Update 06/09 ***
fixed in-call audio
fixed bluetooth in-call audio
*** Update 06/20 ***
fixed GPS
re-enabled backlight notifications (you DO NOT need BLN control app)
disabled (broken) auto-brightness
other misc changes, see my github
This is a WiP, and meant as more of a preview than anything else. If you enjoy it, click the Thanks button. Enjoy
http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip - GAPPS
Click to expand...
Click to collapse
Download link: Click Here

bd, shouldn't this thread be in the development forum for the Mes???

Snyperx said:
bd, shouldn't this thread be in the development forum for the Mes???
Click to expand...
Click to collapse
Could be, but I don't consider it development since this build is temporary until we get a native one built. (I didn't want to post another thread in there since lmartin already has one started and would simply update it once it's done.)

When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize

Is this only for the Mes or is it safe for Showcase?

scarmon25 said:
When you say native. Does that mean a build done specificly for mesmerize. In which most everything will be working. Sorry just trying to make sure I understand the lingo
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
When I say native build, I mean that it's built from source with the appropriate uscc/cellular south edits made pre-build - instead of making a few edits post-build like I've done here with this release. Jt has repos on github for both the mesmerize and showcase but they weren't updated yet so we couldn't build it. When he does (after he get's sensor drivers rewritten) then he will either build it or lmartin92 willl and we'll update the thread in the dev forum. This is just to hold people over until then Regardless of whether it's built native or kang'd like I did here, it's still as functional as listed in the OP - but building natively is the better practice and guarantee of no bugs.
StuckinMemphis said:
Is this only for the Mes or is it safe for Showcase?
Click to expand...
Click to collapse
No sorry, I still have yet to learn exactly what changes are required to make it work for CS, so this is only for the mesmerize.

Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize

scarmon25 said:
Cool deal. Thanks for clearing that up for me. Man I wish I had your guys inteligence when it comes to this stuff. It amazes me how you do what you do. I will be lookin for it as honestly that has been my reason for holding off on cyanogen. Waiting for it to get more functional which looks like it is now thanks to JT and the others. You all rock and thanks for all you guys do.
Tap-a-Talked from my Mesmerize
Click to expand...
Click to collapse
No problem, glad to share knowledge when I can . At first I felt the same way, it was very overwhelming and I never thought I'd be able to actually get involved with bringing things to the community, but the more you hang out in IRC the more brave you get and once you start cracking open .apk's and get the basics down, it becomes fairly easy to learn and progress . Especially when you have brains to pick like jt1134/phidelt82/jamezelle (to name only a few)!

Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!

btoast777 said:
Alright, so I tried to flash this on CWM 3 (I was on Heinz 57 EE19 build before this), and I got an error almost immediately, saying "asset failed", along with a bunch of stuff regarding the Fascinate. I did wipe data and all that, so I'm wondering what I'm doing wrong. I would really like to try this out!
Click to expand...
Click to collapse
Can you be more specific on the "stuff regarding the Fascinate" ? I haven't come a crossed this issue, basically it should reboot as soon as you hit "install .zip" to a CM7 splash screen and then it'll go right back into CWM, finish the install then reboot a few more times before it actually boots up.
EDIT:
Okay someone else just had this happen, he was in EE19 H57 as you were, so I'm thinking that's the cause - I went from EE19 PNP to Cm7MTD with no issue. I'm looking into it further but for now it seems you need to be coming from a rom other than H57.
Here is a screenshot;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know

btoast777 said:
Okay, here's what it says (and sorry, I meant assert ).
assert failed: getprop("ro.product.device") =="aries"|| getprop("ro.build.product") =="aries"||getprop("ro.product.board") =="aries"||
These lines are repeated 3 more times, but instead of "aries", it is "fascinate", "fascinatemtd", and then "SCH-I500".
By the way, this is all on the recovery screen, it doesn't reboot at all.
EDIT: Just read your edit, haha. Alright, so I just flash some other ROM like PnP first and I'm all good? Cool, I'll try it and let you know
Click to expand...
Click to collapse
I would think you could flash pnp then go from there but to be safe you might just want to flash full EE19 stock then CM7
EDIT: Okay, scratch that last. I'm re uploading with a working version (same link). It should finish in 10 minutes or so.

Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!

btoast777 said:
Yeah, just flashed PnP and then tried CM7, but I got the same error...well, looks like I'll have to wait until I get back home to my computer this weekend and ODIN back to stock and try again.
EDIT: Wow, I have to stop posting before your edits, haha. Sounds good, I'll try the updated one in a few, then!
Click to expand...
Click to collapse
No worries , please let me know how it goes! (it's all uploaded and available now)

bdemartino said:
No worries , please let me know how it goes! (it's all uploaded and available now)
Click to expand...
Click to collapse
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?

btoast777 said:
So I clicked the download link and I get a notice saying the "content is not supported for the phone", the file is called Unknown and it won't download. Do I need to download from a PC now?
Click to expand...
Click to collapse
I just deleted the old one and reuploaded with the same name, so it should be fine.
try going to http://olvisfoundation.com/xdadump/bdemartino/
Then click on the CM7.zip there

So, turns out I had to re-download the Dolphin browser in order to download it. Good news, CM7 installed successfully on my phone! However, later when I rebooted in order to add the GAPPS, I lost service; my phone couldn't even identify what network it was on and all that. So, I had to borrow a friend's computer and I ODIN-ed back to stock EE19. I'll try it again and see if I can get data working, but if you know anything about that, let me know! I'm getting closer...
EDIT: Alright, so I tried to flash again after getting back to stock, and this time when I rebooted to install the GAPPS, I got stuck in a boot loop with the CyanogenMod animation. So, I've restored my backup and am back on Heinz 57 for now. So I don't know if I'm just not supposed to flash the google apps or if this version only wants to run one time before something happens :/. Do you have any idea?

I had lost data too, so I pulled the battery and rebooted it's been good since.

Ya I had an issue with signal at one point, I toggled airplane mode on and off and it fixed it right up haven't had issues since, but haven't had any issues with data.
You do need gapps, so I'm not sure what the issue is - make sure you download the ones from jt's post.

Yeah, I don't know what was going on...I'm going to try flashing it again, and I'll see what happens.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alien Stock provides a base TouchWiz ROM for your Galaxy S II Skyrocket. Samsung's original ROM stays fully intact with a few extras thrown in. I painstakingly mirrored all of the settings and files in a stock install. I know some users prefer stock ROMs and this gives them that flexibility. ROM developers, feel free to use this as a base.​
Code:
- Based on AT&T UCLE2 4.0.4
- Zipaligned
- Deodexed
- Rooted
- Busybox and friends
- No CIQ
Alien Stock (full wipe - follow instructions below)
MD5 660610861b37d91f7206fc308b64bd1e​
0) Take a Nandroid backup of your current ROM first!
1) Update to ICS radio if you haven't yet (Use my CWM zip here)
2) Wipe data/factory reset
3) Wipe cache
4) Install from SD card
5) Format /cache under "mounts and storage"
6) Reboot. First boot will take a while, be patient (5+ minutes).
7) AT&T Ready2Go seems broken in this build.​
DesignGears
Original ICS Leak
KennethPenn
UCLE2 ICS Leak​
It's not working when I install! I'm receiving force closes, sitting at bootloops, etc.
Make sure you're installing the ROM correctly. Remember that kernels, MODs, radios, and carriers can mess with your phone's performance and workability.
I'm not on AT&T and this ROM is completely broken!
This ROM is not necessarily designed for international compatibility. Please wait for future updates or attempt an install with a proper international kernel.
Why is my device running/booting slowly?
Your first boot will take an unimaginably long time. After that, your device will continue to run slowly until the application cache is built up. Don't worry, the speed will increase as you use the ROM!
Why is my battery life bad?
Your battery life is often killed when flashing ROMs in CWM. For the best battery life, you must drain your device’s battery until it turns off. Plug the device into the AC adapter and let it charge until the image says 100% charged. Then turn it on and use the volume buttons to boot into CWM. Click Wipe Battery Stats under the advanced menu. Then you should charge to 100% and install the ROM. Battery life should be comparable to (if not better than) every other ROM.
What is this?
With the various trouble people seemed to be having with CWM-flashable ICS zips, I took a few minutes to put this together. This is ICS in CWM form, with a few extras. It has none of the problems with other CWM zips (lag, etc). I've kept it stock for those that prefer stock ROMs. This will be the base ROM for Alien ICS. I'll also do my best to keep this updated for future ICS leaks/releases.

Coming soon (its stock, what do you expect?)​

Changelog:
Alien Stock UCLE2
Updated to UCLE2 leak.
Alien Stock UCLD2 re-release
Fixed busybox. No one told me it was broken.
Properly format /system, /data and /cache using Samsung provided tools.
Alien Stock UCLD2
Updated to the UCLD2 leak.
Few minor bugs fixed. I don't think they affected ROM usage, but never hurts to be thorough.
Alien Stock UCALC4
Initial ICS leak.
Known issues:
The home button has a slight delay. This is common in ICS (check SGS2 for example).
[*]Messages crashes if you delete a thread from the list view. This is a problem with the leak. Maybe I'll fix it if I get time.
Anything else that has been common with ICS from Odin (I really haven't noticed hardly anything to be honest).
If installed properly, this will not have the lag, data connection issues, etc of other CWM stock releases.
Some people have noticed weirdness when coming from GB related to the Home/Search keys. This appears to be related to updating from GB only (perhaps files on the SD card). Flashing the ROM a few times and booting into it between each flash seems to clear this up. Alternately, try backing up your internal SD card to your PC and then formatting it.
Miscellaneous:
If you want to enable "Preferred install location" in Settings -> Applications, run the following through an ADB shell and reboot:
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update system set value="1" where name="set_install_location";'

I love you.

nice!!!!!!

Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?

veebomb said:
Nice, been waiting for this one. Screen shots are coming I assume? Can this be used on 727R's (Rogers)?
Click to expand...
Click to collapse
Granted, I was still fleshing out the post, so maybe it wasn't there yet. But please check Help in the first post.
Short answer, I don't know. I'm an AT&T subscriber But if the ICS leak worked on Rogers, then this should too. The beauty of this release is really in the updater-script

I got an aborted install...Im gonna try to download again and flash.

mossination said:
I got an aborted install...Im gonna try to download again and flash.
Click to expand...
Click to collapse
MD5 should be 3764ce5059fd5174e4840960b0fa43cd

Downloading now
Munching on Ice Cream with XDA Premium

Installed fine. Need me to take screens, just ask. Thanks so much for this.

The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?

MokujinX5 said:
The Vol Down + Power has yet to work for me (for screenshots)... Nvm, you have to hold the buttons down.
ROM is good though. May I suggest adding the dictionary fix for the next go-'round?
Click to expand...
Click to collapse
I'd say save that for Alien ICS, we need a good base around here. i Remember the first Alien back in November..first ROM i used.
EDIT: Donated...thanks romracer.

In case you need them.

So far so good. Smoother than the others so far. Had the home button bug. Reflashed and all is good. Thanks for all the work

mossination said:
In case you need them.
Click to expand...
Click to collapse
Thanks, I'll put them up in the morning. One of my dogs ripped the skin off her lower jaw ("degloved the lower mandible") shortly after I posted this. Been a long night; surgery in the morning. Thanks for taking those SS.

First, I hope your dog is OK, I am a dog lover as well.
Ok, this might be a bit lengthy, but I've just spent 10 + hours trying different things and I want to let you know what all happened in hopes that the info can be used to help make Alien ICS one of the greatest ICS ROMS ever. Alot of this is already known, but I'll cover it anyway. And, of course, this is the experience I had with my phone...others may differ.
Background. I ODIN'd the ICS leak already, but found it buggy, bad connectivity, and a battery hog, so I went back to ALien 6 (GB).
I saw this posted and decided to give it another go. I followed the directions and didn't have any trouble with the actual install precedures themselves. However:
The first time I flashed the ROM, I found that I had the problem with the "Home an search" keys not working as well as the "shutdown and reboot" hanging. I tried to do a factory reset in the settings, but it wouldn't work. So I did another clean install of the ROM using the superwipe script this time as well.
The 2nd install fixed the "Home and Search" buttons, but I still had the "shutdown and reboot" hang. I fixed permissions, re-downloaded busybox and installed your insecure kernel and the 14 toggle mod. Nothing fixed it. SO, I did a 3rd clean install.
The 3rd time seemed to do the trick. Home and search buttons work,shutdown and reboot works, the 14 toggle mod works, etc. and, this time around everything seems alot more responsive and snappy.
Here is what I noticed:
All three install attempts (and the ODIN leak install) acted different in some ways that were suttle and others obvious. It appears to be hit or miss on any install and any method that is based on the ICS leak. I'm not sure why this is. But I am certain that reguardless of install method, it might take the way it is supposed to the first time, it might take 3 flashes or it might take 10 or more tries. It's just the luck of the draw. The fixes that people have reported as working are only temporary. That's why they work for some and not for others. It might make a certain aspect work (ie. installing a program makes shutdown work) but your ROM will still not be installed correctly. The only way to get it to work right is to keep trying until it installs with everything working, otherwise there will still be problems.
It will take of couple of days for me to test the connectivity and battery life.
So, people, as for now, if it isn't working for you the only real fix on this ROM or any based on the ICS leak is to keep reflashing until it finally works all the way.
I can't wait for you (romracer) to start baking the mods into this and if I can help let me know. I'll post back here when I get more results from this last flash. Thanks.

Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?

gravyplaya said:
Is it safe to apply this over Alien #6 (GB)? Just follow the instructions in the OP?
Click to expand...
Click to collapse
That's exactly what I did. Make sure you make a nandroid of 6 before you do it...just in case you want to go back. And follow the directions completely. Make sure you flash the modem first. And understand that even if you follow the directions exactly you might still need to flash this more than one time to get everything working. Just make sure you check for any of the known glitches right after you flash and before you start personalizing it. That way if something isn't working correctly and you need to reflash a time or two or more, you will not have wasted any extra time in the process. When you finally get it the way you want it and feel it is installed correctly (glitch free) do another nandroid so you'll have a point to jump to if you want to try something else and then go back again. Good luck.

Hi Romracer
can you please enable internet call settings under Settings>Call.....

I am currently attempting to port Cyanogenmod as well as Clockworkmod to a device known as the Samsung DoubleTime SGH-I857. It is a very unique end of life handset that I think needs a little hacking attention. So far I have found most of the partitions names and sizes on the device, and I have pulled the boot.img and recovery.img out of a firmware file for it that I found online. I am confident in my skills but I am often running into trouble when it comes to building with Cyanogenmod source. I am currently using the Froyo branch as I believe it might be easier to build with the same version that is currently on the phone. I eventually plan to some how build gingerbread for it but i am trying to build what I can as of right now.
I am making this thread to report progress and hopefully get advice from those who are more experienced than me. Any help or advice is deeply appreciated.

Update*
I finally got my build enviornment figured out, I chose Gingerbread because Froyo didn't like me for some reason...
I used the mkvendor.sh method as recommended on the Cyanogenmod Wikipage for porting. I looked through all of the files and everthing seems to be correct except the recovery.fstab which is saying that the system, cache, data, etc. partitions are in all sorts of diffrent file systems; and are mounted in places called the same name as them. The sdcard partition seems to be correct and I'm assuming that I need to manually put in the data. You can look at the files below and tell me if I'm on the right track. I cannot locate any recovery boot or misc partitions using shell commands. There were however there were loop and bml partitions, but they did not appear in the mount or df command.

Update*
I got sick of getting errors regarding my device not existing and random stuff about an HTC ACE. So I plugged the recovery.img from the firmware package into builder.clockworkmod.com and gave it a go. It built sucessfully but I am afraid of the recovery.fstab not being correct.
Upon inspection of sibiling phones most followed a similar pattern or stl## partitions for cache, data and system. Though they all have boot defined as boot and recovery as recovery; both of which with a BML file system. I also noticed the sibilings said their cache, data and systems were ext4 with a 2nd file system of rfs. This is just confusing to me...
I am unsure if I should flash it. I'm confident that the recovery.fstab's recovery and boot partitions are correct but what will happen if I get one of the partitions wrong.
The CWM recovery builder output is here: http://jenkins.cyanogenmod.com/job/recovery/56329/
A sibiling phone example would be: https://github.com/CyanogenMod/android_device_samsung_fascinate/blob/gingerbread/recovery.fstab
Anything other files I am happy to give out.
How I feel about my progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Due to my lack of experience, and fear of hardbricking my new DoubleTime, I will be postponing my developement of the Gingerbread port to the Doubletime. My priority now will be learning as much as possible about the device.
To Do List (In Order)
1. Find correct Odin version for flashing.
2. Create Froyo ROM that will maximize freespace.
3. Create working recovery.
4. Build Gingerbread kernel.
5. Port over Gingerbread.

I've recently been looking comparitivly at custom ROMs and so far I think the best option might be stock AOSP. I have also been looking into ways to flash onto the phone but ODIN 1.85 doesn't seem to work. It can't be my antivirus as far as I know because I've added firewall exceptions to Odin.
To Do List (in order)
1. Find way to flash things to Doubletime
2. Make Froyo based AOSP
3. Build Gingerbread kernel.
4. Port Gingerbread
(Porting CWM should probably be in there somewhere)

Progress?
legojr said:
i've recently been looking comparitivly at custom roms and so far i think the best option might be stock aosp. I have also been looking into ways to flash onto the phone but odin 1.85 doesn't seem to work. It can't be my antivirus as far as i know because i've added firewall exceptions to odin.
To do list (in order)
1. Find way to flash things to doubletime
2. Make froyo based aosp
3. Build gingerbread kernel.
4. Port gingerbread
(porting cwm should probably be in there somewhere)
Click to expand...
Click to collapse
did you give up on this?

Teknodad1974 said:
did you give up on this?
Click to expand...
Click to collapse
No I haven't but my schedule has not allowed for a lot of time to be dedicated to this. I also am very new to this and I'm taking a lot of baby steps.
The number one problem right now is there doesn't seem to be any way of flashing CWM to the phone as all of the Odin versions/cables/computers I've tried have failed.

Well no better way to learn than hands on and on your own... Good luck! I have one of these worthless phones laying around to give to my youngest girl 6. It's just sucks it's stick on Froyo 2.2
Sent from my SGH-I777 using XDA Premium 4 mobile app

I believe I may have a correct recovery.fstab now I'll run this through Clockworkmod Builder now and hopefully get Odin 1.87 to flash it. If at anytime anyone thinks I'm doing something wrong PLEASE TELL ME. I'd rather not have another hardbricked Doubletime.

Honest to goodness I need some help here I'm trying really hard but I can't seem to get anything right... Odin doesn't seem to work, CWM Builder doesn't even identify the name of the phone, and all of the code available for the Doubletime from Samsung makes almost no sense to me. I do enjoy doing this but I've made almost no progress at all.
As of right now the primary effort needs to be on finding a way to flash CWM onto the Doubletime. The issue being if CWM builder is giving out KitKat level recoveries I doubt the Doubletime could handle it. The only way I can see a reliable CWM img getting built is if we use Cyanogenmod 6, which will require proprietary blobs, and those will be a pain to get since extract-files.sh doesn't seem to be available for the Doubletime as far as I know.
I've started manually finding the blobs by finding files that are similar to those found in the device-vendor-blob.mk of some other Samsung Froyo devices. The link to it is here
If I'm going in the right direction someone please tell me...:crying:

​Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
​The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
​That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|

Legojr said:
​Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
​The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
​That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|
Click to expand...
Click to collapse
I have this phone and would like a little of hacking on it. Have you gotten anything?

migui0401 said:
I have this phone and would like a little of hacking on it. Have you gotten anything?
Click to expand...
Click to collapse
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.

Legojr said:
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.
Click to expand...
Click to collapse
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.

migui0401 said:
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.
Click to expand...
Click to collapse
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?

Legojr said:
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?
Click to expand...
Click to collapse
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.

migui0401 said:
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.
Click to expand...
Click to collapse
How much experience at Android hacking do you have?

Legojr said:
How much experience at Android hacking do you have?
Click to expand...
Click to collapse
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?

migui0401 said:
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?
Click to expand...
Click to collapse
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...

Legojr said:
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...
Click to expand...
Click to collapse
I have the stock firmware extracted, the boot.img and recovery.img.