[Q] [REQUEST][SBF] XT860 - Bell Canada Droid 3 - Motorola Droid 3

Hi there !
Maybe is too soon to ask, but 2 days after I rooted my XT860 (oneclick way), it reboot itself (while in stand-by !) and now I am stuck in a boot loop . Unfortunately, USB Debug is not enabled and already tried factory reset with no success ("recover" type included :-/). So I think that the only way fix it now will be SBF.
I didn´t remove anything from /system (but install tons of applications via androidmarket), so I´m no really sure if it is really a software problem. During de boot loop I see some color lines/retangles/patterns over "M logo pulsing" and then, the phone freezes and reboot again (Is this behavior common when the phone is bootlooping ? )
If anybody have Bell XT860 SPF around, please, let me know. Suggestions will be also welcome.
Regards !
Claudio Cuqui

My XT860 took the root process fine, guess you didn't have such good luck.

May I ask what your Build version is for the Canadian phone?
Blur_Version.#.#.#.Bell.en.CA
Something like that.

Sure !
5.1.544.XT860.BellMobility.en.CA
If you need any further informations, let me know.
Thanks for your time,
Claudio

Thank you. I'm just trying to see which phone versions are out there at the moment.

cuqui said:
Sure !
5.1.544.XT860.BellMobility.en.CA
If you need any further informations, let me know.
Thanks for your time,
Claudio
Click to expand...
Click to collapse
I would also love an SBF for Bell Mobillity's XT860. I created an annoying glitch when I removed some of the system apps and would love to start from scratch -- simply freezing apps I don't want rather than deleting...

I'd settle for an appliable update, the leaked one wont verify the sig for me because it's not from bell I assume

Willis111 said:
I'd settle for an appliable update, the leaked one wont verify the sig for me because it's not from bell I assume
Click to expand...
Click to collapse
I'm worried that an update might have issues with my modified/rooted phone and would love to restore it to it's original state PRIOR to the update that is coming from Bell.

AFAIK, when you update your phone, unless you change A LOT in /system, in the end of day, an updated follow by a factory restore (menu option) will have almost the same effect that a SBF. My biggest concern is, if I can still be able to root it after the update (100% sure that it will be lost after update) and, for me, this is a big problem since I need it for openvpn :-/ Really don´t know why google don´t put it built in as it does with other vpns......
Regards !
Claudio

I read in a thread here that there were a few root methods for the droid 3 that weren't made public so they wouldn't be patched even if the current one is. Only rumor though, no one has said for sure that they have another working root method, just a guy who thinks he knows a guy who said ....

Good to know that they have a plan B in the case of current root method be patched by a new release ;-)
Regards !
Claudio

Same version on mine. I guess there is only one version available (that one.)
I am very much hoping there will be an SBF released for our phones soon. I am reluctant of hacking/altering stuff, because there is no secure way back and I don't want to be stuck with crappy working camera, or car dock battery drain issues. Hopefully our "safety net" will arrive soon!
Sent from my XT860 using Tapatalk

In the meantime, we have a system dump provided here:
http://forum.xda-developers.com/showthread.php?t=1255647

UnhappyDroid3User said:
I'm worried that an update might have issues with my modified/rooted phone and would love to restore it to it's original state PRIOR to the update that is coming from Bell.
Click to expand...
Click to collapse
Do you know of an update coming from bell? I tried to find information on it as I know Verizon is releasing one soon(apparently soak test starts tomorrow). I would love to have the cell standby battery issue fixed.
Sent from my rooted xt860

Don't hold your breath.. Motorola tends to update Verizon's models first, then the rest of the world. I guess due to Verizon being their 'biggest customer'. Maybe in 3-4 months we'll see something (trying to remember how long it took them to release some fixes for Milestone 1... if I remember right we saw Froyo on Milestone 1 about 6 months after OG Droid or wasn't it longer?)

