Is anyone planing to port that PSFreedom recovery image to the Moto Droid 1?
hxxp://forum.xda-developers.com/showthread.php?t=786744
i also would like to know this or at least a kernal update with the new payloads
greendusk said:
Is anyone planing to port that PSFreedom recovery image to the Moto Droid 1?
hxxp://forum.xda-developers.com/showthread.php?t=786744
Click to expand...
Click to collapse
Check the dev's website it's already been done.
Are you sure? I haven't see a psfreedom recovery image for the droid 1 anywhere.
phin1233 said:
Are you sure? I haven't see a psfreedom recovery image for the droid 1 anywhere.
Click to expand...
Click to collapse
LINKpsfreedom.com/wiki/Motorola_DroidLINK
let me know if you need any help... make sure you use the first link for the kernal, the mirror file is damaged (you'll notice it's smaller in size) I also was never able to get it to work with Cyanogen so I recommend Bugless Beast 0.5. I've been using this with no issues for over 2 weeks now.
sorry I am unable to post links right now
That's the regular psfreedom kernel, not the recovery image or the hermes payload.
btw, that works np for me running any version of CM6.
phin1233 said:
That's the regular psfreedom kernel, not the recovery image or the hermes payload.
btw, that works np for me running any version of CM6.
Click to expand...
Click to collapse
Is the point of that recovery image to have a dedicated image for exploiting your ps3? If so why not just create your own with Rom Manager, or am I missing the point of this?
They created a recovery image for the Desire where you can switch between payloads (to play a backup without an original blu-ray disc). It also allows you to update the module if any updates become available.
cold711 said:
Is the point of that recovery image to have a dedicated image for exploiting your ps3? If so why not just create your own with Rom Manager, or am I missing the point of this?
Click to expand...
Click to collapse
The recovery image he is talking about is that the exploit is stored in the recovery menu. Instead flashing the kernel and lose the ability to have mass storage, and charging the phone that all you do is just boot in the recovery menu and just do the exploit from their while at the same time not reflashing the kernels over and over again. Also the recovery works on every rom unlike the kernel exploit we were using.
victorythagr8 said:
The recovery image he is talking about is that the exploit is stored in the recovery menu. Instead flashing the kernel and lose the ability to have mass storage, and charging the phone that all you do is just boot in the recovery menu and just do the exploit from their while at the same time not reflashing the kernels over and over again. Also the recovery works on every rom unlike the kernel exploit we were using.
Click to expand...
Click to collapse
I would LOVE this. wonder if we can get it added to clockwork... Has the hermes updated .ko module even been ported to the droid yet? I see it out for all the HTC phones...
This info might be a little old, but could help others that wind up here when searching.
hxxp:// www .psfmod .klutsh .com/
Called psfMod, a recovery image for Android phones. Supports Moto Droid.
krusaderx said:
This info might be a little old, but could help others that wind up here when searching.
hxxp:// www .psfmod .klutsh .com/
Called psfMod, a recovery image for Android phones. Supports Moto Droid.
Click to expand...
Click to collapse
I kept looking but i couldnt find the asnwer as to which payload they are using, i want to run moh. i dont think pl3 runs good with moh anyhow great image. i always had to do nandroid but not anymore
oscarh24 said:
I kept looking but i couldnt find the asnwer as to which payload they are using, i want to run moh. i dont think pl3 runs good with moh anyhow great image. i always had to do nandroid but not anymore
Click to expand...
Click to collapse
Runs PL3 I believe, but there is an option to install other payloads from the sd card though.
Related
Supposedly Clockwork recovery works on the milestone according to the developer
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I was wondering if it is true or did he just assume that it does because the milestone is essentially a droid
brendanmurphy said:
Supposedly Clockwork recovery works on the milestone according to the developer
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I was wondering if it is true or did he just assume that it does because the milestone is essentially a droid
Click to expand...
Click to collapse
Interesting. Regardless, it's only a matter of time before the exploit for the Droid X gets ported over to our Milestones!
I just tried the Clockwork Recovery, but the Milestone doesn't accept it because the signature was not correct.
dsixda said:
I just tried the Clockwork Recovery, but the Milestone doesn't accept it because the signature was not correct.
Click to expand...
Click to collapse
Cool that be fixed?
Sent from my Milestone using XDA App
Probably, I haven't tried resigning with the usual testkeys.
Could you give it a go?
Silico said:
Could you give it a go?
Click to expand...
Click to collapse
I can confirm it starts up now, you have to move it to /sdcard/OpenRecovery/updates, then in your OpenRecovery menu, launch it from Miscellaneous-->Apply update
It's the same as OpenRecovery almost, I don't know what else to do..
Well that's interesting that it actually works! Got further than me
But could we not flash this as the default recovery rather than having to apply the update.zip and then updating via the recovery?
Sorry to resurrect, but can you confirm that Clockwork works on Milestone, and subsequently ROM Manager as well (since it only works with Clockwork).
Also, what are the differences btwn G.O.T. (which I'm using now) and Clockwork, and which do you prefer?
Thx
Backdraft11 said:
Sorry to resurrect, but can you confirm that Clockwork works on Milestone, and subsequently ROM Manager as well (since it only works with Clockwork).
Also, what are the differences btwn G.O.T. (which I'm using now) and Clockwork, and which do you prefer?
Thx
Click to expand...
Click to collapse
essentially its only the same concept , afaik clockwork uses sprecovery we use 'adb recovery' so what we call nandroid backup is not compatible form one another .
essentially they are no benefits of using either ..except for the fact that Openrecovery was built for the milestone . ie there is no reason at allto try and use anthing else .
Got ' OR is not the only one around , they are a few , its only a question of taste witch one you prefer , although the recovery loader built in GOT's allows you to load any recovery you want from within GOT's witch makes it my favorite choice ..
Does anyone know what happened to Amon_Ra PSFreedom recovery
He removed it because he didn't wanted any problems with sony. Lately sony has been very greedy...
Look it here...
http://www.ps3-hacks.com/2010/09/19/psfreedom-for-android-recovery-mode/#more-2417
arceles said:
He removed it because he didn't wanted any problems with sony. Lately sony has been very greedy...
Click to expand...
Click to collapse
That's a shame, and it probably means that we won't get any updates when the payloads improve or other exploits are discovered.
well i hope amon ra is reading this it looks like sont threats wont really affect people using psgroove payloads as its open source
so im hoping you will update your recovery image as the new hermes payload v3 is now out
if not does anyone know how to edit a recovery image so we can update the payload ourselves?
does anyone have the source for it. I am trying to possibly build it myself. Im reading up on building my own custom recovery.
same here but without the source or some help we cant do anything
klutsh has updated all the other devices recoveries but it was amonra dealing with the dream one
isnt it possible to create a APK Application and NDK with the Payload???
no idea but others may be able to answer that
Anxiously awaiting an update with hermes v3 payload.
here is the recovery 1.1.2 with the hermes v3 payload added and tested on G1
all thanks go to PACMAN366 for this update
I added the v3 payload to Amons recovery image
Dream (tested on G1):
http://www.megaupload.com/?d=X67BL6LU
N1 (untested):
http://www.megaupload.com/?d=81YBQTX7
Iv tested the dream image, it seems to work on my G1. i was able to load a backup of resistance 2 w/o a disc though most games still don't seem to work discless. I have not tested the Nexus one image yet soo i would not flash it unless you have access to a pc w/ fastboot. i assume no responsibility for any damages these images might cause. just select the hermes option on the psfreedom menu and insure your using the latest open backup manager (1.16 as of this edit).
Click to expand...
Click to collapse
All we need now is it running Hermes v4!
skreama said:
here is the recovery 1.1.2 with the hermes v3 payload added and tested on G1
all thanks go to PACMAN366 for this update
Click to expand...
Click to collapse
SICK! tnx a lot
Check the psfreedom g1 thread, I updated the recovery payload to hermesv4b
So, I would of already rooted my Droid 3, exept, that it did not have custom recovery. But I want to make sure that both of these are available
Rom Manager
Custom Recovery(Obviously)
Thanks for any response.
techno-update said:
So, I would of already rooted my Droid 3, exept, that it did not have custom recovery. But I want to make sure that both of these are available
Rom Manager
Custom Recovery(Obviously)
Thanks for any response.
Click to expand...
Click to collapse
You can use Droid 3 Bootstrap or Safestrap as a custom recovery, IMO I see no reason to use ROM manager, as Safestrap (what I use) works perfectly..
Safestrap is better than normal Bootstrap because you can enable the "safe system" and install the system partition on the /preinstall directory (so you can leave your normal system intact) Although it depends on your phone model, if you're running a XT862 (Motorola Droid 3 - Verizon) then you're set. Other phone models have issues with safestrap.
-You might be able to use ROM Manager, but I would stick with Safestrap or Bootstrap because I KNOW that they work.
I like to use custom recovery though because it is easier/simpler and faster to do. I had it on my Droid Incredible. Just want to make sure it works right now. Though i will look at that. How would i apply it?
techno-update said:
I like to use custom recovery though because it is easier/simpler and faster to do. I had it on my Droid Incredible. Just want to make sure it works right now. Though i will look at that. How would i apply it?
Click to expand...
Click to collapse
You should be able to find Safestrap via Hashcode's website, go to the [SELFKANG] Cyanogenmod 7 page in Android Development, and you will be able to find his website that has the file. It is an APK file, so you just install it and run the installation from the app. I have not used custom recovery through ROM Manager, because I don't think it's compatible, but you could try it out..
The Mods need to sticky kshen1's information thread.
http://forum.xda-developers.com/showthread.php?t=1289611
-smc
somemadcaaant said:
The Mods need to sticky kshen1's information thread.
http://forum.xda-developers.com/showthread.php?t=1289611
-smc
Click to expand...
Click to collapse
Okay, so we do have it, can I flash it from Rom Manager?
techno-update said:
Okay, so we do have it, can I flash it from Rom Manager?
Click to expand...
Click to collapse
i don't think we can, rom manager flashes a version of the custom recovery to the bootloader which runs before the phone runs so that if you accidentally mess up your phone, you can easily restore it back to how it was before, and we don't have an unlocked bootloader, so by using the 2nd-init, we bypass needing to unlock the bootloader to be able to run custom ROMs (at least this is the way i understand it), so until they release a bootloader unlock, we're stuck using 2nd-init and bootstrap/safestrap to load up custom roms.....some roms you need to use safestrap and for some you need to use bootstrap, so you'd just have to check their instructions they give before the download link to make sure you're using the right one, using the wrong one can cause unforseen things to happen and can possibly brick your phone
Alright, I rooted, installed bootstrap recovery. Everything is good. Thanks guys.
Have not seen anything like this uploaded so I figured I would get a copy online.
Recently I had a Droid 3 get replaced with an XT861 by Verizon's warranty replacement service.
Physically and electronically the phone is exactly the same as the Droid 3 XT862.
However, the software installed was much different than the usual Verizon ROM.
The ROM reports as 5.8.25.XT861.ACG.en.US
I believe the ACG stands for Associated Carrier Group (Alltel, nTelos, etc...)
How Verizon got this ROM and why they sent it on this phone I have no idea but it is very lightweight, little to no bloat that Verizon typically loads on their stock ROM images.
As far as I know there is no SBF for this but attached is a CWM recovery image.
Not certain if Safestrap will recover from it but CWM will for sure.
***UPDATE*** DO NOT USE SAFESTRAP. CWM ONLY -
THIS IS NOT A ROM. THIS IS A CWM BACKUP IMAGE
Available here: http://d-h.st/kEd
***UPDATE 1/23/13***
This is an extraction of the system.tar and converted into a ROM .zip
Wipe data/cache and dalvik before flashing.
Confirmed working with CWM & Safestrap
Available here: http://d-h.st/mCB
Deodexed ROM (Courtesy of thingonaspring) http://d-h.st/H5w
Doesn't quite work on XT862 - locks up on boot - so it looks like XT861 isn't exactly a rebranded XT862. Thought I'd post this, in case somebody else is thinking of trying it
Nonetheless, this sounds interesting, allright (converting CWM to TWRP for safestrap is trivial btw). Would be interesting to create a frankenbuild of stock XT862 with just the packages in this fella, for starters.
There is also this ROM here, which calls your phone a Milestone 3. (5.8.938.XT862, Android 2.3.6): http://forum.xda-developers.com/showthread.php?t=2068022
It works great on Safestrap 3.05, works great as a Verizon phone.
mionica said:
Doesn't quite work on XT862 - locks up on boot - so it looks like XT861 isn't exactly a rebranded XT862. Thought I'd post this, in case somebody else is thinking of trying it
Nonetheless, this sounds interesting, allright (converting CWM to TWRP for safestrap is trivial btw). Would be interesting to create a frankenbuild of stock XT862 with just the packages in this fella, for starters.
Click to expand...
Click to collapse
Are you running .906 or .890?
I was able to flash it onto an XT862 with .906 no problem.
mionica said:
Doesn't quite work on XT862 - locks up on boot - so it looks like XT861 isn't exactly a rebranded XT862. Thought I'd post this, in case somebody else is thinking of trying it
Nonetheless, this sounds interesting, allright (converting CWM to TWRP for safestrap is trivial btw). Would be interesting to create a frankenbuild of stock XT862 with just the packages in this fella, for starters.
Click to expand...
Click to collapse
And the XT861 definitely is exactly the same as the XT862 physically and mechanically. The boot kernel on it is basically the .906 boot.img so trying to run this ROM on the older boot.img will not work without modification.
RWALEY said:
Are you running .906 or .890?
I was able to flash it onto an XT862 with .906 no problem.
Click to expand...
Click to collapse
RWALEY said:
And the XT861 definitely is exactly the same as the XT862 physically and mechanically. The boot kernel on it is basically the .906 boot.img so trying to run this ROM on the older boot.img will not work without modification.
Click to expand...
Click to collapse
Ok, fair enough, I stand corrected. I must have done something wrong there, as I'm on .906 as well.
What I did was, convert the .zip from cwm to twrp (gzip --best'ed the part images, renamed then md5sum'ed them), then restored the thing (twrp in safestrap3.05) on an empty slot; restore succeeded, and well, it didn't quite boot.
Btw, if it's obvious from the above just what it is I did wrong, by all means, tell me. I only got the d3 last week, I'm still on the learning curve
mionica said:
Ok, fair enough, I stand corrected. I must have done something wrong there, as I'm on .906 as well.
What I did was, convert the .zip from cwm to twrp (gzip --best'ed the part images, renamed then md5sum'ed them), then restored the thing (twrp in safestrap3.05) on an empty slot; restore succeeded, and well, it didn't quite boot.
Btw, if it's obvious from the above just what it is I did wrong, by all means, tell me. I only got the d3 last week, I'm still on the learning curve
Click to expand...
Click to collapse
I really don't use safestrap and I am not familiar with it. You might want to try regular CWM. That's what has worked for me.
Or just extract the system.tar and flash that. Fairly certain that will run on both old and new bootloaders. If I get some free time I will make a flashable ROM that incorporates this XT861 image.
All right, it works. And looks pretty nice! Had to purchase CWM for Droid3 for that though.
I maintain my initial comment - flashing while on SafeStrap is just asking for trouble:
- flashed on a SafeStrap ROM slot: doesn't boot
- flashed over main ROM: had to fastboot to de-brick it
mionica said:
All right, it works. And looks pretty nice! Had to purchase CWM for Droid3 for that though.
I maintain my initial comment - flashing while on SafeStrap is just asking for trouble:
- flashed on a SafeStrap ROM slot: doesn't boot
- flashed over main ROM: had to fastboot to de-brick it
Click to expand...
Click to collapse
Good to know. I am in the process of converting it over to a ROM that should be flashable on CWM or Safestrap.
Not sure why you were charged. As far as I know, it is free through the Rom Manager app.
RWALEY said:
Not sure why you were charged. As far as I know, it is free through the Rom Manager app.
Click to expand...
Click to collapse
Oops, I wasn't using Rom Manager - told you I am a noob Nevermind, it's fine - this ROM installed, so I just got rid of CWM (the logwrapper* deal), got SafeStrap back and am now backing it up w/ SS. Time to see whether the 2.3.6 STK from Milestone3 works on this ROM...
I have updated the post to include a converted system.tar into a ROM that should work on CWM or Safestrap.
I have not had a chance to test it yet so flash at your own risk.
Wipe data, cache and dalvik before flashing.
Re: XT861 5.8.25 Stock ROM. Android 2.3.6 - UPDATED 1/20
I tried to install this rom as a backup and as a zip rom, nothing happened recovery give me - error.
Sent from my DROID3 using xda app-developers app
Tanzior said:
I tried to install this rom as a backup and as a zip rom, nothing happened recovery give me - error.
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Same. Only tried with safestrap(in a secondary slot) and the new zip but get error immediately. Didn't go any further yet.
Looks like it may not work with Safestrap then.
I have only gotten both the backup and the ROM to install in CWM.
If anyone else wants to modify the files to try and get compatibility with Safestrap feel free too. I do not have much experience with it.
Re: XT861 5.8.25 Stock ROM. Android 2.3.6 - UPDATED 1/20
CWM error: can not copy E:/META INF/……/binnary update
Sent from my DROID3 using xda app-developers app
Tanzior said:
CWM error: can not find E:/META INF/……/binnary update
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Very strange. I do not get that at tall.
I will look into it. Wondering if something bad happened during the upload.
I have a feeling the extra xbin folder stuff might be causing an issue for some people.
I have recompressed and signed a new .zip without it.
Have been able to install in CWM multiple times without issue.
Will update the first post.
Linked here: http://d-h.st/mCB
RWALEY said:
I have a feeling the extra xbin folder stuff might be causing an issue for some people.
I have recompressed and signed a new .zip without it.
Have been able to install in CWM multiple times without issue.
Will update the first post.
Linked here: http://d-h.st/pzO
Click to expand...
Click to collapse
Thank you for the last ZIP installed fine, except that it is 177 MB, the old file size was more 350Mb (there probably was an error.)
---------- Post added at 10:49 AM ---------- Previous post was at 10:44 AM ----------
Looks great - there are no unnecessary programs from Verizon. Maybe MiniMoto will be developed on the basis of this firmware, if the author of this idea like.
@Tanzior - maybe it will
Anyone able to install with Safestrap?
hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.
What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.
sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Here are some pics of the phone and build number
sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.
to me, it doesnt look like a n6, it looks like a moto x pro..
simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.
I'm going to try to flash a stock N6 ROM to see if it will load.
Is this prototype the one with fingerprints sensor on the back?
It has a power button on the back.
sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.