Develop Bugs

How do you root properly and other questions.

I am coming from a Samsung Moment with root, custom recovery, etc and I never had this many problems, what am I doing wrong or not understanding?
1. Why do I need to download or have an adb shell on my computer if I can install connectbot and do commands through the phone?
2.What is the proper method for rooting? My understanding is basically this:
A: Get Phone
B: Do not do the OTA update.
C: Download Toast's root (pc36img.zip)
D: Flash pc36img.zip
E: Done?
3. I can't get wireless tethering working using this method, and I have to download unrevoked's root to get it working.
But then again, is that even a root, or is it just for SU access?
4. How do I get the bug fixes from (1.32.651.6), and still maintain root? I downloaded the sprint ruu_1.32.651.6.exe provided in the forums and enjoyed having my phone not error and fc every 10 minutes, now I hear if I did that I just closed off toast's rooting.
5. Is there like an easy step by step instruction on how to make a custom recovery, nandroid backup, how to check for root, etc?
6. Did I kill my chances of root by installing and using ruu_1.32.651.6.exe?

Great first post.
All is explained in the dev forum.

There is no easy step by step method that I can find, sorry. A lot of threads and instructions assume that you have been using and flashing htc devices for a while. I'm coming from the moment and it's completely different.

I agree, it is confusing. I used toasts method and thought my phone was rooted until I tried Titanium Backup and it told me it couldn't get to root.
I figured I'd just wait til the rooting process is more stable. Sorry, I know this doesn't help

[Q] Questions about preparing to root

I'd like to root my Acer A100 and think I know how to do so, this is not a question about HOW to root.
I got basic Linux knowledge and good PC experience but before rooting I'd like to ask what I can do to prepare myself for future events such as;
- I get a bad ROM and it appears bricked, or
- A new update comes out and my root is preventing me to get the stock upgrade.
In essence,
1) is there anything I should do BEFORE I root to protect myself (don't think I can save a recovery image unrooted?), and
2) as soon as I AM rooted, any steps I should take to protect my working ROM (like, how do I take a full system backup, can I take an image of my ROM to flash to?, is there any tool(s) I need to put on asap so that if things go bad I got them.
I've run DeviceID so I have my DeviceID noted down.
Any help/thoughts would be greatly appreciated!

Root without unlocking bootloader someday?

I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta

Why not just unlock? You can always lock it again if you want to return to factory.

^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:

Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.

Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.

sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.

sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).

Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.

Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.

Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail

[Q] MC2 to MK4 Question

Normally, if I do a search with creative enough verbage, I can find the answer here however right now that's not the case.
I have a 2 part question, but first, my device info:
- Currently I am stock rooted with TWRP recovery
- Model: SPH-L900
- Android Version: 4.1.2 on MC2 (both baseband and build)
- I was rooted when I first got the device, and had to unroot, update and reroot (using toolkit I believe)
#1. I have been seeing mixed information out there about this update (MK4) and was wondering if someone can just advise if KNOX is actually a part of the update (either OTA or LORJAY589's)? I would actually like to be able to have KNOX as it would be handy to use my device more for work.
#2. I am a fan of having my device rooted, personally I just like the ability to actually back it up fully, but there are other things that are nice too. The actual question is, if one of the updates does have KNOX in it, and its useable, is it still possible to have the device rooted?
If these could be answered, relatively simply, it would be greatly appreciated. I'm a bit of a n00b, but I have absolutely no issues with flashing my device using any of the standard methods, but a brief walkthrough would be appreciated (if only for the methods used).
Thanks!
Edit:
So here are the steps that I want to take, if someone can advise me if I'm being stupid based on my questions that would be great:
download:
MK4 4.3 SPH-L900 Odex Full Rom Rooted (thanks again LORJAY589),
Follow the following steps (Thanks cullenmq1):
1. Download full rom rooted (either deodex or odex)
2. Download wifi fix .rar
3. Go to recovery (doesnt matter both twrp and cwm work)
4. Make a rom backup just in case
5. Full wipe (not necessary but recommended, we dont need people bricking notes)
6. Flash full rom
7. Flash wifi fix through odin (must unpack rar first and mobile odin does not work with this)
8. MAKE SURE TO THANK LORJAY589 FOR HIS AWESOME WORK!
Then basically recover all my goodies with titanium backup / re-downloading... and from there I should have NO issues with WiFi or anything else as far as anyone here is concerned (if samsung screwed something up, I'm not about to blame a XDA Dev).
Sound reasonable?

umm... no
I'm not a super pro dev. but when I first read lorjays post. he was very specific about what to do. he said not to listen to anyone else's instructions but his own. that included flashing through cwm. not twrp. he said it doesn't work. and I saw for myself how many people where writing and asking questions about how to fix their phones because something went wrong. they forced him to post another comment saying do not listen to anyone elses instructions. follow mine and everything will work fine. so if I were you that's what I'd do. I know cause I did. and unlike a lot of dummy's who where asking for help. I had no problems after installing

Help with rooting Htc M8 marshmallow

Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help

Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.

redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?

Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.

1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.