leobg said:
Don't hold your breath.. Motorola tends to update Verizon's models first, then the rest of the world. I guess due to Verizon being their 'biggest customer'. Maybe in 3-4 months we'll see something (trying to remember how long it took them to release some fixes for Milestone 1... if I remember right we saw Froyo on Milestone 1 about 6 months after OG Droid or wasn't it longer?)
Click to expand...
Click to collapse
I think it's actually because providers (verizon, bell etc) buy the updated software off of manufacturers (motorola, htc etc). That's exactly why I'm not holding my breath either, I've got a bell phone and although they've made a huge leap in getting new phones recently I'm reluctant to say the same about software updates.

Well, since developers are busy cooking some new roms from verizon´s droid3 , and we hear only silence from Bell Canada about a possible update for our XT860 until now, I decide to try somethings in my already bricked phone (since I have nothing to loose). I have experience with linux and take some time studying the images available from verizon. The idea here is the following:
Get backups from the following directories (and all sub-directories) from a WORKING / ROOTED / *BELL* XT860:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
preinstall partition should have only the 2 games and some videos explaining how the phone works (and they take a considerable amount of space, so I think we can work on it latter). One important thing to note is that the backup should be made using a software that is capable to keep permissions/ownership of the files and handle symlinks properly. Since I´m new to android I don´t know which software would meet these requirements (tar definitely will do - so, if you rooted your phone you should trying something like busybox tar -cpzf /pathofyoursdcard/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin - will work - maybe titanium do this as well (?). This will take a while. After that, I will use system.img and preinstall.img structure available for verizon to rebuild one similar for XT860 using the files from dump.tgz.
Once I have build these 2 files, I intent to flash them using fastboot on linux (already available here in XDA forum).
Assuming that I just messed with files in those 2 partitions (like, I think, most of XT860´s owners), they should suffice for bring the phones back from the death (hopefully !).
Here is the problem: since my XT860 is bricked, I don´t have how to backup those files on my own. So, I, if any good soul could create it and make it available in some place (dropbox, megaupload, etc), I will be very grateful and, of course, promise if that idea works (and don´t make my phone crash and burn , I will make those images available for everyone brave enough to try them
Regards !
Claudio
PS: if anyone see something terrible wrong with this strategy, please, let me know

cuqui said:
Well, since developers are busy cooking some new roms from verizon´s droid3 , and we hear only silence from Bell Canada about a possible update for our XT860 until now, I decide to try somethings in my already bricked phone (since I have nothing to loose). I have experience with linux and take some time studying the images available from verizon. The idea here is the following:
Get backups from the following directories (and all sub-directories) from a WORKING / ROOTED / *BELL* XT860:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
preinstall partition should have only the 2 games and some videos explaining how the phone works (and they take a considerable amount of space, so I think we can work on it latter). One important thing to note is that the backup should be made using a software that is capable to keep permissions/ownership of the files and handle symlinks properly. Since I´m new to android I don´t know which software would meet these requirements (tar definitely will do - so, if you rooted your phone you should trying something like busybox tar -cpzf /pathofyoursdcard/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin - will work - maybe titanium do this as well (?). This will take a while. After that, I will use system.img and preinstall.img structure available for verizon to rebuild one similar for XT860 using the files from dump.tgz.
Once I have build these 2 files, I intent to flash them using fastboot on linux (already available here in XDA forum).
Assuming that I just messed with files in those 2 partitions (like, I think, most of XT860´s owners), they should suffice for bring the phones back from the death (hopefully !).
Here is the problem: since my XT860 is bricked, I don´t have how to backup those files on my own. So, I, if any good soul could create it and make it available in some place (dropbox, megaupload, etc), I will be very grateful and, of course, promise if that idea works (and don´t make my phone crash and burn , I will make those images available for everyone brave enough to try them
Regards !
Claudio
PS: if anyone see something terrible wrong with this strategy, please, let me know
Click to expand...
Click to collapse
I would be willing to help you on this. I'm fairly new to android and even newer to Linux but would love to see a reliable method of saving bricks for our device. It might spark some ROM development too. If you can help me with some directions we could make this happen. I assume I would have to restore to stock in order to make a reliable recovery.
Sent from my rooted xt860

First at all, thanks for your time and help !
You will need:
- a sd card (1Gb will be fine - to save the tar file - it is not show stopper if you don´t have it, but it will make things a lot easier;
- rooted Bell XT860 device - as far as I can see by your signature, you already have it ;-)
- access to a root shell - and for that you need a terminal - connectbot from android market will work - it´s free application;
- after install it, you should try to connect as root to ip 127.0.0.1 (ou choose local conection from connectbot) - you will probably see an warning requesting authorization from connectbot to allow it run as root - you should allow it;
- if everything works as expected, you will see a terminal waiting for commands. Then you should navigate (using cd /; and then, running ls -l (will show all files) on directory to see if you can see all the files/directories that I listed in last post:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
and if you can see your sdcard (you should see its contents by running cd /sd-ext; ls;
- if you find all files you should run this command (and assuming that your sdcard is mounted on /sd-ext:
busybox tar -cpzvf /sd-ext/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin
- after that it will create a tar file keeping all file properties below /sd-ext (your sdcard) called dump.tgz with all content need. There are LOTS of files, so, it will take some time to finish.
- If everything ends fine, I will need this file (dump.tgz). Please, upload it where you like most (dropbox, rapidshare, megaupload, whatever) and send me the link to download.
You don´t need to restore your phone to stock. The only side effect would be a bigger image if you have installed some applications.
Again, thanks for your time and help !
Best Regards !
Claudio
PS: Let me know if you need further information/help.
PS2: Sorry if some part of my instructions are not pretty accurate (I´m trying to remember the commands/sequence since I don´t have my phone working right now :-/)

cuqui said:
First at all, thanks for your time and help !
You will need:
- a sd card (1Gb will be fine - to save the tar file - it is not show stopper if you don´t have it, but it will make things a lot easier;
- rooted Bell XT860 device - as far as I can see by your signature, you already have it ;-)
- access to a root shell - and for that you need a terminal - connectbot from android market will work - it´s free application;
- after install it, you should try to connect as root to ip 127.0.0.1 (ou choose local conection from connectbot) - you will probably see an warning requesting authorization from connectbot to allow it run as root - you should allow it;
- if everything works as expected, you will see a terminal waiting for commands. Then you should navigate (using cd /; and then, running ls -l (will show all files) on directory to see if you can see all the files/directories that I listed in last post:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
and if you can see your sdcard (you should see its contents by running cd /sd-ext; ls;
- if you find all files you should run this command (and assuming that your sdcard is mounted on /sd-ext:
busybox tar -cpzvf /sd-ext/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin
- after that it will create a tar file keeping all file properties below /sd-ext (your sdcard) called dump.tgz with all content need. There are LOTS of files, so, it will take some time to finish.
- If everything ends fine, I will need this file (dump.tgz). Please, upload it where you like most (dropbox, rapidshare, megaupload, whatever) and send me the link to download.
You don´t need to restore your phone to stock. The only side effect would be a bigger image if you have installed some applications.
Again, thanks for your time and help !
Best Regards !
Claudio
PS: Let me know if you need further information/help.
PS2: Sorry if some part of my instructions are not pretty accurate (I´m trying to remember the commands/sequence since I don´t have my phone working right now :-/)
Click to expand...
Click to collapse
Seems straightforward enough. Do I need to unfreeze/rebloat? And I'm running update 9 beta of the supercharge which makes changes to build.prop. unsupercharge first? Also I've done theming in uot kitchen. I do have backups of the original framework-res. Also are any of my personal info stored in these folders(name/phone number/website login info)
I'm out and about right now but I'll try it out when I get home
Sent from my rooted xt860

Related

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.

[Q] i9000m + Froyo + Internal SD Card failure ?

Ok so there's alot of info. regarding Internal SD card failure and Froyo.
My question is will this occur with a natural Froyo update instead of a flash ?
I have a stock i9000m - never even rooted, no lag fix, nothing.
I heard Froyo will be coming soon (im guessing via Kies?)
Will the Froyo update mess up my Internal SD as appears to be happening with Froyo Flashs ?
Also, will I lose my apps when I update via Kies to Froyo ?
thanks guys.
From what I've seen on here there is no direct link to sd failure from flashing. I think just as many have failed that were not flashed. Always possible though that a botched flash could spell doom.
An official update should not damage your phone. If it does, you should return it to bell for repair or replacement.
Many on here recommend a factory reset after update, I'm planning to do that myself. Reinstalling apps is no big deal. Takes only minutes and because they are linked to your google account you don't have to buy paid apps again.
Sent from my GT-I9000M using XDA App
However, the linking to the Market account does not restore unpaid apps. These you will have to install again, and of course, you have to remember which ones these are. This could be time consuming.
In my case it took about 2 hours. I had many apps, and in some I could not remember the names: A fair amount of time was lost searching for the names.
Any easy solution to this is to back up this directory on your phone afore you reset:-
Directory: /data/app
It contains all the .apk of your apps.
use the ADB to get a shell on your phone - There are a few guides around on how to set this up. Once set-up, please use this command to get a shell:
adb shell, and then su to root:
adb shell
su
* How to backup.
Change into the directory
cd /data/app
Archive the files to a file on your SD card. In this case the archive tar file is called /sdcard/apps.tar. You can put it anywhere you want with any filename you like.
tar cvf /sdcard/apps.tar .
* Perform a factory reset.
* Restore the files.
Here you should extract the archive into a tempory directory and use a file manager like Astro to click on and then install the apk files:
Create a temp directory for the files:
mkdir /sdcard/apkrestore
Change to the directory:
cd /sdcard/apkrestore
Extract the files from the archive:
tar xvf /sdcard/apps.tar
List the file files in the dir - you will see many files with .apk extensions.
ls /sdcard/apkrestore
Install the apks
Start ASTRO file manager and navigate to /sdcard/apkrestore
Click on the apk you wish to install.
Its funny how people seem to omit this information: as if they think people only ever buy apps and never use the free ones ;P
forgetmyname said:
However, the linking to the Market account does not restore unpaid apps. These you will have to install again, and of course, you
Its funny how people seem to omit this information: as if they think people only ever buy apps and never use the free ones ;P
Click to expand...
Click to collapse
Awesome info. I guess I will try this.
Questions. I obviously have to have a root to use these ADB commands ? I haven't rooted phone yet.
Other question, is there an easier way to back up all apps? Like what if I root ? I can get Titanium Backup Pro -- will this work? would this back up apps to my sdcard ? I have a 32gb external card too -- can I back up apps to this or no ?
Final question,
has anyone in Canada been able to do a normal, official update via kies to froyo 2.2 ?? is it avail. yet ?

[Dec 21][APP]PS3DJB v2.5.1 Supports Eng, Ger, Nor, Esp & Fr

Hello everyone,
Here is my app i have been working on. It will install all files to your sd card needed to jailbreak and downgrade your ps3 with your HD2 Only. Now i have some time think this link is long overdue to be posted. Where this app originated from. Again thank you to all the other devs out there for there hard work that has now become a all in one solution.
What the app does:
This app will allow you to downgrade your firmware to any firmware you want. (PS3 Slim's cannot go as far back as Fat Consoles.) The downgrade only works with FW's up to 3.50. (If you have FW3.55 you are out of luck for now. Unfortunately there is no solution on the market nor in the community for that FW version.) This app will also allow you to patch your android build with all the files needed to jailbreak your ps3.(this will be changed real soon.) It also includes many payloads so u can use the one that best matches your needs.
Other Languages:
German version Located here I have also translated the first post in German as well. Enjoy
Norwegian version Located here I have also translated the first post in Norwegian as well. Enjoy
Spanish version Located here. It is compatible with Esp Rom's storage cards. I have also translated the first post in Spanish as well. Enjoy
French version Located here. It is compatible with Fr Rom's storage cards. I have also translated the first post in French as well. Enjoy
Instructions:
you will need to download both files found below.
DowngradeUpdater(needed)
PS3DJB Updated to 2.5.1 - English Only - Now Includes darkstone hd2froyo v3 in a custom folder just for jailbreaking. Size 103mb
Install:
Make sure you have placed your android build of your choice on the root of your sd card before installing. Your android build must be placed in the Android folder.
1.install downgradeupdater.cab to storage card. (this only contains the downgrade folder)
2. install PS3DJB.cab to storage card. (this contains the main UI and all jailbreak files)(does not include modified 3.41 PUP, lv2diag.self file 1 and lv2diag.self file 2)
Pre Use:
1. run app and select backup original android build (must do this first before you run setup jailbreak if you want to keep your original zImage of your Android build.)
2. select setup jailbreak. This will transfer all the files to your android build. if you replace your android build later on with a newer version just rerun the setup jailbreak.
Use:
1. once you set up jailbreak then proceed to select Launch PS3DJB. Follow the jailbreak instructions on the process. There are tons of tuts on how to do so. It is all they same for the most part. What is different for the HD2 is Once you boot into Android go and launch Gscript and select the payload of your choice. Then wait till it starts to auto countdown then plug the phone into the ps3 and start the jailbreak process.
2. If you want to downgrade your ps3 launch downgrader. This will take you to a mini android build made specifically for downgrading your ps3. This will not affect your other android builds
Questions and Answers:
Q) how do I know when everything backed up, restored or setup for jailbreak?
A) it will complete when the button image snaps back to normal when completed.
Q) im done downgrading and cant turn off the phone with the power button?
A) If you run the downgrade portion of the app you will need to pull the battery out when your done and reboot the phone. this is not due to my app it is part of the downgrade setup.
Q) Where is the Gscript folder located at?
A) gscript folder installs to the root of your SD card. It should install when you install the PS3DJB.CAB if you do not see it. Reboot your phone. Sometimes it caches till a reboot. not sure if its a OS issue or a Rom issue.
Q) I started Gscript and only see a couple of payloads. Isnt there more?
A) if you are missing payloads in gscript listing hit the windows button then select add script. Then finally select load. find a missing script select it and save. it will now populate to your main list in gscript. you will need to add. hermes 3.50 + PSN v4b, CE-X hybrid payload, and 2.76FW payload.
Q) I have multiple android builds will this mess with them?
A) Yes and No. It will only mess the the android build located in the Android Folder. If you want to make sure your stock android build stays stock after jailbreaking run the backup original android build button first to back up a copy of your original zImage. Once your done jailbreaking just run restore original android build to restore the backedup zImage.
Q) Do I need to install the downgradeupdater.Cab if I don’t plan on downgrading?
A) No you do not. It does not affect anything releated jailbreaking. If you hit the launch downgrader button without it installed will cause the app to display a message about it missing.
Q) if i downgrade will i loss my game saves? if so how do i keep them?
A) If you downgrade you may loose your game save. Go to system settings and back up your system. the option is at the bottom of the list almost. you can restore the same way
if you have any suggestion let me know.
enjoy!
PAYLOADS included:
Hermes v4b+355 FW3.41
CE-X FW3.41
Hermes FW3.41
Hermes v4b + psn + 3.50 FW3.41
PL3 FW2.76
PL3 FW3.01
PL3 FW3.10
PL3 FW3.15
PL3 FW3.41
*IMPORTANT*
for downgrading you will need the 3.41 modified pup, lv2diag.self file 1 and lv2diag.self file 2. these are needed once you obtain service mode
Change log:
Version 2.5.1
*added my custom data.img (57mb) to jailbreak rom. Should save a lot more space on the storage card and boot faster. My boot took 1 min 37 sec which was faster than the 1GB data.img created on first boot.
Version 2.5
*Removed setup Jailbreak, backup and restore buttons.
*Jailbreaking now has a dedicated folder that has a pre setup build of android ready to jailbreak
*included a dedicated android launch button for those who have daily use builds of android on there phone located in the android folder
*new start menu icon - thanks to drkfngthdragnlrd
Version 2.0
*removed any backing up or replacing of initrd.gz as it is not really needed for our purposes.
*should work better with new builds of android as i backed off the filestructure some.
version 1.6
*backup original android build now backs up zImage and initrd.gz
*restore original android build now restores zImage and initrd.gz
version 1.5
*added backup original android build button - this will back up your original zImage on your untouched android build.
*added restore original android build button - this will restore your original zImage and delete all files related to jailbreaking in your android folder
*updated functionality of setup Jailbreak button - now will create all jailbreak related directories in the android folder then install all files needed.
Thanks goes out to:
mangahoteles, Darkstone, Dan1j3l for the original builds of psfandroid
The Invisible GoD & KillaHurtz for there payload ports
sorry for noob question... what for this app actually?
Wonderful app! Thank you for your work. Wouldn't this be better suited for the HD2 Apps forum though?
socrated13 said:
Wonderful app! Thank you for your work. Wouldn't this be better suited for the HD2 Apps forum though?
Click to expand...
Click to collapse
i thought it might be but was not sure. if a mod wants to move it feel free.
This app just make things easier/noobier for people who want to jailbreak or downgrade there ps3. i personally got annoyed always having to open file explorer and hit both options to launch. i have a lot of crap on my sd card so this makes it easier for me and i hope others. it will also give you a dedicated folder for the downgrade.
i can always make the jb a dedicated folder but i notice that android runs fine with the jb files integrated. it did not affect my user experience so i did not do that originally.
Thank you! This is an extremely useful app, you have made my life so much easier...
azaini said:
sorry for noob question... what for this app actually?
Click to expand...
Click to collapse
If you don't no for what this app is, probably is not for you!
HackMimic, thanks for the great job!
HackMimic said:
i thought it might be but was not sure. if a mod wants to move it feel free.
This app just make things easier/noobier for people who want to jailbreak or downgrade there ps3. i personally got annoyed always having to open file explorer and hit both options to launch. i have a lot of crap on my sd card so this makes it easier for me and i hope others. it will also give you a dedicated folder for the downgrade.
i can always make the jb a dedicated folder but i notice that android runs fine with the jb files integrated. it did not affect my user experience so i did not do that originally.
Click to expand...
Click to collapse
Very cool good job!!
I am curious to where you get the lv2diag.self file 1 and lv2diag.self file 2 files
youngkwang49 said:
I am curious to where you get the lv2diag.self file 1 and lv2diag.self file 2 files
Click to expand...
Click to collapse
Like here for example...
Doesn't work for german ROMs, cause in german "Storage Card" means "Speicherkarte" and so the path for the setup is wrong ... Installing is no problem.
This is awesome
Thank you HackMimic
the only probem with using ps jailbreak on my hd2 android is that it breaks my camera
had the same problem when I made my multi os launcher app days ago. I have the translation for German and another language. I will make the proper changes for ya. Would you prefer everything visual to read in German.
HackMimic said:
had the same problem when I made my multi os launcher app days ago. I have the translation for German and another language. I will make the proper changes for ya. Would you prefer everything visual to read in German.
Click to expand...
Click to collapse
German is not that important for me, but if it is no big effort it would be fine.
What version firmware does this work on i have .55 firmware, a stupid friend of my sister installed it. I hope it works for this too
supaet said:
the only probem with using ps jailbreak on my hd2 android is that it breaks my camera
Click to expand...
Click to collapse
Same here.
HectiQ said:
What version firmware does this work on i have .55 firmware, a stupid friend of my sister installed it. I hope it works for this too
Click to expand...
Click to collapse
unfortunately if your at 3.55 there is no way to downgrade as they revoked the leaked keys. there where 3 of them i believe. i would not update your ps3 anyfurther down the road and wait till there is a workaround. im always scared my roommate will do the same. thats why i bought two. one jb in the front with a ps3key. thats what my roommate will use since its easy and one in my room with my htc now.
bahoiz said:
Same here.
Click to expand...
Click to collapse
Does it break the camera in WM or android? My camera in WM works fine. if in android it might be the zimage file used. I think i will need to make a backup folder and include a button to backup original zImage of the rom so you can restore it when not jailbreaking.
also doing a pure german rom is no big deal. Let me update the app to do this new stuff first and when i upload it i will upload a translated version as well.
Hi,
I am using an english version wm, still says that the directory can't be opened
Storage Card/blah blah blah..
using android RAM version by darkstone.. maybe that's the cause?
Whenever I click on "Setup Jailbreak", I get an error message saying, " An unexpected error has occurred in SmartDeviceProject1.exe. Select Quit and then restart this program, or select Details or more information." I'm using a dexter wm rom, "TheDarkOne WWE". Radio 2.10.50.26. Any help would be appreciated.

