Related
Hey all,
I've been an xda stalker for a while and have been using all sorts of roms for a while now, but now I am in need of my own question.
For a while now, my mother's G1 has been acting up, whether it be her own fault or a bug. But this one has me confused. Over the past three roms i flashed (dwang, cm, superd) this same problem is always around. Everytime I touch browser, dolphin, etc the page begins loading and then i see the home screen.
Everything else works as it should, which confuses me. Everytime I flash a rom, i wipe, wipe ext, repair ext, wipe, flash.
I'd be happy to post a logcat if someone would be so kind as to inform me how to dump to a txt file.
Hopefully this is something extremely easy so I can get her off my back hah
erkmasterflex said:
Hopefully this is something extremely easy so I can get her off my back hah
Click to expand...
Click to collapse
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM... I'm guessing its something you mucked up by going between builds without wiping, or not fixing permissions between builds, or some app on your ext didnt play nicely.
*oh yeah, wrong section, read stickys, or DIAF, your choice*
jmhalder said:
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM...
Click to expand...
Click to collapse
Nah I think he should install the RC29...just kiddin you should use Super-D or Enom's official. I kinda assumed this thread was about some kind of fix for browser problems.
Ace42 said:
Nah I think he should install the RC29...
Click to expand...
Click to collapse
well, the RC29 might actually force a wipe... and would update itself and have OTA keys... honestly probably not a bad way to go... Super-D is good, but honestly dont notice a huge difference between that and CM.
it was even not working when i reverted to complete stock. could this be a problem with the phone itself? Maybe revert to stock again and take it in to t-mo?
There should not be any problem with leftovers from previous roms, since i completely wipe data and ext as i mentioned in my first post.
Moderators, please move this to correct section. this seemed like the correct section since this seems to be more involved in the development side of things. Definately not Accessories but more involved than Q&A. Thank you
Phone ><---USB--->< PC/Laptop/Mac
adb logcat
watch text fly up screen ... make browser crash
quick !!!!! take a picture of that text.............
if you don't have a usb cable handy, a PC or the time to figure out how to get adb installed
go to terminal emulator on phone, and type
logcat|tee /sdcard/logcat.txt
( get the pipe "|" with alt then s )
make browser crash
go back to terminal press ball then C
Edit : the ball can be a bit of a pain, when in term do menu --> preferences --> control key , and set to which key you prefer, I like left alt as ctrl[\i]
now have a look at the logcat.txt file, it
less /sdcard/logcat.txt
you could just do logcat > /sdcard/logcat.txt
but it doesn't look as geeky
NB use >> instead of > to append > will make new file >> will add to file
to append to file with tee use tee -a file.txt[\i]
and yeah, wrong section
thank you very much for your assistance and the little linux command briefing ha
i decided to try every sort of wipe, repair, etc and do it multiple times. probably didn't do anythin, but worth a shot ha.
Ended up working! I removed the ext and swap partitions, wiped anything i could multiple times, flashed super d, didn't work, wiped a bunch, flashed htc recovery image, then cyan, and presto. For whatever reason it finally worked.
Shoulda done the logcat and posted it so y'all could see whatever was going on and hopefully help someone out later. but all is resolved for now.
If there is a next time, I will post in Q&A. I want to thank everyone for their input and wish all a good night.
-Eric
Moved as not Android Development.
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
I do not have a batterystats.bin i have searched using Astro and i have also used the terminal to try and locate it im also running the latest cognition. Im just having terrible battery life atm
Caw108 said:
I do not have a batterystats.bin i have searched using Astro and i have also used the terminal to try and locate it im also running the latest cognition. Im just having terrible battery life atm
Click to expand...
Click to collapse
I see your was asked in your last thread about battery, you should not post questions in development section. It took 1 minute using the search function in this forum to find your answer to where that file is.
Hopefully this information will make you stop posting these questions in this section, Using Root Explorer or a comparable program navigate to (Mount R/W first): data>system> you will find and be able to delete file batterystats.bin or you can use Rom Manager and boot into clockwork recovery mod go to advanced and there is an option to wipe battery stats. Then you will need to cycle your battery a couple time to get it to show correctly.
Yeah but you know none of these options have worked and neither of the have shown it. I am know thinking that it is a problem with the way I flashed it or a problem with my phones Tom so that's why I posted it in the android development section. You know people like you make us wonder why people aren't nice any more
Questions go in Q&A.
Caw108 said:
You know people like you make us wonder why people aren't nice any more
Click to expand...
Click to collapse
And people like you make us wonder why there isn't a test to get posting rights on the forum. This does not belong in Development.
Caw108 said:
Yeah but you know none of these options have worked and neither of the have shown it. I am know thinking that it is a problem with the way I flashed it or a problem with my phones Tom so that's why I posted it in the android development section. You know people like you make us wonder why people aren't nice any more
Click to expand...
Click to collapse
I guess I am sorry for trying to help, I will just ignore posts like yours from now on. Hope you do get your problem solved.
mcx6 said:
I see your was asked in your last thread about battery, you should not post questions in development section. It took 1 minute using the search function in this forum to find your answer to where that file is.
Hopefully this information will make you stop posting these questions in this section, Using Root Explorer or a comparable program navigate to (Mount R/W first): data>system> you will find and be able to delete file batterystats.bin or you can use Rom Manager and boot into clockwork recovery mod go to advanced and there is an option to wipe battery stats. Then you will need to cycle your battery a couple time to get it to show correctly.
Click to expand...
Click to collapse
Astro will not work, you need root access. Download root explorer and go to the root directory. Data-> System -> Batterybins.bin
just delete it from there.
For future notice, a Google search can avoid all this. Thats what i did when I had this same exact problem.
yogesh892 said:
Astro will not work, you need root access. Download root explorer and go to the root directory. Data-> System -> Batterybins.bin
just delete it from there.
For future notice, a Google search can avoid all this. Thats what i did when I had this same exact problem.
Click to expand...
Click to collapse
A google search brought me to this thread (first link). Thought that was kind of funny.
And how is this relevant to the thread?
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!
THIS PROJECT IS DEPRECATED. I HAVE AN ALTERNATIVE HERE.
Documentation: https://github.com/VR-25/migrator/blob/master/README.md/
Releases: https://github.com/VR-25/migrator/releases/
Reserved for jokes.
It seems really interesting, thumbs up man :good::good::good:
Okay I still don't quite understand the method technically even after reading the description.
The thing is if dev say clean flash(wipe data,system,cache,dalvik) is a must before installing a rom,etc.Then will this adk solution can be used instead of titanium backup?Because you wrote that adk more efficient than tb maybe I'll use this instead of tb
handers1234 said:
Okay I still don't quite understand the method technically even after reading the description.
The thing is if dev say clean flash(wipe data,system,cache,dalvik) is a must before installing a rom,etc.Then will this adk solution can be used instead of titanium backup?Because you wrote that adk more efficient than tb maybe I'll use this instead of tb
Click to expand...
Click to collapse
All you really need to understand are the setup steps. This module prevents app data from being deleted when you use TWRP's "wipe data/factory reset feature".
This sounds too good to be true, lol almost like a proof of concept. Can just binding the new dir with the old make it so there are no issues whatsoever? Will test later this week cause I romhop a lot.
My phone's storage is almost full.The thing i want to ask is if this procedure will need more data space inside /data/media.
alvinator94 said:
This sounds too good to be true, lol almost like a proof of concept. Can just binding the new dir with the old make it so there are no issues whatsoever? Will test later this week cause I romhop a lot.
Click to expand...
Click to collapse
And indeed it is true. No issues whatsoever -- I'm using it myself.
foxmcc8 said:
My phone's storage is almost full.The thing i want to ask is if this procedure will need more data space inside /data/media.
Click to expand...
Click to collapse
No extra space is taken, as data is moved, not copied.
I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.
After typing "adk" it finds all the apps, but after typing "." it lists every app with "pm: not found". After a reboot, the apps are not installed. Am I doing something wrong?
soren25 said:
I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.
Click to expand...
Click to collapse
Lmao same thing happened to me. Figured the module was buggy and uninstalled it. Maybe i did something wrong too, which im not sure how considering how easy the install instructions are
soren25 said:
I installed this and it erased all my app data, ironically enough. Make sure you have a backup before installing.
Click to expand...
Click to collapse
jungle35 said:
Lmao same thing happened to me. Figured the module was buggy and uninstalled it. Maybe i did something wrong too, which im not sure how considering how easy the install instructions are
Click to expand...
Click to collapse
That's really f**ked up... same to me. I think there was no error on my side while following the "install-reboot-forget" process. Only the lib folders had been moved/binded somehow to the SD folder, no base.apks and no odex-blobs(?).
The result was a totally broken system. Sorry, but IMHO the Dev should not proclaim it that way as long as the script seems to be in pre-alpha ... All log files in /data/media/adk/logs/ are empty, too!
Really don't know whether LMAO or :crying:
Sent from my OnePlus3T using XDA Labs
Please add an alpha into the title. Same happens to me.... and titanium can't restore accounts anymore...
The XDA link in the module description takes you to the forum section rather than this thread.
Seemed interesting and installed
But I lose all app data ,
found no logs and nothing just like fresh install of everything
Keep a backup before trying this
I was on magisk 16.7 ,
Redmi note 3 AEX N
Do not install! I lost everything like everyone else. Pictures I just took on vacation of my kids gone. All texts gone. All app data gone. Wtf man. This needs to be pulled. I lost 3gig of data
JohnFawkes said:
Do not install! I lost everything like everyone else. Pictures I just took on vacation of my kids gone. All texts gone. All app data gone. Wtf man. This needs to be pulled. I lost 3gig of data
Click to expand...
Click to collapse
Never ever try magisk stuff without nandroid or other backup in backhand.
I, like everyone else posting here, fell for this extension and lost all my app data.
I'm not sure if this extension is buggy or if we are simply too stupid to get it running but here is what I did:
install
reboot
forget (about all my app data as all apps seem to have lost their data)
I then opened a terminal, typed adk as instructed and am getting:
permission denied. Can't create /data/media/adk/logs/res_apks_verbose_log.txt: permission denied
typing su before adk does indeed give me a list of apps which seems to get longer every few minutes.
Maybe its still busy copying? I'll give it some more time. Not sure what's up though, are we supposed to wait for the ap to copy all app data over then do an initial restore? Or is it not correctly "linking" the apps to the new app data storage?
###edit###
I did not immediately remove this extension as I thought to give it some time. I then rebooted and its now hanging at the boot screen saying: "Starting up ... please wait" - this section usually only takes a few seconds but I've been staring at this screen for minutes now. I'll give it 30 minutes, maybe it is still busy copying all my APKs and app data to the SD card? I mean I was already wondering how this can only need one simple reboot to be ready...
I'll update this thread if I have any new findings as the extension description sounds quite logical so maybe we're all doing something wrong
Dev RECOMMENDED app data backup in first step even BEFORE INSTALLING it through magisk or twrp.
I think nobody is doing it
J4jks said:
Dev RECOMMENDED app data backup in first step even BEFORE INSTALLING it through magisk or twrp.
I think nobody is doing it
Click to expand...
Click to collapse
you're right he did. I didn't say I don't have a backup I only said the extension isn't behaving as advertised OR I don't get how to use it.
Also, he should change that sentence from "recommended" to mandatory if his app wipes app data
---------- Post added at 02:36 PM ---------- Previous post was at 02:18 PM ----------
I have disabled the extension and rolled back my backup. I'm still wondering what went wrong here as the extension actually created the right folders on my SD card. Somehow the links seem to have been missing. I didn't dare try a restore via "adk ." as it was unclear what else could have gone wrong.
I would however appreciate some feedback and clarification from the author.