I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Is there a new update? post/after asa14?
Checked around but after seeing the old do this if you cant upgrade threads pop up I was curious.
Seen some traces of the 9.8.2Q JellyBean update for the Q, but don't know it's current status.
Interesting and good news, Just checked and mine stated not update available sadly..
Gxkon said:
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
Click to expand...
Click to collapse
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
swintec said:
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
Click to expand...
Click to collapse
I dont know it dont look like a new os. One was around 60 mb then i had a small 7 mb update
arrrghhh said:
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Click to expand...
Click to collapse
Yeah, the motofail2go exploit to root works only if you haven't updated. After rooting, you can save root by Voodoo OTA rootkeeper, temp unroot, install any updates, then restore root with OTA rootkeeper. Works great, and you keep your warranty. But of course you can't flash any ROMs or anything, but you can still use Titanium backup, other programs that require root.
see this thread:
http://forum.xda-developers.com/showthread.php?t=2053444
Related
Hi all, I just get my Nexus S and gonna root it.
I'm not sure if rooted Nexus S can get OTA updates in the future? (Just rooting, without ROM flashing)
U will still be able to get updates as long as u dont flash any custom roms but u will probably lose root an have to reroot it. Thats what happened to me when i got the ota for 2.3.1
yup, you'll get all the updates, you'll just loose root after every update.
Silverwzw said:
Hi all, I just get my Nexus S and gonna root it.
I'm not sure if rooted Nexus S can get OTA updates in the future? (Just rooting, without ROM flashing)
Click to expand...
Click to collapse
follow this Guide to safely root the phone http://forum.xda-developers.com/showthread.php?t=895545
neok44 said:
yup, you'll get all the updates, you'll just loose root after every update.
Click to expand...
Click to collapse
Just in case this is where you are coming from OP before your Nexus S (like me), it's similar to an iOS jailbreak where you jailbreak it, then a new update comes along and you loose the jailbreak when you upgrade.
But I don't even know if you had an iOS device Just thought I'd add this in
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
wakkigy said:
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
Click to expand...
Click to collapse
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
buhohitr said:
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
Click to expand...
Click to collapse
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
wakkigy said:
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
Click to expand...
Click to collapse
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Thats OK said:
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Click to expand...
Click to collapse
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
wakkigy said:
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
Click to expand...
Click to collapse
Yup. Assuming you're into the stock experience and have the keyboard (thus appreciating the shortcut keys), CleanROM is eyeing you. Your 700 is behaving normally, so that's one problem out of the way.
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
msmajerczak said:
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Jimmah555 said:
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Click to expand...
Click to collapse
Make sure you delete the old zip file in your sd card.
buhohitr said:
Make sure you delete the old zip file in your sd card.
Click to expand...
Click to collapse
Oh I know that. I just think it's funny that it wants me to "update" to an older software version.
Thats OK said:
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
Click to expand...
Click to collapse
After that i lost root
msmajerczak said:
After that i lost root
Click to expand...
Click to collapse
Sorry man!
Looks you and me are in the same boat.
I just threw up my hands and did another factory reset last evening.
I've heard rumors that we will be receiving 4.4.2. I was wondering if there's any chance that we'll be rootable after this update.
ive heard that every time a bell rings, an angel gets its wings.
brian_199 said:
I've heard rumors that we will be receiving 4.4.2. I was wondering if there's any chance that we'll be rootable after this update.
Click to expand...
Click to collapse
Yeah, so umm... that's not going to happen. I mean, ****, we can hope and dream and whatnot, but I seriously doubt it. They'd have to open up a new update
EDIT:
I meant to say, the new firmware would have to open up a new exploit somewhere, and since 4.4.2 doesn't have any known exploits for any other platforms, I don't think it'll happen for us either.
brian_199 said:
I've heard rumors that we will be receiving 4.4.2. I was wondering if there's any chance that we'll be rootable after this update.
Click to expand...
Click to collapse
Moto X DE here
when we got the update, some who were rooted with slapmymoto were able to keep "root" when taking the OTA, however the update re-enabled write-protection which means most of what root is good for is lost.
Some people report that they can use xposed modules with soft-reboots, but if you do a hard reboot you will have to re-install the framework and soft-reboot to get it back working.
If you want root and currently have it, block the update. (unless you have unlocked the boot-loader when it was previously available from 3rd parties, then you can ignore this post)
Latest DPD1 6.0.1 MM Factory Tar Image
Full System Restore ImagesFully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To KitKat Firmwares)
6.0.1 MM VZW-G900VVRU2DPD1-20160511030450.zip
5.0 KK G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
5.0 KK G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip
5.0 KK G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full System Restore Images With No Aboot Bootloader For Dev Unlocked Bootloaders
6.0.1 MM PD1_Full_Factory_Restore_No_Aboot.tar.zip
Firmware Only (Bootloader,Modem,Kernel,Recovery)
Modem OnlyVZW_BOK3_MODEM_NONHLOS_ONLY.tar.md5
VZW_BOK3_MODEM_ONLY.tar.md5
Kernel(Boot.img) OnlyVZW_BOK3_KERNEL_ONLY.tar.md5
For Dev. Ed. owners
Here is a full stock tar without the bootloader and without the recovery for Dev. Ed. owners
https://www.androidfilehost.com/?fid=24052804347794573
Just make sure you have SuperSU on your SD card to flash it in recovery after updating to re-root https://download.chainfire.eu/696/SuperSU
This is for Developer Edition owners only
jrkruse said:
BOG5 Factory Tar Images
Fully Stock Odin Factory Tar Image (Caution This Will Lock Your Bootloaders And Keep You From Downgrading To Obtain Root!!)
G900VVRU2BOG5_G900VVZW2BOG5_VZW.zip
Full Stock Odin Factory Tar Image With BOD5 Bootloaders (This Will Allow You To Still Downgrade To Earlier Builds)
VZW_BOG5_RETAIL_FULL_FIRMWARE_WITH_BOD5_BL.tar.zip
Click to expand...
Click to collapse
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
equazcion said:
I'm wondering the same thing. It's been a while since I've heard anything about efforts to downgrade from OE1. I'm unrooted and would so desperately like to root, but unfortunately installed stock OE1 :crying:, and then OG5. I really really hope there will be some method of rooting in my situation. Hating the fact that I bought a device that I can't use the way I'd like because some screwball company thinks people are too stupid to be trusted.
I really appreciate everyone's efforts here. Keep up the wonderful work and keep us updated!
Click to expand...
Click to collapse
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
jrkruse said:
Sorry guys! You can try but Im sure the tar image with the bod5 bootloaders will fail if your already on BOE1 or higher
Click to expand...
Click to collapse
Thanks I found out the hard way LOL. All good now tho.
XNO said:
So if I am on Stock OE1 and flash the second link are you saying I can downgrade to root?
Click to expand...
Click to collapse
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
skister77 said:
I too am interested in this. I lost root and was hoping this version that Verizon installed today would allow me to re-root.
Click to expand...
Click to collapse
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
To add to what ldeveraux wrote, your question was literally answered two posts above yours. Does anyone even bother to read anything anymore? Or is it that reading comprehension is completely a thing of the past?
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
DraconicSeed said:
Stuff happens. Maybe somebody made a mistake.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
[/COLOR]
ldeveraux said:
Oh dear lord, no no no no. Stop asking the same questions repeatedly hoping for a different answer. For the last time, if you are on oe1 and didn't keep the od bootloader, that's it, you're done.
And for the record, why would Verizon release an update that would re-allow to root? Why would that ever happen intentionally?
Click to expand...
Click to collapse
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Spartan117H3 said:
It's true that mistakes can happen, but once they patch the bootloader to prevent downgrading, they don't actually have to touch it again. So if they don't change anything in it, then the chance of breaking it is slim to none. Not to mention this update didn't do much anyways.
Click to expand...
Click to collapse
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
XNO said:
So just to be clear Ideveraux, because I don't quite understand, are you saying OE1 is not rootable but OG5 has a chance?
Click to expand...
Click to collapse
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
DraconicSeed said:
It involved a security update so I was hoping maybe someone messed up somewhere :silly: one can hope. I purchased my phone with OE1 already installed so I was kinda screwed from the ground up and going from an S4 rooted running TWRP and a Hyperdrive ROM to a stock unrooted bloated phone rubs me harsh lol
Click to expand...
Click to collapse
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone REPEATING questions.
Click to expand...
Click to collapse
FTFY
XNO said:
Thanks Spartan, I'm just messing with ldeveraux because all i ever read from him is negative comments like he is super annoyed at everyone asking questions.
Click to expand...
Click to collapse
It has been repeated a million times though, in basically every "recent" thread so I can see why people would be frustrated. The issue is, the more people post the same questions, the more hidden the important questions get, leaving people even less likely to read/search the thread for their answers. Just basic forum etiquette IMO. I'm just a little more patient at times answering questions, that's all.
Verizon s5
Spartan117H3 said:
Anything OE1 or higher cannot be rooted. OG5 is higher than OE1, and therefore has the same issues for people who want to root that OE1 has. OE1 has a bootloader that disallows downgrading of firmware which is required to root these phones. The only way you can still downgrade OE1/OG5 is if you came from a rooted phone and did NOT take OTA OE1/OG5, and flashed a firmware that did not change the bootloader.
The stagefright that was incompletely patched was apparently 4 lines of code somewhere in one of the system files, wouldn't be in the bootloader. I understand the sentiments, I would have returned the phone immediately in your case. I'm already running out of patience even being rooted, with the locked bootloader and whatnot. Trying to patiently wait for the Nexus 6 2015 this year.
Click to expand...
Click to collapse
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
trucker950 said:
well it sounds like to me everybody in the computer world cannot find a way to unlock the bootloader that is on OE1 or higher I'm thinking surely there's somebody out there that can figure out a way to do it so I would be able to contain root against
Click to expand...
Click to collapse
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Spartan117H3 said:
There was an $18,000 bounty for a root method and bootloader unlock before one came out. Geohot used Pinkie Pie's findings of an exploit in all Linux kernels to create his root. He now works for Google's Project Zero and isn't allowed to provide root, and even if he was allowed, he probably doesn't care anymore. That exploit has since been patched, hence the need to downgrade to apply Towelroot. Since then, Verizon has blocked the ability to downgrade.
Notes: Bootloader is still locked despite the length of time this phone has been out. This phone is also "dying" and support is mostly gone considering many of the devs went to other devices/new S6, or devices/carriers that don't have this locked bootloader issue. Look at the Note forum. There's still not even a real root for them, they have a temporary one the last time I checked.
So no. Not only are few people looking if they are at all, but support of this phone from Verizon is probably gone as well. This OG5 is more of a mandatory security patch than a new update. 5.0 is most likely the last version for Verizon's S5 (I'd be surprised if they released 5.1/5.1.1).
Click to expand...
Click to collapse
You couldn't have summed up the S5 situation any better. Cheers!
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
RicardoSal24 said:
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
Click to expand...
Click to collapse
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
fatapia said:
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
Click to expand...
Click to collapse
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
RicardoSal24 said:
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
Click to expand...
Click to collapse
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Come on. It wasn't that hard to root it. Just follow the directions. Easy!
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
rebelde80 said:
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
Click to expand...
Click to collapse
about phone/software version
fatapia said:
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Click to expand...
Click to collapse
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
i have software version 10a that is rootable right thats not 10d or are they similar.
RicardoSal24 said:
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
Click to expand...
Click to collapse
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
fatapia said:
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
Click to expand...
Click to collapse
So then its best to wait until something is done with the update?
RicardoSal24 said:
So then its best to wait until something is done with the update?
Click to expand...
Click to collapse
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
fatapia said:
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
Click to expand...
Click to collapse
I think I'll play it safe until its 100% or wait for a new android version with a root method
RicardoSal24 said:
I think I'll play it safe until its 100% or wait for a new android version with a root method
Click to expand...
Click to collapse
it's never 100% safe, hence the quotation marks. there's always a risk of something going wrong such as a power outage, or bad file download. As long as you verify the md5sum of your files you shouldn't have a problem with rooting, the only problems I've seen are people trying to use the wrong files on their device. up to you tho man, good luck with which ever you decide
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
lordodin912 said:
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
Click to expand...
Click to collapse
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
xanderin said:
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
Click to expand...
Click to collapse
It was needed for s-off, so not tech for root (if i remember correctly) but for being able to flash custom roms and such. Theres youtube videos about it.