Related
Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/
Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.
jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477
doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know
evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?
Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it
Hello,
I was wondering, what are the advantages of deodexing, aside from theming?
I've done some tests with my everyday stock ROM and found an odex ROM was faster. I understand that odex files are basically classes.dex, but specifically made for my platform, Android version and is not compressed, thus accelerating the start times.
I went as far as pushing the system apps updates in /system directly (by hand, I can tell you it gets old fast). But I still had low memory in /data. Then I remembered, automatic odex files are stored in dalvik-cache, and thus, when Maps, which has a very big odex file or so, first starts, even if it's on /system, you end up still needing space in /data to start.
So I searched how I could hand-do these odex files, and came across dexopt-wrapper. I loaded it up on my phone, and started odexing all these system apps that used to be odexed.
All in all, you lose room in /system (because odex+apk is slightly larger than the apk, but you're not supposed to have /system writable anyway), or you lose valuable space in /data, where you could put all your apps.
Basically:
I backed up my stuff with Titanium (after cleaning the cache). I was on Geo411m's ROM. I had around 25MB left on my phone.
I then reflashed FRG33 from the PASSIMG.zip
then updated with the FRG83D OTA (straight from Google, not through update.zip)
I updated all system apps through the Market
I used rageagainstthecage to shell root, to read the system and data partitions
I used dexopt-wrapper to create odex files for all the updated apks I had
I pushed everything in /system
Finally, I restarted. Before this, I booted Amon-RA's recovery to clear all the user data
I rooted (permanently this time), restored all my apps through Titanium Backup. I had 65 MB left. That's a 40 MB difference, just by odexing.
So now I wonder, knowing I don't plan on theming, is deodexing useful outside of this, and should I give up some space for something that eluded me?
Sorry for the lonnnnnng post
Thanks!
I'm not aware of any benefit of deodexeding, other than theming.
i've heard people say there is definitely a performance difference between the two, but i really dont know from personal experience. it probably doesnt matter for general usage...
I believe you're right, deodex takes up more of your internal space, which to me is a problem
Sent from my Nexus One using XDA App
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Aside from the first load, deodexed system runs at the same speed as odexed, or with negligible differences (not 100% sure if system-odexed files that are created in Dalvik-cache are the same as .odex that are in the apks).
The disadvantage of deodexed system is extra size of Dalvik-cache. While it can be quite a difference for those using N1's tiny internal space w/o any sort of A2SD solution, it's negligible for those running A2SD or on phones with proper internal memory size.
The advantage of deodexed system is being able to modify the apps themselves, and the framework. In addition to theming, it allows for different kinds of modifications - like trackball wake, or RTL (Hebrew/Arabic) framework patching.
Quite an old thread you managed to dig...
kingdragonfly said:
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Click to expand...
Click to collapse
Way to bump a 1.5 years old thread, lol.
Theshawty said:
Way to bump a 1.5 years old thread, lol.
Click to expand...
Click to collapse
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
magik300 said:
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You felt it was worth a two year bump just to convey that? Oh, ok.
Sent from my HTC One using Tapatalk
I don't know about a 2 year bump, but a 1 year bump to agree that this is a nice simple thread that is exactly what it says on the tin.
Lol
Lol
Is there any good resource I can be pointed to learn about the difference between Odex/Deodex?
nice info from this thread, thanks!
Hi
I would like to start automatically my Htc n1 when i put in the charger.
There are some methods on the internet,for some other phones.
Can someone tell me wich and how the folder i must modify?
My phone doesn't start when it's plugged in and take the battery out and put it back(i dont know why).
Sorry to write to you here, but I see you are very good at what you do.
I thought you could help me.
Thanks
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
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!
known bugs:
occasionally modem may take a while to come up. toggle with airplane mode and/or reboot
fixed bugs:
slider/onscreen kb / phys kb issue.
everything else i tested works. wifi, bt, hwc, camera, calls, webtop, etc
releasing as safestrap V3.10 backup for now., might do flashable zip later.
unzip to sdcard, don't overwrite your own backups, and
restore to a clean romslot, haven't tested overwriting any other builds. it might work since it was an ota but who knows?
Link: http://www.mediafire.com/?x9aec82a8xcm4c1
Updated framework-res.apk fixes keyboard issue.
http://www.mediafire.com/file/jfsc35gr40yf8g5/framework-res.apk
to install framework res: mount system of romslot in safestrap make sure it's the right slot
adb push framework-res.apk /system/framework/
adb shell chmod 0644 /system/framework/framework-res.apk
wipe cache and dalvik cache just to be sure, and reboot
please report bugs.
kernel source here: https://github.com/kfazz/kernel_mapphone_kexec/tree/razr_jb
this rom has been superseeded by this: http://forum.xda-developers.com/showthread.php?t=2199741
it's almost exactly the same, but based on D4 JB leak, and everything works.
Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?
captainstarbucs said:
Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?
Click to expand...
Click to collapse
the slider event doesn't trigger that the hw keybaord is out or away, so
with Hardware keyboard turned on: the rom thinks the keyboard is out all the time, onscreen kb doesn't appear
with Hardware kb off: onscreen kb pops up all the time, regardless of whether real kb is in or out, hardware kb still works
the "mapphone switch" device sends the slider event via /dev/input/event5
runing getevent -l /dev/input/event5 shows SW_LID events, they just don't do anything.
i tried editing keyboard bools inside framework-res.apk, but they don't appear to make a difference.
Boooooo motoblur crap... Otherwise nice port! Will stick with cm10.1 for now. We should be getting jb ota soon anyway
Sent from my XT894 using xda app-developers app
Nice work kfazz
MotoBlur or not, this is a GREAT example of the kind of things we can now do on the phones using the new kexec kernel.
Glad to see it's already being put to good use!
Kexec is amazing. More mods should be coming.
Sent from my XT897 using Tapatalk 2
Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop
cannot wait to test this first thing tomorrow. Thanks so much
Could hash use this rom for fixes to the current issues with the JB builds he is working on?
Sent from my Motorola Droid 4 via XDA-developers app
how do we install this? i'm unfamiliar
edit: specifically the framework-res.apk. I'm assuming that for the ROM we just wipe and open it as a backup
FWIW: restored this from SS 3.11 just fine.
Strange issues with my sdcard, but other than that, everything seems to work.
Would love it if someone could make a flashable patch for the framework. My USB cable is touch and go..
Sent from my DROID 4 using Tapatalk 2
huhu1312 said:
Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop
Click to expand...
Click to collapse
did you restore on a a fresh romslot? try wiping data/cache.
Sent from my DROID 4 using xda app-developers app
Well that didn't take long! Good work.
Sent from my XT894 using Tapatalk 2
This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf
Lum_UK said:
This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf
Click to expand...
Click to collapse
in order for a rom to work right the kernel driver parts and userspace driver parts for things like pvr and ducati need to be in sync.
ramdisk needs to be extracted and modified for safestrap. kernel modules need to be rebuilt for kexec kernel, frameworks hacks for keyboard need to be done, (there may well still be more of these to do) /system/lib/hw/* libraries need to match boardname. ie (lights.maserati.so instead of lights.spyder.so) build.prop needs to be edited...
it's not entirely trivial, but since i already had a kexec kernel around this only took me ~24 hours.
Edit: if you didn't want to kexec a kernel, you might be able to hack roms based on the same version as whatver your stock kernel is, so ics to ics, etc.
more of a pain to do it that way though.
Ahh, this is all probably somewhat beyond me then, though I am definitely interested in how to extract and modify the ramdisk as that's where I need to modify two files to get rid of the cdrom automount.
For now though, I think this ROM is going to be my daily one, even as I continue to fiddle with it.
Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Sent from my DROID 4 using xda app-developers app
kfazz said:
Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Click to expand...
Click to collapse
It was the location of the ramdisk that was defeating me. Thank you!
I gotta say this is the fastest and smoothest I have ever seen my droid 4 run.
I am far from current on how to install things and never got the framework-res.apk installed. If anyone can make a video on how to install the framework-res.apk I would greatly appreciate it.
Also wondering if there is any plans to use this to improve existing roms like "CM10.1 / Jellybean 4.2.2 for the Droid 4". I have fell in love with all the customization's in that rom.
Please forgive me if I used incorrect terms or said anything that is inappropriate. I really have no idea on how all this works.