Database Users

[Q] First time

Hello, I bought my Nexus 4 about a year ago and was always hesitant on trying to "root" it. I am completing new to this and have no idea what to do. The only thing I have come close to this sort of thing was jailbreaking an old iPhone. It was extremely straight forward, I download & install 'X' app. Reboot, app runs and I simply follow the instructions on screen (a series of button pressing). The Nexus 4 seems more complicated but with all the feedback, I'm really curious to see what can be done with a rooted android.
I've read through a few threads but I'm still unsure whether I've successfully completed each step properly. The mainly followed the "Ultimate Nexus 4 Root guide"
1. I installed the ADK onto my computer. (Have no touched the folder ever since)
2. Unlocked bootloader using the no-data-wipe method.
3. Done every step until the "install custom recovery"
It feels like most of the guides are a little outdated because I can't seem to fully follow each step. One example is when I was installing towelroot, the next step is supposed to reboot my device. However, the towelroot app itself indicated my device was succesfully rooted despite not having anything appear on my screen or my device restarting.
Basically, can anyone help/provide a step-by-step guide for a brainless monkey like myself? A video would be a lot better so I could pinpoint where my mistakes are exactly.

It's right that your phone is rooted now, with the latest version of Towelroot it's no longer necessary to reboot the device (afaik). If you want to have a step by step guide check out my guide on how to root the device without wiping data, you may find the link in the stickies

There are plenty of apps on the playstore to check if your N4 is rooted or still not, you can download and try this one https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck

One Click Root For Moto G5 Plus?

Hello,
Recently, I purchased the G5 Plus & am looking to just 1 click root it for the time being. I've seen a lot on Towelroot but can't find any working downloads or further information regarding it.
Does anyone use it & if so, how is it?
Thank you!

Dyke67ny said:
Hello,
Recently, I purchased the G5 Plus & am looking to just 1 click root it for the time being. I've seen a lot on Towelroot but can't find any working downloads or further information regarding it.
Does anyone use it & if so, how is it?
Thank you!
Click to expand...
Click to collapse
I wouldent go anywhere near it do u not have a PC ?

joeeboogz said:
I wouldent go anywhere near it do u not have a PC ?
Click to expand...
Click to collapse
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.

Dyke67ny said:
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.
Click to expand...
Click to collapse
U don't root with computer only flash twrp then flash root with twrp

Dyke67ny said:
Yes, I have a computer but like I had mentioned previously, I had read of numerous complaints of wifi not working after rooting via the computer connection.
Click to expand...
Click to collapse
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.

acejavelin said:
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.
Click to expand...
Click to collapse
I have successfully flashed & rooted the Moto G5 plus via the computer & all is working except I now have a few issues.
1. I receive the following message upon restarting the phone "Your device has been unlocked & cant be trusted message"
2. The camera no longer works as I receive the message "Camera keeps stopping."
3. "ADB Unauthorized" message when trying to connect back to the program.
Are you familiar with any of these issues?
Thank you!
P.S. I rooted using the "Moto G5 Toolkit"

acejavelin said:
Back in the beginning of this device, rooting required flashing a patched kernel... if you had a slightly different radio version than the kernel was intended for, this could occur.
This has not been an issue for some time, at least not since Magisk and SuperSU officially support this device now. I would recommend Magisk though.
If you were going to have issues, it would more than likely be with a One-click root method rather than the documented and proven methods of doing it manually.
Click to expand...
Click to collapse
As I've already rooted the phone using Motorola software, I did read that installing Magisk would fix the camera not working issue. I'm not familiar with this as I had mentioned in the first writing, it's been awhile since I've rooted an android device (last 3 devices I did, 2 required a computer & the other 1 used Z4root <- awhile ago!)
Am grateful for your help!

OK3: any modifications at all possible?

