Related
I'm considering rooting my phone, but I'm kind of on the fence. First, I don't really want to void my warranty, but since I bought the phone used do I even have a warranty anymore? Second, I'm not really that interested in custom ROMs at this point since I'm new to Android OS and I'm happy with the way things are stock for now. So my question is... What can I do with a rooted phone running the stock Froyo ROM? Anything cool/interesting, or does it not even pay to bother rooting if I'm going to keep it stock?
I waited 3 months before rooting and I thought the same as you, wasn't interested in custom ROMs and all. Once I finally rooted and loaded cyanogen ROM, it completely changed my thinking. I highly highly recommend using cyanogen if you root. I can't stress enough. Things wkt can do with root are many, 720p video hack, black notification bar, themes, meta morph, audio volume hack, ROM manager, titanium backup, nand backups! The list is endless. Hell nand backup alone is worth rooting.
Is there a place or a link I can find more information about just stuff that I can do with a rooted phone BESIDES installing custom ROMs? Everything I usually find is just about ROMs. I want to just get my feet wet a little before I decide to just jump right in. For now I'm just interested in stuff I can do with plain old vanilla android once it's been rooted.
Look for apps that require root, see what they are and if you need any of them.
Here's my current list of things "to root for", I haven't yet..
Reasons to root:
Just root, nothing else:
- Adblock host file
- ClockSync
- GScripter
- Remove built-in crap (Amazon MP3)
- Screenshots
After installing recovery image
- Nandroid
After installing custom rom
- Black notification bar
Depending on where you live, you might still have warranty. For example, in Europe, the warranty is by default 2 years on the device. So it doesn't matter if you got it second hand, as long as the device still has warranty, you're OK.
Secondly, you can root your device without unlocking the bootloader. Check this thread for more info. At step 18, before doing the 2 'exit' commands, also take the time to rename /system/etc/recovery-install.sh & install + make executable a file called flash_image (google it to find a download) into /system/bin. This way you can install a custom recovery (e.g. for doing nandroid backups) and will make installing custom ROMs later a lot less painful.
A rooted stock FRF91 can already do many things, search for 'root' in the market and you can find tons of apps that require root privileges and that will run fine on stock. However, the really interesting things (like color trackball alert, firewalling, proxy support, ...) will require you to install a custom ROM.
I rooted my stock N1 with the above procedure a couple of weeks ago, and installed Cyanogen6 RC2 ROM to get some of the more advanced functionality. Been working like a charm and I've actually managed to get a lot more out of my device AND have longer battery life
Sorry for the wall of text and for being a total noob and thank you for all your help !
So I've been researching all night (read the wiki to no avail too; so please don't simply direct me there) and I have some unanswered noob rooting questions questions and need general reassurance...
Basically I want is full and lasting root permissions on FRG83D 2.2.1 so I can remove system apps (twitter, amazon, etc...) through terminal commands and MAYBE a unlocked boot loader to flash a custom recovery image (Amon_RA) so I can make full nandroid backups.
1) It seems to me that unlocking the bootloader is a more flexible and permanent way to achieve root, as opposed to other '1-click' type methods in the face of firmware updates (2.3...), which would just disable root and it might not be re-achievable till another exploit is found whereas with an unlocked bootloader I can flash w/e I want?
2) Is it possible to enable root and use terminal on my n1 without some "superuser.apk" program? In order to do this would I use an insecure superboot and manually deploy SU?
3) How can I make a backup before rooting if I'm not rooted? I've been using my device for 8 months so there's a lot of stuff on there...
3a) If I can't make a full backup where can I find signed stock recovery images and boot images or updates zips so I can reflash them if I need to?
4) I believe if I superboot.img and leave everything (ROM and Recovery) stock will I still be able to receive and install OTA updates...?
4a) Can someone explain the difference between himem with updated wifi driver and not? I think himem removes permanent virtual address mapping so memory can be used for running applications. Asides from having more memory what are the tangible benefits or downsides to this? Would it make the system faster?Would I be able to multitask more apps before the system quits some because of lacking resources? Would the use of this extra memory inhibit system processes because there is no longer its own personal memory map?
4b) Will installing OTA updates remove root permission? If so, would simply flashing superboot.img re-grant me those permissions? But it would seem I need an updated superboot.img for the appropriate newer build(?). Is the development of superboot images still active and timely?
5) How important are OTAs and the stock recovery image? It would seem if I'm going to do any system moding (even just removing twitter/amazon) I should have a full and function Nandroid backup and would therefor need a custom recovery image- at the sake of missing OTAs (not important mainly because applying them would disable root etc anyway?)?
6) With root permissions and stock everything do I have to worry about manual baseband and radio updates? What about with a custom recovery image?
7) Apps2SD+ doesn't work with stock roms period and I would need a compatible custom rom?
Thanks again.
actually you can flash a recovery image without unlocking boot loader
1. Unlocking bootloader voids warranty and it is the official way to offer you the ability to install third-party roms.
You may get root without unlocking bootloader if you're using an old build. I think there are ways to root frg91 and frg83 without unlocking boot loader), then after you get root, you flash a recovery image, and then install whichever Rom you like. Don't bother with those official release, there will always be someone to release a rooted 2.3 rom.
2. not sure but from security's point of view it's better to have super user GUI program, because not all applications should get root
3. don't know sorry
4. Yes, there are lots of people revert back to stock ROM just for getting next OTA.
4a. I personally have never ran out of memory on my Nexus One, I do want to multi task as much as possible, however no matter how I set low mem killer, Android still automatically kills apps according to oom value (or something like that)
4b. If you get a successful OTA then definitely root is removed, and probably your recovery will revert to stock recovery too, thus you have to re-root..
5. I'd suggest to wait for someone to mod OTA 2.3 to make it rooted, then you flash the rom through recovery.
6. You can freely upgrade baseband (it's radio, the same thing) when you have a custom recovery.
7. There are mainly two ways to App2SD, one is Froyo implementation which works with stock Froyo rom, another way is to use App2Ext which requires root.
houzuoguo pretty much summed it up. I'll add what I can.
3) There is backup software in the market that can backup data without root, although it is not as powerful or thorough as the apps that require root.
3a) You can go back to a stock ROM. I believe there is a sticky round here of ROMs that has some stock ROMs in it. I know someone with a N1 that flashed a CM ROM, didn't like it, flashed a stock ROM, and got the OTA afterwards.
5) Even before an OTA is pushed there are ROMs floating around with the latest and greatest. After the OTAs are pushed you see a lot of very good, stable ROMs based off of them with all features working properly. You can do more with the custom ROMs and recovery images than you could ever do with the stock stuff.
7) DarkTremor's Apps2SD script will not only give you better A2SD than what is built into Froyo but it will give you a few more very useful terminal commands that I can't live without. Good stuff.
hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?
proteus665 said:
hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?
Click to expand...
Click to collapse
1. Check if there's application named 'superuser'. Or install any terminal emulator; run it, type 'su'.
**Please make your own thread next time.....
LFact said:
**Please make your own thread next time.....
Click to expand...
Click to collapse
Why?
Sent from my Nexus One using XDA App
Thanks guy!
I think I'm going to superoneclick to get root; back up with titanium and remove the system apps I don't want.
From there I'll be able to flash a custom recovery if I want to get more custom.
I'm probably going to wait till 2.3 comes out cause it's right around the corner; Or did they fix the superoneclick exploit in 2.3...?
Also, doesn't Apps2ext require a custom rom that supports it? i.e. it wouldn't work if I had root and was running a stock rom anyway?
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Don't be afraid....
The worst that can happen is you brick your phone and have to redo EVERYTHING. And chances are that won't happen if you're considering this and have done things in the past.
I only keep one SU app on my phone, but I have heard about being careful if you do have more than one not to confuse the binaries, so maybe if you can uninstall one and just use the one you kept to do everything, I'd say do that, but again I don't know.
I would also be careful about anything frozen especially if it's a system app or bloatware in the system...
See my other thread [Trifecta] Jelly Bean Update...I had all kinds of issues and made it thru, I'm sure you could too.
Cheers.
Ok, but what exactly do I do? I haven't modded anything, just rooted and "froze" apps. I know that after reading that I should take my phone back to where I had it right after root with no changes. Like I said, my phone has no mods and nothing has really changed. So what is the best way to update and keep root? Only reason I want to keep root is because it was easy and I don't want to do it again but more complicated (don't know Linux) If someone wants to type it out, step by step, or link to instructions that you followed exactly and succeeded in updating and keeping root, please do so.
As far as the GSM hack, not sure if I really need that.
Sorry....wasn't leaving you hanging...
You can try an app called OTA RootKeeper by Voodoo, it seems to work most of the time. But from what I understand once you start the update to JB even if it fails you can't go back. So if you update and lose root...
Go HERE
Read thru it, then follow the links to all info, tools & instructions.
Cheers.
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
CycoPuppet said:
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
Click to expand...
Click to collapse
I was chiming in for what little help I could offer on your other thread, and then I ran into an unexpected glitch myself. You can read all about it here. Basically, if you do an FDR for any reason on the stock ROM in SafeStrap, you are probably going to run into problems. It's happening to a ton of other people.
CycoPuppet said:
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
You were trying to use two different superuser apps (superuser and SuperSu) to control the su binary - each comes with its own binary, so when you used one to update su, then the other is naturally going to complain.
Clean Install
CycoPuppet said:
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
ian_mcxa said:
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
Click to expand...
Click to collapse
DO NOT ATTEMPT TO FXZ TO 246 ICS NOW. You've already updated to JB, and you will brick your phone if you attempt to go back.
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
Getting ready to finally root my HTC One now that we have had 4.4.2 for a bit.
1. TWRP or CWM?
- from following the threads for months, it has appeared to me as if TWRP has had more problems with the HTC One than CWM, in terms of soft bricks and other problems. Is this still the case? I always used CWM on my Epic4g, but I had a nice friendly keyboard and sdcard which made things easier, IMHO.
2. Will only rooting and installing SU + Recovery wipe my phone?
- in other words, how much backup work do I need to do if I want to keep apps/data/you name it.
3. Will a utility such as Voodoo OTA rootkeeper allow OTA's if I am unlocked/stock/rooted (and would s-on/s-off make a difference here)?
-this is what I was using on my Transformer, and it worked fine for OTA's until ASUS pooched my updates completely.
4. KitKat Wifi hotspot - is this (still) working?
- when I was first looking at it, there were a few configuration hurdles to get through but it was working. Some threads which I haven't worked all the way through seem to indicate that it isn't currently - where are we here?
Thanks in advance!
Pyperkub said:
Getting ready to finally root my HTC One now that we have had 4.4.2 for a bit.
1. TWRP or CWM?
- from following the threads for months, it has appeared to me as if TWRP has had more problems with the HTC One than CWM, in terms of soft bricks and other problems. Is this still the case? I always used CWM on my Epic4g, but I had a nice friendly keyboard and sdcard which made things easier, IMHO.
2. Will only rooting and installing SU + Recovery wipe my phone?
- in other words, how much backup work do I need to do if I want to keep apps/data/you name it.
3. Will a utility such as Voodoo OTA rootkeeper allow OTA's if I am unlocked/stock/rooted (and would s-on/s-off make a difference here)?
-this is what I was using on my Transformer, and it worked fine for OTA's until ASUS pooched my updates completely.
4. KitKat Wifi hotspot - is this (still) working?
- when I was first looking at it, there were a few configuration hurdles to get through but it was working. Some threads which I haven't worked all the way through seem to indicate that it isn't currently - where are we here?
Thanks in advance!
Click to expand...
Click to collapse
As far as I know twrp is the only recovery being updated for us.
In order to install su and recovery you will have to reset your device to stock settings due to the way htcdev works.
I'm not sure about voodoo ota because I've never tried it but updating this phone is not hard. Usually after the ota goes live someone will post up the Rom and firmware so you can manually do it and maintain root.
As for hotspot I'm not sure if it does work or not since I don't get good internet service where I'm at but I'm sure some of the Roms have it working
Sent from my HTCONE using Tapatalk