Related
While reading this thread on how to run different images in the emulator, I came across ggolemg's directions on how to accomplish this:
Code:
thats the easy part
do a nandroid backup
copy the sdk/platforms/android-1.5
to something like sdk/platforms/MINE
go to your AVD directory AVD/whateveryoucalledit
open up the config.ini
edit:
skin.name=HVGA
skin.path=platforms\MINE\skins\HVGA
image.sysdir.1=platforms\MINE\images\
go to your nandroid backup on your sdcard
copy system.img
go to sdk/platforms/MINE/images/
and paste the nandroid system.img
now run your AVD and it will boot that system.img
im running CyanogenMod rom right now in the emulator
hint* number pad 7 with numlock off in the emulator is how to open up the hardware keyboard
This worked perfectly for me. However, I'd like to mess around with all the ROMs out there, but short of installing them and doing a nandroid (thereby making the testing pointless) or doing the more complicated method of pulling them off via the mkfs.yaffs2 tool, there isn't an easy way to do this.
So I was wondering if you guys would be interested in putting up clean nandroid backups of some builds for testing in the emulator?
No one? Does anyone think this is a good idea?
i make nandroids of every build i try, but they are on my external drive(about 300 miles away for the next week) i can post the system and boot next week for a few older roms, but lately i've been using dude builds only.
it seems like a decent idea but i would think the best way for an individual to do this would be to use the mkfs.yaffs2 tools, wouldn't you rather see what it is like on the actual phone????
Yes, to an extent. I imagine the rom would run faster in the emulator, but it's still fun to check it out.
Maybe I'm not entirely familiar with the yaffs tool.
So I tried to use this method to load my Nandroid' Backup from before I installed CyanogenMod on my g1. Only problem is when I boot the Nandroid System Image on the emulator, it starts out at the t-mobile/google sign-in screen. The phone/emulator won't let you get past that until you sign in with google, but since the emulator has no data connection, I can't sign-in. Any help or suggestions would be appreciated.
Thanks,
Dave-O
im trying to do this with the new 2.1 android and my first nandroid backup and it dont work.. anyone know how to do it right please??
im using a nandroid system.img of my nexus one... i found this thread on google
I've tried this method and never got a system.img to boot in the emulator. It just froze at the bootloader screen (no logcat either). Is that what happened with yours?
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
the same happens with me... :S i need it
If someone knows a solution I'd like to know. Does it involve building a separate kernel/boot.img for the emulator... or maybe just some changes in build.prop... both? I dont know.
Sent from my Droid using the XDA mobile application powered by Tapatalk
Sorry for pulling the old post but no one seemed to continue figuring this out.
As for the system.img pulled from Nandroid, it should work.
I think you need to sign the image file.
Any one knows how to do this?
See links below, the guy who wrote that made the system.img work, I've tried it and it works.
http://android.modaco.com/content/general-discussion/289928/testing-getting-an-emulator-up-and-running-a-full-rom-with-the-market-etc/
This is the "OP" or the Original Post #1....read it before asking any questions that my be answered in this post or in any of the following links!
Background: I started this thread because of the explosive growth of MikFroyo's Roms. The thread got so clogged with total new user's questions that it became difficult to find real answers to real problems. Not that new users can't learn, but I wanted to try and create a place for people who don't depend upon RomManager to control their lives!
Look, the way I see it, if you were smart enough to root your phone and start flashing new ROMs (that is the correct way to spell it btw, not roms, it is an acronym after all!), then you deserve concise answers to your issues based upon my experience in flashing phones that I have gathered in the past 3 years since I first started flashing things for my Razr phone.
I will assume you know how to use, and have properly setup, adb on your home computer. Yes, many of the commands you may see me or others post could be done through a terminal window on your phone, but your life will be much easier and more efficient if you have adb setup and working correctly on your home computer or laptop!
Here as a begining are some of the more useful posts I and others have made regarding flashing MikFroyo ROMs and some of the issues associated with this endeavor:
No touch tone recognition using MikZ?? Check solution here!
Thread that deals with changing the Power Control Widget in Notification Bar
Nick's repost of Mitchellvii's solution to Market D/L problems
Stopping your Market from Updating and losing it's skin
Nick's updated adb installation guide
joeykrim's adb getting started links
My "How to make apps2sd work" on your phone guide
The most recent repository of Netarchy Kernels
How to "flash_image" a recovery image to your phone
Pushing "Removed apps" from MikFroyo to your phone
Having "Wifi scans constantly but cannot connect" issues with MikFroyo?
Using a2sd "Sysinfo" command to learn alot about your phone's current status
Info about different Kernel types here
General statement I posted about different hardware versions
A Hardware Engineer (me ) view on "Color vs Black and White" Themes and battery useage
Much more to follow, but I thought this would get the ball rolling!
Tapatalked from my SUpersonic...
You said razr Mr. Link man
sent from Kings Ultra UNleashed
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Fr3sh2De4th said:
Could you post how to get adb working? I tried it a while ago but havnt given it another shot
Click to expand...
Click to collapse
This is not my work, but a good starting point is provided at: http://forum.xda-developers.com/showthread.php?t=694250
Browse the entire thread if you like, but the download links are in the 1st post. Thanks for the guide goes to joeykrim.
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
chefdrew said:
I just flashed mikfroyo, got it working, then flashed the kernal that you suggested.
My wifi turns on for a second, does not connect, then turns off and says unable to scan for wifi??? I did do a full wipe, cache and dalvik before flashing mikfroyo.
Any suggestions?
Click to expand...
Click to collapse
All in one blow flash the rom and kernel back to back. Then reboot and enjoy!
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
chefdrew said:
thank you I will give it a try. do I need to wipe anything before or after the flash?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do the regular wipe of everything and then just flash the rom n kernel all on the same time n reboot
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Nice thought to start this thread ! Kudos my man!
"Walk by Faith-not by Sight"
chefdrew said:
I just tried it and nothing has changed?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do u have the formatall.zip?
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
chefdrew said:
Not sure I know what that us, so maybe not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
flash cache after format all......i don't think so...... i always boot into ROM before i do the kernel just in case, but i am paranoid haha
luckylui said:
I want u to flash this zip ima link u too.
Flash the zip and then wipe everything again twice then from there flash the rom n kernel all in one recovery visit..
So
One- flash the formatall.zip
Two- wipe cache dalvik n data n sd ext two times
Three- flash rom
Four- flash kernel
On the same recovery session.
By the way what kernel u using?
Heres the formatall.zip link
http://db.tt/VKtEHjt
Click to expand...
Click to collapse
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
chefdrew said:
I did a full wipe, cache/dalvik, system & boot wipe. Flashed mikfroyo then the kernal, reboot...viola!!! Everything is up & running...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
:-D
Good Luck buddy! Enjoy your time w the rom, its a beauty.
Installing ADB
First off I am not the originator of this guide, it can be found here and was created by nephron. I just updated it with some updated links and instructions. The newer version seemed to do a lot of the steps that were in his guide therefore I didn't need to do them to get adb to work.
Another guide I borrowed some stuff from can be found here and was created by joeykrim. If you are using a mac or linux machine go to this thread for the download links.
Again I want to give credit to those guys because they really created the original threads and I just borrowed some from both of them to create an updated install guide. This is only an install guide and if you have ADB command questions you will be better off going to those threads and asking in there or searching XDA for your answers.
Link to the Android SDK site, you might check here to see if there is an updated version of the SDK that I have link below(installer_r10)
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
7-zip - Download
Win 7 Drivers- Download-thanks shep 211
HTC Sync-The one that is in the SD card that came with your phone will work
Windows PC
USB Cable
A Rooted HTC EVO
--------------------------------------------------------------------------
Setting up the Android SDK
I installed the drivers and htc sync first, I am not sure if that matters or not.
Download the file SDK file from above and accept defaults to install it.
Once installed make sure the box is checked that says "Start SDK Manager" and hit finish.
Once SDK Manager opens click on the accept all radio button and hit install. Be patient it will take awhile.
Any problems or questions go here.
Once completed take the "android-sdk" folder and move it to the root of your hard drive (C:\).
It will be located in c:\program files(x86)\android, it's large folder so it might take a little while.
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
On the bottom half (system variables)
go to PATH and edit it to include C:\android-sdk\platform-tools
Make sure to separate it from the rest of the ones in there by a semicolon
Hit Ok
*The reason for this is so that you can run adb from any folder on your drive so that you don't have to copy your files to the tools folder. Big thanks to jadeboy and coiledwire for helping me figure this out.
--------------------------------------------------------------------------
Preparing your phone for ADB
If you are running MikFroyo it should be checked by default but you can double check it if you want.
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and it should automatically install the drivers. I've done this 4 times and every time it finds the phone just fine.
If not check out this thread here.
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands. Go here if you want to learn/test some of the basics, it's in joeykrim's thread. His push/pull of test.apk won't work because that file isn't in there. However you can just create a test.txt file on your c:\ and push/pull that to your phone. That's what I did to test that.
Easiest one to test is
Code:
adb reboot
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
Widget Text edit
Hey you might stick this in your popular solutions OP.
Link
Slow Market.
Thanks to Mitchellvii
JK you can just link to his post on this if you want since he actually found it. Here's the link
POSSIBLE SOLUTION TO SLOW MARKET:
As you use your Market, your /cache appears to fill up with .apk files call Download-1, Download-2, etc. Why Market chooses to just continually add these without deleting the older ones is beyond me. It eventually just eats up your /cache and slows Market Updates.
From what I can tell, there is absolutely no harm whatsoever in deleting these. You can delete them using Root Explorer + Multi-select or you can boot into Recovery and Wipe Cache. I am not sure if wiping /cache also clears Dalvik Cache if it is on /cache. However, if your phone takes a long time to reboot after wiping /cache then I would assume it does since your phone has to rebuild Dalvik. Either way, nothing is damaged.
I have looked at the various "cache cleaners" on the Market and have not found one that clears out these "Download-#.apk" files. If someone knows of one, please share it with the room.
The act of going into Applications and clearing MikMarket Data & Cache does NOT delete these extraneous files.
CONCLUSION:
If your Market is being unresponsive, use:
1. Root Explorer to delete all of the "Download-#.apk" files from your /cache (root), or
2. reboot into recovery and wipe cache.
After this, your Market should become much more responsive. Option #1 is easier.
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
I'm kind of a noob but im trying to learn how to create a rom. How can i test a rom without flashing it on my phone is there some type of emulator i can use? I tried ADK Manager but i dont know how set it up to the specification for infuse.
Best way is to load it to your phone, that way you can experience what others are....or find a second phone....to test with...
Sent from the Black Star`d ICS GNote.
I use adb to push modified apk and jar files to my phone. You can stop the phone, mount system as read/write, copy over the new files to their spots in system, remount as read only, and reboot all by using adb. You want to test small changes at a time, and one apk at a time so you know what works and what doesn't on the phone.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2