Hey Guys -
I have an HTC One A9 which I recently upgraded to Nougat (AT&T - 2.18.617.10). The phone has an unlocked bootloader, is s-off, and was previously rooted. I have not re-rooted or even applied TWRP yet, but will soon.
My question is - what's the best way to root with phone & Nougat that ensures Internal Storage still works without going through a long process? After purchasing the phone about a year ago, I found that after rooting any time I tried formatting an SD for internal storage, it failed. The workaround was to re-install the RUU, back up the boot partition, root the phone using SuperSU, back up it's boot partition again, extract both boot partition backups, swap a couple of files over to the rooted backup (verity key), re-wrap the rooted one, then flash the newly modified & rooted boot partition back to my phone. - whew.
Surely that process isn't still required! If not, though; I'll still go through it if its the only way I can achieve root with Internal Storage support.
Thanks!
Anyone have suggestions for this? Thanks
Related
So I flashed M p1 and then updated to p2 without need of root.
Now I just needed that for a particular reason and I used NRT root option, but it was too late when I realized that it was flashing the stable version of SuperSU and would not work. Since then I've flashed 2.49 (beta) one that I read somewhere that should clean the files from previous installations, but it's not booting at all.
So, any advices for me? Basically I want to keep the files on SD and applications.
So, what should I choose? Deleting SuperSu files from Recovery? Flashing only System back? Any other method available for my scenario?
Thanks,
Alex.
darkeingel said:
So I flashed M p1 and then updated to p2 without need of root.
Now I just needed that for a particular reason and I used NRT root option, but it was too late when I realized that it was flashing the stable version of SuperSU and would not work. Since then I've flashed 2.49 (beta) one that I read somewhere that should clean the files from previous installations, but it's not booting at all.
So, any advices for me? Basically I want to keep the files on SD and applications.
So, what should I choose? Deleting SuperSu files from Recovery? Flashing only System back? Any other method available for my scenario?
Thanks,
Alex.
Click to expand...
Click to collapse
Flash the latest twrp recovery. It has mtp support, so if your OS supports mtp you can get your files from the sdcard (internal storage)
I am caught in a bootloop after attempting to root using the following process.
Using Odin3 v3.10.6, I flashed the following:
n915t-cwm-recovery-6.0.5.1(1128).tar - THIS MAY HAVE BEEN AN ERROR. SHOULD I HAVE USED "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"
I did a full backup to my phone's external SD card from cwm-recovery-6.0.5.1.
I then flashed both the files below without rebooting in between. I did not wipe any cache or data.
Emotion-TW-nightly-r23-RC1-SM-N915T
UPDATE-SuperSU-v2.46
The phone locked when I rebooted and would not move past the first black screen.
I pulled the battery and rebooted to recovery.
I did a restore of my backup that appeared to complete successfully.
I got a message asking to root the phone. I said yes, then rebooted.
Now stuck in a bootloop.
Hoping I can recover from this?
Root only with extra Kernel
When recovery asks to install root at the end, hit no. Thats your issue. You already installed supersu, so you've already got root. Personally I prefer stock kernel, with the latest beta supersu, you can still get root. With Universal init.d app, you can still get init.d support. With a custom build of xposed for Samsung lollipop, you can still get xposed. There's even a special version of viper audio. So yeah all you lose is the overclock ability.
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
rootnooby said:
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
Click to expand...
Click to collapse
There have been reports that the emotion r23 kernel is finicky, some work soem dont. Try another kernel or older version. That could be toir problem.
Sent from my SM-N915T using Tapatalk
Right guys the information in here is vast but a little confusing.
Few posts say there's root and custom recovery for locked Bootloader and some say different.
My question is this. My daughter has a D2303 With 8gb of storage and can't even install 2 of her favourite apps.
Is there a way to root on a locked Bootloader? If so can I flash TWRP? And then say RR / Lineage / CM? Can I flash Xposed and get what I need?
As I need either foldermount or adopted storage so she can actually make use of this phone and not get angry at the 'no space' after installing 1 game and taking 5 pictures.
TLDR:
LOCKED BOOTLOADER
NEED - Way to adopt storage or enable 'foldermount'? Or xposed?
Thanks for the hints.
You can easily root with Locked BL and install TWRP by using eagle root tool by @linuxct
Just search for it in the android developement section
And for CM/RR/LOS it will not ever happen on locked BL
For xposed you cant do any thing with stock rom but you can flash Z5 STYLE by linuxct too, Xposed works fine there.
Goodluck.
On my d2303 (5.1.1) I used KingRoot to root the phone because the other methods were too much hassle at the time (coul'd be different now). Then you can get custom recovery from here https://forum.xda-developers.com/xperia-m2/development/d2303-philz-touch-recovery-6-t3047492.
Optionally after you install the custom recovery, go into CWM recovery (press camera button when the blue LED lights up during boot) and select reboot system. You should get a message that the phone may not be rooted. Select Yes - root the phone and it will install SuperSU. After it reboots you can get rid of KingRoot.
As for the storage problem I use Link2SD pro with a second Ext4 partition on my SD card but I think with new versions of Link2SD you can use the main FAT partition but I've never tried it myself.
The only problem I'm facing right now is that SuperSU bugs me about a binnary update but if I do the update the phone gets stuck in a bootloop :-\... Root still works though...
Same issue. Did you find a suitable solution?
Find myself in the same situation, but with a D2403 model. Did you find an appropriate solution for the memory partition?
Hazeno said:
Right guys the information in here is vast but a little confusing.
Few posts say there's root and custom recovery for locked Bootloader and some say different.
My question is this. My daughter has a D2303 With 8gb of storage and can't even install 2 of her favourite apps.
Is there a way to root on a locked Bootloader? If so can I flash TWRP? And then say RR / Lineage / CM? Can I flash Xposed and get what I need?
As I need either foldermount or adopted storage so she can actually make use of this phone and not get angry at the 'no space' after installing 1 game and taking 5 pictures.
TLDR:
LOCKED BOOTLOADER
NEED - Way to adopt storage or enable 'foldermount'? Or xposed?
Thanks for the hints.
Click to expand...
Click to collapse
Hi there, I'm having no luck finding a solution to my problem anywhere.
I'm using a Galaxy S7 running Oreo (I know, old school), and like many phones, it came with a bunch of apps that can't be uninstalled unless you have root access. So, I installed TWRP, and then Magisk v23, and then I installed a root uninstaller in order to remove the apps in question.
However, I use Revolut and an app for the bank I'm with, and so while my device is rooted, I am locked out of both.
What I want is to have the disable-only apps gone, and my device unrooted and back to normal so I can use Revolut and said banking app.
I believe uninstalling Magisk should unroot the device, but without Magisk installed, I can't boot into the system because of TWRP and the whole dm-verity thing. So, I want to replace TWRP with the stock recovery, which, if I'm correct, should achieve the desired outcome.
I downloaded the exact firmware for my phone from sammobile, and the recovery file can be extracted from it easily, but I don't really know how to go about flashing said file, or even if I can. Odin isn't working for me.
I tried flashing the whole "AP" file via Odin (the latest version), but that restored the device back to it's factory state, disable-only apps and all.
So can anyone help me with this? Or is what I want to do here even possible? I'd really appreciate some input / advice. Thanks!
P.S. maybe you can tell, but I'm kind of a noob, so apologies if I'm overlooking something obvious.
Android's recovery where it doesn't matter whether it's Stock or Custom can't be used to unroot Android if it got rooted by TWRP and/or Magisk this because phone's boot.img got tampered by those: you'ld have to completely re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Okay then, thanks for explaining.
Just to be clear, what you're saying is that it isn't possible to unroot a device and then restore just its stock recovery (to replace TWRP). You cannot undo modifications made to boot.img and therefore must re-flash the stock firmware?
What I do with unwanted system apps on other android phones is to remove the .apk from /system by booting into recovery and using the shell/adb with u**x commands (actually move them somewhere they can't be seen by the O/S with mv command).
Also when faced with dm-verity, Magisk just modified the boot.img
and changes fstab to take out verify from system mount & patches init and removed /verity_key.
I was able to uninstall Magisk (only phone mod was unlocked boot loader allowing custom boot over usb).
Hello! I've been rooting and installing custom ROMs for years but it's been a long while since I last did it, I got a oneplus 8 global (IN2015) late last year, unlocked the bootloader as soon as I got it out of the box since I knew eventually I would want to flash some stuff. but I have kept it stock this long. Running latest Oxygen 11 android 11
Since I want to start flashing some kernels or roms I wanted to ask about making a backup since I've never had a phone without sd card slot where I would usually store backups.
Can I still use titanium backup to keep all of my apps/data/photos/videos and the state they are in, store it in my pc , then go about flashing a custom Rom and then bring my titanium backup back into the phone and restore everything?
since I'll be installing custom roms based on android 11 I believe it will be fine with no conflicts? or does it matter that my apps were installed in Oxygen OS?
that's what I used to do with older phones anyway. is there a way to flash a rom while having the titanium backup still in storage since most roms require full whipe when clean installing them?
Recently twrp added official support for OP8 and when I open the official app it recognizes my phone as instant noodle but when I click search for phone it says it can't connect to the server? should I flash official twrp from the app or via fastboot? which I'm also quite rusty with.
any tips for a step by step would be appreciated
Hello, I was in the same boat as you since I came to the OP 8 from a Galaxy S4. Titanium backup should work for what you want to do, as long as the custom rom is also based on A11 (disclaimer: I haven't tried it; I'm running rooted stock OOS 11 with a custom kernel). If the rom you want to install requires a data partition format, you can't keep the backups there during the flashing process. If it only needs a data wipe / factory reset, everything in the sdcard directory (also known as /data/media) should be preserved.
I'd say just flash TWRP in fastboot. Flash it to both recovery slots, and read up on how flashing works with A/B slot devices if you aren't familiar, since you'll need to know about it when flashing roms also. It's a big difference from what I was used to with older devices.
Thanks for the reply, yeah I was thinking of just going with a custom kernel since I have so much stuff going on the phone I find it really a chore to backup, but still might want to try it.
What kernel are you using and how are you liking it ?