Please ignore the original question: I've fixed this already . Plesse see post #2
Hey guys,
Ok I am following all the instructions to the letter and still I am having problems with this.
I am successfully able to run tacoroot to the Android system recovery (3e) and then after resetting it via Vol Up + Vol Down + Power and rebooting when I try to see if tacoroot made a temp root by checking in CMD: ADB Shell for a #
i see a $ instead.
What am I doing wrong???
Bootloader says "Locked"
Android OS : 2.3.4
I appreciate the help from all you great people on here!
PS: One more thing . I don't know if this is relevant or not. After running tacoroot.sh, after Red Exclamation mark pops up and I press Vol UP + Power , there is an error message displayed below
"E:Can't open /cache/recovery/command"
Ok I feel dumb for asking. I was able to get it to work !!!
One other question: Is it possible to have the phone operate ONLY on GSM (I bought this phone from someone else and I do not have verizon) I know it does work on GSM but I want to strip away all CDMA from it permanently until I sell it off to someone else in the future.
Thanks again guys :good:
There's more discussion on this topic in some unlocking threads.
It's possible, but you need the unlock code in order to get on a different network.
-CM7 on DInc2
phonetool said:
There's more discussion on this topic in some unlocking threads.
It's possible, but you need the unlock code in order to get on a different network.
-CM7 on DInc2
Click to expand...
Click to collapse
I'm already unlocked and using GSM but what I don't want to be able to ever do is log into verizon network if it auto switches to CDMA.
I was just wondering if there was a way to get into the hard coded verizon settings and just wipe them out, that way it never auto connects.
Related
I'm starting this to help those who want to root and/or unlock their Samsung Captivate 2.2. I had to search so many forums and didnt find a thread with all the instructions in one place. There maybe other ways to do this, but here's how it worked for me.
=======================================================
DISCLAIMER: I AM NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR PHONE AS A RESULT OF YOU TRYING OUT ANY OR ALL OF THE FOLLOWING PROCEDURES.
=======================================================
First, if you're running Android 2.2, you need to root your phone in order to unlock it. I dont know if reverting back to 2.1 using ODIN, unlocking and then upgrading to 2.2 will keep it unlocked or not. I didnt try.
You need to ensure that the phone is in USB debugging mode and connected to the PC. Drivers may be needed, and this is covered in other posts.
Step 1: Root the phone. The program I used was SuperOneclick, from shortfuse.org. I used the default settings to run the program (i.e. On the Universal tab, select exploit = "psneuter" and click "root".
(choosing the "get unlock code" in this application didnt do the trick for me)
Now your phone is rooted. You will see an app called "Superuser", confirming this. This should NOT be uninstalled. Should you wish to un-root your phone for warranty purposes, SuperOneClick allows for that too... though I havent tried it.
Reboot.
Step 2: I needed to update Busybox, and while there maybe easier ways, here's what I did. On the phone, go to Android Market and download the free version of Titanium Backup. Open this program, and click the "Problems?" button at the bottom center of your screen. Choose update busybox (and you can update superuser if needed, as well).
Reboot.
Step 3: Finally, lets unlock it. Using the update.zip process, or the adb shell commands + a hex editor to read the codes from ~/efs/nv_data.bin did NOT work. The only gimmick that did work for Android 2.2 was a Market application called "Galaxy S Unlock". Its free. When you launch it, there will be a separate popup asking if superuser rights should be granted to this app. Answer yes. You might get several prompts like this. I dont recommend you tell it to remember your answer and automatically grant superuser rights to all such requests in future.
Just follow the steps when you launch it and you should be unlocked. This cool app even allows you to re-lock the phone, should you need to obtain service while under warranty. I havent tried re-locking it though.
From your phone numeric keypad, dial *#7465625#
If you see the following:
Personalization Status
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
You have successfully unlocked your phone. Reboot and try a SIM card from a different carrier. Should boot up seamlessly, without asking for any codes.
Now that the phone is rooted, you might want to remove some of the preinstalled bloatware. FREEZE unwanted apps, do not uninstall. Otherwise, I'm told, you lose your ability to obtain future over-the-air updates.
The program I used for freezing unwanted apps is "AntTek App Manager", available free from Android Market. The free version of Titanium Backup doesnt allow you to freeze apps, only the paid version does. So I uninstalled it after updating Busybox.
When you launch AntTek app manager, there will be several prompts asking if Superuser rights should be granted to the requesting program. Choose the apps you dont want ATT Maps, ATT Navigator ($10/month to use), ATT Music etc are good candidates.
I hope this proves helpful. Feedback welcome.
thanks alot bro i did with this method really appriciate that i tried alot of method didnt work any but with your method i did it thanks
I get a "no code found unknown error" message my phone is a Captivate running 2.2 rooted. Any suggestions?
Did you first upgrade busybox and superuser using titanium backup? This step must be performed after rooting and before unlocking.
Can't think of anything else though.... except repeating the whole process from start to finish.
This worked great! Thanks for the step by step. Did it on my Captivate i896 Rogers.
question
I'm a noob, had my captivate for a few months and I am hesitant to root because I don't want to brick my phone (as cool as a few hundred dollar paperweight sounds it can't be better than a working phone) and i was wondering what the chances of bricking my phone are using this method. i have done a lot of research on rooting and i have found that sites often contradict themselves, and i figured if there was a site i could trust it would be xda, any help would be greatly appreciated, thanks!
I can offer no guarantees, so you assume the risk for whatever you do to your phone. All I can say is that it worked fine for me, and a few others on this forum seem to have had the same experience. Good luck!
will this method work for vibrant also ???
No idea. Only tried it on a Samsung Captivate running Android 2.2.
Thanks
Worked great for me, thanks a lot man!
Tried tto unlock on an Infuse, but step one keeps telling me to fix busybox or unplug my phone. Phone isn't plugged in and I've upgraded and down graded Busybox.
Any suggestions?
I recall some tips on using SuperOneclick, either at shortfuse.org or on XDA, that mention what you need to do with the USB cable if you get an error message when rooting. Hopefully appropriate search terms might point you to the correct resource. Good luck!
worked great for me too...thanks a ton
I have an AT&T Samsung Captivate running 2.2 and im trying to use it with my Verizon Sim card..... i completed the process and my network says unlocked when i type in *#7465625# ...however when i reboot and put the sim card in..i go to "settings">"about phone">"status" and under "phone number" and "network" it says unknown..and i am unable to call or text on the phone because it shows i have no signal...also after rebooting, a message saying "Sim not provisioned MM#2" pops up....please help?
Is there like a setting i need to change or what?? Anybody have a solution?
Does your Verizon Sim card work on another phone? The "SIM not provisioned" error usually appears when the SIM card has not been activated yet, or has been deactivated. Confirm that the Verizon SIM is working first. Also try throwing in a different SIM (borrow one from a friend who has a T-Mobile connection, for instance) and confirm that the unlocking was successful.
Good luck!
Alright, thanks!! I will try that!
Man, This is another thread of people kanging my code and ideas. How about show some respect to the dev that did this unlock? Rather then spit in his face.
Last time i EVER put a unlock on this site.
Kang my code
rhcp0112345 said:
Man, This is another thread of people kanging my code and ideas. How about show some respect to the dev that did this unlock? Rather then spit in his face.
Last time i EVER put a unlock on this site.
Click to expand...
Click to collapse
Man I hate it when people kang my code!!!
I also have a Rogers Captivate unlocked and I am using it on the Telus network. I have found that I can not use the mobile ap (wifi hotspot) because Rogers has blocked it. Does anyone know which apk file this is or in and how to remove it so I can use my phone as a wifi hotspot?
Thanks in advance.
Hi folks,
I don 't know if this is in the right section so sorry if it isn't.
I have a serious problem in which I hope someone can help me with as this is causing my stress levels to boil.
Problem... My xoom's bootloader is unlocked using fastboot oem unlock. However I want to return it to stock android and have therefore got the files from motorola developers for the wi-fi only xoom. when flashing these using fastboot all goes fine.
When using fast book oem lock the device has a lnx error can't remember the exact number was 004 I think. how do I relock this device.
Also using the img from motorola I cannot perform OTA updates as the device has the android bot with an exclamation mark in the middle and restarts with error during system update.
please help as I am still stuck on buggy android 3.0
Much appreciated!
Please can anybody help me here.
Phoned up Motorola UK and they don't know nothing. They just want to charge me loads of money to send it in for technicians to look at.
Regards.
1. Take a look here: http://goo.gl/A0klY
2. Take a look at "1"!!!!!
3. You took a look at "1" and "2" now take a look here: http://goo.gl/lACvI
4. You´re welcome!
Is there a way to unlock or root from 4.0.4 without a working power button?
Long story short:
My power button is broken and I have a crack in my screen so Samsung will not honor my warranty (even though the two have nothing to do with each other).
I had my Nexus unlocked and rooted but brought it back to stock and relocked so i could bring it back to Verizon where I found out that the crack would void the warranty anyway.
I've been looking for 3 days and haven't found anything (though did find a couple tips on how to reboot the phone if it isn't recognized by adb). I have also looked to unroot without unlocking but am at 4.0.4 and have only seen that possible on 4.0.2.
Any help is appreciated.
Thanks
open up the phone and manually power the phone on?
I'm not sure what you are saying. I can power up the phone but once powered on I cannot wake it without a working power button. It only wakes if I plug it in or receive a phone call.
Unfortunately if your power button doesn't work and you don't have root, you cannot unlock. And you can't root 4.0.4 without unlocking
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the reply,
Just the answer I didn't want to hear.
Am I SOL or is this something you think the geniuses on these boards will figure out in the upcoming days/weeks? From what I've read it looks like they "fixed" whatever allowed you to gain root in 4.0.2 so I'm probably screwed.
If I cannot unlock or unroot, is there a way for me to make the volume buttons wake the phone?
Or is it possible to revert back to 4.0.2?
cohrs said:
Thanks for the reply,
Just the answer I didn't want to hear.
Am I SOL or is this something you think the geniuses on these boards will figure out in the upcoming days/weeks? From what I've read it looks like they "fixed" whatever allowed you to gain root in 4.0.2 so I'm probably screwed.
If I cannot unlock or unroot, is there a way for me to make the volume buttons wake the phone?
Or is it possible to revert back to 4.0.2?
Click to expand...
Click to collapse
there is a free APP in the google play called "Fix Broken Power Button" that allows you to wake your phone with your volume keys. I use this app in my N1 that have the same issue with the power button to wake the phone in android 2.3.6.
it works fine but you have to reconfigure it each time you reboot your phone in order to work
BTW some one mentioned in this thread that found a way to make the phone to boot even if the ADB didn't recognized it. I like to know how to do this.
finally i have the same issue. My N1 is on 2.3.6 no root and the bootloader locked and I searched with no luck on how to unlock the boot loader or root it.
The PASSING method not worked for me because the bootloader say that the main version of the update is older and do no let me downgrade to froyo
alternatively I used the windows tool to root gingerbread the .bat script that runs some exploit in the android but didnt worked for me. so I think im scrued but if some one knows something i like to know
that's all jejeje and forgive me for my bad English
my goal is to install Cyanogen Mod 7 in order to use the trackball of the nexus one to wake the phone ans to use an app that requires root access to reboot the phone without the power button
I just come back to update the previous post.
I manage to get my nexus one unlocked and rooted.
even if you have 2.3.6 stock, and a broken power button it is possible to make this
After searched the net for day i found that if you install the blackrose bootloader it will unlock the phone. then with blackrose you will no receive the "main version is old" message that you get when you try to downgrade to froyo using the PASSING method. so if you successfully downgrade to froyo, it is very easy to root with the super one click application witch for me din't make it on 2.3.6.
once you root your phone you can either go back to 2.3.6 via OTA or PASSING method or install a ROM like CM7 and take full control of your phone with no power button
and that's it. hope someone use this information
bongo_24 said:
there is a free APP in the google play called "Fix Broken Power Button" that allows you to wake your phone with your volume keys. I use this app in my N1 that have the same issue with the power button to wake the phone in android 2.3.6.
it works fine but you have to reconfigure it each time you reboot your phone in order to work
BTW some one mentioned in this thread that found a way to make the phone to boot even if the ADB didn't recognized it. I like to know how to do this.
finally i have the same issue. My N1 is on 2.3.6 no root and the bootloader locked and I searched with no luck on how to unlock the boot loader or root it.
The PASSING method not worked for me because the bootloader say that the main version of the update is older and do no let me downgrade to froyo
alternatively I used the windows tool to root gingerbread the .bat script that runs some exploit in the android but didnt worked for me. so I think im scrued but if some one knows something i like to know
that's all jejeje and forgive me for my bad English
my goal is to install Cyanogen Mod 7 in order to use the trackball of the nexus one to wake the phone ans to use an app that requires root access to reboot the phone without the power button
Click to expand...
Click to collapse
You should probably take your issues over to the N1 forum instead of the GN forums here...this is all completely irrelevant information except for the broken power button app, assuming it works on ICS.
You actually don't need fastboot or volume buttons to unlock the bootloader this way: http://forum.xda-developers.com/showthread.php?p=41612401#post41612401. HTH!
Hello everyone!
Im a bit of a newbie when it comes to unlocking phones and flashing roms and such, but i did buy an s3 off of a friend of mine, its on 4.1.1 and i have to unlock it. i found this method http://forum.xda-developers.com/showthread.php?t=2176721 and i was wondering if it was still applicable? if it is that would be awesome! if it is not, could some please point me in the right direction for do- it- yourself unlocking?
By the way, the phone is locked to rogers
Thanks everyone!
I am on Rogers and that is the method I used.
I can not remember if I had to go back to 4.0.4 or if I did it on 4.1.1 but you must be on TouchWiz and not a custom aosp/cm/aokp Rom.
Give it a shot on 4.1.1 and if it doesn't have the menus Odin back to 4.0.4.
Odin firmware links http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my SGH-I747
Punstoppable said:
Hello everyone!
Im a bit of a newbie when it comes to unlocking phones and flashing roms and such, but i did buy an s3 off of a friend of mine, its on 4.1.1 and i have to unlock it. i found this method http://forum.xda-developers.com/showthread.php?t=2176721 and i was wondering if it was still applicable? if it is that would be awesome! if it is not, could some please point me in the right direction for do- it- yourself unlocking?
By the way, the phone is locked to rogers
Thanks everyone!
Click to expand...
Click to collapse
Yes it does work and yes you do need to be on 4.1.1, the most important thing is when the instructions say wait certain time, you wait and watch for the proper code, if you don't get that code, your not unlocked.... try over...... oh and don't touch anything else though you might be tempted too......
Just noticed that post doesn't mention the code...
MENU NOT EXIST
PRESS BACK KEY
Current Command is 118640
I suggest you use the link for redflagdeals on the link you posted
http://forums.redflagdeals.com/free...2-all-gsm-carriers-galaxy-rugby-bell-1266487/
Gage_Hero said:
Yes it does work and yes you do need to be on 4.1.1, the most important thing is when the instructions say wait certain time, you wait and watch for the proper code, if you don't get that code, your not unlocked.... try over...... oh and don't touch anything else though you might be tempted too......
Just noticed that post doesn't mention the code...
MENU NOT EXIST
PRESS BACK KEY
Current Command is 118640
I suggest you use the link for redflagdeals on the link you posted
Click to expand...
Click to collapse
awesome thanks! and when the first step is like dial the number, where do you do that? like in the phone dialer thingy? sorry for the nooby questions haha. also the menus button..... is it the big button in the middle? and lastly, if i were to screw it up somehow, how would i start over? will i do any lasting damage to the phone if i mess up?
sorry had to edit out your link, wouldnt let me post it haha
Thanks again
Punstoppable said:
awesome thanks! and when the first step is like dial the number, where do you do that? like in the phone dialer thingy? sorry for the nooby questions haha. also the menus button..... is it the big button in the middle? and lastly, if i were to screw it up somehow, how would i start over? will i do any lasting damage to the phone if i mess up?
sorry had to edit out your link, wouldnt let me post it haha
Thanks again
Click to expand...
Click to collapse
The number is entered through the dialer and the menu button is to the left of the home button (the big one in the center) To my knowledge you cannot break your phone you may want to write down you apn data before you start just incase although there are postings for all carriers....system settings>> more settings>> mobile networks>>access name points tap the one with the green dot and write down what you see there.... then go for it...
You need to watch the codes though if it ends with a 30 (if you do this twice or wrong) then you will have to do it again... this I have done myself lol
Gage_Hero said:
The number is entered through the dialer and the menu button is to the left of the home button (the big one in the center) To my knowledge you cannot break your phone you may want to write down you apn data before you start just incase although there are postings for all carriers....system settings>> more settings>> mobile networks>>access name points tap the one with the green dot and write down what you see there.... then go for it...
You need to watch the codes though if it ends with a 30 (if you do this twice or wrong) then you will have to do it again... this I have done myself lol
Click to expand...
Click to collapse
awesome thanks a lot! ill hopefully be getting the phone tomorrow, ill give you an update when i try to unlock it
Thanks!
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have had consistent issues flashing this s3 sprint to boost mobile.
My main two questions are where is the general knowledge you guys have about qpst , qpxt, dfs and cdma workshop coming from ?
I mean there are 10 + guides on the sprint s3 to boost BUT all the guides to not explain a thing. Neither do any other guides for other flashes. The are only explicit directions. Which I have followed and consistently get errors no matter the variable that I change ( different roms mainly ).
I have searched the internet from morning to night trying to find answers and it seems this giant ball of knowledge about these programs is either hidden or not there for some odd reason.
Either way I can post up screen shots of the errors if that would help.
Or does someone know 100 % of a current working guide?
Any help will be much appreciated as I agreed to flash a phone after only rooting 4-5 phones and being very knowledgable of that area assuming from all the threads on how to flash phones interpreting them as a "doable" task but this is some deep stuff.
I retract my statement about being able to post screen shots as I do not have the required 10 posts yet. I am not that knowledgeable about quite a few things on this site so looking to learn a lot.
I am assuming I can still send a link to the screenshot via PM for anyone feeling crazy enough to help. :good:
99428813
And now after trying flash a few different roms I am getting a new error in dfs - get sec code cds error. That is after sending what has previously worked as the spc. Does the spc change ? I would presume it doesn't.
This should steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2581259
SPrposi Rebecca
retailguy said:
This should steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2581259
Click to expand...
Click to collapse
Thank you for the post! I did try that one. My phone at this moment will not let me get passed the put your password/spc in portion of the guide.
I actually purchased the Galaxttoboost.com guide and it worked well on the incognito side but the galaxy side it failed.
Thinkskater said:
Thank you for the post! I did try that one. My phone at this moment will not let me get passed the put your password/spc in portion of the guide.
I actually purchased the Galaxttoboost.com guide and it worked well on the incognito side but the galaxy side it failed.
Click to expand...
Click to collapse
You have to downgrade your rom for the old password to work. I forget how far you have to downgrade, maybe 4.1.1? I don't remember but that is what you have to do. I am also not sure if there are any implications if you have knox in your bootloader. There might be, read up on that.
retailguy said:
You have to downgrade your rom for the old password to work. I forget how far you have to downgrade, maybe 4.1.1? I don't remember but that is what you have to do. I am also not sure if there are any implications if you have knox in your bootloader. There might be, read up on that.
Click to expand...
Click to collapse
LIF_update_FULL_Odex (4.1.1).zip (
Per the galaxytoboost.com guide this is the needed rom to access msl info and is whats currently downloaded. They did specify another rom to use with QXDM that I just noticed. Is that normal?
And I just found out that under baseband version ( where the label for what bootloader I have ) it says unknown.....
Thinkskater said:
LIF_update_FULL_Odex (4.1.1).zip (
Per the galaxytoboost.com guide this is the needed rom to access msl info and is whats currently downloaded. They did specify another rom to use with QXDM that I just noticed. Is that normal?
And I just found out that under baseband version ( where the label for what bootloader I have ) it says unknown.....
Click to expand...
Click to collapse
The new rom yielded the same results. No msl via the get my msl app or no response via getprop ril.MSL in terminal. Same response in QXDM as well. When I put in password and the correct 01f..... password for the 4.1.1 it displays the error - RequestItem - Error response received from target.
What would make my phone completely unresponsive to these programs????