Interestingly enough (I don't know the reasons), it looks like Motorola left a copy of Nvflash and Atrix-specific bootloader.bin for it on the Atrix. What's interesting about Nvflash is that it allows for targeted backup and restore of partitions (i.e. something along the lines of what Nandroid allows for, except at a lower level), which decreases recovery time when developers do something that ends up soft-bricking their phone. It should also break us free of our dependence on SBFs because we'll be able to create our own backups.
Anyways, the Nvflash on the phone is the Linux i386 binary. The bootloader.bin isn't platform specific, as it's meant for the target, rather than the host. THe archive is available in /usr/local/share/motorola/fireboxmake/OSH_tools.tgz.
Unfortunately, this is where we get stuck, because we don't currently know how to get a connection to the phone. And that's where all of you come in! Can you get further? I've gotten this far:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
I imagine that some of the functionality may end up requiring the --sbk flag (and we don't know the SBK right now), but I'm hoping that we can at least backup and restore /system, /data, and /osh.
Update: Information I've obtained indicates that this is the error you get when the SBK you pass in doesn't match the SBK on the system. So, no luck until we get that SBK.
Update 2: Additional links from dasmoover:
Tegra crypto engine source snapshot
/osh/usr/local/share/motorola/fireboxmake
Credit to dasmoover for the find.
Correct me if I'm wrong but isn't this the same thing as which apparently folks are trying to get taken down in the name of keeping the info under wraps?
I would like to excuse myself for earlier. I am glad that you have turned this in to something positive.
Sent from my MB860 using XDA Premium App
JdeFalconr said:
Correct me if I'm wrong but isn't this the same thing as some other thread, which apparently folks are trying to get taken down in the name of keeping the info under wraps?
Click to expand...
Click to collapse
It's related, but it's not quite the same thing. If nothing else, you have the binaries for this right now on your phone (dasmoover posted a link on the IRC channel 12 hours ago or so). I'm at this mostly for the backup/restore capabilities of Nvflash rather than bootloader hacking. Even if we only ever had that much, I'd be thrilled, because I hate having to re-SBF and set everything up again every time I soft brick my phone.
Also: I've been planning on posting this for a few hours now, before that other post even went up. I'm... disappointed to see that other post, but these two things aren't after the same thing.
http://gititbit.ch/fbm1 - /osh/usr/local/share/motorola/fireboxmake
also contains OSH_tools.tgz.
Firebox is the development name for the Webtop system. This contains the tools to prep the partition image for flashing. There are also some files IDA generated.
May be of use: http://gititbit.ch/tces1 - Tegra Crypto Engine Source Snapshot
do you mind me asking but.. what was that other thread about that it warranted getting deleted.
seven2099 said:
do you mind me asking but.. what was that other thread about that it warranted getting deleted.
Click to expand...
Click to collapse
it got deleted for a reason - let it be
I think we are getting warmer now .......... this calls for some investigation.
minooch said:
it got deleted for a reason - let it be
Click to expand...
Click to collapse
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)
http://forum.tegratab.com/viewtopic.php?f=13&t=18
They've been using nvflash to flash their tablet.
Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.
I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Sent from my MB860 using XDA App
sifon187 said:
I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Click to expand...
Click to collapse
The recovery state would be similar to the RSD recovery state (set on boot by pressing Volume Down) except that there's a specific Nvflash one. But, that's the one I can't get to respond properly.
LOOK HERE
LOOK HERE
http://forum.xda-developers.com/showthread.php?p=13145274#post13145274
blackax said:
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)
Click to expand...
Click to collapse
there is a separate dev forum that we can't access for DEVs only that that information is being used on. it being in the open here might hurt our chances of being able to exploit anything as moto might find it and patch it before the devs have a chance to get at it.
Is the Dev forum on XDA or.somewhere else just curious
Sent From My Gibgerblurred Phone
it's on xda, but you have to be a recognized developer of xda to access it.
PAulyhoffman said:
Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.
Click to expand...
Click to collapse
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
thats just my 2 cents
sent from XDA mobile
Wow give a dime at least...
Sent from my MB860 using XDA App
drock212 said:
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
Click to expand...
Click to collapse
Ends up being the same thing. Running sudo cat on the file prints nothing. That was one of the first things tried, even before copying the file.
Related
I have the one click root on my computer. I was able to root stock 2.1 but not Froyo. I cant seem to get a normal Update.zip to reinstall to root it. Can anyone help me out with this? Thank you
Have you used adb before? Its easy. Just need to get the sdk dev kit. Then go here.
http://forum.xda-developers.com/showthread.php?t=797397
smokestack76 said:
Have you used adb before? Its easy. Just need to get the sdk dev kit. Then go here.
http://forum.xda-developers.com/showthread.php?t=797397
Click to expand...
Click to collapse
I never have. But Im to nervous to attempt it bud lol
Its not hard. You can PM me if you want. Its easier than all the flashing to swap Kernels i think.
smokestack76 said:
Its not hard. You can PM me if you want. Its easier than all the flashing to swap Kernels i think.
Click to expand...
Click to collapse
+1 Its easier to cut and paste between windows. I also like to see how adb commands are used.
Terrigno said:
I never have. But Im to nervous to attempt it bud lol
Click to expand...
Click to collapse
If you're comfortable with flashing Froyo using adb shouldn't be a problem.
cappysw10 said:
If you're comfortable with flashing Froyo using adb shouldn't be a problem.
Click to expand...
Click to collapse
I sent smokestack a PM to see if he can help me out on how to do it. I just flashed the phone with Froyo following the directions here. I wasnt to sure about what I was doing but I did everything and it all eventually worked out well, with a couple scares lol. Im new to the rooting scene. I mean Im pretty savy when it comes to certain stuff and I was easy to install beta leaks and builds with BlackBerrys for 3 years. Im new to Android since the Captivate came out, so Im slowly trying to learn the tricks of the trade
Terrigno said:
I sent smokestack a PM to see if he can help me out on how to do it. I just flashed the phone with Froyo following the directions here. I wasnt to sure about what I was doing but I did everything and it all eventually worked out well, with a couple scares lol. Im new to the rooting scene. I mean Im pretty savy when it comes to certain stuff and I was easy to install beta leaks and builds with BlackBerrys for 3 years. Im new to Android since the Captivate came out, so Im slowly trying to learn the tricks of the trade
Click to expand...
Click to collapse
Sent you a reply as well.
I was wondering if someone was also willing to help me, the instructions on the link are kinda of vague I think
we are working on it
Seems that adb does not like Win7. Anyone else see issues?
smokestack76 said:
Seems that adb does not like Win7. Anyone else see issues?
Click to expand...
Click to collapse
nope. been working fine on mine since July....i have it on 3 machines all running win7 64bit ultimate
alme1304 said:
I was wondering if someone was also willing to help me, the instructions on the link are kinda of vague I think
Click to expand...
Click to collapse
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
you are forgetting one important step that nobody seems to want to do.
learn what all that means
its a gimme gimme gimme world....gimme now, i dont want to understand it! just do it for me!
Pirateghost said:
you are forgetting one important step that nobody seems to want to do.
learn what all that means
its a gimme gimme gimme world....gimme now, i dont want to understand it! just do it for me!
Click to expand...
Click to collapse
Kinda. Seems the OP here has win7 and i cant get it to play right. I see the above poster said they have it. Please post some info
rajendra82 said:
The instructions seemed clear as day to me. Put the phone in debug mode, use adb to push the files, execute a shell script, use sqlite3 to allow side loading, change permissions on the files you pushed, and reboot.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I think what they are looking for is where to put the files that they download. I know in the rooting tread, it was missing. I also think some people do it differently, so it may help just to let them know how you find it easiest to navigate to them, etc.
Personally, I take the files that were downloaded and extract them all. Then make sure you have downloaded the android SDK program and put it on the root of your computers hard drive such as drive C:. Then add those files you downloaded to the "Tools" file within sdk.
To navigate to them with command prompt, it would look like: cd C:\android-sdk-windows\tools
Then run the commands as listed in the tread.
Hope this helps.
Perhaps this is not the answer you are looking for, but if you are comfortable flashing roms, flash Cognition 2.2 (its already rooted).
Good luck
ronandi said:
Perhaps this is not the answer you are looking for, but if you are comfortable flashing roms, flash Cognition 2.2 (its already rooted).
Good luck
Click to expand...
Click to collapse
Its funny all the n00b post. I guess i dont know what im doing
Gr8Danes said:
I think what they are looking for is where to put the files that they download. I know in the rooting tread, it was missing. I also think some people do it differently, so it may help just to let them know how you find it easiest to navigate to them, etc.
Personally, I take the files that were downloaded and extract them all. Then make sure you have downloaded the android SDK program and put it on the root of your computers hard drive such as drive C:. Then add those files you downloaded to the "Tools" file within sdk.
To navigate to them with command prompt, it would look like: cd C:\android-sdk-windows\tools
Then run the commands as listed in the tread.
Hope this helps.
Click to expand...
Click to collapse
I'm running W7 and am having issues with adb. I'm a noob to android but I'm learning. Anyway, I tried your suggestion of adding the files to the tools directory but when I enter "su" the system returns "su: not found". Any help?
Moved to Q&A.
So as a little side project I've tasked myself to review the security features and potential risks to data being stored within the Android OS and I've been using my Captivate as the test rat. Since pretty much everyone with an android device uses Gmail I wanted to focus first on the Gmail app. I know that information for many apps are stored under the /data/data/[app package]/databases directory structure in an SQL Lite *.db file.
That being said, I wanted to inquire with everyone here about being able to access the /data/data directory and all info there-in WITHOUT having to root the device. Im sure there might be some on that but Im just trying to be thorough in my review...any potential thief would obviously just instantly root and delve right in afterward the data but what other potential ways are there to get into that directory, if there are any?
I've been playing around with ADB and from what I can tell that is not a viable path. The only thing I could think of is somehow tricking the ADB daemon into thinking my phone is a development phone which would allow ADB to run as root but haven't found that to be possible.
So in any case, just looking for insight from the more experienced folk as to other avenues of attack against the user data beyond the obvious root method. Thanks very much for any help!
You can run adb shell as root if the phone is in clockworkmod recovery - but if someones going to the trouble of dropping a clockwork update.zip could just as well and as easy drop a root update.zip on the phone.
If someone physically gets a hold of your phone anything tied the google account/s on the phone would have to be considered compromised - as these phones are so easy to root anyway.
I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.
dayv said:
I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.
Click to expand...
Click to collapse
you dont need odin. adb will do it too
Pirateghost said:
you dont need odin. adb will do it too
Click to expand...
Click to collapse
Can you do a system dump in adb without root?
dayv said:
Can you do a system dump in adb without root?
Click to expand...
Click to collapse
yes
adb pull /system
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Learn new things every day.
I like this phone allot, but there just is no way to secure it against someone physically gets their hands on it.
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Yep thats actually very easy to do however it doesn't contain any critical private data really. I looked through the directories and while there is some interesting information that can be gleaned (e.g. the generic APN configs and other hardware information) there isn't any actual private stuff such as Gmail data, authentication info for apps, etc. That is all contained within the /data/data directory from what I understand.
You CAN get a list of all the packages on the device through /SYSTEM as well as all the APK's of the installed apps but otherwise not much I've found to be worrisome.
I'll have to check out Odin and see what that can offer from a non-root perspective.
Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
But, that is why you don't leave USB debug on all the time - and why there is a warning when you do turn it on.
PIN or pattern lock keep prying eyes out, and protect your phone from ADB, but not if you leave USB debug on. But, like other hardware, if someone has physical access and enough time, they can get to your data.
So now that Im rooted, is there an easy way to write up a script to copy all files in the /data/data and whatever other folders I decide onto my PC?
At some point, I had created a soft link under Copilot so that I could have the maps on my external SD card... and it was working great.
But now, after installing new firmware, I am trying to recreate that link, and having trouble doing so. The image shows that I have tried two different ways to create that soft link, and either way should work (at least on other platforms they should!). But as can also be seen, they do not.
Can some kind soul point out what I might be doing wrong here?
Of course, when I try this without 'su' I get 'permission denied' or some variant.
Thanks,
Edit: I apologize. This dang "improved" app is not properly uploading pictures. Will update when I'm home, since, apparently, xda-developers isn't friendly with IE7, which is all I have here at work.
Edit2: Updated with picture. Thanks for any advice.
Sent from my GT-P1000 using XDA Premium App
Use a portable firefox which you can load on an external flash drive and leaves no traces at work
DarkPal said:
Use a portable firefox which you can load on an external flash drive and leaves no traces at work
Click to expand...
Click to collapse
Yeah, I used to do that before my employer decided to disallow any USB access. Ports are deader than dead. :\
Have a day. I'm off to my real home. Back online tonight.
Even with root powers you cannot create symlinks on filesystems that do not support them. Like FAT32.
Technomancer said:
Even with root powers you cannot create symlinks on filesystems that do not support them. Like FAT32.
Click to expand...
Click to collapse
Ah, thanks! But it seems I have done this. Ah well... not the first time I was wrong today.
Some of the recent posts have suggested that we may soon see a patch for the root exploit we currently have.
Being that we have root now is there some place we could hide SU where we could access it later should root be closed on us, allowing re-rooting of the device? It would have to be some place that does not get overwritten when an update is pushed...and I am not sure if that even exists on Android.
Not easily, since system is one of two partitions that doesn't have nosuid or noexec set.
Sent from my DROID3 using xda premium
Dunno about that, but I've been told there are a couple root methods being saved for later....
So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?
slow88lx said:
Dunno about that, but I've been told there are a couple root methods being saved for later....
Click to expand...
Click to collapse
Thank god for this!
Sent from my DROID3 using XDA App
calash said:
So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?
Click to expand...
Click to collapse
It doesn't get overwritten, but the update does reset all permissions. Thus, the su executable will still be there after the update, but will be chmodded 0755.
Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Sent from my DROID3 using Tapatalk
calash said:
Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Click to expand...
Click to collapse
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?
Xenoproctologist said:
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?
Click to expand...
Click to collapse
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!
rynosaur said:
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!
Click to expand...
Click to collapse
No, no... I only use pre-existing back doors. ^_^
I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?
hiddenhandgun said:
I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?
Click to expand...
Click to collapse
There are only one or two lines in build.prop that need to be changed to prevent receiving OTAs or update notifications. Search on the DroidX forums and you'll find these values.
Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.
cellzealot said:
Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.
Click to expand...
Click to collapse
Thanks. I'll give that a go.
There is always something being worked on to retain/get root again after a patch. There is also a good reason it doesn't get talked about in any kind of detail.
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!