Related
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Nice work!
Did you try this for a 32A or 32B board?
Looks interesting... anyone tried this for 32A since 32B don't have this issue in the first place?
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
cminion said:
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
Click to expand...
Click to collapse
Well keep us updated if you get anything working for 32A since all of 32A users are stuck with the htc kerel... if you need someone else to test you can pm =D
I've been trying my best at building a kernel for 32A, but no matter what I do it doesn't boot at all.
Does anyone know how you can debug a kernel the kernel's boot process at all? I just get hangs or reboots from any of the kernels I build and I've no idea what is missing or where it's going wrong. If it gave some sort of output then I might be able to figure out what I'm doing wrong! (adb logcat doesn't kick in until AFTER it's booted unfortunately)
How have the 32b users gone with this? Anyone managed to boot one?
cminion said:
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Click to expand...
Click to collapse
Hey, just saw your post and I'm taking a look. So far it's OK, but I think you're missing (at least) the keypad files. Also, a little legal note (in case you didn't know), you aren't legally able to pack the qualcomm libraries on the proprietary/ folder. Not that I really care about it, but I thought you should know since maybe you're going against xda rules by posting copyrighted files -not sure anyway-. Maybe it's better if you leave the propietary folder empty (or just with the minimal stuff like the keymaps, audioparametters and .ini files) and let the extract-files script do the job for whoever uses it to compile. After all, if someone uses this, he already has the libraries on the phone
Anyway, I'm going to compile, if I see something else missing, I'll modify accordingly and send you the changes made, ok?
Regards!
PS: Nice work
EDIT: Okay, I did some little changes on the board file definitions,renamed the folder to sapphire-open (to match dream-open added the keymaps, and a kernel & wlan.ko I had laying around (it's still compiling so maybe the kernel doesn't start, but it still needs an hour or so to end the build, but so far, it's not failing). I have packed it, you can get it here: http://rapidshare.com/files/266633357/sapphire_config.tar
If I see something else I'll repost
GApps2zip
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update. If it doesn't work even if you have Java, you may have to reinstall Java as it is not in your PATH variable for whatever reason.
UPDATE: Updated and, as far as I know, should now work fine with the 1.6 developer images from HTC as well as personal NANDroid backups of most all 1.6 Android ROMs.
INSTRUCTIONS
1) Either do a or b. It is advised to use a personal NANDroid backup (b) as it does not violate any licenses, but it has not been testeda) Google for the file "signed-dream_devphone_userdebug-img-14721.zip" It should be on the HTC support page for the ADP 1, but it wont be the first result in Google. It is not advised to use this method as you need to agree to a license prohibiting modification of the file in order to download it. Rename the file to "backup.zip"b) Restore to a regular build that has all of the Google Apps (like the regular OTA cupcake update) and then run a NANDroid backup. Then make a zip file that only has the system.img file from the NANDroid dump and name the zip "backup.zip"2) If you haven't already, unzip the entire contents of the gapps2zip.zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "backup.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it or unzip it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the backup.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.
Great job unk!
amgupt01 said:
GApps2zip - Created by Ankush Gupta (twitter.com/unkzdomain and unkzdomain.com)
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1. This update.zip should be flashable on any build and it should work without a problem, but since I'm just a n00b sophomore in highschool, I am naturally poor and can't guarantee anything.
Because there are already a few alternatives to this for Linux and the majority of Android users use Windows, I decided to make this a Windows-only batch script.
You MUST have the Java Runtime Environment installed in order to run this script! The signing utility requires Java and you won't be able to flash an unsigned update.
This script does NOT work on a build that includes the new market as there are some incompatibilities with the files for it and the ones provided by HTC (namely the MarketUpdater.apk for the new market). This is pretty much doesn't matter however, because all AOSP builds will not include ANY Android market anyways.
INSTRUCTIONS
1) Google for the file "signed-dream_devphone_userdebug-img-150275.zip" (It should be on the HTC support page for the ADP 1, but it wont be the first result in Google)
2) If you haven't already, unzip the entire contents of this zip file into a directory. For sake of simplification, I am assuming it is unzipped to C:\gapps2zip
3) Place the "signed-dream_devphone_userdebug-img-150275.zip" file in the same directory as the GApps2zip.bat file (C:\gapps2zip) and DON'T rename it.
4) Open up a command prompt window (Hit Windows + R, type in CMD, then click OK)
5) cd to the directory in which the GApps2zip.bat file, utils directory and the signed-dream_devphone_userdebug-img-150275.zip file. For example:
Code:
cd C:\gapps2zip
6)Type in "GApps2zip.bat" (without the quotes) and hit enter. Watch and wait.
7) If all goes well, you should have an update_gapps.zip folder in C:\gapps2zip. Put it on your SD card, make a NANDroid backup, and flash after flashing an AOSP (Android Open Source Project) build that doesn't include the Google Apps.
Credits
Cyanogen for his hard work and dedication
Maxisma for a similar script on which this is based
Google for their ingenious ideas (although their legal department can be a pain)
Everyone who is willing to test this script out
Everyone else xD
Redistribution
Feel free to redistribute the archive wherever you like, but please give me credit along with Maxisma and do not modify the archive in any way.
Click to expand...
Click to collapse
when it asks u to replace system.img, do you click yes or no?
Looks interesting ill test it out later
Guyver75 said:
when it asks u to replace system.img, do you click yes or no?
Click to expand...
Click to collapse
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.
Looks interesting ill test it out later
amgupt01 said:
You click Yes. You shouldnt have extracted the zip though, but it won't make a difference anyways.
Click to expand...
Click to collapse
oh ok, oops. i clicked no. guess ill have to redo it
ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?
xile6 said:
ok trying to understand this. From what i get is you download, Lets say cm 4.2 without google (made up rom dont go looking for it)
then you flash that to are phone.
next when flash update_gapps.zip
Then we will have a cm rom with google apks?
And in returns the update_gapps is kinda like a theme only adding the needed files?
Click to expand...
Click to collapse
Exactly. The only thing is that since this uses an official, legal source, it doesn't include the new market and stuff...
Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?
amgupt01 said:
This script makes an update.zip file that only contains the Google Apps from the HTC release of the 1.5 firmware upgrade for the ADP 1.
Click to expand...
Click to collapse
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.
xile6 said:
Ok cool but once 1.6 adp1 is out we will have to update the script and do this again?
Click to expand...
Click to collapse
Well, provided that HTC distributes ADP 1.6 the same way as they are 1.5 and that the file dependencies for closed-source apps are similar, we could just reuse this same script with maybe a few minor modifications.
ytj87 said:
I applaud your efforts to help the community. Many thanks.
For those who think this is proof modding and this community will live on, think again. What he's doing aids and abets violation of Goog's rights. This thread will be locked and the links taken down. Welcome to the new world of Android.
Click to expand...
Click to collapse
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
@ amgupt01
Thanx now all we got to do is let the builds continue.
great job mr. sophomore, you should get together with cyanogen on this although i'm sure he's probably going to do something similar.
is it safe to sign in to google with the newly created update_gapps2zip?
amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
I think the issue is that Google doesnt want its closed source apps put on non google-experience phones. This guy's method allows just that.
Cyanogen's method (from what I can gather) is to run an app on your phone that backs up the apps that you have on your phone (presumably licensed copies that you acquired when you purchased your phone, or during an OTA update), and then restores them after you run his barebones ROM. In this manner, you are only using backed up copies of software you are entitled to use.
I read somewhere (maybe in Google's C&D? I'm to lazy to go look) that Google does not allow these applications to be copied or extracted or something to that affect.
Honestly, why on earth would we expect them to react any differently?! This is a growing pain. We will all be better for it when its passed.
Here's how I'm planning on riding this out:
1. When Cyanogen releases 4.2, I will unroot my phone, and get the most recent OTA update from Tmobile.
1. Install Cyanogen's 4.2 ROM, using whatever method of installation is required to back up my closed source applications and restore them.
2. Continue to update Cyanogens ROMs this way until we discover that our old closed source apps are no longer compatible with our state of the art ROM.
3. Begin to seek out alternative apps, or check progress of the new "Open Android Alliance" or whatever those guys are calling themselves since this whole fiasco started, to see how feasible that option is.
4. Buy a new phone? I mean, how far down the road are we talking here?! And yes, when the time comes, assuming Google doesn't do something completely draconian that makes us pine for the good old days when they sent a C&D to Cyanogen, it will be another Android phone (subsequently rooted, of course)
I don't really see another legal option.
Code:
Cyanogen on twitter
So I think I've come up with a solution that should work and not violate any licenses. Just need to polish it up a bit.about 14 hours ago from twidroid
Thanks for this script.. i am amazed of how fast the community is getting up from the C&D .... Open Android Alliance is kicking off, Maxima is already out with a NO Google ROM, and this script, to get google's apps... wonderful...
amgupt01 said:
How does it aid and abet to violations of Google's rights? I am basically linking to an official mirror (HTC) that is licensed by Google to distribute the files.
Click to expand...
Click to collapse
amg, I'm worried on two fronts.
1, HTC is redist'ing Goog bits. They may very well get a c&d. I can't imagine HTC has a license to freely distribute them to anyone and everyone. I have to believe the license is for use on HTC hardware, not any user worldwide as download and extraction would allow.
2, you are aiding in the grabbing of those bits that a user may not have license to.
Granted, I know the vast majority of us have license. But there a few non-Goog experience phone owners around here. I suspect the mods will lock down.
But again... I think that would be wrong. We have license to the bits and grabbing them from HTC is not a violation IMO. But we'll see.
Thank you.
amg,
From the HTC license page when you download:
-----
You may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Google Software or any part of the Google Software. You may only load the Google Software onto the Android Developer Phone 1, and except in conjunction with third party software that makes up the Android system image, you may not combine any part of the Google Software with other software, or distribute any software or device incorporating a part of the Google Software.
-----
So it's clear this is illegal. I think HTC will have to pull this down sooner or later as widespread extraction starts.
btw, I think you're fine. HTC will hear from Goog and this thread will be locked. But otherwise don't worry.
This is still not a bootable build
update 10/16/09 ------
Qteknology has got it booting to splash screen but its in a bootloop
this amazing progress
everything i do will be based off this work from here on out thans so much Qtek!
ill need to get some information on what exactly he changed but i know
modified build.prop
modified hw folder
modified bootscreen (tattoo one wouldnt play right)
still wont boot all the way waiting to work out a few things before i post a link i also wanna ask him if its ok for me to post a link
THIS BUILD WILL NOT BE FLASHABLE YET IT IS SPECIFICALLY FOR INPUT/Developement ONLY!
Code:
*****!!!!!! DISCLAIMER!!!!!!!*******
This is still not a bootable build
i am not responsible if you try to flash these roms
for any damage that may occur to your device
these are not finished and are not bootable
still in EARLY EARLY EARLY BETA!
This is about where im at right now
closed-10.07.09
Tattoo Only from the WWE 1.65.405.1 build
Merged lib and hw (for sensors) folders with 1.6 doughnut for magic 10/13/09 will try new lib folder idea tonight and report back with logcat and DDMS report
Specific items will be listed later today when i can think of everything
added some stuff in system/bin (super user access etc)
cyanogens 4.1.11.1 kernel and corresponding wlan.ko added (Thank you so much jubeh for the boot.img)
update-script should be super barebones... really just hoping for a boot right now
______________________________________
Update 10/07/09
so Jubeh might be my saviour He packed the Tattooboot.img with cyanogens kernel
A big thanks to: Jubeh(wouldve never got this far without his knowledge),Nk02(for dump used), Drizzy Drake Rogers(is my personal htc hero),Qteknology (you rock man), Jac, Haykuro, Cyanogen, ccyrowski,JF,twizzzzzzted and any others I forgot to mention you guys are great lets keep building a better bot
you cant mixe 2 different builds together, rosie is tied to many apps, so if you were to only try and port the rosie onto a hero build already out, then rosie wont load just your regular laucher!
mixing builds is bad, especially if they are odex!
Drizzy~
I have a night job and I'm getting ready to sleep. Sorry I didn't reply to your last PMs, but the questions are a little involved and I'm very very sleepy. When I have time (maybe later today, or tomorrow, or could be the weekend) I'll try to get a very simple (no a2sd, no compcache, no nonsense, no nothing, just tattoo and root) build working so that people can take it and mod it as they wish. I won't promise anything though, I'm a known procrastinator.
jubeh said:
I have a night job and I'm getting ready to sleep. Sorry I didn't reply to your last PMs, but the questions are a little involved and I'm very very sleepy. When I have time (maybe later today, or tomorrow, or could be the weekend) I'll try to get a very simple (no a2sd, no compcache, no nonsense, no nothing, just tattoo and root) build working so that people can take it and mod it as they wish. I won't promise anything though, I'm a known procrastinator.
Click to expand...
Click to collapse
Id feel alot more accomplished if i can make it work with a small ammount of direction (ill try not to ask REALLY stupid questions hahaha OMFG I BRICKED
coding makes all kinds of sense to me I jsut need to know what points where and where the system starts the read from
starts at kernel and kernel on firstboot compiles my libs and runs scripts once the environment is built from kernel loads framework and apps stuff like that
once that happens you have live system
Drizzy Drake Rogers said:
you cant mixe 2 different builds together, rosie is tied to many apps, so if you were to only try and port the rosie onto a hero build already out, then rosie wont load just your regular laucher!
mixing builds is bad, especially if they are odex!
Drizzy~
Click to expand...
Click to collapse
i knew about the odex thing becuase the odex is SPECIFIC to the build correct? when you add it i think youll get a error like doesnt match stored signature no signature on file ignoring in logcat
i need a NON Odex'd hero like haykuro's and update it all with tattoo stuff and the newest hero apps to fill in where tattoo doesnt cut it
I know rosie is tied in with alot of stuff and when you just try to merge rosie it wont parse properly because it needs the sdk4 to parse the package
THEREFORE! haha i want to make basically 1.6 Rosie with hero apps filling in for the tattoo ones that i dont wanna edit all the drawables in
i want functionality of 1.6 speed of the dumbed down rosie for tattoo and apps from hero i know ill have to cook this and in no way am i asking someone to "just make update.zip so i can flash"
lets limit me to 1 n00b question a day and after a week or so of patience ill prolly have it done
Question of the day: Can I Un ODEX builds or do the ODEX's directly correspond with the apk and are necesary for the apk's functionality i know that dexopt will run at firstboot on odex'd builds but the odex's exist before the dexopt runs right?
yes you can unodex. http://jf.andblogs.net/2009/09/10/slay-those-pesky-odex-files/#more-153
alritewhadeva said:
yes you can unodex. http://jf.andblogs.net/2009/09/10/slay-those-pesky-odex-files/#more-153
Click to expand...
Click to collapse
then ill see if unodex'd tattoo and unodex'd TwiztedZero6.14r3 can play nicely together :-D
sounds like a headache to unodex the whole build
*shoots self in head* this will take almost a week man i need my own computer
the classes.dex items go back into the apks right? (sorry that makes 2 stupid n00b questions today
NEVER MIND SCRATCH THIS WHOLE ENTRY
per mister drakes words
dont mix builds its bad!
so build off this droid i will
ok so last night i compiled the two different ideas weve had
1) Mashed Tattoo's APP/framework and merged the lib folder with TwiztedZerox6.14
2)Tattoo Alone with Cyanogens kernel and bin xbin folders and some build.prop changes for LCD DPI density changed from 120 back to default
On test flash i get the same message from both update scripts
(the update scripts had been pulled from the latest cyanogen update to be used in my build)
problem line 64 Chown perm *some numbers* bin:reboot
on both update zips tried editing the update-script and it still has issues
any ideas anyone?
Zarboz said:
ok so last night i compiled the two different ideas weve had
1) Mashed Tattoo's APP/framework and merged the lib folder with TwiztedZerox6.14
2)Tattoo Alone with Cyanogens kernel and bin xbin folders and some build.prop changes for LCD DPI density changed from 120 back to default
On test flash i get the same message from both update scripts
(the update scripts had been pulled from the latest cyanogen update to be used in my build)
problem line 64 Chown perm *some numbers* bin:reboot
on both update zips tried editing the update-script and it still has issues
any ideas anyone?
Click to expand...
Click to collapse
in /system/bin from system.img there is a toolbox symlink "reboot" ? if there is, you have to remove it (because all symlink must be create during installation, as write in update-script)
its actually easy to edit the script ... check every line and try to see! what it is doing , you shouldn need xbin at all, remove all lines about it for now, no busybox nothing
as nk02 said remove all links (do you use linux ?) and then your script hould copy system and data , make a symlink for app_s and change some permissisons that's it.
so clean upp the script , and make your own. I will pst one for you here , make sure you have all files in your system ...
shwan_3 said:
its actually easy to edit the script ... check every line and try to see! what it is doing , you shouldn need xbin at all, remove all lines about it for now, no busybox nothing
as nk02 said remove all links (do you use linux ?) and then your script hould copy system and data , make a symlink for app_s and change some permissisons that's it.
so clean upp the script , and make your own. I will pst one for you here , make sure you have all files in your system ...
Click to expand...
Click to collapse
thanks started using textpa and now my update scripts are fine got the hero+tatto mashup to boot but its giving me all kinds of odex issues
im gunna have to find a UN odex'd hero to mash it with and un odex the tattoo build
havent worked on the ONLY tattoo with cyanogens kernel yet i got busy and i dont have a tester phone just my mytouch and i cant go more than 3 hours with out being able to use it haha
no im not on a linux machine i am still getting comfortable with command line functions and have been doing nothing but reading the android developers page and anything linux related on the internet
my betas are uploading right now neither will boot one boots enough to get into logcat but because i mashed the odex'd builds together i know i know im a bum and i didnt wanna deodexarnt the whole thing (take time to do it right and never do it twice)
next on my list of things to try
get unodex'd hero build and unodex tattoo then mash
see if i cant just get straight tatoo to boot then trim the resolutions of the rom to fit on our 32b devices
any input is greatly appreciated
Zarboz said:
thanks started using textpa and now my update scripts are fine got the hero+tatto mashup to boot but its giving me all kinds of odex issues
im gunna have to find a UN odex'd hero to mash it with and un odex the tattoo build
havent worked on the ONLY tattoo with cyanogens kernel yet i got busy and i dont have a tester phone just my mytouch and i cant go more than 3 hours with out being able to use it haha
Click to expand...
Click to collapse
You can use my Hero build, it's unodexed.
maxisma said:
You can use my Hero build, it's unodexed.
Click to expand...
Click to collapse
wouldnt i need to unodex tattoo as well to ensure that they will work together?
i assume yes since the whole build would be unodexed
**edit**
wich one your new drizzy stuff or the old one thats in sapphire forums
yes would be need to unodexed too.
Can anyone deodexerant the tattoo dump I have no Linux machine
Zarboz said:
Can anyone deodexerant the tattoo dump I have no Linux machine
Click to expand...
Click to collapse
virtualbox ?
Help!
I am willing to help with the Deodex if I can, I already started doing something similar to you but against the latest Cyanogen experimental build which is already Donut.
I am trying to Deodex Tattoo but am struggling, I am trying to get my head round what we need to do to deodex it.
According to the readme of deodex you need to have the phone running the exact firmware you want to deodex (I don't have a Tatoo or know anybody who does), or use a CH Root environment to do it.
This is where I get stuck, are they on about a CH root environment on our phones or within my Unbuntu environment (it is not very clear)? Can somebody give me a clue or even better instructions on the CH root process required to use Deodex?
Thanks
James
james194zt said:
I am willing to help with the Deodex if I can, I already started doing something similar to you but against the latest Cyanogen experimental build which is already Donut.
I am trying to Deodex Tattoo but am struggling, I am trying to get my head round what we need to do to deodex it.
According to the readme of deodex you need to have the phone running the exact firmware you want to deodex (I don't have a Tatoo or know anybody who does), or use a CH Root environment to do it.
This is where I get stuck, are they on about a CH root environment on our phones or within my Unbuntu environment (it is not very clear)? Can somebody give me a clue or even better instructions on the CH root process required to use Deodex?
Thanks
James
Click to expand...
Click to collapse
take my tattoo only build unzip it and take the update script delete the line about system:xbin save and resign then flash this will load the android environment through cyanogens shell for the tattoo i just dont know if it will display anything on the phone itll probably have a bunch of errors in logcat
i just havent gotten this far yet because i dont have a phone that i can flash just to test stuff all i have is my mytouch and i cant afford to be without it for very long and i dont know how to boot custom roms on emulator nor do i think we can boot this due to htc parts missing from the SDK
next on my list to try....
*****************
-get virtualbox up and going and deodexarnt the tattoo build (i think itll boot enough to get dalvik manager to run so we can deodex it)
-once deodexed i would like to see if i can get this thing to boot standalone (if the standalone i have now will boot {not been able to test yet like ive said no device to test with} if the standalone is being a big pain in the [email protected]# and not booting properly or we have issues with screen size differences ill have to stop because my knowledge of these things is limited..)
we cant deodex tattoo without being booted into tattoo
so
oh well for that
lets work on getting original tattoo to boot so we can deodex and build off it
if anyone has started to do these things or is already in the process of doing these things please let me know
Zarboz said:
next on my list to try....
*****************
-get virtualbox up and going and deodexarnt the tattoo build (i think itll boot enough to get dalvik manager to run so we can deodex it)
-once deodexed i would like to see if i can get this thing to boot standalone (if the standalone i have now will boot {not been able to test yet like ive said no device to test with} if the standalone is being a big pain in the [email protected]# and not booting properly or we have issues with screen size differences ill have to stop because my knowledge of these things is limited..)
we cant deodex tattoo without being booted into tattoo
so
oh well for that
lets work on getting original tattoo to boot so we can deodex and build off it
if anyone has started to do these things or is already in the process of doing these things please let me know
Click to expand...
Click to collapse
went through about 15 flashes last night
none booted
the furthest i got the logcat is posted on the OP
i have two more ideas but i need someone to pack my boot.img for me for one of them (i know i should have my own linux machine but im not about to download anything over 100 megs on my tether SLOW!)
and the other ill work on tonight and see if i cant get it to work
So I have a bootable Tattoo build. is that all you need? Different phone but I don't see why it matters. I can unodex but I don't see the point... Tattoo and Hero share a lot of apps and functionality. All I see are cosmetic changes, which I'm working on as well. But, if you tell me what to run I can have it posted within the hour.
I'm not sure what you're really trying to do by backporting to Cupcake based Hero. I can unpack the boot.img, unodex Tattoo, whatever but I don't see what you want to accomplish with this. I don't have your phone so I can't test whether the kernel would work if I mod boot.img for you but it doesn't sound hard. Got the tools in my PATH.
Hello, since there seems to be some confusion I decided to start this thread for the 32A port.
The G1 / Magic 32B thread is here: http://forum.xda-developers.com/showthread.php?t=776922
Note that all the work on PSFreedom was done by KaKaRoTo, and he was helped by DrMon in the MSM72K port, i merely compiled their work and put it in a simple package for everyone to enjoy.
I created 2 packages, an enabler and a disabler, that you have to flash over your working CM 6.0 Final installation.
Flashing the enabler will install the modded kernel and PSFreedom module. You will lose usb functionality completely (no adb, no mass storage etc.) until you flash the disabler.
After flashing the enabler the module will always start upon boot, you have to enter no commands on the terminal emulator.
[SIZE=+2]HOW TO:[/SIZE]
Preliminary: Make sure you are on CyanogenMod 6.0 Final and everything is working correctly. It has been reported that it works also with older CM6 versions and CM5 too, you may try if it works and report it in this thread. If it's the first time, do a Nandroid backup before testing!
Download these files: http://www.multiupload.com/MY1LOGZ6YP (32A-Enabler), www.megaupload.com/?d=3UU2L0UX (32A-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_32A.zip
Reboot
Now psfreedom should be loaded as a module, you will see no difference, except for the loss of normal usb functions.
To run the exploit:
Make sure you are on 3.41 (DO NOT UPDATE OVER THE NETWORK!)
Connect the phone to the PS3 using usb
Turn it off completely (unplug power cable or turn off back switch on Fat models)
Plug it back in (turn on back switch)
Turn it on and immediately press the eject button (you should hear 3 quick beeps)
Booting should take a bit longer (5-10 seconds)
If you see two new options under the games tab, the exploit worked. You can now unplug the phone. Mind that you will have to do this procedure every time you boot your PS3. Try using another USB cable if it doesn't work with a few tries.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Payloads:
This version of PSFreedom contains the new PSGroove 1.1 payload (peek & poke)and is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
If you want to try other payloads (F.I. the new AerialX's apploader), you just have to load it into /proc/psfreedom/payload . You can do it by typing:
Code:
cat payload > /proc/psfreedom/payload
The payload can be wherever you want and has to be in the classic binary format. (just remember to substitute "payload" with the correct path).
Even better, if you put the new payload in the /data/local directory, named "payload" (no quotes), it will be automatically loaded upon startup, thus becoming the default payload.
Mirrors:
Code:
Enabler: http://depositfiles.com/en/files/o1qpcbkeo
http://www.zshare.net/download/80630364707ab8fe/
http://rapidshare.com/files/420315547/Enable_PSFreedom_32A_v3.zip
Disabler: http://www.zshare.net/download/801637791c6185b2/
Versions:
Code:
v0: initial release
v1: +module loaded on startup
+created disabler
v2: updated payload (peek & poke)
v3: resolved bootloop bug, updated PSFreedom, dynamic payload loading.
reserved (10 characters long)
Thanks for yours work!
What about an application to enable/disable psfreedom? Will it be possible in the future?
My Magic (32A) does just reboot over and over after flashing the enabler.......also after flashing the disabler........so now restoring (i ALWAYS back-up befor flashing anything!)
But thanks for trying!
radio version for cm6
one question, CM6 can be for New Radio, or just Old radio?
H3llSp4wN said:
one question, CM6 can be for New Radio, or just Old radio?
Click to expand...
Click to collapse
there's a port also for new radio showthread.php?t=723520
But there are some issues (like broken camera)
Old Radio, new radio requires a different kernel.
For the app, for now psfreedom requires a modded kernel, and it is not possible to switch them on the fly using an app. I know they're working on using a different driver, to avoid having to recompile the kernel. Still don't know if it can be done though.
Can anyone provide a mirror please?
cm6
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
I always use the vanilla one, straight from the cyanogenMod forums. I think it should work with any of those versions though. Just make sure you're on old radio and you make a nandroid backup before trying.
got everything right now.
thanks for the mirror.
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Hi , just have a question , looked arround with google , couldn't find my answer, maybe someone here knows,
Before trying this out, I would like to know if I can revert my ps3 to original state,
or to how it was before running psgroove?
yes as the exploit must be ran on every boot so simply reboot and delete bxxm
H3llSp4wN said:
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
Click to expand...
Click to collapse
i use redux and it works for me (i still use the release that u have to do thru the terminal)
focus400hp said:
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Click to expand...
Click to collapse
MT3G is 32B, so head off to the Dream section and get that one instead.
with cm6 my g1 go in loop... why?
Hey guys, I'm running into a little trouble after installing the PSFreedom enabler. My htc magic 32a (3.5mm jacket) just sits on the "HTC Magic" screen for eternity after flashing PSfreedom. I do have CM 6.0 installed, I believe its from Cyanogenmod 6.0 S/D version, I don't know what ebi I am nor if need to do something with kernel, but I just know I go into recovery, flash PSfreedom enabler, reboot, the "htc magic" logo shows up and then it sits there forever...Is there something I'm doing wrong?
@ repukken, rock187. You should use the 32B port. The link is in the first post.
Lollipop_Lawlipop said:
MT3G is 32B, so head off to the Dream section and get that one instead.
Click to expand...
Click to collapse
its mt3g slide i believe its different though i did use the precompiled for the dream 32b on a g1 yesterday and works very well and with no probs at all still want to see something for the slide. i asked in the slide forums and everyone just had s*** to talk really
Amon_RA just sent word — KaKaRoTo’s PSFreedom is now available through recovery mode on your HTC Android-enabled phone. What’s that mean? It means no more flashing kernels leaving WiFi and whatever other functions inoperable. Not to mention it’s way less tedious than backing up, flashing, and restoring all the time. Three separate recovery images have been released:
HTC N1 by Amon_RA
Features everything from RA Recovery v1.7.0.1 including ABD & mass storage.
HTC Dream / Sapphire 32B by Amon_RA
Features everything from RA Recovery v1.7.0.1 including ABD & mass storage.
HTC Desire by Klutsh
Features everything from ClockworkMod v2.5.0.9 including ABD & mass storage.
It’s simple: Flash the new recovery, boot to recovery mode, select the new PSFreedom menu option and select a payload to use. Each recovery image comes with these 4 payloads:
Homebrew only: No Blu-Ray Disc (BD) emulation, meaning no backup support.
Homebrew only with peek/poke: Again, no BD emulation, but adds peek & poke sys calls for certain homebrew. Peek/poke was introduced in PSGroove a couple weeks back.
Homebrew + BD Emulation: As the name suggests, this version enables homebrew and backup support.
Homebrew + BD Emulation with peek/poke: Put two and two together.
Amon_RA’s recovery also comes with a “test only shellcode” payload that is used for debugging purposes. Regular end-users will likely never use it. Then all that’s left is attaching your phone to your PS3 and following the jail break steps:
Kill main PS3 power source
Reconnect main power
Press power button immediately followed by eject.
If you know what you’re doing, then go ahead and download the appropriate recovery image and flash it. Otherwise you can follow Amon_RA’s instructions here. Just like a cat — there are multiple ways to flash a recovery image.
Update: You may need to re-download the N1 or Dream version if you’re experiencing BD emulation issues. Both downloads have been updated to v1.1.1.
Download:
PSFreedom Recovery for N1
PSFreedom Recovery for Dream / Sapphire 32B
PSFreedom Recovery for Desire
Source:
http://www.ps3-hacks.com
Awesome , thanks for all the effort
So with this img it leaves the phone fully working right? I saw another img that broke wifi and usb storage
xile6 said:
So with this img it leaves the phone fully working right? I saw another img that broke wifi and usb storage
Click to expand...
Click to collapse
Whit this you will not have problems... it do all in the recovery and when you boot the phone to the system, dont have to worry whit the wifi or usb problem...
Great now I just need to get my hands on a ps3
EBI1 32A, Rogers drean
can someone plz post a version of this for the 32A rogers dream?
thanks
any plan to update this to Hermes V3?
onilink67 said:
any plan to update this to Hermes V3?
Click to expand...
Click to collapse
We can only hope. I am anxiously awaiting.
G1ForFun said:
We can only hope. I am anxiously awaiting.
Click to expand...
Click to collapse
Its not going to happen. Amon-Ra actually pulled this due to not wanting to get targeted by Sony. The actual rom may continue with updated payloads but I dont know how this will get updated. I searched for the source to this but cant find it anywhere. I wanted to replace the Hermes V1 payload with the Hermes V3 payload and recompile but have no idea where to start. I looked for a good write up on how to build your own recovery image but I think this may be a little above my programming scope. Im going to dive in anyway if I can find source or if I can figure out a way to decompile the img I already have and inject the V3 payload. If I can get it working I will release but dont get your hopes up. I really hope Amon-Ra changes his mind but Sony is out for blood.
bigd5783 said:
Its not going to happen. Amon-Ra actually pulled this due to not wanting to get targeted by Sony. The actual rom may continue with updated payloads but I dont know how this will get updated. I searched for the source to this but cant find it anywhere. I wanted to replace the Hermes V1 payload with the Hermes V3 payload and recompile but have no idea where to start. I looked for a good write up on how to build your own recovery image but I think this may be a little above my programming scope. Im going to dive in anyway if I can find source or if I can figure out a way to decompile the img I already have and inject the V3 payload. If I can get it working I will release but dont get your hopes up. I really hope Amon-Ra changes his mind but Sony is out for blood.
Click to expand...
Click to collapse
All good I got the controller stuff working on v1 payload.
maybe someone can do an "annon" and have the same skillz amon has and release a new "version" maybe amon's twin with a different name
i search a amon_ra version for desire
wub wub this is just a test message ^^
so, is this SFdsGRATE?
asb123 said:
so, is this SFdsGRATE?
Click to expand...
Click to collapse
Thats the best part