How to restore deleted (stock) System Apps?

Let me apologize first of all as I come from 5 years of using Windows Mobile knwoing what I am doing (cooking ROMs included) and now just got my Galaxy /Android a couple weeks ago and am blank at all of it.
After messing up with some system files and (useless) stock applications (like I removed stk.apk and other stuff) I decided to do a full hardware reset as the phone started getting random crashes.
But after the full reset things only got dramatically worse. I quickly realized all the missing system apps are still missing (I thought they'd be "restored") and basically nothing works, just crashes one after the next, cant use anything.
So, a hardware system reset on the galaxy, doesnt really reset anything except user installed apps and settings... amazing
Can someone please tell me (the idiot here, I know) how to do a real full restore where all system files, all missing files and positively everything gets back in the Tab as it was originally?
What a flippin' nightmare... Thanks in advance very much!
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
Click to expand...
Click to collapse
OK, first of all a big thanks for both file and info. Aside from the Stk.apk, the biggest thing that made me run into problems was trying to update my Contacts.apk:
http://forum.xda-developers.com/showthread.php?t=907399
things didnt work out for me and even after restoring the original files (Contacts.apk and Contacts.odex) nothing really worked again, reason for wich I tried a system reset.
Now, do I need to re-root the Tab or its still rooted, and can I perform the operations easily with Root Explorer like I did before? You mentioned to use adb and set permissions to 644 after push but, sorry again for the ignorance, I have no clue what adb is nor what/how to set permissions. Pathetic to be ignorant huh?
My last 2 questions are, where could I find the original Contacts.apk and Contacts.odex and if needed a full ROM to do a total restore?... hopefully I wont need to get to that point?...
Thanks a million again.
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
bartito said:
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
Click to expand...
Click to collapse
Hmmmm thanks again but I think Im beyond all this. I dont have a file manager on my system, just realized I deleted the useless stock one and had repalced it with Root Explorer and ES File Explorer. I have them on my External SD Card to install them again but withou a file manager or an app installer cant get to them. And I tried download an app installer from the Market and get Framework errors non-stop and downloads do not initialize... I think Im beyond a quick fix... how do I get my hands on a stock full ROM to restore everything... and how? What a nightmare... gotta tell you, I love Windows Mobile... I love it... never ran into anything like this in the past 5 years of using it... never...
Thanks again!
use "adb" in order to access to your tab from your desktop pc.
bartito said:
use "adb" in order to access to your tab from your desktop pc.
Click to expand...
Click to collapse
Cant. Dont even know if I need Kies installed or not (I did have it installed) but adb just asks me to connect the phone and thats it... its connected aready... this is desperating...
OK I did manage to connect with adb but, how to I install applications? I can navigate to my SD card where I have ES File Explorer and Root Explorer but dont seem to be able to install them... Also if i try to copy Stk.apk I get immediately an failute message... this is crazy...
OK so I managed to install ES File Explorer and Root Explorer with adb... crazy process. It seems my phone is still rooted after the reset. From the phone I copied Stk.apk back to /system/apps where it was before deleted.
But needless to say nothing got fixed... not sure if Stk.apk is now "actually" installed or just there in the folder. But still nothing works and crashes every 10 seconds... logs provider, dialer, phone, framework, contacts... its all a firework of crashes...
Given that you've hard reset your device already, you are pretty much wasting your time trying to "fix" what you broke by messing with /system, and you should really just flash another ROM.
My suggestion would be to follow the advice on this thread.
Regards,
Dave
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
VeEuzUKY said:
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
Click to expand...
Click to collapse
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
foxmeister said:
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
Click to expand...
Click to collapse
Yes Dave you are right, right and right again!!! Thank you for the wisdom and advice!!!
The main thing I have understood with today's messy experience was that the actual ROM files are never deleted or damaged as long as you dont access them via a rooted tool and start deleting them. Now I understand that Titanium Backup, Sprint Backup (my favorite), My Backup Pro and others, only back-up and restore what the user installs on top of the ROM itself. So a full "reset" wipes all that data but leaves the ROM files as they always were. If they got damaged in the process, they'll still be damaged till a a full ROM restores all system data, now I get it.
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Till I find an app or way to do a simple one-click "backup everything" and then "restore evertything" I always feel vulnerable to changes I make to the Tab that may get it unstable or corrupt and then not being able to be restored properly without a full ROM Flash and then re-installing all from scratch.
With WinMo, I could do all sorts of crazy experiments and tweaking and after that, a registry restore or back-up restore would bring me back my phone to exactly like it was with all my stuff and configuration in a matter of seconds or minutes. Thats what I need to find out with this Tab/Android and then Im ready to be able to explore messing up with this knowing I can always easily go back within minutes to the state I had before with all my apps and settings.
This is what I need to learn next how to do! Trampoline without a safety net is not a good idea. Ive alwways loved WinMo for the ease of backing up and restoring whatever I was doing on my handsets withjout ever worrying to put myself at risk to loose it all. I need to learn this on Android and its definitely more intricate!
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
instechgainza said:
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
VeEuzUKY said:
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
Click to expand...
Click to collapse
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
instechgainza said:
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Where is the modaco kernel section you refer to? I can search for hours and find zilch... these blogs are endless...
VeEuzUKY said:
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Click to expand...
Click to collapse
What you want is a Nandroid backup, which you can only make from a recovery image like Clockworkmod recovery.
Essentially, this does exactly what you want, but you need to flash a new kernel (e.g. the MoDaCo kernel) which supports Clockwordmod.
Regards,
Dave
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
Click to expand...
Click to collapse
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
b0ricuaguerrero said:
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
Click to expand...
Click to collapse
When I delete stk.apk (for me useless useless useless) the first thing that happens immediately is that when I hang-up on a call made or received, the Tab vibrates then freezes for about 5 seconds then tells me the phone application has crashed. I tried this with 2 ROMs now as a test and its guaranteed. More even, if you use a program like SYSTEM APP REMOVER you can emulate the removal of an app by disabling it... it only takes me to disable STK and a reboot for the phone not to work. cant get rid of it, that simple

[BOOTSTRAP] Custom Safestrap v1.08f Released - 4-16-2012

Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u
i need this about 6 hrs ago lol.
Quite useful mate cheers.
=smc
Thank you so much for sharing this file. Your work is greatly appreciated.
This is a nice little(big)addition to safestrap! Thanks for adding it in!
I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!
Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.
TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.
I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium
Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.
I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.
This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!

Categories

Resources