Related
This is NOT for those on 2.1 leak. It is ONLY for those on 1.5 Stock or 2.1 OTA OS version.
This is a Windows Only version. We are porting it to JAVA now for cross platform compatibility.
Major update - Re Uploaded the App
We have brought back the Eris Master App as the Android Master App. It has a new name in preparation for support for more Android devices. We are working on fixing the XP bug where files wont download. Until we get a full fix working, DO NOT USE IF YOUR ON WINDOWS XP Stay tuned for updates. We have also included an Error Log handling feature. If there are any errors, it will try to automatically send us an email with the log file. If it cannot send us the email, the log file will pop up for you so you can get in contact with us and send us the log so we can fix the issue.
Again, if you are on Windows XP, DO NOT USE. We have been getting a lot of email logs from those on XP, and we know its not working, so dont bother wasting your time trying to see if it works.
Download the application from here: http://tinyurl.com/2doknnb then run the self extracting .exe zip file, and let it extract to its default location, which is c:\AMA\ then go into the folder there and run the application. Select a ROM to download, and the Root Image, and Recovery Image, then start the downloads.
If you need any support, it is always available on the IRC server.
You can also follow us on Twitter: www.twitter.com/THE_ECLIPS3
Check the thread and the IRC server for updates.
ECLIPS3 and Jamezelle
- Fixed files not downloading in windows XP a little bit more, full fix in works
- Fixes a few minor bug fixes
- Streamlined the code more
This App is being worked on by ECLIPS3 and Jamezelle
We are now on Google Code. Please visit the page here to let us know of any bugs / errors you get while using the app. It is not meant to help you solve your problem there. That is what this thread or our IRC server is for. The IRC server login info is at the bottom of my signature. A web based IRC server is available through this link.
On step 2, when you get to the part of doing the update. our app will tell you to push volume up to start update. you might also have to push the trackball in as well. the link will say <action> YES. push trackball in to start update.
- Market updates for apps. (coming soon)
We have figured out how to restore apps, and restore market update links, need to roll it into the app, but it is possible. We might even have a way to restore links for those non root. Any other app that does market update links requires root first to backup the links.
UPDATE 5/5/2010
Version 2.1 (released 5/5/2010)
Files are now hosted on http://android.grdlock.net
-Fixed where app wont upload custom rom to phone
-New download links for files
-Ability to download roms via app, instead of including them
-Choose what rom to install easier
-Download of ROOT Image instead of including it
-Progress bar for downloads
-Splash Image install
-Cleaned up a lot of the code
-Many bug fixes
-Made user interaction a lot more friendly
-Fix device not found in app.
-Check if phone is connected to PC. If not, setup will not continue.
-Fixed spelling issue.
We have now finished the core of the Application. What it consists of is a GUI (Graphical User Interface) to make going from 1.5 stock to 2.1 root with a custom ROM installed. There is also an easy way to reboot your phone, enter the recovery mode, and enter the bootloader mode. Finally the third part available in this release is a way to backup all of your applications along with restoring all of them. Currently this is root only. We do have an update coming to backup apps for non root.
For rooting there is a 4 step process. Just go through the steps, one at a time and make sure you read and pay attention to the instructions.
We will be adding more functionality and options to this application. Stay tuned for future updates. If there is an update, just re download the whole app.
Please let us know of any bugs or options you would like to see in the application and we will do what we can to add those in or fix those bugs.
Prereq's for using the application:
You must have Microsoft .NET version 4. Direct Download Link
Then also download the drivers file. Unzip it to your desktop. Follow these instructions on how to install a driver. Select have disc, then navigate to your desktop, inside the corresponding folder, and continue the prompts.
Requests
- Support for other android phones.
- Save Layout and Scenes. (Working on now)
- backup apps for those NOT ROOTED (Have it working. need to roll it into an update)
- Restore email settings for Gmail and HTC Mail (Working on now)
- Download speed for file downloads
- Boot andimations (new name for animations)
- Progress bar for copying files to sdcard
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok though because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
ch4sethe5un said:
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok thought because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
Click to expand...
Click to collapse
Thanks for your feedback. I am working on creating a standalone application for backing up the apps, reinstalling, rebooting, rebooting into bootloader and recovery. It will also be able to install the bootanimation files amongst other things. hopefully i will be able to have it do the rooting process as well. though im not sure how often that will be used considering most have already rooted their phones. if some people would like to vote on those options and let me know what they want as well as requests for other features that would be great.
bootanimation is good and boot image logo like in here, maybe?
http://forum.xda-developers.com/showthread.php?t=654042
though im not sure how often that will be used considering most have already rooted their phones.
Click to expand...
Click to collapse
Thats not necessarily true, because 'all people' aren't trolling the internet like we are all the time.
So im sure there are people that dont even know we have root access on the eris. I bet there are also a ton of people that dont know what root is and even how to go about it, so an automated system would be a great addition.
Most of the world is not technology oriented. Think of (most)Best Buy shoppers.. hahah (i used to sell computers there) They look for someone to 'deal' with the tech for them.
i may just be a ritard but i plug my phone in to computer with debugged mode on, i have the skd driver thing updated and my sd card is mounted and it says error device not found any idea wat im doing wrong like i said im a ritard lol thanks guys yall do amazing work keep it up!!!!!!
I use these scripts whenever I flash! I will be glad to test your app!
iamgodnkg said:
i may just be a ritard but i plug my phone in to computer with debugged mode on, i have the skd driver thing updated and my sd card is mounted and it says error device not found any idea wat im doing wrong like i said im a ritard lol thanks guys yall do amazing work keep it up!!!!!!
Click to expand...
Click to collapse
dont mount your sd just leave it ur phone on charge. And follow the instructions that are mentioned in the script before you start it.
I the core of the app done which is going from stock 1.5 to 2.1 root, with recovery image and new rom installing. i have a few people beta testing it for me. once i make sure it is stable for the XDA community i will release that with periodic update of new features.
ECLIPS3 said:
I the core of the app done which is going from stock 1.5 to 2.1 root, with recovery image and new rom installing. i have a few people beta testing it for me. once i make sure it is stable for the XDA community i will release that with periodic update of new features.
Click to expand...
Click to collapse
I was having issues using the scripts to backup on aloysius 2.0 port I did yesterday. It refused to backup; I'm not sure why..
Spencer_Moore said:
I was having issues using the scripts to backup on aloysius 2.0 port I did yesterday. It refused to backup; I'm not sure why..
Click to expand...
Click to collapse
the rom you ported, its a hero rom? thats probably why because i have found that roms that have been ported from other devices have issues with my scripts, which is because of how the rom and its core are built. will try and add that functionality at some point.
for everyone else. these scripts only are verified to work on eris based roms and legend based roms.
Great job! saves so much time and work!
UPDATE: Application is now released. please view first post for more info.
Nice work!
ch4sethe5un said:
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok though because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
Click to expand...
Click to collapse
On fresh installs, or after wiping, it takes some time to build up the cache again.
Eris Master App update file
The update file can not be found.
he requested URL /Eris_Master_App_By_ECLIPS3.exe was not found on this server.
Re: [Application] Eris Master Application
The update file can not be found.
he requested URL /Eris_Master_App_By_ECLIPS3.exe was not found on this server.
Click to expand...
Click to collapse
that is because I don't have an update for it yet.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
ECLIPS3,
Ok....Well my Eris now has the latest 2.1 ROM and when I ran the program it told me that the ROM installed is older that the one being installed. So if I replace the newer rom in the upload/root folder should I be ok?
-Tony
Re: [Application] Eris Master Application
Are you on 2.1 leak, 1.5, or 2.1 root? This only works on 2.1. The file in the root folder is the 2.1 root image. In rom folder is custom roms to install. An update will be released today.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
ECLIPS3,
I am on the 2nd 2.1 leak unrooted.
-Tony
Re: [Application] Eris Master Application
I hate to say it but please read first post again. It will be answered for you.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
Ok..sorry Sir!
Well hello everyone.
I am an application development student from Belgium.
I am proficient in Java, VB.NET, some c/c++ and also PHP/JS/HTML/CSS
Anyways, my recent interest has been going out to creating custom roms for the galaxy S!
The problem now is though, I was able to find some guides and such, but most were incomplete, and for HTC(and other) devices.
I have no idea what is different between making a ROM for galaxy S or a ROM for an HTC device.
If anyone would like to link me to some good resources that can help me on my way, or would like to collaborate (and in the meanwhile teach me a bit) I would be more than happy! (I am open for collaboration as I am pretty proficient in Java and I'm always happy to code and learn more about coding!)
I think the question is really want you want to do!
Custom ROMs for Android are as simple as using recovery console to replace files on the system with your own versions.
ie. Replace the framework.apk which contains all theme images with your own modified one, which you can use to skin the device. Same for replacing other system apps.
Unfortunately, most of these apps are closed source, so modifying them is difficult. The stock android system has open source versions of most of them though, and you can modify those and build them, and then replace the ones on the device. I'm not entirely sure how to build them up though, but it probably isn't too hard.
Then there are custom kernels, which let you actually change the underlying linux system underneath android - Samsung has an open source version of the kernel available that you can compile, and then flash to your phone using Odin or other tools. Compiling the kernel is pretty tricky though.
Well i'm really talking about stuff like SamSet, MoDaCo, Doc's ROM and others.
I'm not saying I want to create a pro ROM in a day or anything, but i'd really love to learn more to get better (always looking for more stuff to put on the resume, I guess?!)
Thanks a lot,
Kenny
Bump for some help
(sorry for the double post but i'm really eager to learn)
I don't have time to give a detailed response right now. However you will want to read up on yaffs (file system) and odexing/deodexing ROMs.
Thank you I will definately do that,
I am following a guide now to start out creating custom ROMs for android, however it was written for Motorola Droid and I have no idea what you have to do different for a samsung galaxy s.
I am a good coder, even though I say so myself, with a lot of experience. I also have a lot of linux experience, you name it
Only the problem is the old, and much known "where do I get started?"
So if anyone can point me out in the right direction on that, tell me how/where you started out, I would appreciate it greatly!
Thanks!
Very sorry to bump again
I set up my environment in ubuntu today to get started (just gotta fix a few errors, didn't know android wouldn't compile on java 1.6, only on 1.5)
Anyways, still need some help here! thanks!
Again I am awefully sorry for the bump here but i'd really like some help.
Note that i'm not a newbie at coding whatsoever and i'm not unfamiliar with some hardcore java, c/c++ and other languages, I'm just having trouble getting started when it comes to modding an existing android release (there are tutorials on HTC and other devices but some methods do not apply to the galaxy S)
If you're trying to create a ROM from scratch then unfortunately you're out of luck at the moment. No one has really managed to do so yet. By "from scratch" I mean the Android Open Source Project (i.e. official Android git repository).
What you can do is grab an existing firmware. Extract the contents, de-odex the apks, modify them or add new apks, optionally you can also compile a custom SGS kernel using Samsung's kernel source. Then you can re-odex the ROM, pack it back up and distribute it.
There's no real "starting place" as such and you won't yet find any tutorials about how to create SGS ROMs. Just give it a go and see where you get.
Yes, I do mean creating a ROM from stock samsung firmware, of course.
So my next logical question would be now:
How do I go over extracting contents from the existing samsung firmware, de-odexing and so on?
Any links/guides/tips are greatly appreciated, as long as they are applicable to this cell phone and not totally crap, thanks!
Samsung uses rfs, I think you should know. There is a thread somewhere in this forum regarding extracting .rfs file. Understood you need Debian though.
For some readup, go search for a famous guy named JesusFreke. Tons of materials...
Hope that from here onwards, this can lead you on, and to find out more. Google is your friend too...
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Raykoid666 said:
I'm afraid my biggest problems already occur in setting up the environment, so it's really the very beginning that gets me stuck, i'm sure coding would be a bikeride compared to setting up the environment for me (i'm no hero in linux,not at all, i'm afraid)
How the hell do I get from point A (being downloading the full source) to point B (starting to create a custom ROM?)
thanks
of course if anyone has the time, and wants to, you can PM me your msn or something, if anyone is up to it
Click to expand...
Click to collapse
Agreed completely! Getting a full cross-compilation to Samsung's Android going is seriously difficult! There have been some promises for tutorials and guides for setting things up though, but none have appeared yet. Probably because it's hard!
Well thank you for agreeing with me on that.
I am really hoping for anyone that can help me out here, either on here or in private, and give some detailed instructions on how to get started.
Hell there is enough information on creating roms alread, deodexing, adding/removing apps etc etc etc... The real problem lies in setting everything up properly.
I think I have gotten to the point where I'm compiling the android source (without samsung specific files)
note i'm saying "i think i am compiling" because i'm hoping it won't error out on me again after an hour of compiling!
But once that is done... I have no idea where to go next, where to get the samsung specific files, or what to do with them whatsoever once i have them
thanks!
Android generic source won't actually help you much. Samsung has made a huge number of changes to it, and while it is all open source, backporting their changes to get your stock source running on the phone is a major undertaking. I believe cyanogenmod was actually working on this, but it seems without much success so far.
What the other rom makers you see are doing is taking a snapshot of a running rom, copying over all of the APKs and the files on a running device, and then tweaking those. ie. Opening up framework-res.apk and changing the image files inside.
The update.zip roms that are what most people are doing are really just using the Android recovery to replace files on the phone with their own versions. Since the underlying system is linux, and everything is a file, this actually works pretty well.
The kernel development effort is completely separate from the rest of the system though, and Samsung has provided the entire source tree that just has to be compiled. I'm a bit stumped myself on all the details of setting it up, but I have seen some threads on this forum about it, and it didn't seem too bad to set up. Apparently you shouldn't use the codesourcery toolchain though, or something. Not too clued up on it, sorry. Hopefully someone with the details can chime in, or give us a link to the old post on it (I'm failing to find it using the search function! )
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Raykoid666 said:
Alright sounds good!
So these recovery files you are talking about (the contents of /system) how do i retrieve those from a base ROM such as JM7 or the likes after a clean flash?)
Click to expand...
Click to collapse
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
RyanZA said:
Root your phone, zip them up onto the sdcard, and then copy them off.
There are probably better methods, but this works fine.
Also, with credits to Unhelpful, he has told me that the correct toolchain to be using is 'uClibc or eglibc toolchain with ct-ng'. I have no idea what to do with that yet, but it's a start.
Click to expand...
Click to collapse
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Tayutama said:
You don't even need to root your phone to pull /system Ryan
adb pull /system <random folder>
is all you need ^^
Click to expand...
Click to collapse
Haha cool, didn't know you could pull whole folders!
Raykoid666 said:
Alright thank you, I managed to get all the /system files using abd pull /system
now next thing up would be de-odexing right, before I go editing stuff?
Now before I go de-odexing. Can anyone tell me what exactly de-odexing is and why I need it?
and what do I need to do to create an update.zip again?
thanks a lot all!
Click to expand...
Click to collapse
The apk files in Android are odexed - that means they have a special index applied for dalvik that speeds them up somehow! I don't know how, I haven't checked how it actually works.
The important point is though:
odexed is faster, but you can't edit it because of signatures or something technical
deodexed means you can change it however you want
More useful info can be found from google - lots of it!
update.zip is easy - it's a zip file in a special format that can be understood by Android's recovery console. The easiest way to do it is to grab an existing update.zip and modify it as needed. Tayutama has millions of em around, so use his!
Then you need to sign it once you're finished with it so that the SGS will accept it. Samsung made a boo-boo and didn't disable the test keys for the 2.1 SGS firmwares. That makes it easy!
http://www.londatiga.net/it/how-to-sign-apk-zip-files/
Just use the test keys to sign it, and then copy it to /sdcard/update.zip and reboot into recovery and it'll work.
NOTE: This is a thread for the build devs.
Users who want to try this solution themselves should head over to TheAgent1982's thread: RTL Support Project, or go to the Hebrew guide at htcaddicts.com.
Update: Hey devs. Just so you'd know, we're even willing to do the framework.jar patching for you!
All we ask from you is to deodex your builds, and include the patched framework.jar (which appears to be almost the same for all builds, barring sense/non-sense differences).
PM if you're willing to let us help
Hey devs
First of all, thanks to all the devs who are doing a great work with everything!
There's one thing though that's a pox on all Android builds (even native android devices), and that is full-on right-to-left support. What do I mean?
Sure, there are Hebrew (and I assume Arabic) fonts in Android, and MOST applications work just fine, with the notable exceptions of Gmail, Google maps, and most native Google-apps, who all display Hebrew backwards.
A far more stressing issue, however, is that ALL android applications without exception display numbers backwards in right-to-left texts (so 10 becomes 01, 12 becomes 21, etc. It can get really confusing really fast).
Any way, there exists a solution for both these problems that can USUALLY be fixed with a medium amount of experience on native Android devices, but requires a bit of a hassle for HD2 owners.
Hopefully, you devs can incorporate this fix to future releases, once the fixed files are obtained it shouldn't be too hard to spread in the future.
Here's the process:
BTW, This only works on completely deodexed builds!
First, you have to download this zip file. It basically contains the fixed files and some other stuff you devs probably won't need.
The fix then involves extracting 'framework.jar' from the phone, and extracting the 'classes' file thusly:
Code:
java -jar baksmali-1.2.2.jar -o classes classes.dex
Then, in the subsequently created "classes" folder, you need to replace the files in "/classes/android/graphics/" and "classes/android/text" with the relevant files in the aforementioned zip file (from the corresponding folders, of course, under "files/froyo/")
After that is done, you need to re-create 'classes.dex' using:
Code:
java -Xmx512M -jar smali-1.2.2.jar classes -o classes_new.dex
Then, replace the old 'classes.dex' in 'framework.jar' with the new one (after renaming it back to 'classes.dex', of course), and push the new and fixed 'framework.jar' back to the phone.
Reboot, and voila: full-on Left-to-Right support!
I'm sure you devs have far better ways of including these fixed files without having to edit the entire thing every time, but what would I know?
We would be extremely appreciative to all you builds devs if you could incorporate those fixed 'classes' files in future builds, it'll save us a ton of work.
Also, if any of you guys also need volunteers for beta-testing this solution (as I'm sure you don't have Hebrew content to test it with), feel free to PM me.
Thank you for listening, and keep up the great work!
((PS, thanks to member silverbluem who helped simplify the process))
+1
i use the htc sense to read sms so
the msg wont appear word4 word3 word2 word1
+1 for that. although i am using bifbif ver 1.2 with CM6 and its OK here.
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
silverbluem said:
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
Click to expand...
Click to collapse
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Ambious said:
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Click to expand...
Click to collapse
still need to figure out how to replace the graphic file
cause the view is not perfect without it...
Ambious said:
Edit: I tried this method, and while it DID boot, the solution didn't work - numbers still backwards, Google applications still reverse.
Click to expand...
Click to collapse
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
silverbluem said:
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
Click to expand...
Click to collapse
My WM rom is OzDROID2.0, my Android rom is MDJ FroyoHD 3.7
Well, the phone book was never a problem for me, only hybrid text/numbers like in text messages etc.
Anyway, turns out I didn't modify framework.jar correctly, so I tried again using the script, and this time the phone just won't boot (like when I used Linux, it just hangs at boot screen).
Edit: Tried all day, all combinations of 'texts' files and with or w/o the 'graphics' file, and it always either just didn't fix anything (when I did the fix manually), or didn't boot at all (when I tried the script). This got me to conclude that I must not be doing it right, or else it would fail to boot for me as well (at least, I'm not even considering me being able to totally fix it myself )
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
+1000
Thanks
nir36 said:
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
Click to expand...
Click to collapse
It COULD be used to reverse engineer some of the stuff, but I doubt it's similar enough to the HD2 builds to use it.
+1
Thanks
Hebrew RTL Support
For those who are asking, i have made a working framework.jar , time ago.
It is working for most FROYO Sence, CM6.+ does not need it...
BUT NOT Desire HD Sence ( Because is is odex files, not only *.jar).
If needed i will upload it, and put a tutorial how to make it work...
Good Day!
RTL HEbrew
Please do that !
Thanks
Framework.jar
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
This fix is a must for all RTL language users.
As mentioned, CM6+ already includes the fix and is working pretty good!
Problem is, for some reason, CM6 builds are rare...
I tried a few Sense builds but eventually i came back to a CM6 based build
because of it's support for RTL languages.
Devs, please include this fix in you builds, to make them as much accessible
as possible.
Thanks.
TheAgent1982 said:
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
Click to expand...
Click to collapse
I sure will!
Thank you
However, as a Sense user myself, I'm pretty anxious to see if a fix can be applied to any of the Sense builds (especially DesireHD, which is my current build).
Well Organized Post
I have made well organized post for it:
RTL Support Post.
I must say, it will NOT Work for Desire HD for now, because it is ODEX and jar combined, and as you have read at iAndroid, for now there is NO solution for it,
and i do not have the experience and time to learn and convert it, since i am a student.
But i will give it a try between the semesters...
Hey,
The HD2 Desire HD builds are fully deodexed.
Froyo HD 3.7 for example: http://forum.xda-developers.com/showthread.php?t=795914
Maybe you could use them for preparing a RTL fix for when the deodexed desire HD ROMS come and for us HD2 android users.
Cheers.
It may be my semi-n00bness, but all my attempts to create a fix for DesireHD 3.7 failed.
Also, trying the supplied fix in the thread above on MDJ Sense Clean (non HD based) failed, wouldn't boot.
Hopefully someone can get it to work, and better yet - that the devs will incorporate those fixes in their builds.
https://opensource.motorola.com/sf/projects/flipout
particular
https://opensource.motorola.com/sf/sfmain/do/go/rel1490?returnUrlKey=1294483663414
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
ghostwheel said:
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
Click to expand...
Click to collapse
Full ack with the accelerometer. But I fear it's not possible to install a custom rom without signing it with the Motorola key (at least that's what I heard).
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
zerghase said:
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
Click to expand...
Click to collapse
Interesting.
But I don't think this is the problem with the Flipout. Many apps actually adjust for screen orientation. Just the wrong way. No matter which way you hold the screen, orientation is off (e.g. Layar, wikitude).
And, the problem is old. It was around before 2.2 came out, or maybe when 2.2 was very young. So, I think most apps weren't written for 2.2 at that stage.
But to a question:
To produce a custom firmware we need to be able to sign stuff. (How was this found for droid?). But with root, we can overwrite anything on the phone, probably except for the init.rd, where the kernel is stored. Is that true? Could we patch by overwriting some files in, for example, /system/lib ?
Yes, with root you can change everything in the running system, but I don't know how far the kernel is protected. It could be possible that the kernel is signed and the system refuses to boot if it has been altered (but you should ask that a Motorola-pro, I'm new to that).
I think it's easier to modify the apps themselves. When they're open-source just apply the fix and recompile, if not...
maybe the developers will be grateful for some hints on bugs in their apps (I would be). And if they are not, it still appears easier to make a change to the bytecode of the erroneous apps than hacking something into the system to make some apps work (and maybe breaking others...).
If I have time, I'll read into the dalvik system and play around a bit with some apps.
I made a mistake and formatted the hard drive of my old computer and sold it, without backing up my keystore for my app published in the Android Market.
My attempted solution:
Take the version from the market signed with the original key (key A), sign it again with my new key (key B) and upload it to the market. Then I will be able to upload another version signed only with key B.
I successfully signed the application with both keys, the problem is that I can't upload the same application again because the version code is still 10, I need to change it to 11. I've opened the AndroidManifest.xml and found that I can change the irrelevant versionName, but can't find the versionCode in there.
Anyone have any ideas? I would really prefer not to unpublish the application because I rely on the income I make from advertisements in it and I don't want to compromise my downloads/rating/position in the market.
Thanks in advanced to all who provide constructive feedback.
Nexeo said:
Take the version from the market signed with the original key (key A), sign it again with my new key (key B) and upload it to the market. Then I will be able to upload another version signed only with key B.
Click to expand...
Click to collapse
I think Market will require signing by key A in every new version of an app. Otherwise signing would make no sense, because anyone could hack it using above technique.
Second, even if you modify AndroidManifest.xml, then signature for key A will be invalid.
If you have lost your key then you're screwed. I don't think you can do anything, but release new versions of your app as new app - with different package name. Even Google can't help you.
I could try to modify version number in your AndroidManifest.xml file if you really want, but I don't see any sense in this.
Brut.all said:
I could try to modify version number in your AndroidManifest.xml file if you really want, but I don't see any sense in this.
Click to expand...
Click to collapse
The sense/hope was that I could take version 1.9 (currently in the market signed with the now lost key) and sign it again with the new key, then upload it with both signatures as version 1.9.1 so therefore I could upload version 2.0 signed only with the new key. If I had both keys this would be a successful way of switching between keys, but because I do not have both I was hoping to modify the compiled/signed app to change the versionCode (not versionName) from 10 to 11 (so the android market would accept it as a new version) and then sign it with the new key, and somehow make it so the signature with the old key was still valid.
The more I work on this and try the more I realize it's probably not possible. I've tried inserting new MD2 hashes for everything that has changed after I've tried modifying files and such but I always get that the application failed to install on my device...
Nexeo said:
The sense/hope was that I could take version 1.9 (currently in the market signed with the now lost key) and sign it again with the new key, then upload it with both signatures as version 1.9.1 so therefore I could upload version 2.0 signed only with the new key. If I had both keys this would be a successful way of switching between keys, but because I do not have both I was hoping to modify the compiled/signed app to change the versionCode (not versionName) from 10 to 11 (so the android market would accept it as a new version) and then sign it with the new key, and somehow make it so the signature with the old key was still valid.
The more I work on this and try the more I realize it's probably not possible. I've tried inserting new MD2 hashes for everything that has changed after I've tried modifying files and such but I always get that the application failed to install on my device...
Click to expand...
Click to collapse
I was just in a similar situation and emailed Google directly. Surprisingly, I received a personally written response. So I can tell you with 100% confidence that you are out of luck: to update a published application you HAVE to use the same digital signature as the original. Otherwise, you'll have to publish the update under a new package name. There is absolutely nothing Google can do. Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Nexeo said:
The sense/hope was that I could take version 1.9 (...)
Click to expand...
Click to collapse
Yeah, you said that already and I gave you two reasons, why you can't do that:
invalid signatures for key A
requirement for key A in all future versions of your app
Chalup said:
Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Click to expand...
Click to collapse
Google can't do anything even if they want - it's technically impossible. They could replace your app with new one with different package name, then copy all ratings, comments, etc. from old one, but they simply can't change key for existent package name.
Been there, done that...lost keystores of 3 published apps. Wrote Google too...no joy.
You are puckered As am I because I can not post an update to my apps without a new package name. Which of course, leaves all current users unable to get the update without repurchasing.
I wish there was a better way.... we all lose files from time to time. Why not make part of the publish process an upload of your keystore to the Google servers? Seems like a solution to me
In the meantime, I now have at least 5 copies of my keystores saved on various medium: e-mails to myself, file server, CD etc. Just have to deal with it I guess
Sending the hard drive off to a data recovery company who seems to be pretty confident. Hopefully they can find .keystore files.
I GOT MY KEYSTORE BACK!!!
I used the best f-ing software in the universe to restore the file (it truly is amazing): http://www.ntfs.com/boot-disk.htm
Nexeo said:
I GOT MY KEYSTORE BACK!!!
I used the best f-ing software in the universe to restore the file (it truly is amazing): http://www.ntfs.com/boot-disk.htm
Click to expand...
Click to collapse
Sweet find, I have all my stuff backed up on an IronKey flash drive. But it's a lot more than just my Keystores, it's also all of my work files and such. If you have some extra money I would recommend one. The only bad thing is the highest model's capacity is 32GB.
Rootstonian said:
Why not make part of the publish process an upload of your keystore to the Google servers? Seems like a solution to me
Click to expand...
Click to collapse
I think you don't understand what is this signing for. Its purpose is to make sure you're installing application from original author, not some hacked or infected version. And you want to open some backdoor for installing an application created by different author (no keys = different author). Your "solution" would make signing totally useless.
Chalup said:
Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Click to expand...
Click to collapse
I don't think that's true. Recently, the wildly popular app "Vignette" suffered from pretty much the same issue and had to republish.