Related
Hey guys!
Noob here who has flashed other phones in the past, but never anything Android based. Is there a step by step guide anywhere for the Mesmerize? Something generic and simple to follow from post root to a fully flashed phone?
Thanks for any input.
Tyler
Well our moderator is nowhere to be seen.. we should have a step by step sticked.. but we don't.
1) Root your phone. Search the forums to figure out how to do that.
2) Install RomManager and the ClockworkMod Recovery. There's a thread for that as well.
3) Download and install the ROM of your choice. Roms are located in the Dev Forums.
The details can be found in the Mesmerize General and the Mesmerize Development Forums. Search is your friend.
tyler.raven said:
Hey guys!
Noob here who has flashed other phones in the past, but never anything Android based. Is there a step by step guide anywhere for the Mesmerize? Something generic and simple to follow from post root to a fully flashed phone?
Thanks for any input.
Tyler
Click to expand...
Click to collapse
When I began this process about 2 weeks ago, I was at the same experience level as you Tyler. This is what worked easiest for me for my US Cellular Mesmerize.
(I'm just going to elaborate a bit on what Dcow posted, hopefully he doesn't mind .
Also keep in mind there are many variations to each step, this is what worked for me the easiest as a newb, hoping it does for you too.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda).
So take your time, read each step that these people have taken the time to carefully write up, and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. There is alot going on behind the scenes so just give it time, trust me!
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is to acquire the z4root.apk.
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it.
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal, trust me.
After it reboots open z4root again and run it, this time it will run no problems and phone will reboot.
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone.
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I downloaded with these instructions.
Download the two zip files located in the first post here
Place both files on your SD card root
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that.
Now open the TerminalEmulator
NOTE:The spaces below are actual spaces and the bml8 is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the mesmerize
At this point you're all stock and ready for new kernel/rom.
3) Install Voodoo lagfix kernel and new 5.0 sound
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
Note: There are a few ways of getting into this recovery mode, the best way if all else fails is to hold phone from the back with left hand (thumb on volume button, in the middle holding both down and pointer on power button) hold these down until the mesmerize logo pops up then slide your thumb down a bit to volume down only (if you slip don't worry it might blink but it'll still go to recovery)
Note: If you are more code/computer oriented there is a method using a program called ADB, which I'm not familiar with and seemed more complicated than what I went with. Search for that on the forum if you wish to do the above process that way instead.
4) Download and install the ROM of your choice.
Just pick one from this list Here, read through the first post of each before you decide, some are plug and play some take a few steps first.
Credit goes to all of the OP's and many others included in my sig, these people are awesome show them some love!
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
dcow90 said:
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
Click to expand...
Click to collapse
Agreed this should be a sticky! Thanks for the AWESOME write up bdemartino!
dcow90 said:
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
Click to expand...
Click to collapse
Did you PM me? I don't recall ever getting one from you. If I did, I apologise! I always try to be proactive in my forums
I check in on all my forums many times per day (even at work ) so if I miss something, please feel free to PM me anytime and I'll try to help where I can
I'll get in touch with bdemartino regarding getting a guide together that I can sticky
In the meantime Ill move this to general.
I few days ago I found an explanation here on how to do this:
http://www.howardforums.com/showthread.php/1694111-Installing-Clockwork-and-Voodoo-onto-the-Samsung-Mesmerize
(The same explanation bdemartino gave here today)
1. I used the files from there. How do I tell if I am running voodoo5?
2. If its not the same, I've read that I can install voodoo5 over another voodoo, correct?
3. Is anyone having trouble with 3g, vibrate, etc...on the mez? I saw in the voodoo5 thread that a few people were having trouble with these things. I couldn't tell if they were fascinate, mesmerize or captivate.
Sent from my voodooized Mesmerize using XDA App
gr4ybu5h said:
I few days ago I found an explanation here on how to do this:
http://www.howardforums.com/showthr...ockwork-and-Voodoo-onto-the-Samsung-Mesmerize
(The same explanation bdemartino gave here today)
1. I used the files from there. How do I tell if I am running voodoo5?
2. If its not the same, I've read that I can install voodoo5 over another voodoo, correct?
3. Is anyone having trouble with 3g, vibrate, etc...on the mez? I saw in the voodoo5 thread that a few people were having trouble with these things. I couldn't tell if they were fascinate, mesmerize or captivate.
Sent from my voodooized Mesmerize using XDA App
Click to expand...
Click to collapse
That is the old Voodoo kernel, you will need to go to the link I listed in my post for Voodoo 5, and yes you can simply disable lagfix and flash the new one over the old.
And no problems on the write up, I spent a good amount of time digging up the links and stuff but I'll spend a little more time polishing it and will post it in another thread for Scotsman to stickie.
And to answer your last question, no I'm having no problems with any functions of my phone after upgrading to voodoo 5.
Thanks for the write up and nice job on it too. It seems, sometimes when people try and tell others how to do something, they don't break it down enough. But you did and made it easy for us noobs. Thanks again.
My clockwork ( or voodoo, not sure) didn't come with a "disable lag-fix" button. I just have to create an empty file called "disable_lagfix". I'm just unclear where to put it. I saw it somewhere before I just have to find it
Sent from my SCH-I500 using XDA App
gr4ybu5h said:
Thanks for the write up and nice job on it too. It seems, sometimes when people try and tell others how to do something, they don't break it down enough. But you did and made it easy for us noobs. Thanks again.
My clockwork ( or voodoo, not sure) didn't come with a "disable lag-fix" button. I just have to create an empty file called "disable_lagfix". I'm just unclear where to put it. I saw it somewhere before I just have to find it
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There isn't a button, per se. When you go in to recovery, there is a disable lagfix option under voodoo. You can put the file, disable_lagfix, in the voodoo folder on your sdcard to do the same thing.
He does write up a good how-to, though, doesn't he.
Haha thanks guys, and you're welcome!
I think the reason you don't usually see this much detail from others is because they are more developmentally enabled and therefore "forget" to break down the little steps that are second nature to them but foreign language to a non-developer.
Thanks. I found it. and disabled it aready. now i just download the file in the write-up and boot into recovery, install zip from sd card and select my file correct?
I always wipe dalvik cache (in advance settings within Recover) before flashing anything.
So it's;
Disable Lagfix
Reboot (you'll hear the chick reversing the process)
Clear Dalvik
Install voodoo 5.0 from zip
reboot
re-enable lagfix and reboot one last time.
Then you'll need to download the voodoo controller app from the market to control the amp gain and set a few other eq settings.
Man you guys are fast. Thanks for the quick replies. WOW
Ive done all that except re-enable lag-fix. Noone ever mentions that step. Do I just remove the "disable_lagfix" file from the voodoo file and reboot?
I just enable/disable it through the voodoo menu in recovery, much easier than pushing files around. In your case i think you should be able to delete the file and reboot, but if not you may just need to go into voodoo and enable it that way (after removing the disable file)
I guess if I edit a post and dont finish it, the post gets deleted. Oh well, I asked how to reenalbe lag fix but i figured it out. Like I said I had to put the disable lag_fix file in the voodoo folder. I just had to remove it from that folder.
Is there a way to tell (besides the quickness and the extended battery life) how do i tell if its voodoo5? just out of curiousity
Just a guess here but possibly under About Phone the kernel version might? Mine is listed as 2.6.29
I would also think that when trying to use the Voodoo app it would fail if you didn't have the kernel so that would be a sign too, if that's what you're looking for.
Well thanks alot. Thats what mine was listed as also. And the voodoo app did work, so I guess I've got it. And I think thats all for now.
Now I think I might wait to see the awesome developers come up with for 2.2. I dont mind the stock 2.1 for now. I just dont want to keep flashing ROM's, if they might be close to getting a version of 2.2 going. I can wait....I think.
Thanks Again
gr4ybu5h said:
Well thanks alot. Thats what mine was listed as also. And the voodoo app did work, so I guess I've got it. And I think thats all for now.
Now I think I might wait to see the awesome developers come up with for 2.2. I dont mind the stock 2.1 for now. I just dont want to keep flashing ROM's, if they might be close to getting a version of 2.2 going. I can wait....I think.
Thanks Again
Click to expand...
Click to collapse
2.2 is so close, you should be able to smell it. I've had it's froyo-ey goodness all over my phone and even with the issues we're still having, I flash it back every night when I get home to play with it.
phidelt82 said:
I've had it's froyo-ey goodness all over my phone
Click to expand...
Click to collapse
That's what she said....
After bdemartino wrote his AWESOME thread for the Mesmerize it seemed only fitting that the Showcase get their very own... And since his Thread was Flawless, with his permission I'm mostly copy/pasting word for word.
THIS GUIDE IS SPECIFICALLY FOR THE SHOWCASE
If you're Looking For FROYO Skip down to the bottom of this post to the Section Labled FROYO!!!!!
Keep in mind there are many variations to each step, this is what worked for me the easiest.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps to Customize Your Stock Showcase (For Eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Showcase on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
I use Root Explorer
It's a few bucks, but there's hardly a day that goes by when I don't use it.. (Well worth the money)
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two Files you need from the bottom of this post
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/zImage /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the Showcase. This is just what works with our model.
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
Accessing Recovery!!!!!
NOTE: There are a few ways of getting into recovery mode. The easiest is to download QuickBoot.
Once installed you can install the widget to any homescreen or just use the app from the app drawer. Once you open the app, click Recovery and it automatically reboots the Phone into Recovery..
You may have to click the install update.zip (while you're on the stock kernel after Voodoo you won't have to anymore)
The other method, which you will need incase you EVER Bootloop! Is the 3 finger method (Hold down the volume up and down keys and the power button all at the same time when you're turning your phone on) Once you see the Samsung splash screen you can remove your finger from the power button, but keep holding down both volume keys!!!
Incase of Bootloop, remove the battery and do this while Rebooting...
AGAIN WHILE YOU STILL HAVE A STOCK KERNEL, YOU WILL PROBABLY HAVE TO *apply sdcard:update.zip* after you enter the FIRST RECOVERY...
The next Screen will be Clock Work Mod, this is where you will want to do your First Nandroid Backup!!!!
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
Now onto Installing a Voodoo Kernel
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
Now you can install Voodoo Control and get new life out of those earbuds!!!
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
4) Custom ROM : Download and install the ROM of your choice.
Right now we really only have 1 that I recommend..
It's Phidelt82's PicknPack Rom
This is a deodexed Rom which allows you to use MODS and themes. This ROM is 100% Stable, I've been running it for a WHILE with ZERO issues...
MODS/Themes/Customization
NoClock in the Status Bar
Midnight Theme
HoneyComb Digital Clock
Shutdown Animations or Images
Bootanimations with new Boot Sounds
Of course there is WAY more than these listed, but this should fill up your afternoon playing around with your new and IMPROVED Showcase!!!
FROYO FOR THE SHOWCASE = YUMMY!!!!
Yes, for those of you that didn't already know, thanks to Phidelt82 we now have Froyo!!!! I've been running it for about a week and it's Delicious!!!
I'm not going to Write as much as I did for the 2.1 b/c the directions are in the threads already.. Just follow the Directions, if you have any problems after that read through the threads and see if anyone's already figured them out...
And this will work with a Factory Showcase!!!!!
First of all you need to go to:
[Froyo-Odin] Showcase EB11 - Cellular South Update (be sure to Thank Phidelt82)
After this you will have 2.2, now you can use:
SuperOneClick to root your new Froyo Showcase (if you want)!!!
And if you plan on doing Mods/Themes/etc.. You should go ahead and Flash the EB11 Showcase Pick-n-Pack, again be sure to thank Phidelt82 for this!!!
If you flash the PicknPack Rom made by Phidelt82, then there's no need to root... It comes PREROOTED.. You only need to ROOT if you're staying on the Stock 2.2!!!
If you're flashing the picknpack do a Nandroid backup after you're done.... If you're going to stay on the Factory 2.2, do you a Nandroid backup after that...
Thanks to lmartin92, JT1134, Phidelt82, we now have a voodoo kernel with lagfix for 2.2 which can be found HERE...
If you're new to using voodoo lagfix kerenls.. Remember to always disable lagfix before doing Nandroid Backups/Restores/Flashing mods/Themes for YOUR SAFETY
I'm working on a few themes... sbrissen has already Made us the NoClock and NoAmPm mod (you have to be on the picknpack for these)
For a list of the Mods/Themes/Roms for the showcase look HERE
Always check the Mesmerize forums for new Android Development, Mods, Themes, etc...
And for help Don't be afraid to ask (after you've read this legnthy post) or drop by the #samsung-mesmerize channel at http://webchat.freenode.net/
Thanks to Phidelt82 for all of his dev support for our phone!!! If you want to donate to him click HERE
Thanks to bdemartino who wrote the AWESOME tutorial HERE that i mostly copied/pasted from!!! Be sure to click his thank you button if this helped you out...
Reserved FOR Me!!!!
Great work elijah, you are the Showcase king
bdemartino said:
Great work elijah, you are the Showcase king
Click to expand...
Click to collapse
my Kingdom sure is small lol
It is probably bigger than you think Elijah
ocs111 said:
It is probably bigger than you think Elijah
Click to expand...
Click to collapse
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse
ocs111 said:
I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
Click to expand...
Click to collapse
I'm hoping Bubbakoush will test since he has a showcase that needs to be flashed back to factory... I wouldn't recommend flashing this until after he can confirm it works
elijahblake said:
my Kingdom sure is small lol
Click to expand...
Click to collapse
Hey bro, don't think we're not around... I'm just enjoying my rooted Showcase, waiting for some more ROMs to give a try.
Thanks for all the work putting this together, and everything else you've been working on for Showcase!
Nice write up!
elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse
We're here... For the most part i'm waiting on a stable 2.2 or 2.3 based rom. Running pick-n-pack for now with Voodoo5.
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
you more than likely are going to need to install Root Explorer onto your phone.. And use it to move the files (that's what I and many others had to do)
blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
Are you typing su first to grant root permissions? You should see a # instead of a $ at the prompt.
Sent from my voodoo froyo Mesmerize
I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?
blroberts228 said:
I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?
Click to expand...
Click to collapse
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
will Root Manager allow you to do this? If not Rootexplorer will.
if you do this:
I'm not sure if you can do this through terminal or not... I did mine from my pc... you may have to leave off adb shell and just start at su when using terminal...
This is making the file executable
adb shell
su
chmod 777 /sdcard/redbend_ua
while it's still on the sdcard (Before moving it then you don't need to worry about it)
Ok, it seems that the Mes instructions were infact different on this method... I've updated the first post... If you'll read now you'll see what you should be typing in..
sorry about that, and thanx for pointing it out
I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?
blroberts228 said:
I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?
Click to expand...
Click to collapse
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.
elijahblake said:
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=860250
look at that thread and tell me where you're at....
Yep, ive done all of that stuff also...and whenever I take the entire zip file, rename it to update.zip and reboot into recovery it tells me that the sdcard is busy
I downloaded the netflix.apk that has been floating around, and with a few tweaks to my build.prop, I was able to get it to work on the galaxyXT ROM.
You have two choices, either download the attached build.prop file and stick in into your /system/ directory... or make the modifications yourself. FYI, please make a backup of the original build.prop before you mangle it.
I changed three lines in my build.prop. Just find these lines in your build.prop and change them to this:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2.1/FRF91/277427:user/release-keys
Reboot, and that worked for me! If you have different experiences, please be sure to post them here.
FYI, If you make the changes yourself, make sure they are exact, case and everything. Use Notepad++.
Enjoy!
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
c_urbanek said:
how/where do you access the /system/ directory? I looked on my SD card but cannot find.
thx
Click to expand...
Click to collapse
Not on your sd card.
It is in the /system/ Use Root Explorer or something like it.
It's in the phones internal memory, not on your sdcard. You would either need a file explorer with root access (e.g. Root Explorer) or you need to push it with adb.
tried using root explorer & it says the system files are read only...
Nevermind, clicked the R/W button & it allowed...
I'll try Netflix now after a reboot.
At the top of window while in root explorer you'll see a MOUNT R/W button, you need to toggle on read / write access.
Wow! Works Beautifully!
Wow! Works Beautifully! Thank YOU!
Work on Dexter's 1.3 too!
Sorry for the ignorance but what is it?
Streaming movie/TV service. Not everybody has it, but its a big deal for Android phones to FINALLY get it since iphone and Windows 7 phones have had it for a while.
I'm not sure, but there are several apk XDA of netflix, and other folders, I can not understand yet. Apk is installed, replace the buildprop and that would be enough? You may be able to give us the link to the apk please because in my market does not appear.
For the payment of subscription must be from the website or can be within the application?
The truth was unaware of this application, it looks very interesting. Thanks for sharing.
can someone share here the apk..tq
This is where I downloaded it from
3rdstring said:
This is where I downloaded it from
Click to expand...
Click to collapse
Thanks for posting that. I couldn't remember where in the forums I had found it.
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
donovanx3 said:
Hey I'm running stock 2.1 rooted on the xt720. I swapped out the build.prop you supplied in the .zip and installed numerous versions of the netflix clients to see if any would work. The apps installed fine but when I tried to open them (every single one) just opened to a black screen, then it force closed with a bunch of Japanese lettering. Any suggestions? Thanks.
Click to expand...
Click to collapse
Unfortunately
"Latest version: 1.2.0 build 819145-1.2.0-102 (for Android version 2.2 and higher)"
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
see 1st post in this thread....
ErnFuggit said:
I got Netflix installed and everything seems to work. But when I hit play, it starts to load and says that I don't have a Netflix ready device. I have Dexter Froyo v1.3 on XT720. Anyone have this problem?
Click to expand...
Click to collapse
once you install the apk, you need to do the hack rev explained in the 1st post.
New APK
Has anyone tried the new "stock" Netflix apk with the XT720?
I running the 1.20 APK, haven't seen an apk for the 1.21 yet, though I haven't gone looking yet either.
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?