Hello,
A few months ago, I was able to successfully root my AT&T S4 (SGH-I337, builld LRX22C.I337UCSGOK3) using KingRoot. The KNOX warranty bit was not set at the conclusion of the root process.
After wrestling with storage problems, including the "system memory" taking up 6.29 GB out of the meager 16 GB that is on this phone (preventing practically any Google Play updates from occurring, as the available space would always dip below 500 MB periodically), as well as performance problems (very long delays for some touch events and a general resentment of TouchWiz), I decided that enough was enough, and I decided to change my ROM/OS out for LineageOS.
LineageOS offers builds for jfltexx, which is reported to work for jflteatt since they are similar enough. I am not really willing to try "older" builds, as one of my goals is also to bring the security of the operating system up to date, so I am not exactly inclined to go for old CyanogenMod builds. The LineageOS install guide stipulates that I install TWRP to successfully install the OS via a supported recovery; however, the message SECURE MAGICCODE FAIL: recovery appears, as the upgrade process seems to be expecting something signed by Samsung (right?). Other guides warn that the stock recovery only allows stock OS installation and not custom operating systems, so I decided not to try that route. This effectively prevents me from installing LineageOS due to a problem that is inherent in OK3.
Why did I make the mistake to install OK3? More than a year ago, I decided to do the final update that AT&T pushed out for this phone. Thinking that it would be something significant, I went for it, only to find out months later that it was a minor update whose purpose was also to add an additional lock to the bootloader. As this phone is "fairly old" (is 2013 already considered ancient times?), I have not found many guides that cover OK3, and those that do pertain to either rooting the S4 (already done) or something about downgrading (but I can't really do that, seemingly due to the OK3 lock-in). Oops.
That said, is there any hope to bring more life out of my phone, or is it time to throw the phone out and buy a Pixel or related product like any typical consumerist would do? My goal is to move to another OS to end the storage problems and other quirks of this phone that I have grown to deplore; that is all I wish to attain.
The phone is relatively reliable: it had ~1200 hours of uptime before I had to reboot it a few days ago to fix a data connectivity problem. The battery is also very manageable and can last a day and a half in regular use, but it can last 2-3 days under maximum power-saving mode.
I have read the rules and done some research on this forum, among some others. Thank you for your assistance.

Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.

audit13 said:
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
Click to expand...
Click to collapse
I see; so I was already screwed when I had OK2?

oldmud0 said:
I see; so I was already screwed when I had OK2?
Click to expand...
Click to collapse
Yes, anything past MDL has the bootloader flaw patched. MDL firmware and below have a flaw in the bootloader that allows loki doki to be installed bypassing the bootloader lock so you can install TWRP recovery and custom AOSP ROMs.
Since you're on OK3, you're forced to use safe strap recovery and can only install custom touchwiz ROMs like golden eye and albe95.
If you want to read up on the MDL bootloader, I have written a guide here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122

My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.

oldmud0 said:
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
Click to expand...
Click to collapse
If you want away from touch wiz, I think there's a Google play edition ROM for the galaxy s4 that you can use with OK3, but I am not too sure. I would just check the galaxy s4 ROM section for it. I'm on the MDL bootloader which allows me to use TWRP, so I don't know too much about safe strap recovery.

Even if one wanted to do a TouchWiz-based ROM, I don't think we on OK2/OK3 even have the option to install SafeStrap, so far as I can gather
Hold the phone, I think I've found something. Evidently we can Odin back down to NB1 and go from there! Experiments, here we come.

Yes, NB1 is as far back you can go I believe without bricking your phone.

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.

Question How to update rooted Nothing Phone 1?

Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).

Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022​

Can't help you unfortunately, but let me know, after you manage, if your vibration intensity went down at all after the update or if it's all just my brain playing tricks on me.
FWIW, I don't have any issues with the latest version, except maybe lower vibration intensity, though that might just be because I started wearing a case more often.
Also the updates apparently have different features in different regions (for example, EEA had optimized battery ever since I first received the phone with version 1.1.2). They don't document the differences so it's possible other regions are buggy-er

This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!

Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com

Add offlineOTAUpgrade from activities tab (like nova launcher), and download the full rom, simply update, and unfortunately it reboots before magisk can install to unused slot, so Fastboot boot rooted boot img and do a full install

Pho3nX said:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. Unfortunately, that guide is missing all the commands and clearness.

Pheggas said:
Thank you. Unfortunately, that guide is missing all the commands and clearness.
Click to expand...
Click to collapse
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?

Pho3nX said:
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?
Click to expand...
Click to collapse
Hi @Pho3nX (and @Pheggas )
It's the same "my" problem...
I'd like to update me NP1 (rooted), waiting next custom roms that unfortunately are not ready
I'm not so smart with modding and we appreciate some detailed info/guide, step by step, with full commands to write, avoiding dangerous bricks...
I've stored in a folder my first boot.img and the magisk.img but I'm afraid to do some mistake with CMD strings...
Thanks for Your cooperation and... patience...
Ciao

notexcited said:
This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!
Click to expand...
Click to collapse
this worked great for me the last few times, but this method no longer works for me after I installed version 1.1.4. can someone help me?

+1 for a detailed list of possible methods to update when rooted.

Sib64 said:
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022​
Click to expand...
Click to collapse
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.

Pheggas said:
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.
Click to expand...
Click to collapse
Wait for full package and follow the same tutorial