Database Users

New one click root program

so i don't post on this site ever, and i know next to nothing about rooting a phone aside from what i read
i just hit it up this for info on rooting my atrix i aquired... long story short i found a beta program called rescue root that works
i just rooted my bell atrix 4g, gingerbread 2.3.6, build 4.5.2a-51_oll-17.8
all i did was install motorola device manager program from the moto site, installed rescue root, connected my device and ran the program and rooted in under 10 mins, confirmed by root checker app, titainium backup and other various app requiring superuser permission
also i did not have to unlock the boot loader before i ran the program

robyn402 said:
so i don't post on this site ever, and i know next to nothing about rooting a phone aside from what i read
i just hit it up this for info on rooting my atrix i aquired... long story short i found a beta program called rescue root that works
i just rooted my bell atrix 4g, gingerbread 2.3.6, build 4.5.2a-51_oll-17.8
all i did was install motorola device manager program from the moto site, installed rescue root, connected my device and ran the program and rooted in under 10 mins, confirmed by root checker app, titainium backup and other various app requiring superuser permission
also i did not have to unlock the boot loader before i ran the program
Click to expand...
Click to collapse
u still have to unlock to flash custom roms. so it dosent really matter

rev.
you have to unlock the bootloader to flash roms? i must have misunderstood what i read...
i thought you had to unlock the bootloader first in order to root... not root in order to unlock the boot loader, guess i'll hit up moto's website again as theres a unlock your boot loader option there
but either way, just thought i'd share a new quick root method with the world that caters to those less technically gifted like me
i guess they only just released this beta and turns out the developer is actually just across town from me which is kinda cool
forgive the newbish excitment i only just snagged this phone off ebay since i bricked my old android by deleting things i shouldn't have without backing up first
Hai_Duong said:
u still have to unlock to flash custom roms. so it dosent really matter
Click to expand...
Click to collapse

I think you have it all completely mixed up.
You have to unlock the bootloader to be able to flash custom ROMs. Rooting is completely separate and has nothing to do with anything else - you don't need to unlock anything to root, and rooting won't help you get anything else (unlocking, flashing) done. It is literally completely separate.
It would probably help you to do more reading on the subject. Getting informed and educated can only ever be a good thing.

[Q] reset system status on AT&T GS4

My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?

scmagee said:
My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?
Click to expand...
Click to collapse
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.

reset system status on AT&T GS4
Plexicle said:
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.
Click to expand...
Click to collapse
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.

scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.

scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
Using the search function and doing some reading would have revealed that this subject is being or has been discussed in several places in the AT&T S4 forum already. I mention this in case you are interested in reading about what has already been discussed about the issue. However, this thread goes a lot more in depth about the issue...
http://forum.xda-developers.com/showthread.php?t=2303022
It is just a beginning but if you have any knowledge to contribute to that thread or if you know anyone that can help it would help greatly.
In short, an APK named Sysscope scans the phone at bootup. There are a few other processes that support sysscope as well. Sysscope uses several methods of checking the phone to see if certain parameters have been changed, deleted, or modified. If it shows that they have, the next boot will show "custom" status and the unlock icon. It appears that a method was found to keep the Verizon S3 Official, but the method needs to be figured out and implemented on the AT&T S4. That is beyond my capabilities. The thread I posted and the threads linked in that post describe this all more in detail.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
Plexicle said:
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.
Click to expand...
Click to collapse
The bootloader remains locked (unfortunately). Dan's exploit sidesteps the bootloader to allow for custom recoveries and kernels but the bootloader itself remains locked. The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.

scott14719 said:
The bootloader remains locked (unfortunately). The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.
Click to expand...
Click to collapse
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.

Plexicle said:
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.
Click to expand...
Click to collapse
Thank you.

The custom status seems to be a scan at the moment. If you Odin back to stock firmware and start from scratch, you will be back to Official status. AOKP doesn't run this check so as long as you Official you can flash AOSP and AOKP freely I'm pretty sure and be safe from the ugly custom status.

Try this:
http://forum.xda-developers.com/showthread.php?p=41955085#post41955085

Root/Recovery issue

