i have an incredible. i spent days on end to figure out which root effort paid off.
once rooted, i found the filesystem was read only.
i have my eye on some nice roms you all have created, but they all seem to have their own little quirks.
for now, i would be estatic to get a stock ROM with read/write FS so i can screw it up all by myself.
does a stock ROM for incredible with r/w FS exist?
is it possible?
It's only possible through recovery as of right now.
binny1007 said:
It's only possible through recovery as of right now.
Click to expand...
Click to collapse
i understand an incredible;s stock OS is limited to recovery, but i was hoping to hear you guys have superpowers to edit a ROM in other ways i am unfamiliar with.
lol thanks.
luvit said:
i understand an incredible;s stock OS is limited to recovery, but i was hoping to hear you guys have superpowers to edit a ROM in other ways i am unfamiliar with.
lol thanks.
Click to expand...
Click to collapse
We don't have NAND root access yet. Root Explorer is what you can use for R/W access, but when you go to mount the system again it will reboot... meaning we need NAND root. haha
taypotts said:
We don't have NAND root access yet. Root Explorer is what you can use for R/W access, but when you go to mount the system again it will reboot... meaning we need NAND root. haha
Click to expand...
Click to collapse
ah thanks. i didn't know what nand meant until now. i have much to learn with no time. i;ll hang in there until cm6 seems flawless. d:
ultimately, i'm aiming for vpnc to work on my incredible.
it's the only vpn app that i can use with my employer.
Here's a clarification I posted in another thread like this:
You have superuser access on your phone, that means you have root.
An additional level of protection that HTC has added to their phones is a NAND-flash chip which is locked by a memory protection unit. This is below the OS level, and thus below superuser. You can still have full root access to your phone, and not have access to this chip. The reflash tool unlocks NAND and reflashes the recovery partition.
The only way to unlock this at the hardware level is an exploit, or by changing hboot such that it does not initiate the NAND protection. We are still hesitant to flash hboot. If you mess up reflashing recovery, you have an unlimited number of chances to get it right. If you mess up reflashing hboot, you have a permanent brick.
Thus, since the recovery partition is protected by this hardware-level memory protection unit, ROM manager cannot reflash the recovery partition. You people seem to say that this is "not fully rooted" so "it is not sticking". Whatever. Yes, it won't "stick". No, this doesn't actually matter. You get *precisely* the same effect by updating in ROM manager. If there is a critical update that requires flashing, we will make sure that our users obtain this update.
Note that you don't need this for vpn as far as I know--you just need a kernel that supports it. I could be wrong on this.
Moved as not Development.
rpearl said:
The only way to unlock this at the hardware level is an exploit, or by changing hboot such that it does not initiate the NAND protection. We are still hesitant to flash hboot. If you mess up reflashing recovery, you have an unlimited number of chances to get it right. If you mess up reflashing hboot, you have a permanent brick.
Thus, since the recovery partition is protected by this hardware-level memory protection unit, ROM manager cannot reflash the recovery partition. You people seem to say that this is "not fully rooted" so "it is not sticking". Whatever. Yes, it won't "stick". No, this doesn't actually matter. You get *precisely* the same effect by updating in ROM manager. If there is a critical update that requires flashing, we will make sure that our users obtain this update.
Note that you don't need this for vpn as far as I know--you just need a kernel that supports it. I could be wrong on this.
Click to expand...
Click to collapse
thanks, rpearl. i want to rephrase this so that you can verify i understand correctly:
even if i flash with CM6, i may still not have permanent r/w permissions due to NAND will still reflash the CM6 recovery partition.
Correct. While you still have "full root" access, and you have ClockworkModRecovery available, you're able to flash new roms. There is not currently a way to unlock NAND protection which would allow you to delete system files. Which is really alright, because the safest way to not brick your phone is to do all your testing on your computer via emulator.
If you want to dig in and start deleting apps, please do it in the kitchen, cooking up your own rom. And don't share it until you know it won't ruin phones.
luvit said:
ultimately, i'm aiming for vpnc to work on my incredible.
it's the only vpn app that i can use with my employer.
Click to expand...
Click to collapse
vpnc works fine. There are other threads on how to get it working.
Is there a Stock ROM available for use in recovery available, or is it phone specific?
Related
hi ive been looking round how to root my g1 and had no conformation if the UK version g1 are different to root than the US.
can some give me some clarification on how to root them.
thanks in advance
i am a us g1 users so i might be incorrect but i believe that you need to use rc9 or a gold card. if it is rc9, the rest of the method is the same just a different .nbh
porkky said:
hi ive been looking round how to root my g1
Click to expand...
Click to collapse
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Afirejar said:
No, you didn't.
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Hey I’m having some trouble getting to grips with rooting too; there is quite a lot of information (some of it contradictory or at least inconsistent) for someone new like myself to take in. I consider myself pretty tech savvy but my G1 is uninsured and I’m frankly terrified of bricking it as I’ve got a year left on my contract to pay.
Anyway my point being...the guide your pointing to is specifically tailored to US models as are most guides on the net it’s very hard to find anything definitive about rooting the UK models with regard to SPL and Radio, etc. Also, given that this stuff moves soo quickly (which is an amazing testament to the hard work that all the devs and everyone else involved puts in, thank you!) it’s hard to catch up on everything and understand what exactly to do.
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
seaweeduk said:
One click root works fine on crc37 uk phones ive rooted a couple now just follow the usual instructions, there's little danger of anything getting bricked if you arent touching radio which you dont need to do to load CM using the one click root app
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
Click to expand...
Click to collapse
I'm a little confused with all this too.
I've been to that blog and that seems simple enough.
It should work on this right? -
firmware - 1.5
kernel - 2.6.27 [email protected] #1
Build Number - CRC 1
Now, this means by phone is rooted, (Basically giving me sys admin rather than root user?)
Which in turn means I can install custom ROM images? Is there anything else this allows me to do?
And is all this permement? Or will it go back to the original ROM on the hardware when I hard reboot?
Sorry for all the questions, I got my phone today .
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
AdamPI said:
That's an original and most up to date UK version, so no you're not rooted. Easiest way is the one-click root, just install, put rom on SD card, run prog, reboot, flash (Read full instructions though).
Having root enables you to have full access, so you can do whatever you like from terminal and applications which require special permissions to run can, some cool stuff can only be done with root.
Click to expand...
Click to collapse
Thanks for the quick reply and I'm not trying to Hijack the thread, (But the OP will probably want to know this too), once I've rooted and installed the new ROM from the boot menu loader thing, how do I go about formatting my SD card to ex2?
I'm looking at this guide - http://forum.xda-developers.com/showthread.php?t=535232
But in this thread - http://forum.xda-developers.com/showthread.php?t=537204 CM himself says not to install APPS2SD. Can you do the format from inside that ROM or does it do it automatically for you?
Yeah cyanogen roms already contain their own method of app2sd, so trying to use another method on top just screws things up.
All you need to do is partition the card, then when you reboot it will see the partition, move your current stuff over and be good to go.
Follow this guide for partitioning from recovery console: http://forum.xda-developers.com/showthread.php?t=534714
So what is the difference between this and the simple root process. It seems the new unrevoked will allow you to install custom roms, so if that's all you want, is there a reason to do the simple root?
Also, in the faq- it says it only unlocks nand flash long enough to put the custom recovery (clockwork) on the phone- what are the implications of that? I was confused because it says with clockwork you can still do nandroid backups. So what do you lose out on with NAND still being locked
i just saw their update and looks like the main page has stopped working...i prefer the original app simple root method as that is what i have on my evo now. its easier than flashing, etc etc. and suits what i need.
IceCreaMan said:
i just saw their update and looks like the main page has stopped working...i prefer the original app simple root method as that is what i have on my evo now. its easier than flashing, etc etc. and suits what i need.
Click to expand...
Click to collapse
It doesn't seem to work with my phone with the latest software update.
Bobby_C said:
It doesn't seem to work with my phone with the latest software update.
Click to expand...
Click to collapse
I think the root and clockworkmod recovery are both done using the unrevoked3 program, on your computer. No more rooting from your phone's browser.
If you're going to do this, you might as well just do the simple root, just don't update your wimax radio because you'll be ****ed-4g-less.
So when a device is NAND, it means after each reboot the kernel and any modifications to it will be put back to normal right? But does this mean that an application could gain root for the session, and keep it until its rebooted?
Or in order for the root to work, you would have to reboot the device? at which point your kernel goes back to normal and you lose root?
Also if the above is right, and you can temporary root phones, wouldn't that mean ALL android devices are prone to temp rooting (doesn't matter if its htc, samsung, etc..) since the kernel is all the same on the devices?
That's WAY old scroll. Unrevoked and yer done.
Last-Chance said:
So when a device is NAND, it means after each reboot the kernel and any modifications to it will be put back to normal right? But does this mean that an application could gain root for the session, and keep it until its rebooted?
Or in order for the root to work, you would have to reboot the device? at which point your kernel goes back to normal and you lose root?
Also if the above is right, and you can temporary root phones, wouldn't that mean ALL android devices are prone to temp rooting (doesn't matter if its htc, samsung, etc..) since the kernel is all the same on the devices?
Click to expand...
Click to collapse
NAND is the type of memory the evo uses, the NAND lock just means the radio locks certain parts of it from being changed so only the recovery and bootloader have access to it. You can get a temporary root with the NAND locked but you won't be able to change anything on your bootloader, recovery or system partitions.
xHausx said:
NAND is the type of memory the evo uses, the NAND lock just means the radio locks certain parts of it from being changed so only the recovery and bootloader have access to it. You can get a temporary root with the NAND locked but you won't be able to change anything on your bootloader, recovery or system partitions.
Click to expand...
Click to collapse
don't you need system access to write custom su files? or do you mean the changes wont last?
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
geronimo711 said:
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
Click to expand...
Click to collapse
What is the end result you are trying to get to?
If you are wanting S=off so you can flash custom ROMs.
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/; do that and it will lead you to perma root the easy way.
if you are wanting s=off so you can have complete control over your phone, which will enable the possibility of a brick. including SuperCID, ./gfree and some other goodies...... But this will give you the option to severally screw up your phone including up to a 500.00 paper weight.
http://forum.xda-developers.com/showthread.php?t=858996
If you haven't screwed up the HBoot and the bootloader you can use this to get back to a factory spec.
http://forum.xda-developers.com/showthread.php?t=863899&highlight=level
But if this is your first android, and your first time rooting i would HIGHLY suggest doing alot of reading before you jump in head first. There are alot of people who have tried to do and get stuck. This phone is confusing once rooted with 2.2 ROMs and 2.3 ROMs and different recovery images you need to read and make sure you understand everything before jumping in feet first.
Temp root with visionary is the easiest and safest way, but gfree is pretty simple as well. The hardest bit is getting the drivers and ADB to work, and thats not overly difficult. (remember to use the command "ADB devices" to know if the drives are working) It just matters what you plan on doing, stock root or custom ROM.
There is really only two points that risk a hard brick, flashing the radio or hboot.
The gfree method does not require either, but you can flash the engineering hboot as optional.
The biggest thing with recoveries and ROMs is know that gingerbread based ROMs (like CM7) use ext4 file system and froyo ROMs use ext3. So it is important to use the right version of Clockwork recovery. Use v2.5.1.2 for froyo ROMs and v3.0 for gingerbread ROMs. Soon clockwork mod will support both on the same version.
Just read the instructions well and have all files downloaded and ready to go.
If you want to use gfree and a custom ROM, there is no need to get perm root on the stock ROM first. After the steps that get s=off, just run visionary as temp root with system r/w access and install ROM manager from the market, then use ROM manager to flash a new recovery. Reboot into recovery backup your stock ROM then flash a new ROM.
If you never touch the hboot or radio firmware, then at worse you can bootloop or soft brick the device. That can be fixed with varying amounts of work, depending on the exact issue.
Read and learn how the different parts work, learn how to use ADB and you will be better prepared.
newbie here
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
ibnird said:
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
Click to expand...
Click to collapse
Temp root is just that, temporary. It creates a copy of the essential files in the system partition that it runs from rather than the actual system partition. If you allow it r/w access, (an option you can choose when using visionary) it can uninstall apps that normally can not be. (and more, but causing big changes would require more work on your part)
Because it is temporary, there is no need to get nervous. Unless you are doing some major changes, ones that need a root explorer app or terminal emulator, then you can't really hurt the phone. Download terminal emulator from market and run it, then type in the super user command "su" (no quotes) then hit enter, if the cursor changes to a # symbol then you have root. (you may get a popup asking for root permission, choose to allow) If it works after a fresh reboot, you either ran perm root in visionary, or you have the option checked to temp root every reboot.
S-ON means that the bootloader security is still in place. You need it off to install custom software. While you can root the stock software with S-ON you can not install any software that has potential to brick your phone, so no need to worry at all. If you are really that worried, keep a copy of the stock software on your SD card. Make sure it is named PD15IMG and at any time you get nervous, you can boot into hboot (the bootloader) and it will run automatically. It will wipe your phone and return it to complete stock. The irony is, that flashing this stock image file does things that can brick a phone if it goes wrong. It flashes more than just the OS, it also flashes hboot and recovery as well, and if the process is messed up in anyway like loosing power at the wrong time, it can brick the phone.
Really as long as you make sure you have the phone charged and you follow instructions you should be fine. The only times you can brick a phone to the point it can not be brought back is when flashing hboot and the radio firmware. Both of which you would rarely flash. Hboot only needs flashed to the engineering version once (OEM testing/DEV version) and only if you choose to, as it is not required. The radio will only need flashed if an update for it comes out, and that isn't often, and it is rarely mandatory.
The chance of truly bricking your phone is not very high, unless you just can't follow the directions. Now you can put it into a bootloop or soft brick it. (bootup stuck on mytouch screen) But if you can boot the phone into hboot (vol down + power on) then you can fix it. Even if you can not boot into recovery (an option in the hboot menu) you can even fix that with a good hboot.
theres a video on youtube by mackster its awesome and it gives you all the links very easy to use.
it wont let me post the link but just search root mytouch 4g on youtube and it should be the first or second one.
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
ibnird said:
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
Click to expand...
Click to collapse
Uninstalling an app will not hurt anything. OTA updates will still work fine. You can temp root and then perm root the stock ROM and revert easily. Heck, even perm rooting stock doesn't break OTA I believe.
Voiding the warranty is one of those grey areas. As long as you can revert to stock, then they will never know. Temp root does not void warranty at all, because you do not alter the system files. (unless you want to, and enable the ability to read/write system) Just uninstall terminal emulator and super user apps and there is no evidence.
The only time you might get caught, is if say the screen stops working, and you can not see to revert back. Though even then, just putting the stock OTA image on the sd card then booting up the phone in hboot will restore without needing to actually see anything. It does ask for confirmation to restore, just wait several minutes then hit the power button and it would do it on its own.
The set of circumstances needed to prevent you from restoring to stock, are rare. Basically a borked hboot or radio firmware, and you never need to touch those to get full root and custom ROMs. If you never touch them, the chance of issue is almost zero.
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
goldfish524 said:
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
Click to expand...
Click to collapse
You dont need apps2sd, as the mytouch 4g has Froyo installed, and you can move some apps to the SD card. Just go into settings-Applications-chose the applicaiton you want on your SD card, and look for "move to SD". If it's grayed out, then you cant move it.
Also download appfreezer from the market, and just "freeze" the bloatware. That's what I do, and it gets rid of those annoying looking apps they installed.
Question about clockworkmod
OK i just rooted my phone, flashed the rom, and installed all the goods... it works perfectly and looks great.
Ty for all the guides/ instructions.
My only question is about the clockworkmod. When I turn off my phone and plug it in to charge the recovery screen always appears when off and connected. Is this suppose to happen? Or is there a solution to this?
If there is a solution can some one post a link or provide instructions so it doesn't constantly boot to clockworkmod recovery.
Thanks.
The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.
Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache
KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC
Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X