Related
Here's a good one for any devs. I have been fussing with this for 3 days and am at my wits end.
I noticed the other day there was a software update from VZW for my droid X. That night I get home launch ADB name all the renamed .apk bloatware back to normal, and DL & install the update.
After doing so I as expected lost root. No biggie I thought as I Had rooted my phone previously with little effort. Long story short after numerous attempts and now several different methods including z4, 1 click root, etc... I still am unable to regain root access, and am stuck with read only access to the file system.
I have posted on a coupe different forums with this query, and it seems to be a mixed problem. some are able to regain root, others are like me and locked out completely.
So.. the question here lies in this??? is there something VZW or Motorola have done with this update to disallow rooting, and if so is it possible to roll back my OS to stock 2.2 Froyo prior to this update? Alternatively does anyone else know of any tricks I may have overlooked in successfully rooting my DX.
Thanks in advance!!!
Same here. Tried z4 and onion root. Tried the terminal emulator method. Nothing works.
Sent from my DROIDX using Tapatalk
is there something VZW or Motorola have done with this update to disallow rooting,
Click to expand...
Click to collapse
No, nothing they did. It happened because you accepted an OTA while rooted. Every root guide on here should tell you never to accept an ota when rooted, or you could permanently lose root.
i'm in the same boat as the poster. i accepted it while rooted, unrooted and then installed it. It appears i am locked out from rooting.
http://forum.xda-developers.com/showthread.php?p=9778968#post9778968
worked for me
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
CoinCoin88 said:
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
Click to expand...
Click to collapse
Just to make sure you do have SuperUser, SuperSU, and I generally prefer to include BusyBox all into the mix. Also, if you would download Root Checker by Joey Krim in the Play store. Just to confirm and we know you are missing root click the verify should indicate the appropriate SU's are red and not engaged, slide to the right verify BusyBox, chances are it is green, if so you are in good condition. With Busybox in green, exit go into SuperUser and update the binaries, once that is completed go into SuperSU and click the update. Go back to Root Checker and double check, click verify root on SuperUser/SuperSU and should be green = rooted. :good:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
CoinCoin88 said:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
Click to expand...
Click to collapse
If the color is Red all around then yes, there is little you can do. However, there are ways to get out of this and gain root without waiting even if they have Jelly Bean 4.1.1. For instance those on JB that own the XT926 can use the Droid Razr HD Utility 1.10 > go back to ICS 4.0.4 > apply the 1st update > Root > Voodoo OTA, SU Backup > apply the JB 4.1.1 update. I have done this twice and have been quite successful on my XT926 with Verizon.
But, in general going back to the discussion. If after the update the Supers are not showing, as long as Busy Box is Green and in place, Root can be restored by updating the binaries.
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
tech_head said:
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
Click to expand...
Click to collapse
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
CoinCoin88 said:
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
Click to expand...
Click to collapse
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
tech_head said:
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
Click to expand...
Click to collapse
edit the XML ?? I'm new to RSD lite, but from what I've understood so far, edit the xml is only neededn when flashing via RSDLite/fastboot so that you don't end-up with the "unknown fastboot command" or something like that (by removing 2 lines in the fw xml file, indeed).
How is this related to going back from JB to ICS ? I'm not sure that's possible with a locked bootloader (which I'm probably not going to unlock). Also, how is my carrier related to this operation ? (the phone was SFR simlocked, but I bought an unlock code online and I'm no using it on Free Mobile)
Or did I miss something ? (btw, no mention of a JB root for the Razr HD, only for the Razr M, and it is assumed it won't work on HD because for reasons I am yet to find)
I have a brand new stock verizon S3 and am wondering if I can use the MrRobinson root method to root for the very first time. I swear someone in one of the forums said they did but it sounds like most people are using those images to just update. I originally tried this 4.1.1/4.1.2 method and it bricked my phone on flashing the VRALEC bootchain step, everything looked good in odin, the phone looked like it tried to restart, then went black and never came back. I got a new phone and am wary of trying the same method again. If that is the method I have to use any thoughts on what could have went wrong?
I appreciate any input.
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Ryno77 said:
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Click to expand...
Click to collapse
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
idk why that happened. My best guess is if the battery was low prior to you using Odin then it may have needed charging. But that VRALEC/Odin method is proven working countless times and those files linked in the OP have been used countless times.
Just know that with mrRobinson's pre-rooted images, you'll still need to unlock your bootloader with say EZ Unlock v1.2 (available on Rootzwiki so google it) before you decide to flash custom roms/kernels.
Ryno77 said:
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Click to expand...
Click to collapse
Like I said above, may have been the luck of the draw or it could have needed charging.
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
If you want to have a 4.1.2 rooted stock version, you need to download MrRobinson, K3 full wipe image with root (http://www.androidfilehost.com/?fid=9390214368362234355), unzip it first, then use Odin to flash this, then install Voodoo OTA root keeper from the market to preserve root, then let OTA update back to 4.1.2, finally use OTA root keeper to restore root. Done, simple and risk free.
You guys rock thank you!
As a followup for anyone that may stumble upon this thread in the future, I used the method provided by buhohitor and it worked like a champ. I flashed the mrRobinson image used ez unlocker to unlock the bootloader then used ez recovery to flash the latest version of TWRP. I'm now running this Paranoid Android 4.2.2 Rom and it is fantastic!
Okay, so I am on 4.2.2, rooted using the RockMyMoto method. I have not yet seen an OTA, but I see zips galore and confusing banter in the threads about the .zips. What I am wondering is what would my course of action be to upgrade to 4.4 and keep my WiFi tether?
Not an ADB, Fastboot, or RSD noob, just being super cautious so I don't rush things and get bricked.
darthespa said:
Okay, so I am on 4.2.2, rooted using the RockMyMoto method. I have not yet seen an OTA, but I see zips galore and confusing banter in the threads about the .zips. What I am wondering is what would my course of action be to upgrade to 4.4 and keep my WiFi tether?
Not an ADB, Fastboot, or RSD noob, just being super cautious so I don't rush things and get bricked.
Click to expand...
Click to collapse
Wait until you get an OTA notification - many many people including me have been bricked by the .zip and are now without our phones for possibly weeks until the firmware is released, it is too risky to update using it as you must follow the posted directions to the letter, and even then something can go wrong, especially if you are rooted. I highly recommend waiting
Also if you are rooted when taking the OTA, ensure your stock recovery is working (boot while holding power and volume down, then select recovery) if you don't see the Android with an exclamation mark, and your device instead boots after selecting "Recovery", then you must first use the MotoWpNo tool to get permanent write-off protection. But once again taking the update while rooted in general has posed some problems (especially if you use this tool improperly) and if anything I personally from experience recommend taking the update while not rooted, and waiting for an official 4.4 root to be released, which shouldn't take too long anyways