Alright, so I finally found a Razr M that has the bootloader unlocked and went to root it and it wouldn't root. I booted into recovery and it has TWRP installed on it so I tried to install CleanRom and it failed and said something about it tried to patch something but I can get a picture if need be.
I'm kind of at a loss on what I need to do, bootloader is definitely unlocked since it has the splash screen and it says unlocked on the black screen (sorry don't know what it's called). It's on baseband .81P so if there is anything anyone could tell me I would greatly appreciate it.

collins521 said:
Alright, so I finally found a Razr M that has the bootloader unlocked and went to root it and it wouldn't root. I booted into recovery and it has TWRP installed on it so I tried to install CleanRom and it failed and said something about it tried to patch something but I can get a picture if need be.
I'm kind of at a loss on what I need to do, bootloader is definitely unlocked since it has the splash screen and it says unlocked on the black screen (sorry don't know what it's called). It's on baseband .81P so if there is anything anyone could tell me I would greatly appreciate it.
Click to expand...
Click to collapse
Which tool did you use to root? The first time I tried to root right after getting the phone, I had to wipe cache/dalvik and FDR. Also, since your BL is unlocked, you should just be able to flash a SU binary in TWRP and get root. I know there's one running around here somewhere.

RikRong said:
Which tool did you use to root? The first time I tried to root right after getting the phone, I had to wipe cache/dalvik and FDR. Also, since your BL is unlocked, you should just be able to flash a SU binary in TWRP and get root. I know there's one running around here somewhere.
Click to expand...
Click to collapse
I tried the Batman utility and also motofail2go

collins521 said:
I tried the Batman utility and also motofail2go
Click to expand...
Click to collapse
Motofail was for 4.1.1 and Motochopper was for 4.1.2 (this was included in the utility 1.20). Sometimes these things have to be run multiple times, at least that's what I've seen.
Here's Chopper by itself: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/ . However, you might have to wipe to get this to work, I did anyway. Before it comes to that, I would try to flash SU in recovery.

Thanks, flashed the SU Binary's and I'm up and running..now I have root and all is well in the world haha

Awesome! Been trying to solve that world peace issue like forever, man! Good deal!
Sent from my XT907 using Tapatalk 4 Beta

Lol now to get a 4.2.2 rom (Well maybe it isn't .2 I can't remember) to actually boot on here...can't seem to get it past the boot animation and I've flashed SlimBean, Chameleon, and another

Trwp not working

Hi guys, i m new to this world but i learned from xda and somehow managed to root my S7 Edge, but the whole purpose of rooting my device was to install Walkman App and Xperia Keyboard in my S7 Edge.
Unfortunately even after rooting i could not use the full potentiel of TRWP Recovery as i could not Install Zips, could not backup or wipe data as it shows 'unable to mount storage' failed to mount data'
requesting you to help me if i may have skiped some important fact.
thank u all.

We cannot install custom recovery due to locked bootloader. Use Flashfire in the play store to flash zips.

Vickyyykaal said:
Hi guys, i m new to this world but i learned from xda and somehow managed to root my S7 Edge, but the whole purpose of rooting my device was to install Walkman App and Xperia Keyboard in my S7 Edge.
Unfortunately even after rooting i could not use the full potentiel of TRWP Recovery as i could not Install Zips, could not backup or wipe data as it shows 'unable to mount storage' failed to mount data'
requesting you to help me if i may have skiped some important fact.
thank u all.
Click to expand...
Click to collapse
Wait... you were able to install TWRP recovery? How?
Is your knox 0x0?

Binary100100 said:
Wait... you were able to install TWRP recovery? How?
Is your knox 0x0?
Click to expand...
Click to collapse
Yeah, I was just about to ask the same thing.

Hi,
Any news or comment about this?
Because i'm reading this article: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-s7-edge-us-sprint.html

MTechRD said:
Hi,
Any news or comment about this?
Because i'm reading this article: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-s7-edge-us-sprint.html
Click to expand...
Click to collapse
Don't know who wrote that, but it's completely wrong. There is the possibility of root with a locked bootloader. Which is the current situation for all US Qualcomm variants. We've had it since the beginning of the month.
There is no possibility of actual custom recovery with a locked bootloader. At all. The closest anyone has come to it, ever, would be something like safestrap. Which we do not have.

