Related
First off sorry if I got your hopes up with the above heading
Anyways Now that I got your attention
I would like to know how do you undo all cache to the sd
I used the stupid @ss ta utility from the market trying to see if I could undo the marrket cache, that isn't revertable(< is this even a word???)I tried multiple methods searched found one posting that was a total fail
And now I'm looking into straight up commands to revert
I know uninstalling the app doesn't undo the changes it just leaves them alone and still keeps on telling the phone to push all cache to sd
So what's next deleteing the folder that stores the cache just causes force closes so what the hec?
I've tried reflashing, over the current settings but with no wipe cuz I don't want to lose my current setup
So anyhelp appreciated
Thanks In Advance
If you don't want to wipe you will need to remove the symlinks, copy the folders to internal memory, and reboot the phone.
BTW did you notice it took 10 hours to get a response. People aren't too eager to help after being mislead into reading. Next time try a subject that fits the post & I can almost guarantee you will get responses quicker.
Agreed. I just now checked this out after seeing ONE post maybe 1 or 2 more now that it reads 2 replies I thought this was someone asking if a hero rom had bluetooth support and was gonna laugh
If you are running Dwang on a Stock SPL and you are having problems installing a theme, I have some suggestions and ideas, some of these are very basic and common but ill repeat them anyway because youd be surprised at how many people dont follow these:
1) Make sure the theme you are using is compatible with the right version of Dwang that you are using. (keep in mind that v1.13-1.17.1 themes are interchangeable among those versions. ex: you can use a 1.13 theme on 1.17.1)
2) Make sure to ALWAYS have a Nandroid/BART backup, in case anything goes wrong.
3) Make sure youre using an EXT 3 file system.
4) Do NOT wipe BEFORE or AFTER flashing a theme. If you are using one theme and wish to switch to another theme, simply flash your base ROM over the old theme, then flash the new one.
5) Always have your apps backed up if you dont want to go looking for them again. I suggest ASTRO File Manager which can be downloaded from the Market for free.
Q. STUCK AT THE G1 SCREEN?
A. This happens sometimes if the theme is a little too large and you have Stock SPL....but what if you really want the theme and are afraid to upgrade your SPL because youre afraid of bricking your phone, or because youre one of the few people like me who are unable to upgrade to the latest radio? Theres a solution for that, I cant promise itll work for every single theme, but Ive tested it with Darkstar and DBeCe's black theme which gave me problems before I tried this method. I believe it will work for most themes on Dwang.
The solution is simple, try to free up space in your SYSTEM partition by moving your ringtones, sound effects, alarms, etc to your sdcard. This will free up around 2.66mb in the system partition. You can do this using Terminal Emulator.
type in
$su
mount -o remount,rw /system/dev/mtdblock3 /system
cp -r /system/media/audio /sdcard/
rm -R /system/media/audio
and you should see your audio folder in the root of your sdcard. You can add ringtones and sounds there too if you like, but the point is, now your SYSTEM has a little more space.
Restart your phone and boot into recovery and try to flash the theme again, and it should work now.
Q....OKAY SO I GOT PAST THE G1 SCREEN AND IT SHOWS THE ANDROID SPLASH SCREEN BUT AFTER A WHILE I GET A BLACK SCREEN!!!
A. If this happens to you, then you must format your EXT 3 partition. I suggest using the latest Amon_RA Recovery (v1.5.2 at the time of this post, MAKE SURE YOU DOWNLOAD THE CORRECT RECOVERY FOR YOUR PHONE).
If youre still having problems, i suggest wiping everything including the phone, dalvik cache, battery and rotate settings (i like to wipe everything 3 times, but thats just me), reinstall dwang, login at the beginning, wait for the sync, and make sure to open up market and agree to the terms otherwise you might have problems with the market when you install a theme, (also keep in mind when u flash the rom again, you have to move the ringtones back to the sdcard again using the method i mentioned above), after you have done all that, reboot into recovery, flash the theme again, and it should be okay.
I hope Ive helped. Im still new to the scene but Ive found that this works for me and I just wanted to share, and I hope I helped and that your themes are working now.
If you have any suggestions or feedback, please feel free to share.
Thank You!
well done on a detailed and excellent advice. Keep it up
Great tutorial. I have the HardSPL and I am getting the same symtoms. All the themes that I have tried get to the theme splash and then stop. The longest I have allowed one to run is an hour. Do you think that space is still the issue? I am going to try these steps as they cannot hurt, but I thought that I was good with the HardSPL.
s2welee said:
Great tutorial. I have the HardSPL and I am getting the same symtoms. All the themes that I have tried get to the theme splash and then stop. The longest I have allowed one to run is an hour. Do you think that space is still the issue? I am going to try these steps as they cannot hurt, but I thought that I was good with the HardSPL.
Click to expand...
Click to collapse
the hard spl has the same partition spacing as the stock spl, it is the 1.33.2005 spl that provides more space to system.
tryed it..
Tried this method and only got darkstar to work for a min then force close when I tried to login to my google account and wouldn't stop force closing....U got any other methods that might work.
tom_me said:
Tried this method and only got darkstar to work for a min then force close when I tried to login to my google account and wouldn't stop force closing....U got any other methods that might work.
Click to expand...
Click to collapse
Thanks everybody, if you have any other suggestions, ill add them to the first post.
darkstar 0.6.7 is kinda complicated... you said google login so im guessing you wiped before u flashed? normally you shouldnt do that but for this theme i had to, ill explainin the next paragraph, but first of all, did you try to skip the initial sign in and then try to login by clicking on gmail or checking sync settings? i had a similar problem with another theme, and thats how i solved it. let me know if that works.
this is why darkstar 0.6.7 is a little different and more challenging to install compared to most themes (at least for me):
darkstar 0.6.5 flashed fine with me, when i had dwang 1.15 but when i upgraded dwang 1.17.1 and used darkstar 0.6.7, it gave me a little trouble and i had to get a little creative in order to install it properly because for some reason the market app was pushed to ext and it was no longer available after i wiped the ext before, and i kept getting a black screen if i didnt wipe the ext system. so what i did was wipe everything flash the stock rom, backup the market app using astro file manager (some reccomend backup for root users, i havent tried it yet), flashed the theme got a black screen, wiped the ext3, then i reflashed the theme again and i got it working but i was missing market, and i couldnt download astro without market.....unless i went to google using the browser and i looked up astro 2.2.3 apk and i downloaded the app directly to my phone, and restored market. however the market will start force closing even after you run fix_permissions so i went against the rule of wiping after a flash, and i decided to wipe the phone....lo and behold its been running flawlessly ever since, but it took a lot of work, idk why it gave me such a hard time this time, but i managed to get it working. try the first method first and let me know how that goes.
david1171 said:
the hard spl has the same partition spacing as the stock spl, it is the 1.33.2005 spl that provides more space to system.
Click to expand...
Click to collapse
Thanks, that clears up some confusion.
got it
Ok the first time I did it I had to wipe cuz it would never get pass the G1 screen and it worked for a min. Now I tried wiping everything and repartition my sd and restored backup and then I flash theme again and reboot. I finally get pass g1 screen then stuck on android screen. I took out the battery reboot and flash theme again reboot, same thing happen then took batt out powered on regularly did it four times and it finally worked.....
tom_me said:
Ok the first time I did it I had to wipe cuz it would never get pass the G1 screen and it worked for a min. Now I tried wiping everything and repartition my sd and restored backup and then I flash theme again and reboot. I finally get pass g1 screen then stuck on android screen. I took out the battery reboot and flash theme again reboot, same thing happen then took batt out powered on regularly did it four times and it finally worked.....
Click to expand...
Click to collapse
im glad u finally got it working. idk why that specific theme was so difficult to install. the g1 screen was still stuck even after you moved the ringtones to sd?
speedysilwady said:
im glad u finally got it working. idk why that specific theme was so difficult to install. the g1 screen was still stuck even after you moved the ringtones to sd?
Click to expand...
Click to collapse
Yea moved ringtones to sd... and still got stuck......but I think u just need to run the rom for a bit before flashing a theme. But yea it looks great.... and thanks for the help.
Tom
there are a few things that could be removed from the /system partition of dwang's rom.
rm /system/app/GenieWidget.apk
rm /system/app/Maps.apk (since the updates are installed on the /data partition)
rm /system/app/BugReport.apk (its not in cyan's roms anymore)
cp /system/app/Mail.apk /data/app/
rm /system/app/Mail.apk
(cyan did it in his latest release)
(maybe? haven't tested this one)
rm /system/app/LatinImeTutorial.apk
There are probably some more "useless" .apk's that could be removed.
david1171 said:
there are a few things that could be removed from the /system partition of dwang's rom.
rm /system/app/GenieWidget.apk
rm /system/app/Maps.apk (since the updates are installed on the /data partition)
rm /system/app/BugReport.apk (its not in cyan's roms anymore)
cp /system/app/Mail.apk /data/app/
rm /system/app/Mail.apk
(cyan did it in his latest release)
(maybe? haven't tested this one)
rm /system/app/LatinImeTutorial.apk
There are probably some more "useless" .apk's that could be removed.
Click to expand...
Click to collapse
thank you so much for confirming my suspicions. i knew there was more useless stuff in the apps folder but i wasnt sure how to test it all. ill try this method out later tonight and try to flash a large theme and see what happens, ill add this info to the first post tonight!
sorry im late guys ive been pretty busy. i stumbled upon this page on cyanogenmods wiki
http://wiki.cyanogenmod.com/index.php/Barebones
it shows which files can be deleted safely out of /system and /dev. im gonna try removing a lot of those apks from my dwang rom and i wanna find a huge theme to flash thats supposed to be used only with danger spl, anyone have any suggestions? i think this might work. btw does anyone know if its possible to make a script to make removing multiple apks easier?
I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?
Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.
the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.
Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!
flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data
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!
Don't know it this is a setting somewhere or what, but I have a question on using the Kindle app on the Nook Color running cmod 7 (7.20 stable). The app runs okay, but I seem to be missing a navigation bar once I start reading a book. It only shows the title and where I am - no options to go back to the Kindle menu (like if I want to read a different book). The only way I can get back to the Kindle menu is to reboot.
I've searched the forum and the closest thread to this problem talks about changing the settings - I don't seem to have any settings to adjust. Even if I go to settings/applications/manage applications/downloaded/kindle there still aren't any changable options.
Sorry for so many questions - I'm a noob. I've searched the net on this and searched this forum with no luck.
any help is greatly appreciated!
Thanks in advance!
Dave
dweaton said:
Don't know it this is a setting somewhere or what, but I have a question on using the Kindle app on the Nook Color running cmod 7 (7.20 stable). The app runs okay, but I seem to be missing a navigation bar once I start reading a book. It only shows the title and where I am - no options to go back to the Kindle menu (like if I want to read a different book). The only way I can get back to the Kindle menu is to reboot.
I've searched the forum and the closest thread to this problem talks about changing the settings - I don't seem to have any settings to adjust. Even if I go to settings/applications/manage applications/downloaded/kindle there still aren't any changable options.
Sorry for so many questions - I'm a noob. I've searched the net on this and searched this forum with no luck.
any help is greatly appreciated!
Thanks in advance!
Dave
Click to expand...
Click to collapse
On my device I only have to tap the middle of the page and the menus all pop up.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Still no go......
Tried that - I still only get the title at the top and the how much I've read meter at the bottom - no menu.
Thanks for replying!
Dave
dweaton said:
Tried that - I still only get the title at the top and the how much I've read meter at the bottom - no menu.
Thanks for replying!
Dave
Click to expand...
Click to collapse
What version of the Kindle app are you using? Try updating to the latest version.
Also try playing with the settings in cm. Go to settings, cyanogenmod settings, tablet tweaks, and play with checking and unchecking disable full screen.
Sent from my NookColor using Tapatalk
uh.....I'm not sure
Thanks for the reply! I downloaded the Kindle app via Amazon, so hopefully it is whatever is their latest. I sure didn't know about the settings, so I'll give the go and see what happens! I do get the drop down from the top stating the title, and the pull-up from the bottom, but the bottom only has how much I've read so far.
Thanks again!
Dave
EDIT: Well, I don't have the tablet options. Everything in there is for a phone! Seems kind of weird on a device that doesn't have a phone.
lost cm settings
I tried the cyanogenmod settings, and while everything there was for a phone, I turned off things like vibrate, etc. - pretty much everything dealing with a phone. Now when I try to go back to cyanogenmod settings, the app aborts.
I also look in the dev settings and see a config file in there that set s default resolutions, etc., and includes an option that looks like it hides the menu bar, so I used terminal (I am familiar with Linux) and checked for such a file for the system but wasn't able to locate one. I'm wondering if there's a setting like that somewhere, as I don't get any back arrows, menu, etc., just on the pages, and was wondering if that was also stopping me from getting the full menu bar in the Kindle app?
So you do NOT see the word Kindle in orange Aa, magnifying glass and three vertical dots and a bookmark icon as well as the blue dot and position in book at the bottom of screen when you touch anywhere that is NOT the far left and far right of the screen?
And you do NOT see the back, home, recent apps and "menu" button in the bar at the bottom of the screen outside of the kindle window?
Dev settings? no such beast in CM7 or CM9
There is a Developer options which has nothing to do with any sort of resolutions..
I suggest you reinstall CM7.2 release from the official site, stay out of ADB, and stay away from all the various "work in progress" roms until you can actually navigate the default device...
I think you probably got a bit happy and broke something .. there is a setting in CM7 settings to disable fullscreen apps from hiding the "menubar" at the far bottom of the screen and that should be under tablet tweaks in the system settings app.
Yep, none of those
Yep - none of those. This was just after getting 7.0 stable installed and loading in the gapps, since the gapps file was dated just slightly after that release. Immediately went and got Kindle and Nook reader apps. Tried them to be sure they looked like they were working and then applied the zip of 7.2 stable. I didn't try the cyanogenmod settings until later when it was posted in this thread. Again, there are no options in there for a tablet - only a phone. I don't mind going back and doing everything over, just as long as I don't end up in that deadly embrace of things aborting and google market not working. I'll let you know what happens.
If I flush out the Kindle cache I can get back to seeing my titles, but that really defeats the purpose of reading on the device.
Something is not right
Okay, I downloaded everything again and made the microSD. I booted the microSD, did the format data/system reset, went to mounts and did the format /system, while there I tried the format /data - it fails. I had noticed before that when the data/system reset is run and completes, I can no longer do anything - I have to manually power off, wait a while, and power back on. Did all that, went to advance and cleared the kelvich or whatever it's call cash. Installed the cmod7.20 stable. Took out the microSD and rebooted. All of my old apps, etc., are still there. I also was looking at settings and see that the settings I changed were under "phone", not using the cyanomod settings app - it still just aborts.
So, what have I got to do to completely clean all this stuff off and then try installing again? As you can imagine, the number of attempts, partial successes, successes (at least I thought it was only the Kindle app that wasn't showing the menu), etc., we're talking all kinds of hours starting Monday night - probably at least 10 hours each day. Now I'm no further than when I started. For now I'm going to load the old 1.4.1 image again for the umpteenth time and hope someone can tell me how to clear this all up, or else recommend a different android that will run on the Nook Color without problems.
I still think if I can clear EVERYTHING (well, not /boot, obviously) so I'm starting with a CLEAN slate again it may help. I just don't have a clue how to do that using cwm recovery.
Still no good
I redownloaded everything again, created the microsd and tried to install 1.4.1 just to get back to a clean starting point. Can't get beyond where it asks for B&N userid/password as the keyboard shows for about 1/2 a second, no matter what I do. So, I tried the format data/system reset again and just loaded in the cmod 7.20 stable. Again, after booting, everything is still there - the google apps and all. How do I get rid of all this stuff so I can try an install from a clean slate? Right now I've been going thru all the data folders I can find and manually removing everything there. I would like to delete a lot of apps, but I never seem to be able to "uninstall".
So, before I start over again, can someone tell me how to clear EVERYTHING (except /boot, /emmc [unless I need to],/sd*) so I have a clean system first?
Thanks!
Dave
dweaton said:
I redownloaded everything again, created the microsd and tried to install 1.4.1 just to get back to a clean starting point. Can't get beyond where it asks for B&N userid/password as the keyboard shows for about 1/2 a second, no matter what I do. So, I tried the format data/system reset again and just loaded in the cmod 7.20 stable. Again, after booting, everything is still there - the google apps and all. How do I get rid of all this stuff so I can try an install from a clean slate? Right now I've been going thru all the data folders I can find and manually removing everything there. I would like to delete a lot of apps, but I never seem to be able to "uninstall".
So, before I start over again, can someone tell me how to clear EVERYTHING (except /boot, /emmc [unless I need to],/sd*) so I have a clean system first?
Thanks!
Dave
Click to expand...
Click to collapse
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.
no good
leapinlar said:
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.
Click to expand...
Click to collapse
That's what I've been doing - format data/factory reset option from cwm. Before rebuilding the entire microSD on my Windows PC I have also done a complete format of the media. I then boot CWM from the microSD and install the cmod7 7.20 stable zip - I always assumed this was going straight to the device since when I remove the microSD and boot cmod7 is there. However, none of the pre-existing apps are gone - everything is still there.
I've tried using CWM, advanced options, and format /data - it always fails. So I'm wondering if perhaps the format of /data the is part of the factory reset also fails but the script doesn't error out. Right now I'm going through an extremely time consuming task of manually removing the files and folders in /data via the terminal and su so I get the permissions. If there is another quicker way to clear /data I'd sure appreciate knowing. I've tried some of the treed removes from my Linux experience but they don't seem to work.
Thanks!
Dave
EDIT: forgot to mention - I'm trying your partition restores from the link in your signature - only the "safe" ones - I don't to do that partition 2 stuff and really mess up. Perhaps this will clean everything off.
Thank you thank you thank you!!!!!
leapinlar said:
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.
Click to expand...
Click to collapse
I followed the link and did the repartitioning and formating with the first 2 scripts (left partition 2 alone!). Installed 7.20 stable - I now have the bar at the bottom of my screens. I'm waiting to format a 16gb microSD then I'm going to try the Kindle app out again, but I'd say this looks REALLY promising! Your scripts did what I wanted to do - they cleared everything out!
Thank you SO much!!!!!
Dave
Thank to everyone!
I just wanted to post a big THANK YOU to all the people who made cwm and cmod 7 so this whole thing would even be possible. Thanks to everyone here who helped me! Now "all" I have to do is just try to learn this! Maybe some place down the road I might try some programming, but I don't know how different it will be from my C using GTK++ on Linux. But first, to learn!
Thank you everyone SO much!
Dave
dweaton said:
That's what I've been doing - format data/factory reset option from cwm. Before rebuilding the entire microSD on my Windows PC I have also done a complete format of the media. I then boot CWM from the microSD and install the cmod7 7.20 stable zip - I always assumed this was going straight to the device since when I remove the microSD and boot cmod7 is there. However, none of the pre-existing apps are gone - everything is still there.
I've tried using CWM, advanced options, and format /data - it always fails. So I'm wondering if perhaps the format of /data the is part of the factory reset also fails but the script doesn't error out.
Click to expand...
Click to collapse
I know you got it all working and I am glad, but just for future reference, the problem you were having probably stemmed from using an old version of CWM. You have to use version 3.2.0.1 or newer or the format of data will fail on the newer nooks. The one in my tips thread is the newest version.
Thanks!
leapinlar said:
I know you got it all working and I am glad, but just for future reference, the problem you were having probably stemmed from using an old version of CWM. You have to use version 3.2.0.1 or newer or the format of data will fail on the newer nooks. The one in my tips thread is the newest version.
Click to expand...
Click to collapse
I did look at the the tar file I downloaded when I was trying to install from a 4gb microSD - it does say only 3.0.2.8, so I'm sure the 16gb I ended up installing from was probably the same, so I'll go grab what you recommended!
Since I don't want to have the problem again, I'm DEFINITELY going to follow your advise!
I had another suspicion for what may have happened, and why I had so much problem from the get-go with cmod 7 - I tried someone else's "put android on your nook" thing, which I know tried to root the nook and then dump some stuff in, and that didn't end up working.
I'm just glad your posts have gotten me going correctly!! BTW - the Kindle app works fine now, too!
Again, thank you SO much!!
Dave
Want to make sure I get this all right
You've been such a great help - I hope you don't mind a couple of more questions:
- The new CWM you recommend is the 5.x.x.x that's on the link, correct?
- Are there any newer releases of Android for the Nook Color? Right now I don't know anything about Android (complete noob [LOVE the movie on the registration page!] ). I know someone who is quite versed in all of this he mentioned that I'm running some name (honeycomb or something like that) and that there are newer ones out there (maybe that was honeycomb). At any rate, are there some updates I could run to make this any "better"? I know the version I'm running also seems to think it's a phone - is there one where it actually thinks it's a tablet?
Again, thank you SO much!
Dave :good:
dweaton said:
You've been such a great help - I hope you don't mind a couple of more questions:
- The new CWM you recommend is the 5.x.x.x that's on the link, correct?
- Are there any newer releases of Android for the Nook Color? Right now I don't know anything about Android (complete noob [LOVE the movie on the registration page!] ). I know someone who is quite versed in all of this he mentioned that I'm running some name (honeycomb or something like that) and that there are newer ones out there (maybe that was honeycomb). At any rate, are there some updates I could run to make this any "better"? I know the version I'm running also seems to think it's a phone - is there one where it actually thinks it's a tablet?
Again, thank you SO much!
Dave :good:
Click to expand...
Click to collapse
Yes that CWM is attached to my tips thread linked in my signature.
You can try CM9 which is tablet based, but it is still in alpha and not as stable as CM7. Don't use honeycomb, it is old and very buggy.
Thanks!
Thanks again for the info! I'll get that copy of cwm right away. Since CM9 is still early, I'll wait on any updates. I really don't know anything yet, but I am having fun with the Nook Color being all Android now. It's nice having the Kindle app and the Nook app - this way have all my books on 1 device, and that works great!
Thanks again!
Dave :good: