Ooh kaay, can Anyone solve this one?
A couple month ago, I had to get a refurb of my phone, and I went to root it and it's been as painful as rubber band to the butthole!
I've used both Wug's and Gnex's toolkit. Hard reset it, used, and watched ALL of QBking77's gods, used every way possible to get this dang thing rooted. I'm no noob, but, I'm also no expert. Below is the stats of my phone, PM me if there's any other info you need and I'll try and provide it for you.
Thanx guys, I appreciate all any and all help I can get
Ridge
I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
You should've made this thread in the Q&A section
Sent from my Galaxy Nexus using xda premium
I have, and got zero responses.
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
TheRidge69 said:
I have, and got zero responses.
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
Click to expand...
Click to collapse
You have mismatched radio. Flash full ga02 radio.
Sent from my Galaxy Nexus using xda app-developers app
Thank you. That's was what I was thinking, but I wanted to be sure & hear it from someone else! I'll try that one the morning, after I find the right tar for it. Couldn't even get twrp or any custom recovery on it. Again thanks
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
They did the same thing when I got a refurb. Mismatched radio. First thing I noticed.
Sent from my Galaxy Nexus using xda app-developers app
But radios are independent of os. Root comes from the system.
I agree you'd be better off with matching radios, but I read your post as having problems getting root access, correct?
Have you downloaded proper drivers to a computer?(using PC or Mac or Linux?)
Do you have adb set up?
If ya do, have you tried to boot into fast boot and flash a custom recovery?(I've always used most current twrp recovery without issue)
Sounds like your asking for help to gain root access, get a custom recovery installed, then want to flash a custom ROM?
I hear ya, not a noob right? Help us help you, give us more info on what you've tried and why you think it has been unsuccessful
Sent from my Galaxy Nexus using xda premium
ElfinJNoty said:
But radios are independent of os. Root comes from the system.
I agree you'd be better off with matching radios, but I read your post as having problems getting root access, correct?
Have you downloaded proper drivers to a computer?(using PC or Mac or Linux?)
Do you have adb set up?
If ya do, have you tried to boot into fast boot and flash a custom recovery?(I've always used most current twrp recovery without issue)
Sounds like your asking for help to gain root access, get a custom recovery installed, then want to flash a custom ROM?
I hear ya, not a noob right? Help us help you, give us more info on what you've tried and why you think it has been unsuccessful
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks. I take it you're being sarcastic with the noob comment, but yes I've used the proper adb & drivers I've it unlocked and can can get into fastboot, then that's where my problems start. Nothing happens. I've tried dl'ing it to the my pc and transfer it to my phone. I've also tried dl it to my phone, however, I just can't get access.
I don't know if I want to put a new ROM, I DO know, I want more control over my phone again at the very least.
I've been rooting and ROMING all my phones since I had an LG Rumor. This is why I'm so flustered. It has been about a year or so since I've had to mess with my Gnex. Because it's run like a Champ until my cat thought it was a play toy and swatted it off my kitchen table, & i needed a new one and ended up with crap refurb.
Anything else you wanna know, shoot me a message or reply to my "noobian"rant.
Thanx,
Ridge
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
Have you tried using an older tar like 4.1 and rooting from there that usually works then if it works you'll be able to flash radios after getting root and upgrading to 4.2 later
Sent from my Galaxy Nexus using xda premium
thegod2012 said:
Have you tried using an older tar like 4.1 and rooting from there that usually works then if it works you'll be able to flash radios after getting root and upgrading to 4.2 later
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanx TG. I have gone back and then when I had updated it, no matter what I do, I just can't seem to get back. I used to have all the files and good stuff on my last pc before it ate it's HD & I lost everything. Ended up starting from zero. Did all the proper downloads over again, blah, blah. This was before I began to decide to get root access. My pc ended up being yucky windows 8. Would that make a difference? Never dealt with the Damn os before. Could I be missing something there beside a brain? Here's a pic of my cat log if that would help. I really feel like an ass. I haven't done any of the suggestions yet to it. Because I just don't know where I should start.
Thanx guys,
Ridge
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
Try this
Download a 4.1 Odin via Google search
Run Odin
Root phone via Gnex tool kit
Then flash anything your heart desires
Windows 8 doesn't make a difference as long as you have the necessary drivers and files
Sent from my Galaxy Nexus using xda premium
Thanks TG, I will try that. It's 3:20am so I will try that again. I've used the toolkit and the Wugfresh kit as well. I think if I follow that course, I just might get this thing rooted, with a custom recovery as well.
I'll let you know what happens OK? Chat w/U in the morning.
Sent from a dusty, deserted hwy somewhere in Nv. in a '71 Dodge Dart.
While we wait for a Mod or Admin to move this, I just wanted to clarify, if nobody answers your question in the Q&A section, it doesn't give you a reason to break the rules and post in the Development section, here's my advice, if no one answers in the Galaxy Nexus Q&A, go to the Android Q&A, the forums have more people, and you won't break any rules.
Sent from my Galaxy Nexus using Tapatalk 2
I am not sure if I'm being ignorant or didnt go through all ur posts, but as u said, you have the bootloader unlocked, get ur cell in fast boot download the latest recovery.img put it in the same folder as adb then open the cmd navigate to where ur adb is located and issue the command; "fastboot flash recovery recovery.img" once the installation is completed boot into recovery to flash just the superSU or ROM of ur choice..
Make sure you execute the cmd as Administrator...
Sent from my Galaxy Nexus using xda app-developers app
Related
I'm inching closer and closer to rooting my Wildfire S, daunting as it seems. I'm not that fussed about custom ROMs (yet) but more in removing the useless crap that's currently filling up my internal memory... However, one thing I haven't found on the internet is what I'll actually end up with when it finally gets rooted.
I understand that it's not gonna change everything and make it all shiny, but does it unlock additional options/tickboxes/menus? Does it have a different UI to the regular "explorer"? Or does it mean I need to learn command line (<-- dealbreaker btw) ... In what format do these additional superpowers come?
TIA
Oh, and while I'm at it: When it comes to uninstalling useless crApps (such as Orange TV), is it just going to add the Apps to the list of applications in Settings>Applications>Manage Applications? Or is it completely different?
Sorry for the noob questions, but I'm the only person I know with a smartphone who wants to root it... and this whole learning process is making me feel a bit like amoron
A rooted phone is a lot like a unicorn galloping over a colorful rainbow.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Smashysmash said:
I'm inching closer and closer to rooting my Wildfire S, daunting as it seems. I'm not that fussed about custom ROMs (yet) but more in removing the useless crap that's currently filling up my internal memory... However, one thing I haven't found on the internet is what I'll actually end up with when it finally gets rooted.
I understand that it's not gonna change everything and make it all shiny, but does it unlock additional options/tickboxes/menus? Does it have a different UI to the regular "explorer"? Or does it mean I need to learn command line (<-- dealbreaker btw) ... In what format do these additional superpowers come?
TIA
Click to expand...
Click to collapse
Rooted phones grow two little green legs, two little green arms and two little green antennae and start walking around the palm of your hand. Custom ROMs can make them dance every time you touch the screen.
Smartarses! I thought this was supposed to be a noob-friendly advice forum ;P
SENT FROM MY FRICKING COMPUTER BECAUSE I'M A PROUD NOOB!!
/\ those two seem very inclined to help. I kind of was in the same boat as you until I did alot (hours) of reading of articles and forums. I only just rooted this week. rooting changes almost nothing about the phone itself, atleast to the eye. its akin to having administrator privileges on a computer. it will install an app called superuser which is how you will grant rooted apps permission to access system files and such that would normally be off limits, because of carrier or manufactuer limitations. Rooting is really just the first step that allows you to begin truly customizing your phone. cosmetically nothing will change. I highly recommend, after you root, but before you strat fooling with anything, to download titanium backup which will allow you to back up your entire collection of apps and their data. then you are going to want to get clockworkmod recovery, which replaces the stock recovery, and will allow you to make a system backup,(boot image) and also is a very useful tool for effortlessly installing custom ROM's and other system tasks.
Sent from my SPH-D710 using XDA App
Hi,
I rooted my wildfire s a few weeks ago. Im assuming you have already unlocked the bootloader. Next thing i did was to flash clockworkmod before rooting and make a nandroid backup.
Next i rooted via cwm using a root.zip file.
Once rooted via the root.zip you will have a superuser app installed. Now download titanium backup and install. When you run this it requests superuser permissions via superuser app and you allow it by "choosing "yes".
Titanium backup allows you to then choose apps to uninstall but note that it often cant restore system apps so if you mess up the phone boot into recovry/cwm and restore from cwm backup you made earlier.
Your phone wont have extra options etc but you can install apps that need root/superuser access via superuser app.
You do gain access to the root id via command line but unless you are familiar with linux in general you may want to stay away from it.
If you want some detailed instructions in cwm flashing and rooting then let me know and i will tell you exactly how i did it.
Scott
Sent from my HTC Wildfire S A510e using XDA App
scott_doyland said:
Hi,
I rooted my wildfire s a few weeks ago. Im assuming you have already unlocked the bootloader. Next thing i did was to flash clockworkmod before rooting and make a nandroid backup.
Next i rooted via cwm using a root.zip file.
Once rooted via the root.zip you will have a superuser app installed. Now download titanium backup and install. When you run this it requests superuser permissions via superuser app and you allow it by "choosing "yes".
Titanium backup allows you to then choose apps to uninstall but note that it often cant restore system apps so if you mess up the phone boot into recovry/cwm and restore from cwm backup you made earlier.
Your phone wont have extra options etc but you can install apps that need root/superuser access via superuser app.
You do gain access to the root id via command line but unless you are familiar with linux in general you may want to stay away from it.
If you want some detailed instructions in cwm flashing and rooting then let me know and i will tell you exactly how i did it.
Scott
Sent from my HTC Wildfire S A510e using XDA App
Click to expand...
Click to collapse
+1 well said
it looks exactly like one of those...http://www.letsgodigital.org/images/artikelen/681/htc-wildfire-s-smartphone.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sorry couldnt resist... if you need any help i give you a guide just pm meh
Sent from my HTC Wildfire using xda premium
Think of it like.a computer your normal phone us like being on the guest profile which its limited in what it can do while rooting your phone is like running it as administrator and being able to do everything even tho both would look the same
Sent from my HTC_A510c using Tapatalk
Thanks guys that was really useful! I didn't know superuser was an actual app, and yeah I was worried about command line so that's reassuring...
Scott, I haven't actualy unlocked the bootloader yet, I'm waiting til I completely understand the process before I actually do anything to avoid screw-ups.
TBH, I was going to use Unlock Root... is there anything to be gained/lost by opting for the 1-click solution?
As for the offers of assistance, I may hold you to that in the near future! thanks a lot!
Smashysmash said:
Thanks guys that was really useful! I didn't know superuser was an actual app, and yeah I was worried about command line so that's reassuring...
Scott, I haven't actualy unlocked the bootloader yet, I'm waiting til I completely understand the process before I actually do anything to avoid screw-ups.
TBH, I was going to use Unlock Root... is there anything to be gained/lost by opting for the 1-click solution?
As for the offers of assistance, I may hold you to that in the near future! thanks a lot!
Click to expand...
Click to collapse
Nothing is different but when you are done just download a root checker app to make sure its done right
Sent from my HTC_A510c using Tapatalk
Smashysmash said:
Thanks guys that was really useful! I didn't know superuser was an actual app, and yeah I was worried about command line so that's reassuring...
Scott, I haven't actualy unlocked the bootloader yet, I'm waiting til I completely understand the process before I actually do anything to avoid screw-ups.
TBH, I was going to use Unlock Root... is there anything to be gained/lost by opting for the 1-click solution?
As for the offers of assistance, I may hold you to that in the near future! thanks a lot!
Click to expand...
Click to collapse
after taht you will want a custom recovery, and in my signature there is link to 'Taking Screenshots on your device' there you have some screens of custom recovery, and in the end of post you can find explanation of each image... made just for guys like you ...
Superuser - yes its an app but i would guess that under the covers its doing an 'su' command somehow to switch to the root id, or irs just alliwing other apps to use 'su'.
I unlocked via htcdev as i thought there was a better chance of it working as it was the official method and im sure the wildfire s is hard to unlock via unofficial methods
Scott
Sent from my HTC Wildfire S A510e using XDA App
b02 said:
after taht you will want a custom recovery, and in my signature there is link to 'Taking Screenshots on your device' there you have some screens of custom recovery, and in the end of post you can find explanation of each image... made just for guys like you ...
Click to expand...
Click to collapse
Awww aren't you sweet
Hello every one.
Could someone help me please, since i am on 4.0.4, I have a bad reception (sorry i'm french). I have to go outside of my house to call and receive calls. It's a little bit laggy too. I didn't root or change anything.
I'm noob with nexus, i used to have a desire hd, galaxy s2 and a xperia play, and installing custom roms was easy. With nexus, i don't know what to change to have a good reception and a smooth system (kernel, radio etc)
Actually, i'd like to know if there's a rom who could make my phone smoother and stable. No overclock or things like that, just a stable system and a phone who would have a good network reception (i don't know the words for that, i mean that i'd like to call from my house not outside ^^)
I know my question is noobish, i'm sorry for that, but could someone help me?
Bye everyone and thanks in advance!
Yann
Go to general section and download the toolkit for Nexus everything you need its there.. Theres also a baseband (radio) section where you can download all kind of radio files CWM flasheables and fastboot flasheables, but be carefull if your english its limited... Dont do something you dont understand or you could brick your phone
First create a backup of your phone cuz unlocking the bootloader will wipe the phone then root it and install CWM, and then you are able to flash any kind of radios you like until you find whats Best for you and theres some tips to follow everytime you flash a new radio like wiping the cache and stuff.. You should read some before trying
Sent from my Galaxy Nexus using xda premium
@msedek, you should be doing a little more reading/testing yourself.
first, unlock bootloader (you'll need fastboot for this).you don't have to root to install cwm, neither to install kernels, basebands or bootloaders. you can do it the google way, which is using fastboot. don't go telling people that root/cwm is needed to do these things.
@op, do some reading. use a translator if you need to. read roms/kernels/bb/bootloaders threads's first posts fully at least twice, particularly the install instructions. at this stage, there's pretty much all the info you need.
and just so we're clear, it's pretty hard to brick a nexus. just be extra cautious when flashing bootloaders.
Sent from my TF201
thank you guys
bk201doesntexist said:
@msedek, you should be doing a little more reading/testing yourself.
first, unlock bootloader (you'll need fastboot for this).you don't have to root to install cwm, neither to install kernels, basebands or bootloaders. you can do it the google way, which is using fastboot. don't go telling people that root/cwm is needed to do these things.
@op, do some reading. use a translator if you need to. read roms/kernels/bb/bootloaders threads's first posts fully at least twice, particularly the install instructions. at this stage, there's pretty much all the info you need.
and just so we're clear, it's pretty hard to brick a nexus. just be extra cautious when flashing bootloaders.
Sent from my TF201
Click to expand...
Click to collapse
Well its easiest and safest way for a starter i managed to do all kind of stuff by myself just with the toolkit, im also a starter and you dont need to come here and pretend to be the gnexus allmighty saying bull**** and not giving other option than go read xxxxxx bull****... Stop being a troll...
Sent from my Galaxy Nexus using xda premium
msedek said:
Well its easiest and safest way for a starter i managed to do all kind of stuff by myself just with the toolkit, im also a starter and you dont need to come here and pretend to be the gnexus allmighty saying bull**** and not giving other option than go read xxxxxx bull****... Stop being a troll...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
bs? a troll?.... i was correcting/adding to what you said.. using a toolkit is not the safest way. the safest way is to learn what that script does or doesn't, or by using the tools themselves.
and as to searching, it's one of the rules of xda. actually, it's the number ONE rule.
gnexus almighty? LOL you amuse me
Just got a replacement DInc2 for a charging port loose warranty replacement (again).
The phone has software verison 6.01.605.05 710RD
and baseband version 20.32W.30.0813U_1.09.01.0312.
zergRush fails on this latest software version...
FOR ANYONE THAT GETS THIS PHONE WITH THE ABOVE MENTIONED SOFTWARE BUILD:
When attempting the downgrade method in order to S-OFF, a lot of people (myself included) have run into boot loop issues. On initial boot up, everything works normal, but as soon as you power cycle the phone, your phone will go into an endless reboot cycle where the phone boots up all the way to the lock screen, but then after being on the lock screen for ~2-3 seconds, the phone will reboot and will continue to do so. The only way I was able to break the reboot cycle was to do a factory reset in recovery, but again, the phone will stay on during that initial boot up, but will resume the reboot cycle after any sort of power cycling.
In all my efforts of returning to stock after any sort of tinkering (including flashing the full 5.xx RUU and restoring the stock hboot 0.98), I was UNABLE to get my phone functioning normally. Even full stock, I had the reboot issue mentioned above. I had to get another replacement from Verizon and haven't attempted the downgrade yet.
Work arounds to date:
1. Don't reboot EVER after you initially boot up after a data wipe!
2. If you need to reboot, it seems like enabling airplane mode prior to power cycling prevents the reboot cycle. Even if WiFi is on with a power cycle, there isn't any issues, it's only when the cell radio is on during power cycle that triggers this.
3. Run an AOSP ROM like CM7/CM9/AOKP. This issue seems to be isolated to only Sense ROMS (this could be do to all the Sense ROMS available today being based on the 5.xx RUU and when flashing the downgrade RUU, something isn't getting downgraded properly..?)
If anyone else has any other work arounds, let me know and I'll add it to this list.
I'll say it again, the only way I was able to break the reboot cycle was to do a factory reset in recovery.
With pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interesting. I've actually had the RUU for this build for a while, but since it only adds emergency alerts as far as I could tell, I didn't release it. Not sure it's worth doing now, since it's such a minor revision.
Archon810 said:
Interesting. I've actually had the RUU for this build for a while, but since it only adds emergency alerts as far as I could tell, I didn't release it. Not sure it's worth doing now, since it's such a minor revision.
Click to expand...
Click to collapse
Unfortunately it was enough of a revision that zergRush is failing to gain temp root access!
I just finished getting S-Off and Root on my new CLNR today.
mastamoon said:
I just finished getting S-Off and Root on my new CLNR today.
Click to expand...
Click to collapse
Did you start with HTC Bootloader Unlock?
mastamoon said:
I just finished getting S-Off and Root on my new CLNR today.
Click to expand...
Click to collapse
Please do tell how you achieved this.
XTC Clip. Bought one almost a year ago and never got to use it. Till today!
Does anyone have an RUU of this?
Archon810 said:
Interesting. I've actually had the RUU for this build for a while, but since it only adds emergency alerts as far as I could tell, I didn't release it. Not sure it's worth doing now, since it's such a minor revision.
Click to expand...
Click to collapse
If you could release it asap, that would rock. In attempting to root, I've fried my radio and need to reflash the latest rev. The current releases that are out won't flash.
Sent from my ADR6350 using XDA
randomdeanna said:
If you could release it asap, that would rock. In attempting to root, I've fried my radio and need to reflash the latest rev. The current releases that are out won't flash.
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
Taco root should still work for the unlock part. Otherwise, htcdev unlock flash something that is rooted, relock and revolutionary.io as usual.
Sent from my Incredible 2 using XDA
aeroevan said:
Taco root should still work for the unlock part. Otherwise, htcdev unlock flash something that is rooted, relock and revolutionary.io as usual.
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
Cool I'll try TacoRoot to see if I can get temp root on this build to do the downgrade. For anyone looking for the link: http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/
Sent from my ADR6425LVW using Tapatalk 2
aeroevan said:
Taco root should still work for the unlock part. Otherwise, htcdev unlock flash something that is rooted, relock and revolutionary.io as usual.
Click to expand...
Click to collapse
I'm (shockingly, ha) having an issue with tacoroot putting me in endless boot cycling when I get to the root step. See my post in this thread on rootzwiki.
I can't seem to find clear how-tos on htcdev/flashing. When I've tried to flash a stock upgrade (see this thread), I get a failure because the RUUs posted are older than this new one. I suspect this will be true of something rooted, no? If not, if I'm wrong there, can I just make an image of my current happily rooted dinc2 (I haven't sent it back yet) on 2.3.3 and flash that? (and if so, links to how-tos for that would be great. Good lord, I'm demanding!)
randomdeanna said:
I'm (shockingly, ha) having an issue with tacoroot putting me in endless boot cycling when I get to the root step. See my post in this thread on rootzwiki.
I can't seem to find clear how-tos on htcdev/flashing. When I've tried to flash a stock upgrade (see this thread), I get a failure because the RUUs posted are older than this new one. I suspect this will be true of something rooted, no? If not, if I'm wrong there, can I just make an image of my current happily rooted dinc2 (I haven't sent it back yet) on 2.3.3 and flash that? (and if so, links to how-tos for that would be great. Good lord, I'm demanding!)
Click to expand...
Click to collapse
You can make a nandroid backup in recovery on your old phone and restore it on your new phone. The only catch is if you use HTC Boot loader unlock and load a custom recovery that way, the restore will not restore the kernel. You will have to find the boot.img for the ROM you are running and use fast boot to install it (flashboot flash boot boot.img)
Sent from my ADR6425LVW using Tapatalk 2
For some step by step advice: see my post here
Just so everyone is aware, if you do get a replacement DInc2 from Verizon, it will come with newer than OTA software, and when attempting the downgrade process using TacoRoot, you run into bootloop issues that I think are not correctable without the RUU of the shipped software.
Myself and one other person both ran into the same bootloop issue after the downgrade, which persisted even when restoring everything to stock using the 5.10.605.9 RUU. See more about this issue here I have heard of at least one person having no issues after the downgrade though, so I don't know how many had issues and how many had no issues...
I ended up getting another replacement from Verizon, and until an RUU exists, probably won't attempt to root, just FYI for anyone considering getting a replacement from Verizon.
This is horrible news. I just got an Incredible 2 yesterday (gf's had charger problem, I bought her a Rezound and took her warranty swap to replace my Droid X).
I'm sure persistence will pay off though.
Bad news indeed. I just got a replacement as well with the same softare version. Sounds like the XTC clip is the only way to root it at this stage. Ugh.
cheesiepoof said:
Bad news indeed. I just got a replacement as well with the same softare version. Sounds like the XTC clip is the only way to root it at this stage. Ugh.
Click to expand...
Click to collapse
Tacoroot seems to be working for some people. Just follow the updated instructions that a few people who have done the new downgrade process have posted.
Sent from my Incredible 2 using XDA
aeroevan said:
Tacoroot seems to be working for some people. Just follow the updated instructions that a few people who have done the new downgrade process have posted.
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
Yeah I wonder what the difference is...its driving me crazy. PalmerCurling had zero issues with the downgrade. Even more alarming though, at least in my and random's case, that even going back to full stock 5.xx RUU, the reboot issue is still there, so right now for us there is no clear path back to bone full functioning stock...
Can some experts throw out a comprehensive list of the consequences/side effects to rooting in general, but especially the S III? I've seen a post or two about precautions to take with Google Wallet and such. Include everything please (comprehensive) from not being able to download OTAs (or it not being preferable to do so due to potentially losing root), the need to wait for/find someone to take the OTA and make it rooted and available for us to install, etc.
Thanks in advance!
Edit: If this should be in General, I apologize - mod please move.
s1dest3pnate said:
Can some experts throw out a comprehensive list of the consequences/side effects to rooting in general, but especially the S III? I've seen a post or two about precautions to take with Google Wallet and such. Include everything please (comprehensive) from not being able to download OTAs (or it not being preferable to do so due to potentially losing root), the need to wait for/find someone to take the OTA and make it rooted and available for us to install, etc.
Thanks in advance!
Edit: If this should be in General, I apologize - mod please move.
Click to expand...
Click to collapse
It probably ought to be in Q and A, but only after you have searched Q and A, as this question generally speaking, has been asked quite a few times.. Please, use search...save a life
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
s1dest3pnate said:
Can some experts throw out a comprehensive list of the consequences/side effects to rooting in general, but especially the S III? I've seen a post or two about precautions to take with Google Wallet and such. Include everything please (comprehensive) from not being able to download OTAs (or it not being preferable to do so due to potentially losing root), the need to wait for/find someone to take the OTA and make it rooted and available for us to install, etc.
Thanks in advance!
Edit: If this should be in General, I apologize - mod please move.
Click to expand...
Click to collapse
Do your research.......
the main side effect is getting a hard brick by flashing something you shouldnt have flashed (rom for another phone) other than that, you can recover from anything and flash back to out the box stock if need be.
Read forum rules before posting
Development is for developers to make threads
Moved to Q&A
FNM
Sent from my SPH-L710 using xda premium
The biggest drawback is it gives folks the ULTIMATE ability to do anything they want to their phone. Why is this a drawback????
Sadly, way too many folks just "do" things on blind trust of random folks they don't know on the internet without knowing what they are doing and the consequences of their actions.
Compusmurf said:
The biggest drawback is it gives folks the ULTIMATE ability to do anything they want to their phone. Why is this a drawback????
Sadly, way too many folks just "do" things on blind trust of random folks they don't know on the internet without knowing what they are doing and the consequences of their actions.
Click to expand...
Click to collapse
This is true... but those of us that are not programmers and not as farmiliar with modding these roms are at the mercy of the devs. I am not a noob but am trying to adjust to the s3, came from the OG EVO. Basically what I do is do some google research, search threads on here. eventually you find devs who you prefer and trust their work w/o question.
dbenney said:
This is true... but those of us that are not programmers and not as farmiliar with modding these roms are at the mercy of the devs. I am not a noob but am trying to adjust to the s3, came from the OG EVO. Basically what I do is do some google research, search threads on here. eventually you find devs who you prefer and trust their work w/o question.
Click to expand...
Click to collapse
Same here, I have only dealt with the original EVO. I want to put the leak JB on my S3 but I want to be able to get the official OTA when that comes out as well. I'm good with this stuff if I have a good guide, I'm just so lost with this one.
leperme5siah said:
Same here, I have only dealt with the original EVO. I want to put the leak JB on my S3 but I want to be able to get the official OTA when that comes out as well. I'm good with this stuff if I have a good guide, I'm just so lost with this one.
Click to expand...
Click to collapse
you wont get both with rooted custom rom installed...it is one or the other...
choose your path..
Naddict said:
you wont get both with rooted custom rom installed...it is one or the other...
choose your path..
Click to expand...
Click to collapse
Well sir, he could could flash the stock recovery > take the OTA > he'll lose roo, then can simply re-apply the rooting procedure in 1 minute and have root back. The only thing is it'll be 100% stock rom, with root access.
We both know its just better to wait, but to each his / her own.
dbenney said:
This is true... but those of us that are not programmers and not as farmiliar with modding these roms are at the mercy of the devs. I am not a noob but am trying to adjust to the s3, came from the OG EVO. Basically what I do is do some google research, search threads on here. eventually you find devs who you prefer and trust their work w/o question.
Click to expand...
Click to collapse
leperme5siah said:
Same here, I have only dealt with the original EVO. I want to put the leak JB on my S3 but I want to be able to get the official OTA when that comes out as well. I'm good with this stuff if I have a good guide, I'm just so lost with this one.
Click to expand...
Click to collapse
Exactly my same situation.
teh roxxorz said:
Well sir, he could could flash the stock recovery > take the OTA > he'll lose roo, then can simply re-apply the rooting procedure in 1 minute and have root back. The only thing is it'll be 100% stock rom, with root access.
We both know its just better to wait, but to each his / her own.
Click to expand...
Click to collapse
How would you flash the stock recovery, and why is this needed? Wouldn't you still get the OTA prompt after rooting and just be able to accept the install - why need stock recovery?
s1dest3pnate said:
How would you flash the stock recovery, and why is this needed? Wouldn't you still get the OTA prompt after rooting and just be able to accept the install - why need stock recovery?
Click to expand...
Click to collapse
In the dev section, there is a thread in the there that has the stock recovery you can flash via odin. You need stock recovery because the OTA flashes through stock recovery; which is why on anything but stock, the OTA fails to flash.
And you wouldn't get the ota at that point cuz you'd have it. There are other ways to disable it though.
Naddict said:
you wont get both with rooted custom rom installed...it is one or the other...
choose your path..
Click to expand...
Click to collapse
That's remembers me, my ex g/f bikini line.
Sent from my O=O
Will the root methods out there work if you're already on the Sprint Jelly Bean OTA (LJ7)?
Before rooting, any precautions to take other than resetting Google Wallet?
First off, resetting Google wallet isn't necessary. That's old news
And second this question should go into the noob question thread because if you don't already know the answer to this than you don't need to do it. You'll be just another rooted noob that ends up fukn brickin. Dont do it until you can answer this question yourself
Nobody is gonna hold your hand especially not when youre back here in a week askin how to repair your doorstop of a phone
billard412 said:
First off, resetting Google wallet isn't necessary. That's old news
And second this question should go into the noob question thread because if you don't already know the answer to this than you don't need to do it. You'll be just another rooted noob that ends up fukn brickin. Dont do it until you can answer this question yourself
Nobody is gonna hold your hand especially not when youre back here in a week askin how to repair your doorstop of a phone
Click to expand...
Click to collapse
Lol... The issue is that all the information is fragmented all over the place. I understand the general process but am asking the noob questions so that all bases are covered. I was on the OG Evo, rooted and updating ROMs all the time. Don't assume man - just trying to get "comprehensive" details before messing up something - you shouldn't be able to blame me for that. So many different OTAs, versions of Galaxy S III (international and different carriers), Google Wallet comes into play, etc...
So back to my main question: Will the root methods out there work if you're already on the Sprint Jelly Bean OTA (LJ7)?
And is there consensus that no precautions need to be taken with Google Wallet or anything else?
s1dest3pnate said:
Lol... The issue is that all the information is fragmented all over the place. I understand the general process but am asking the noob questions so that all bases are covered. I was on the OG Evo, rooted and updating ROMs all the time. Don't assume man - just trying to get "comprehensive" details before messing up something - you shouldn't be able to blame me for that. So many different OTAs, versions of Galaxy S III (international and different carriers), Google Wallet comes into play, etc...
So back to my main question: Will the root methods out there work if you're already on the Sprint Jelly Bean OTA (LJ7)?
And is there consensus that no precautions need to be taken with Google Wallet or anything else?
Click to expand...
Click to collapse
Root methods don't change. This is a Samsung not an HTC. They don't upgrade hboot or lock the bootloader with an ota none of that stupid crap.
Jb or ICS makes no difference. And Google wallet stores that personal crap that had the potential to make wallet brick up outside of the phone now so reset isn't needed. Although I think that was all hype originally anyway. As someone who has owned the phone since 6-21 I have flashed anything and everything and never reset wallet a single time
Seen a lot of comments, so I thought I would throw my 2 cents into the ring
Concerns:
1) flash counter - The SGS 3 has a counter that show how many times you have used ODIN to flash something. The program "Flash Away" resolves this, but to get it 100% back to the stock setting, you also need to flash a 100% official stock ROM. If you never plan on using the warranty, this is a non concern, but it might cause you issues if you bring it in for service.
2) loss of data - some flashes will wipe the internal SD card (yet to see anything wipe the external), so before doing anything major, it is probably a good idea to backup the internal SD to an external source
3) USB cable quality - one of the number one items I have seen that causes issues, is a bad and/or faulty USB cable. Make sure you got a quality cable if you are going to flash with ODIN
4) check the md5 checksum of the file you are going to flash. A bad download will also cause you issues, from minor to serve, so it is a good idea to do a double check before you use the file, just to make sure it is not corrupter
DCRocks said:
Seen a lot of comments, so I thought I would throw my 2 cents into the ring
Concerns:
1) flash counter - The SGS 3 has a counter that show how many times you have used ODIN to flash something. The program "Flash Away" resolves this, but to get it 100% back to the stock setting, you also need to flash a 100% official stock ROM. If you never plan on using the warranty, this is a non concern, but it might cause you issues if you bring it in for service.
2) loss of data - some flashes will wipe the internal SD card (yet to see anything wipe the external), so before doing anything major, it is probably a good idea to backup the internal SD to an external source
3) USB cable quality - one of the number one items I have seen that causes issues, is a bad and/or faulty USB cable. Make sure you got a quality cable if you are going to flash with ODIN
4) check the md5 checksum of the file you are going to flash. A bad download will also cause you issues, from minor to serve, so it is a good idea to do a double check before you use the file, just to make sure it is not corrupter
Click to expand...
Click to collapse
Kinda insulting to chainfire to call it flash away. Just saying...
And the counter isn't even that big a threat to ne one anyway. Hell u can even reset it using my stock rom. Definatly second checkin the USB cable tho
Hi, I'm getting a galaxy s3 tomorrow. I was just wondering if someone would give me a run down of anything I should know. My last phone was an inspire 4g. I don't know what a modem is. I was wondering what people are talking about "tripped flash counter" is it important? What is it? Any thing else like that, it would be greatly appreciated
Sent from my RM-820_nam_att_100 using Board Express
trh1341 said:
Hi, I'm getting a galaxy s3 tomorrow. I was just wondering if someone would give me a run down of anything I should know. My last phone was an inspire 4g. I don't know what a modem is. I was wondering what people are talking about "tripped flash counter" is it important? What is it? Any thing else like that, it would be greatly appreciated
Sent from my RM-820_nam_att_100 using Board Express
Click to expand...
Click to collapse
Welcome to the the dark side!!! Well the tripped flash counter is a Samsung can check to see how many times your flashed a non Samsung kernel on the phone using Odin or heimdall. Its important to have it at 0 if your sending your phone back to Samsung for repairs or if your exchanging for a new one with att.you can look up chainfire on xda. He has a app call triangle away which is can reset the flash counter.if you find his thread on xda he explains the flash counter a lot better. The only other important things I believe you should know is you can flash some T-Mobile galaxy s3 roms (search the thread to make sure tho), as you may know every phone is different so some kernels may work for you others may not and the root method is different from HTCs so read the stickes and theards or find a update to date video on how to root. I hope you enjoy this beast of a phone!!! Once again welcome
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks alot! I have one more question. The "casual" root method..will that install cwm or twrp or 4ext? And lind of recovery? Or dobi need to do that separately? I'm looking for the easiest way to root. Thanks for the help, i just dont have much money and since im coming from an HTC phone i know its going to be different...dont want a very expensive paper weight do i??QUOTE=blackstar_329;39618110]Welcome to the the dark side!!! Well the tripped flash counter is a Samsung can check to see how many times your flashed a non Samsung kernel on the phone using Odin or heimdall. Its important to have it at 0 if your sending your phone back to Samsung for repairs or if your exchanging for a new one with att.you can look up chainfire on xda. He has a app call triangle away which is can reset the flash counter.if you find his thread on xda he explains the flash counter a lot better. The only other important things I believe you should know is you can flash some T-Mobile galaxy s3 roms (search the thread to make sure tho), as you may know every phone is different so some kernels may work for you others may not and the root method is different from HTCs so read the stickes and theards or find a update to date video on how to root. I hope you enjoy this beast of a phone!!! Once again welcome
Sent from my SAMSUNG-SGH-I747 using xda premium[/QUOTE]
Sent from my RM-820_nam_att_100 using Board Express
Since you'll be getting the att model look here http://forum.xda-developers.com/showthread.php?t=2042775 ape made an excellent tutorial for beginners when it comes to rooting the s3. it has pictures and he even package a root kit follow the instructions and you should be fine. Before trying make sure you have a good understanding of it first. I believe it even helps you install cwm. Once your Rooted if you want twrp just download its either goo. Im or too manager I don't remember from the android market and install twrp from there. Once again if you run into a problem search the thread first because more then likely someone had that same problem or you can message me and I will try my best to help you and guide you through it. Like i said before there are turns of tuts ane vids out there to help you
Sent from my SAMSUNG-SGH-I747 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
The best thing you could do right now is read up and understand these different processes and procedures. There are many who don't and find themselves on this forum with broken, sometimes unfixable phones.
Look over the link in my signature. It can guide you from start to finish and ensure that you cover all your bases as safely and smoothly as possible.
Cheers
trh1341 said:
Hi, I'm getting a galaxy s3 tomorrow. I was just wondering if someone would give me a run down of anything I should know. My last phone was an inspire 4g. I don't know what a modem is. I was wondering what people are talking about "tripped flash counter" is it important? What is it? Any thing else like that, it would be greatly appreciated
Sent from my RM-820_nam_att_100 using Board Express
Click to expand...
Click to collapse
Unlike your HTC you have to try really hard to brick a Samsung phone...other than that make backups of your EFS, IMEI, and keep a nandroid of rooted stock ROM on hand and you are good to go. Like more Galaxy S phones its fairly fool proof and if something happens you can get out of it. Don't flash anything for the international version. I prefer TWRP for recovery because its user interface is a lot better but to each there own.