Database Info

[Q] Rebooting to Bootstrap

I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!

That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App

Wait. I have a normal reboot. Maybe mine is messed up?

Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App

The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z

If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.

Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer

jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way

Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.

jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.

Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol

jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.

Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.

jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App

DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse

I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...

Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App

Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it

Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?

DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.

[Q] Step by Step?

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....

perm root my 4g

I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan

The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.

thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?

i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....

kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.

neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.

kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.

neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996

kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.

neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.

kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.

neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?

kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.

ok thanks.

Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan

lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.

Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?

Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.

My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App

danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun

Samsung Galaxy Indulge 4G nand lock

I just got one of the new Galaxy Indulge 4G phones and tried rooting it.
BusyBox installer is telling me that the phone is rooted however it is nand locked.
and ideas on how to unlock nand on this phone?

How did you root it?

Thaxx said:
How did you root it?
Click to expand...
Click to collapse
SuperOneClickRoot.

Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!

So basically I think this means we a need a custom recovery, flash image and stuff. Bah, that'll probably take like a month

K, also tried visionary rooting, which did some wierd ****. I rebooted and it seemed like i had root, but super user still didn't work. It fooled a couple programs into thinking i had root, but it would not let me "touch" the files on the phone. Even though it claimed I had r/w permission.

Silvist said:
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
Click to expand...
Click to collapse
The Samsung Epic 4G drivers worked for me, also tried the rooting process used on the Epic whoever busybox says im rooted but that nand is locked, i downloaded Terminal emulator and it says im not rooted, also installing superuser not possible, I was able to install root explorer but not any good if doesnt let me delete the bloatware only read.

Yeah, busybox says the phone is rooted but nand locked.
superuser app was added to system/apps. however im not able to mount system/apps with R/W from root explorer. The rooting process seems to gain access to r/w the files but the apps cant.

seems 4G still have far distance from us...

Supposedly there's a work around for Nand locked, but the first one didn't work for me.
With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can’t copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don’t need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.
Click to expand...
Click to collapse
This didn't work still for me. So the only other option was unrevoked, but when I went to the site, it listed only HTC. Kinda confused how using HTC roms is a work around for a samsung phone lol. Still need some master guru's help on this stuff.

I too have been trying and am unable to get nand unlocked, I would really love some other ideas. Anyone out there able to help?

I'm waiting 'till the $50 MIR on the 1st, then I'll jump in with both feet.

Some guy suggested to shell root > perm root > restart device. That doesn't work either. I also noticed something called "media scanner" that scans as the phone boots up, i wonder if that's preventing any modified files.

If anyone knows how NAND unlocking has worked for other phones (and im not just talking about what apps to run or what room to use) please contact me so that we can try a few things out and hopefully get a full root for everyone.

Supposedly Mr. Parker rooted:
http://forum.xda-developers.com/showthread.php?t=803682&page=260
I'm asking him through both post and through private message if he could elaborate. Apparently he had trouble with getting Win 7 x64 to work, but it worked with Win Xp. I'm still not sure what drivers he used, and he said he had it not in debug mode. I tried in non debug, and my phone wouldn't even register. So hopefully he'll expand on how he did it. If not, back to the drawing boards, at least till we get a real pro in here.

Got my hopes up that even though we dont have full root yet, I would be able to get rid of the bloatware.
The SuperOneClick is able to get read/write access and send commands to the phone so I opened Root Explorer on the phone and then rand the superoneclick. As soon as the program mounted the phone with Read/Write I started clicking on the Mount R/W button in root explorer until it showed the app as having read/write access to the system/app directory. I tried deleting the Iron Man app and it said it was deleted successfully.
but then I checked and the app was still there loading root explorer agian then showed that the file was still there and had not been deleted.

Wow you managed to get root explorer to work? Mine just tries to obtain root, and crashes everytime i start it up now. I've tried to unroot, and uninstall and reinstall it. I used Linda manager to view the files on the phone, but like you if i deleted they would return on boot. That's why I think metro or samsung has some kind of media scanner that scans at start up, and it somehow reinstalls files, or prevents root. Can't confirm this yet because super user fails ;/

I've been trying also to get root. Programs often will think i have root access. as far as adb is concerned i do have root access till i dont something that requires it. I've been able to install root manager and look through some files. Im under the impression metro or samsung did install something odd, though im not sure the media scanner is it. Also the phone does not require root in order to install other-market software.

What do you mean programs "think" you have root? You mean you have super user? And what "programs" are you referring to? You can install root manager without a root yes, but in order to put it into "r/w" mode and delete the files from the phone itself, such as bloatware, you need root and Super user access. Most people here I hope are aware that you don't need to root to install "MOST" apps. There "is" apps that require root, and you cannot run them without root access.
Such as:
Titanium backup
Set CPU
Why do I want to root is like everyone keeps saying, to delete all the metro apps, and have "full" manufacturer control over the phone. That's the whole point of rooting. So far no one has rooted this phone PERIOD, or at least shown proof they were even able to. So any info you find regarding rooting please post it here.

Alright, so I tried what Mr. Parker did, and no go. Whether I ran super one click on Win 7 x64 (which was all in admin) or win xp, it would not install super user. In fact I noticed a couple of the files copied from super one click were already on the phone, and weren't able to be overridden. Which may relate to nand lock.

Rooting tablet, system stays write protect even with ro secure=0,?

Hi folks!
Need some advice, before i invent the wheel again for myself.Learning by trying, but where to go or what to check from here...?
Busy with rooting an tablet, yes tried many apps, only kingroot works..What do i see, my system is only write protected and stays that way.
Made boot.img, ro secure=0(was=1),ro debugging=1(was=0),adb service=mtp/adb(was nothing).
Offcourse still no root, adb is now always root, and i can get su also.
So i thought what could be next..I checked for selinux, but cant find anything in the rom, inside when extracted, my last idea....Would be that.
Yesterday i tried Tsparky root script what installs busybox and supersu, same thing happens...No writing allowed, and offcourse no supersu found....While it was installed true the google play way...But adb was running in root..Uhm...????
So tonight i will try my last effort, in placing supersu in the system.img....I only sometimes think to straight, must i remove the other su..?And sometimes they change su in supersu...Got me confused alittle bit, i already read the supersu config file and i will try to place them and give them permissions...
But i have the feeling after reading other forums and peeps with the same issue that maybe....It will still not update the binary..
If my last effort doesn't work, what or where can i go further in rooting the tablet...Because its so difficult i learn a lot...But now...I really dont know what could be next! Read something about maybe there are ''flags'' in the system..How 2 check, can i remove them...
I hope its clear where i am at, and where i wane go, but what bump is still there in the system, some advice please.
Thanks
Erik