LeftyGR said:
Don't know who wrote that, but it's completely wrong. There is the possibility of root with a locked bootloader. Which is the current situation for all US Qualcomm variants. We've had it since the beginning of the month.
There is no possibility of actual custom recovery with a locked bootloader. At all. The closest anyone has come to it, ever, would be something like safestrap. Which we do not have.
Click to expand...
Click to collapse
Thanks!

LeftyGR said:
Don't know who wrote that, but it's completely wrong. There is the possibility of root with a locked bootloader. Which is the current situation for all US Qualcomm variants. We've had it since the beginning of the month.
There is no possibility of actual custom recovery with a locked bootloader. At all. The closest anyone has come to it, ever, would be something like safestrap. Which we do not have.
Click to expand...
Click to collapse
Or Flashfire which we do have. You can still make backups and flash some update.zip files.

[SM-G950W] Running official Android 9 on Samsung S8, help me understand my options (root, custom ROM)

Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!

temuri said:
Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
Click to expand...
Click to collapse
Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
temuri said:
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
Click to expand...
Click to collapse
Depends on the binary version, the screen text in Download Mode should tell you. You can't downgrade the binary, so if it changed from 3 to 4 (for example) and is currently on 4, you can only flash binary 4 firmware, but you can't downgrade to 3.
temuri said:
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!
Click to expand...
Click to collapse
I'll try to put this simply:
Enable OEM unlocking in developer options
Unlock bootloader (wipes data)
Boot device, set up Google/Samsung account, connect to the Internet
Perform a manual update check, do not download update
Check to ensure OEM Unlocking is still visible
Put device in download mode and flash TWRP; immediately boot TWRP, do not allow device to reboot into system, otherwise it will restore the stock recovery
Make sure you flash the Multidisabler in TWRP to disable encryption and recovery restoration
Flash Magisk in TWRP to gain root
Boot into system and set up device, install the Magisk app to manage root.

I would leave it on Pie. Anything below that has nasty vulnerabilities like X helper.
If you want more performance optimize it with Package Disabler or adb edits.
If that doesn't get it, get a N10+, a huge performance and cam increase.
How to read Samsung build numbers

@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
I heard that Extreme Syndicate for S9 series may seem nice. (OUDATED THOUGH TAKE EVERYTHING NOT FOR THE FAINT OF HEART.)

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
Click to expand...
Click to collapse
Are you saying it can't be unlocked? Or simply that it is not unlocked?
The bootloader unlock has nothing to do with the Android version. Whether you can unlock it might though.
temuri said:
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
Blackhawk is a cranky old curmodgeon, don't listen to him. Totally kidding, he's a smart guy.
So let's focus on Step 1. Enable Developer Options, do you see the OEM Unlocking toggle?

@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.

temuri said:
@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.
Click to expand...
Click to collapse
Your device is set up, you have a Google account added, and you're connected to the Internet?

V0latyle said:
Your device is set up, you have a Google account added, and you're connected to the Internet?
Click to expand...
Click to collapse
that's correct.

temuri said:
that's correct.
Click to expand...
Click to collapse
Okay. Current firmware version?
Settings > About phone > Software information

Baseband version: G950WVLU8CUF3

temuri said:
Baseband version: G950WVLU8CUF3
Click to expand...
Click to collapse
Okay, so you're on the latest update. See if you can download and flash CSL1
If that works try AQD9
Next time you're in download mode, either take a picture of your screen or post what it says for SW REV or RP REV

consider downloaded - 6min left.

should I use standard ODIN to flash it?

Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh92 for US/Canada Samsung BL unlocking

webhook said:
Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh62 for US/Canada Samsung BL unlocking
Click to expand...
Click to collapse
uh-oh... can you please explain the "low bit" part and how do I check it?

@V0latyle
An attempt to flash CSL1 failed with:
FAIL! (Auth)
Complete(Write) operation failed

Disregard message

ouchies. was too quick and contacted the guy already

temuri said:
ouchies. was too quick and contacted the guy already
Click to expand...
Click to collapse
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected] Before Starting...
forum.xda-developers.com
I've tried this with my T-Mobile US GS8+. Works like a charm. Since you are on Bit 8 the stuff there is compatible with your phone. However you may brick stuff so be careful
You can join their Telegram chat for more information.