Related
LATEST AND LAST EDIT TO THIS THREAD:
Download the new maps from Google in the marketplace for Google Navigation. Works Android Phones running the 1.6 platform.
No need to follow these instructions anymore!
---------
#Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of #problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's #setup correctly.
#Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. #Thanks goes to aad4321 who posted it.
#The edit is simply changing the ro.build.fingerprint line to:
#ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
#You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the #attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use #these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
#This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook #(force closing), etc as reported in the other thread.
#<EDIT 1>If you get the errror "Device not found," make sure you have USB Debugging enabled in settings (thanks kizer).
#<EDIT 2>After performing a rm command, if you get a statement about the directory or file not existing, all is fine. Those rm commands are just trying to #find all possible places the old maps app could be stored, and so if it doesn't exist, you don't have to worry about it. Just go on to the next step.
#<EDIT 3>If you don't see the navigate function, install google voice.
#0) Connect phone
#1) Unzip downloaded file
#2) Run Part 1.bat
#3) When prompted to press any key, do so; the phone will reboot
#4) When your phone is running again, run Part 2.bat
#5) When prompted to press any key, the installation process is done.
#6) Make sure GPS is enabled
#7) Open Maps and press OK
#8) Press Menu
#9) Press Directions
#10) Enter an end point
#11) Click Go
#12) Just under "Show on map", click Navigate.
#13) If prompted to install the voice codec, do so.
#http://www.mediafire.com/?znzizmd1mmm
junker02 said:
Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's setup correctly.
Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. Thanks goes to aad4321 who posted it.
The edit is simply changing the ro.build.fingerprint line to:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook (force closing), etc as reported in the other thread.
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
While I placed the files from his zip directly on my SDcard and used terminal to run the command, Junker's method appears stable. I have Google voice, protected apps in market, and functional Navigation. (can't answer for facebook, since I don't have an account.)
Note to someone who does not know shell commands...don't try and copy the ADB commands they are not the same. Know what you are doing before you do it.
Thanks for the post Junker02
i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.
I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.
krstnsn said:
i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.
Click to expand...
Click to collapse
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
kizer said:
I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.
Click to expand...
Click to collapse
Thanks for the tip! I'll add it to the first post.
junker02 said:
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
Thanks for the tip! I'll add it to the first post.
Click to expand...
Click to collapse
I agree, the other threads over complicate it and cause problems for those who don't know what they are doing. If they learned how to do it themselves there would be less questions and complication.
But then again, now this is just another thread about nav. Really, they should all be locked and something like what is in the first post should be put in the informative links thread.
wanted to thank you for instructions, possibly a better forum wiulda been q&a, as I go there to find answers and help solve some =) other than that this does clear some things up such as the ro line. Like in the other post it says almost same thing but fails to mention the line to change. Etc..etc... this did catch my eye and I was was about to try another method for my buddies phone and this saved me of searching through a thread. My penies, again ty.
junker02 said:
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
I had no problems, but I did it myself:
from scratch (no map mods, orig build.prop):
adb remount
adb pull /system/build.trout.prop build.trout.prop
open it with notepad and edit the line
ro.build.fingerprint=tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys
so that it reads
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
save it
adb push build.trout.prop /system/
adb shell reboot
now reininstall google voice from market and reinstall maps with the new one
help me out here man, i dont have adb, i just use my phones terminal
bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
ok, even easier, do you have astro?
you can navagate to the /system directory, copy the build.trout file to your sdcard directory. mount your sdcard and edit the file with notepad. copy it back over to the /system directory and reboot
then install voice and maps
or try doing the same from your pc using droid explorer
http://forum.xda-developers.com/showthread.php?t=558108
haven't tried it either way way but it seems like it should work
scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
Yes, that's exactly what it will do.
bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
The ADB app is included in the download. I'm not sure if it will work without the driver installed, but you can give it try and report back. Simply run the two .bat files and it will execute all the necessary ADB commands automatically.
Worse comes to worse, you would just need to install the driver for your phone.
Ok, here are the steps I took without adb, since comps at work do not allow USB write.
I uploaded the build.prop and maps.apk and sent them to my email using yousendit.com
Downloaded both into sdcard/download
Using "Root Explorer" navigated to /system and set it R/W (there's a button on the top)
Moved the build.prop to /system
Reboot
Install Maps
Reinstall GoogleVoice
Voila!
When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?
scrappyabs2 said:
When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?
Click to expand...
Click to collapse
Is your usb debugging enabled on your device?
Settings>Applications>Development
xavina said:
Is your usb debugging enabled on your device?
Settings>Applications>Development
Click to expand...
Click to collapse
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.
scrappyabs2 said:
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.
Click to expand...
Click to collapse
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.
junker02 said:
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.
Click to expand...
Click to collapse
adb remount says "error: device not found"
Here you go guys, safe simple and so easy a caveman can do it... (insert the, "If you break it, it's your own fault disclaimer here.)
Download the file in the first post of this thread.
extract the file on your hard drive and copy the build.trout.prop file and the Maps.apk, then put them on to your SD Card.
If you can't get this far....we have a bigger issue.
Then in terminal emulator type
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/build.trout.prop /system
reboot
When the device reboots then do this one in the terminal emulator
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/sd/app/*Maps*
rm /system/sd/dalvik-cache/*Maps*
rm /system/app/*Maps*
reboot
*Note: Someone might say that the reboot at the end of this code is not needed. That maybe, but it worked just fine for me.
Now using Astro, or another file manager, install the maps.apk from the sd card.
If prompted, install the voice. I had it from other programs.
Turn on GPS
Open the drawer
Click on Maps
Let the Maps program find you
Then click menu, directions
Enter the destination, and click go.
It should show
Code:
My location
<the destination address you entered>
Show on map
[B]Navigate[/B]
Thanks for making clear instructions for the terminal emulator [email protected]
Everyone please remember that one can only use the build.trout.prop file in the first post if they are also running Cyanogen 4.2.5 on the G1, else you run the risk of app errors and force closes. If you are running a different version of Cyanogen, make a copy of your own build.trout.prop file found in your system directory, and edit it.
I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.
so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.
Post Removed to maintain consistancy, see 1st post in thread.
root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title
Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.
Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.
Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise
HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!
New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need
confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).
You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk
i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.
1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!
[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."
Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!
Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.
Good work! This should be a sticky!
Sent from my Epic 4G
dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
you might wanna add how to set adb
Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.
Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.
not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
by posting lamely, U r not helping the developer u r just spamming his thread
to really get help, make sure u have a logcat of your problem
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
You can see what processes are running, if a process is running after a certain interval of time, it will eat battery. So you can also find out what is draining your battery.
What developers need is a logcat To know what is the issue
i will tell u how to make it on a phone itself
1) download an app called ALOGCAT
2) install app and open
3) u will find random text coming there (its not random literally )
leave it in background by pressing homekey
4) this step is specific
for eg. if are having trouble in switching on wifi , try to swtich it on or do fiddle wid anything u have .. just play around with your cell, run the app u think is buggy or whatever
once done
5) press home button for long, select alogcat app,
6) click on options hardware button (right one ) and click on save.
logcat will be saved to sdcard/alogcat folder in the form of txt files.
7) now either u can directly upload the logcat.txt while telling about your problem
or
u can copy the contents of that txt file and paste on www.pastebin.com
after pasting u will get a link something like pastebin.com/******
just copy link and paste along wid ur problem
8) now next time u have a problem make sure u attach a logcat along with it
this method is not useful if u r not able to boot the phone
for that u need to have a pc and android sdk installed along with the drivers
if u have everything installed then
Open the 'run' dialog by pressing the 'Windows' + 'r' buttons on your keyboard (minimize the browser & other non-windows programs)
cmd (this will open a DOS prompt)
cd c:\Android\tools (go to the directory where you extracted the SDK)
adb shell
Now you'll see just a '$'
logcat
You can now just press the power button on your phone to see what happens. It displays everything the device is doing.
This is my first post regarding logcat , so i m sorry for any discrepancy (if there, notify me plz)
P.S - logcat is also useful in case if u r having some trouble wid stock roms
thanks @El_Dark for extending the op.
When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
Thank you, Now problems will be solved easily.
__________________
Sweet Devil >_<
GT-P3100
Android 4.0.4 ICS
Sun Cellular
"LG should go bankrupt"
GApps+ | Not your typical Gapps.zip
Very good to know. Thanks!
Sent from my SGH-i777
Nice tks!
Thanks for the tips, I use app called CatLog. Works good.
Sent from my Nexus 10 using Tapatalk HD
Thank u very much for ur thread
Sent from my Micromax A50 using xda app-developers app
doctor_droid said:
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
..............................
...............................
Click to expand...
Click to collapse
Thanks. This is very useful...
Thanks for the post. :good:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
El_Dark said:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
Click to expand...
Click to collapse
i will add this to op if u permit ..
doctor_droid said:
i will add this to op if u permit ..
Click to expand...
Click to collapse
Of course!! That's the idea
Thank you! Very useful to know.
please note ,this is only for mac users
Many MAC users are facing this problem that BLUESTACKS keeps showing loading screen after every reboot.....
well the fix is simple....:
1. open terminal
2. type the following command
Code:
rm -Rf /Users/<your username>/Library/Preferences/com.BlueStacks.AppPlayer.plist
3. e.g. if your username is john then it would look like rm -Rf /Users/john/Library/Preferences/com.BlueStacks.AppPlayer.plist
4. launch bluestacks, click accept ,wait for a while and HOLLA....bluestacks is up and running...without loosing any data...
now some mayn't like typing the command again and again after avery reboot.....
so i just made an app to make it a breeze...
1.download the bs fix.app.zip from the attachments
2.extract it and save the bs fix.app in the applications folder.....
3.right click on the app and select show package contents...
4.browse to contents/resources/script
5.right click on the script and open with text edit.app
6.replace <your username> by your real username...as done above...(e.g.:john)
7.save it and then open preferences>users and groups>login items and add bs fix.app to the list by using the small plus button at the bottom...
next time you won't have to do anything......after very reboot ,just launch bluestacks and enjoy.....
if any errors occur just post here.....or better look up the internet for a solution to the error.....if nothing happens then post here.....
...
This thing works for me even today......please explain your problem I will guide you.....maybe you are doing something wrong....
Hello,
I tried your solution by running the script in the package.
BlueStacks keeps loading, a quick black screen is showing up then bluestacks is totally closing.
Followed all your steps two times. Uninstalled BlueStacks and did it again.
Thanks
Got me pass the enable app store...
but now stuck at the 'loading channels'...frozen
Hi i my bluestacks games isn't playing in the sense that the games won't even starrt loading when you click them can you help me with this?