Related
It is really pissing me off that i can't get wifi to work properly when porting Dream roms over to the 32A. I have changed all drivers, a heap of wifi and init files but still nothing.....
We have rebuilt the boot image with the correct kernel, replaced wlan driver, renamed trout files etc......
Wifi will start up and find the networks nearby but will not connect to any.
Anyone have any suggestions? I am hoping there is one little file we are missing that a simple transfer of that file will get it working.....
Radix and I have tried a bit as well as a few others. He might be able to pop in and say exactly what he has done with what files (I am at work so can't remember everything i have tried to change)....
IDEAS?
****edit*** just noticed this tweet from haykuro: "rogers peeps: you may be able to flash all sorts of craziness soon. "
I have had no problem getting WiFi to work on any of the Dream-based ROMS. As long as the wlan.ko matches whatever kernel you are using (from whatever boot.img you are using) it seems to work as normal.
I'd imagine you will never have much success using a different wlan.ko and kernel combination than was compiled for.
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
MontAlbert said:
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
Click to expand...
Click to collapse
I use the entire boot.img (I know this is lazy and loses alot of the cool features of the ROM) and then the corresponding wlan.ko from whatever image the ROM came.
ok. I was trying to keep as much of the original intact as possible.....
I've tried replacing the entire boot.img - makes no difference - wifi will load, but not actually get an IP with any of the newer roms (like cyanogen's or JACxROM).
I suspect it's interacting with some of the /system/bin/ files and something has changed in that department that makes it incompatible with our kernel/wlan.ko.
I've tried replacing wpa_supplicant/wpa_cli/wlan_loader and no luck.
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 G1, 32B port.
For the 32A version click here: http://forum.xda-developers.com/showthread.php?p=8039074
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.
Note also that I cannot test my G1 builds myself, as I have only a Magic 32A, so please do a Nandroid backup before testing them for the first time.
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: www.multiupload.com/23BTK9TRSW (G1-Enabler), www.megaupload.com/?d=KNC9MXW3 (G1-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_G1.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.
If it doesn't work, try with another USB cable, it has been reported that the original data cable works best for this purpose.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Mirrors:
Code:
[STRIKE]Enabler: http://db.tt/XEKCdBi[/STRIKE] - Old version
Disabler: http://db.tt/QkpccHB
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.
Payloads
There seems to be some confusion with payloads. Attached here you will find some working ones. Unfortunately i have yet to manage to make the <3.41 payloads working, so there aren't any for now. The default one is presently the psgroove 1.1 payload.
How to change a payload:
Download and extract one of the payloads
Put it in your SD card (it could be named anyway you like, but it is usually called payload, with no extension)
Copy it to /data/local/ , make sure it is named 'payload', without quotes and any extension. To do this you could:
use a root file system explorer, such as ES file explorer or Root explorer to copy the file to /data/local, make sure it is named payload (no extensions!) OR
Use a terminal emulator and type: cp /sdcard/payload /data/local/payload (change /sdcard/payload accordingly to how you named it)
Reboot phone
How to prepare your own payloads
Get your payload in binary format. I'm not going to cover this part thoroughly, because any distribution (PSgroove, psfreedom, aerialx, hermes) does it differently, plus you can usually find the precompile payload minutes after the source is released. It is usually named port1_config_descriptor.bin or default_payload.... something like that.
If it is not a psfreedom payload:
Open it in an hex editor
Strip the first few bytes so that it starts with 00 00 00 00 00 00 FA CE B0 03
Save and name it payload (no extension)
Test it with the guide above
have you done enable/disable packages also for the 32a?
here: http://forum.xda-developers.com/showthread.php?p=8038887
I have a HTC Dream with CM 6.0 but i need to install ebi1 to boot up else my phone freezes on the logo screen
PSfreedom zip does not allow my phone to boot up.
Is there a work around?
Phone:
Dream/CM6.0 needs EBI1 to run.
DREAM PVT 32B ENG S-OFF
HBOOT1.33.2005 DREA20000
RADIO 3.22.20.17
Try the 32A port, that should work.
I'm gonna try this on my touchpro with the android port see if it works with that.
Im having issues with 6.0.0 final ( cant recieve calls) Will this work with 5.0.8?
.kAroshi said:
Try the 32A port, that should work.
Click to expand...
Click to collapse
Success. Thanks to kAroshi for the enabler.
What's the problem of creating nandroid backup and then after flashing the required kernel and booting ps3, restoring the backup? I also have problems with this kernel flashed on my g1 (ie. wifi doesn't worik) but as soon as my ps3 is jailbroken I just restore nandroid backup.
No problem, it should just be faster using the disabler, and you won't have to backup every time.
Can anyone confirm that wifi isn't working with this release?
Hi
I have a 32b magic SFR, 6.0final cyano, then flashed the psfreedom zip update.
I did the terminal, it's ok.
When I boot the PS3 3.41, the boot animation froze, any idea ?
Cheers
TPLO
tplotplo said:
Hi
I have a 32b magic SFR, 6.0final cyano, then flashed the psfreedom zip update.
I did the terminal, it's ok.
When I boot the PS3 3.41, the boot animation froze, any idea ?
Cheers
TPLO
Click to expand...
Click to collapse
Do you fallow the ps3 boot instructions?
can you reup the G1-Disabler link, the link gives me "The file you are trying to access is temporarily unavailable."
and thanks for the work
Link works again now.
Need disabler, Link is dead. Can someone upload it for me?
Xoti said:
can you reup the G1-Disabler link, the link gives me "The file you are trying to access is temporarily unavailable."
and thanks for the work
Click to expand...
Click to collapse
Still not working for me. Btw, do you have to plugin the G1 everytime you want access to the extra menus? Or is this a one-time deal?
And can someone confirmed whether this worked or not to jailbreak your PS3 please? Thanks!
Stryder5 said:
Still not working for me. Btw, do you have to plugin the G1 everytime you want access to the extra menus? Or is this a one-time deal?
And can someone confirmed whether this worked or not to jailbreak your PS3 please? Thanks!
Click to expand...
Click to collapse
yes you have plug your phone in each time u want to hack the ps3 , and it does work , i tried it last night
my only question is . Is the files in here patched to play backups?
illusive817 said:
yes you have plug your phone in each time u want to hack the ps3 , and it does work , i tried it last night
my only question is . Is the files in here patched to play backups?
Click to expand...
Click to collapse
Thanks! And according to OP, it should be:
.kAroshi said:
This version of PSFreedom is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
Click to expand...
Click to collapse
Yeah please mirror the link OP.
Its still not working for alot of people heh.
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