Related
I see, in ROM Manager, that a new recovery (2.5.1.3) is available........anyone tried it?? I read a tweet from Koush referencing this build on a G2 and N1 and the use of the touch screen. My phone is working pretty good right now and I am kind of gun shy on changing recoveries. I have not seen anything else about this.
wwjdd44 said:
I see, in ROM Manager, that a new recovery (2.5.1.3) is available........anyone tried it?? I read a tweet from Koush referencing this build on a G2 and N1 and the use of the touch screen. My phone is working pretty good right now and I am kind of gun shy on changing recoveries. I have not seen anything else about this.
Click to expand...
Click to collapse
Mine still shows 2.5.0.5 as the lastest, so no help here.
well I guess we will know when something happens....hopefully not tho
Sent from my ADR6300 using XDA App
You can see it at the bottom of ROM Manager, All Clockwork Recoveries, or something like that. If it's under there, it's considered experimental. Latest is 2.5.1.4, now.
Sent from my ADR6300 using XDA App
Koush
I remain perplexed that Koush is not showing as having valid copies of these versions for the DINC on his web site.
http://koush.tandtgaming.com/recoveries/
Only 2.5.0.5 and 2.5.1.1 show for the DINC. Because of that I moved to 2.5.1.1 via ROM Manager, and my phone REALLY started acting wonky (I know recovery should not affect operation). I wound up reflashing the stock radio (which includes 2.5.0.5) to get them both replaced at once (I have ALWAYS been stock radio; so I wasn't changing anything), and the phone went back to normal. No more random recoveries for me.
Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!
Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?
K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!
Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.
makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?
G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF
i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.
Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
internetpilot said:
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
Click to expand...
Click to collapse
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.
That's what I recall from when I still had stock about 9 months ago...
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.
Sent from my buttered S3
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
internetpilot said:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
Click to expand...
Click to collapse
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there.
Click to expand...
Click to collapse
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
internetpilot said:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
Click to expand...
Click to collapse
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
Click to expand...
Click to collapse
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
internetpilot said:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
Click to expand...
Click to collapse
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
flastnoles11 said:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
Click to expand...
Click to collapse
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
internetpilot said:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
Click to expand...
Click to collapse
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
flastnoles11 said:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
Click to expand...
Click to collapse
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).
In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.
Sent from the future via Tapatalk 4
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
internetpilot said:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
Click to expand...
Click to collapse
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
edfunkycold said:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
deutscher3891 said:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
Click to expand...
Click to collapse
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
internetpilot said:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
Click to expand...
Click to collapse
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
deutscher3891 said:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Both directly from Sprint.
lvpre said:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
Click to expand...
Click to collapse
The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.
When last Feb. I finally switched from my iToy to my N7100, I thought that 'flashing' was something that some perv did while wearing a raincoat.
(Hey, I'm pushing 70)
I Finally got my device rooted. I know that it's rooted because while using CF Auto, It wanted me to flash a Triangle Away update, and my binary count went down from 22 to one... so I know at least that worked.
Overjoyed that in Odin, when flashing I first got the notice "Reset!" and then after a few minutes and a restart, I got the "Done" notice (or whatever it said) as I never unplugged from the USB as it says you're supposed to. I just forgot.
Prior to "upgrading" to 4.3 Indian version, I had the stock Rom 4.1.2 running the Perseus Kernel... loved it, but upgrading to 4.3 has turned out to be the worst decision so far.
I still have a lot of Root apps on the phone but they don't work, but as I said, Triangle Away did work.
Should I uninstall the existing ones like Tit. Backup Pro and a few others and re-download them?
Does CF Auto Root automatically install SuperSU? Or should I uninstall that and re-download that too?
One last question....
Assuming that I do have Root, and I'm able to get Titanium Backup Pro working and am able to freeze and/or uninstall the Knox files... What about the ODEX files with Knox.
On this site, I have heard both pieces of advice... Delete and not delete the ODEX'd files.
What is it?
Nobody ever comes up with a definitive answer on this site... it's just a bunch of opinions, usually with the disclaimer, "Worked for me", or something like that... combined with the fact that I really hate working with the Windows partition on my Mac to do the flashing.
Oh, one more thing.
I'd like to go back to the Perseus kernel which somebody mentioned here on XDA.
Are there any kernels for the N7100 that are only useable with 4.1.2 that I should NOT use with 4.3, or does it matter. In other words, would it work with 4.3 as it did with 4.1.2?
Too bad that I don't have somebody like ChainFire living next door. Haha!
I have to thank the XDA site for most of my knowledge since last Feb. when I thought that rooting had something to do with digging up a tree in my front yard.
One more thing (again), I just got an update for Rom Manager Premium and it looks like I can download a CM stable release, which I'm gonna do as soon as I get some of these things ^^^Above answered and ironed out.
I'd like to stick with AOSP as opposed to AOKP but I'll do anything to get away from this current ROM.
Thanks in Advance to anyone who can answer some of these Noob questions.
1-ok i think that you have a custom recovery now, i had these issues a lot on 4.3, if you have custom recovery TWR or CWM you can install any rooted 4.3 rom, but before you do so make sure you backed up your efs folder (VIP you will lose signal if this folder corrubted), after a clean install of any rooted rom, just install ur apps again, if you don't have custom recovery you will need to flash any recovery from Odin, if you can't install recovery from odin so this will be bec. of knox, report back bec. this is another story.
2- some kernels works fine with 4.1.2 or 4.3, and some old ones are only 4.1.2, so make sure that you will flash the right kernel (e.g. devil, AgniPure Stock, ....)
3- don't try to update to CM now, frist make sure that you have a fully working rooted rom with custom recovery install, i also don't recommend flashing roms using any app (rom manager fore example), i think the best flash is the one you do from recovery with clean flash
Just A Follow-Up...
Hey, thanks, evaworld!!!
UPDATE:
I decided to try Root Explorer again (It never worked before to delete anything before this time) and do a search for anything with Knox in it.
I found everything Knox and checked all the boxes except for the ODEX'd files, hit the trash can and wow... it asked for Root privileges. I gave it, and everything was gone in a flash (Pun intended).
Then I tapped on Ti Backup Pro and got the dreaded 'Android device I.D. changed' message so I came back here to XDA and read literally every post on it (Again, opinions are divided) and decided to ignore.
After that, nothing was working for me in Google Play, so I just deleted the data in Google Play Services, Google Play Store, and now I'm waiting for it to take effect in Google Play... whenever I did that in the past, it usually took a couple of hours for it to register. (?)
Now, all of my Rooted apps that I've tried so far are working, but somewhere along the line they pushed Samsung Link on my phone even though I've had Samsung Apps disabled since day one.
The funny thing is that with a Binary Count of 22, I did absolutely nothing differently than this time (Except for an abortive try with Philz_Touch that I don't particularly like the GUI in P_T)... same USB cable, same port, same Windows partition on my Mac, etc. etc. it took this time and I'm pretty overjoyed!
I'll follow evaworld's advice on the ROM... better not throw too much into the mix until I decide that everything is all ironed out.
And, yes, I did click the "Thanks" button for you.
Very good that you have root, but also note that your setup isn't so stable (besides the fact that 4.3 isn't very stable with root apps e.g. I always have problems with titanium and Super and alot of other apps that requires root) , so just clean install a good 4.3 app (I recommend DN3), and after that you are free to do whatever you want (don't forget efs backup in sage place).
Sent from my GT-N7100 using XDA Premium 4 mobile app