Develop Bugs

[HOWTO] Software Unlock; How to unlock Bell Galaxy S Vibrant i9000M

Now that we have enough people with the new version on hand already.
It's time to setup this topic.
The aim obviously is to unlock this the Bell Galaxy S Vibrant i9000M
There are possibly 3 ways to go about this:
1. Software
2. Hardware
3. Pay $75 the carrier and get the unlock code after 60 days of purchase, or until some online unlockers gets the code, which ever first.
4. Pay $35 to rhcp0112345 for the hack unlock method
5. Self Hex Hack unlock method
Past experiences in the PalmOS world leads me to believe it should be possible to be unlocked via software/firmware, so rooting the phone will be the first thing to do
For hardware unlocking we'll be able to confirm once the iSim I've ordered arrives next week more or less
Bell will not provide the unlock code until their "exclusivity" expires which is roughly November, that's when Fido/Rogers will get their own locked version for sure.
So, I'm inviting any Android/Mobiles developers to pitch in with any ideas or if they know more or what to look for, change edit, hack replace, flash, etc.
That's why i bough this device, it'll be a guineapig to possibly find the software unlocking method (flashing a ROM count as software)
Stock Bell firmware:
PDA/Phone: i9000ugjg9
CSC: i9000bmcjg9
WARNING: for anyone reading this DO NOT use the firmwares for the USA Vibrant / Captive, the Bell Vibrant is closer to the i9000 than to the USA variants
- Update 1 -
Adding unlock bounty! it actually started on the SGS Captivate subforum http://forum.xda-developers.com/showthread.php?t=739201
Condition to hit the jackpot, it must be unlocked via software ROM flash, SPL, or something along the line.
Lets all pitch in to make it work for all the SGS phones.
List of members pledge & donation:
AllGamer paid "unlocked" via ismartsim then by SGUX
MKVFTW withdrawn he paid $75 to Bell way to get it unlocked
SS2006 $25 payment pending
decepticon paid unlocked by rhcp0112345
BA_Flash_GOD paid unlocked by rhcp0112345
- Update 2 -
rhcp0112345 found out how to hex hack unlock the phone, it requires a file dump and a $35 fee.
The bounty would still apply for anyone Developer able to release a ease to use software unlock for all XDA member at no charge, but if you can't wait you can go with rhcp0112345 solution or the self hack solution.
- update 3 - [BOUNTY] goes to
rhcp0112345 for finding the hack, and allowing rbnet.it and marcopon to create the SGUX tool for all of us.
Please donate to our XDA members that made it all possible for you.
AllGamer for jump-starting this project and providing the initial bounty, and for his regular contribution in the SGS forum
rhcp0112345 for finding the hack
rbnet.it & marcopon for the SGUX tool
DaGentooBoy for keeping the Unlock Guide updated with the latest changes

Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7536130&postcount=11
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source http://developer.android.com/sdk/index.html )
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volume up/down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Step 2. Self Hex Hack unlock method
Once you are done Rooting the phone
1. Run ADB Devices on your PC
open CMD
change to your Android SDK folder
type ADB devices
hit Enter
it should show your phone listed
if not then check to make sure you have Enabled the USB debugging in Applications < Settings in your phone
2. Once successful with the above step
type ADB Shell
hit Enter
type SU
hit Enter
back on your phone screen you should see a pop up for "Superuser Permission" (try to keep your screen on, the timer automatically turns the screen off, you might miss the pop up message)
"grant it permission" to allow, else you will get a "permission denied"
3. back on the ADB shell
type cd /dev/block
hit Enter
type dd if=/dev/block/bml3 of=/sdcard/bml3.bak
hit Enter
you should get something like
Code:
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.826 secs (12694624 bytes/sec)
the bml3.bak file should now be at the root of your internal SD card
4. Unplug the USB cable from the phone
Disable the USB debugging in Applications < Settings
5. Plug the USB cable back to the phone
Use either Samsung Kies mode, or Mass Storage mode
6. Copy the bml3.bak file from the internal SD card to your working folder where you have downloaded SGUX2
7. Run CMD
CD (change directory ) to the folder where you have the files
execute/run sgux2.exe bml3.bak (assuming both files are in the same folder)
then you should get something like this
Code:
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <bml3.bak>...
Searching code block...
Found.
Searching codes...
Freeze code : 98765432
Network Control Key: 12345678
8. power off your phone
9. power the phone back on
10. now enter the NCK (Network Control Key) code you found on step 2 part 7
It should say "Requesting network unlock"
followed by "Network unlock successful"
Done, enjoy your phone with your favorite network.
*** Alternative Unlock Methods ***
Hardware unlock method
Get an imartsim from ebay or deal extreme
Software unlock method
easier than ever please see guide for details
http://forum.xda-developers.com/showthread.php?t=761045
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bell unlock method
Call Bell convince them to unlock you, and Pay $75
Paid Hack unlock method
rhcp0112345 said:
Guys.
If you cannot wait. I found an easier way for me to get the codes for you. And the file is 10MB. and if you zip prob smaller as hell.
Code:
adb shell
cd /dev/block
# dd if=/dev/block/bml3 of=/sdcard/bml3.bak
copy to computer / upload
Send me $35 USD to [email protected]
Click to expand...
Click to collapse
original topic link http://forum.xda-developers.com/showpost.php?p=7772955&postcount=588

Well first thing is have you tried flashing a different MODEM file onto the phone using Odin?

I tired flashing Asian EU version of radio but no luck.
I believe simlock is something totally different,
I ended up using a sim adapter that was lying around for last 2 years.
Put the sim adapter along with my fido sim
settings, APN typein APN setting (internet.fido.ca)
3G is now active,
I can make calls and recieve calls.
EDIT:+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
http://www.dealextreme.com/
you can order any sim adapter, they all do the same thing.
+++++++++++++++++++++++++++++++
When you FLASH to JP3
don't flash the RADIO, (just flash PDA with 512)
I find RADIO FW on Stock BELL ROM works better than the one included in the JP3.
=======================================================================
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
=======================================================================
Another weird thing I noticed,
the "download mode" for Odin (press vol down home pwr)
works on one of the phones only.
for the other phone, I had to plug in debugging mode and use "ADB reboot in recovery command.
======================================================================
I ended up exchanging my 2nd galaxy S, If you can't put your phone into ""download mode"
there's something wrong with your phone.
as far as the unlock sim goes, yes it's like a turbo sim, any adapter will do.
but the problem I noticed, 3G works great, I can make outgoing calls, BUT 1 out of 2 times, incoming call goes directly to my voicemail.
it's probably because of my sim not seen as fido sim on the network.
neways, I am going to try.
http://unlockgenie.com/ for factory unlock code.
they have the lowest price for bell unlock so far 26$
====================================================
I assembled one click solution for ADB , no need for command line,
double click the bat file while connected in DEBUG mode.
it's for those people who are having trouble getting into the download mode by pressing keys.
http://www.megaupload.com/?d=3H9UZNI4

you can also unlock it using SAMSUNG factory code.
you can get one code for around 25~30$ US
seeing that EU version of the froyo rom JP3
works fine with i9000m 3G
I'm guessing I am on NAM network. (despite the radio rom being EU version)

Well I started looking through the Android source for where it determines if a device is network locked but I got lost after a while (I'll have another go later). Presumably it's stored on a chips firmware that you can't easily flash, however just in case... Would someone mind backing up their whole system exactly prior to unlocking and then again afterwards using clockwork mod so we can look for changes.

Benjamin Dobell said:
Well I started looking through the Android source for where it determines if a device is network locked but I got lost after a while (I'll have another go later). Presumably it's stored on a chips firmware that you can't easily flash, however just in case... Would someone mind backing up their whole system exactly prior to unlocking and then again afterwards using clockwork mod so we can look for changes.
Click to expand...
Click to collapse
that's my plan, in the worse case scenario then we can de-brick and reload the original firmware that came with Bell
i'll be trying more stuff later today, still at work

Im looking into getting this phone as well... problem im not sure if the deving for the tmobile vibrant will transfer directly over to the bell galaxy s...
Anyone try rooting the bell one with the root out for that phone??
Edit: Nvm just saw that the root is for the i9000 :|
But still would the root for the tmobile version work on this and vice versa?

Subscribed. Going to follow this thread til DEATH. Now i need solution to buy one. Someone please find a vendor that ships to US.

leegoon84 said:
you can also unlock it using SAMSUNG factory code.
you can get one code for around 25~30$ US
seeing that EU version of the froyo rom JP3
works fine with i9000m 3G
I'm guessing I am on NAM network. (despite the radio rom being EU version)
Click to expand...
Click to collapse
Which site can I pay & sim unlock it please?

Yea same, subscribed.
Im on the same boat as some of u : Want to trade up my magic for bell i9000
But first i must wait for unlock. Root is already done. Then for a vibrant cm6 to be out and see if someone can flash and see how well it works out. Considering its identical hardware except for a few soft buttons + front facing camera, i wouldn't be surprised if its the same deal as with g1 / 32a magic.

leegoon84 said:
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
Click to expand...
Click to collapse
True for anyone reading this DO NOT use the firmwares for the USA Vibrant / Captive, the Bell Vibrant is closer to the i9000 than to the USA variants

AllGamer said:
Now that we have enough people with the new version on hand already.
It's time to setup this topic.
The aim obviously is to unlock this the Bell Galaxy S Vibrant i9000M
There are possibly 3 ways to go about this:
1. Software
2. Hardware
3. Pay $75 the carrier and get the unlock code after 60 days of purchase, or until some online unlockers gets the code, which ever first.
Past experiences in the PalmOS world leads me to believe it should be possible to be unlocked via software/firmware, so rooting the phone will be the first thing to do
For hardware unlocking we'll be able to confirm once the iSim I've ordered arrives next week more or less
Bell will not provide the unlock code until their "exclusivity" expires which is roughly November, that's when Fido/Rogers will get their own locked version for sure.
So, I'm inviting any Android/Mobiles developers to pitch in with any ideas or if they know more or what to look for, change edit, hack replace, flash, etc.
That's why i bough this device, it'll be a guineapig to possibly find the software unlocking method (flashing a ROM count as software)
Stock Bell firmware:
PDA/Phone: i9000ugjg9
CSC: i9000bmcjg9
Click to expand...
Click to collapse
Guys,
I just called "Bell" again & I was transfered to a "level 2" technical support informing me that these are the conditions to sim unlock it:
1- Have to be on an Active account even a prepaid is ok.
2- Have to be after 30 days of activating the account.
3- Unlocking will be instant right on the phone for $75.
Seems like we can't do it that way, anyone knows a paid way of sim unlocking it rightaway from any site?

Has anyone managed to root the phone yet? If yes, can you point to where? I've tried a few to no avail. Thanks.

I'm looking for the modem.bin from the Bell Vibrant. If anyone has it could they please send me a PM.

Yay
Hah glad to see it, and glad there will be quick dev on this device. I'm with the other USA folks in here like stated before, we just need to wait a bit to see it around online or know one of our fine neighbors to the north to hook a bro up hah. Thanks guys will be checking this out.
** at least it's not so bad having to wait for us US folk then if it's currently unlockable. Heck i'll thrown down a couple bucks to whomever pulls it off as well

leegoon84 said:
I tired flashing Asian EU version of radio but no luck.
I believe simlock is something totally different,
I ended up using a sim adapter that was lying around for last 2 years.
Put the sim adapter along with my fido sim
settings, APN typein APN setting (internet.fido.ca)
3G is now active,
I can make calls and recieve calls.
EDIT:+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
http://www.dealextreme.com/
you can order any sim adapter, they all do the same thing.
+++++++++++++++++++++++++++++++
When you FLASH to JP3
don't flash the RADIO, (just flash PDA with 512)
I find RADIO FW on Stock BELL ROM works better than the one included in the JP3.
=======================================================================
BTW you don't have Vibrant,
you have I9000 don't flash CAPTIVATE, VIBRANT ROMS
=======================================================================
Another weird thing I noticed,
the "download mode" for Odin (press vol down home pwr)
works on one of the phones only.
for the other phone, I had to plug in debugging mode and use "ADB reboot in recovery command.
Click to expand...
Click to collapse
what adapter are you using? kind of turbo sim? what is called to use it while waiting for unlock code?
i have old iphone turbo sim, i have no clue if this can be used , as i tried it still no network

I'll donate 20$ to any dev who cracks this
im anxously awaiting a solution my galaxy is just sitting on the table right now collecting dust

Guys, just get a code from unlockallcellular.com. I got my European I9000 unlock code from there.
Sent from my GT-I9000 using XDA App

post removed

[REF} All in One guide for NOOBS with Videos! "WORK IN PROGRESS"

If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful then show your appreciation and hit that thnx button.
As of now this thread is under construction, I have not seen any noob helper all in one thread & i have always had one for the phone I have. So here it goes for Note 2. Feel free to give me suggestion but keep in mind that I only do this on my free time so this might take while to finish.
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.

Credit for this Post goes to TRusselo!!!!
Here is how to do Advance research/help your self + Mods!​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here is how to Root Your Note 2 Mac & Windows!​
Root Note 2 on Windows without Tripping Flash counter!!!
Step 1: Download the files Here and unzip them.
Step 2: Do this Only if you want CWM. Connect your phone to computer and copy over CWM recovery.img to your internal sd card. Make sure you do not put that in any folder.
Step 3: Put your phone into down load mod. First Turn off your phone. Then Press Volume down, Power and home button. You will see following screen.
Step 5: Then Press Volume Up and you will see following screen.
Step 3: Open up Odin folder and run Odin3 v1.85 and unselect F. Rest Time.
Step 6: Connect your Note 2 to computer. Once you connect your phone you will see yellow box on upper left corner on Odin.
Step 7: Now Press PDA and browse for the location of the downloaded files. And Select root files that you downloaded and open it.
Step 8: Press Start.
Step 9: Phone will reboot once its done flashing. And you will get Pass on upper left corner.
Step 10: Now download any of the app that requires root permission(titanium back up) and make sure you have root.
Option One: Install CWM Recovery Hard way!
Step 1: Go to your phone and enable usb debugging under setting>developer's option.
Step 2: Connect your phone to your windows computer and open up command prompt.
Step 3: Type adb on your command prompt then you will see all the commands that adb offers.
Step 4: Type adb shell then type su after that type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Step 5: You will see following in your command prompt.
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
13992+0 records in
13992+0 records out
7163904 bytes transferred in 1.672 secs (4284631 bytes/sec)
Step 6: Now Just type " reboot recovery " in command prompt.
Step 7: You now have rooted At&t Note 2 with CWM installed.
Option 2: Flash TWRP Easy Way!
1) Download Goo Manager from Play Store.
2) Open the app & press Menu button. (Make sure to give superuser permission)
3) Press "Install OpenRecoveryScript"
4) Recovery will be downloaded & installed.
5) Once You see message saying Recovery Installed, press boot into recovery.
6) Done you have custom Recovery.

Here is How to Unroot Your Note 2.

fourth for all in one links.

fifth for video reviews.

sixth for themes.

seventh for how to use xda
This order may get changed.

eight for how to flash themes.

Last one

appdroid said:
Last one make sure to hit thnx guys.
Click to expand...
Click to collapse
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks

used all my thanks!! great write up!!! you always provide us with great information!!!

fxbreaker said:
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks
Click to expand...
Click to collapse
Rooting will allow you to completely remove an app. You can disable(removes from app drawer and totally deactivates the app) without rooting by doing the following:
Go to setting/applications manager
Select desired app
Will give option to 'disable'
Select disable and the app will no longer run or be visible.
If the option shows 'disable updates' select that then go back and select the app again and it will then let you disable the app.
This method leaves the file on your phone so it doesn't free up any space but it will free up some memory as you will no longer have this 'bloat' running.
Sent from the Millennium Falcon

I Don't know why someone would rate this thread down???

appdroid said:
I Don't know why someone would rate this thread down???
Click to expand...
Click to collapse
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
cdshepherd said:
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse

appdroid said:
For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
Click to expand...
Click to collapse
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

I appreciate the work done in this thread. and all he is asking for is a thanks in exchange for hours and days of research sounds good to me .goodjob op keep it up
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
cdshepherd said:
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse

appdroid said:
Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
Click to expand...
Click to collapse
Ahhhh the skyrocket days. Life was soo simple
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Samsung Galaxy S7 Active Root! (SUCCESS)

I have an AT&T Galaxy S7 Active - US Model - SM-G891A
I haven't seen any credible sources with a root for this device. From what I can tell, it is identical to the Qualcomm version of the Galaxy S7(non-edge) with one exception; The S7 Active has the "Active button".
Since almost every Qualcomm variant of the Galaxy S7 has been rooted, is there a chance that the S7 active is rootable? or is there already a root?
Let me know if you need any other information or if you would like a test dummy.
UPDATE: Successful Root Of the Galaxy S7 Active (Qualcomm)
PLEASE USE THE POLL TO LET US KNOW WHAT VERSION OF FIRMWARE YOU END UP ROOTING. IF YOU FAIL, PLEASE PROVIDE US WITH AS MUCH INFORMATION, ABOUT YOUR EXPERIENCE, THAT YOU CAN. THIS WAY WE CAN DO OUR BEST TO HELP YOU AND CONTINUE IMPROVING THIS ROOT.
ROOT - CLICK BELOW
Original Tutorial Credit(HERE)
Updated for Galaxy S7 Active (by NotSoMiniGun)
Make sure you have downloaded these files:
• SuperSU v2.74 (updated) SuperSU v2.76
• Modified ODIN
• Unlock boot.tar
• Fastboot
• Samsung Official USB Drivers v1.5.40
Make sure you meet these requirements:
• Firmware PG7, PH2, PI2, PK2, PL1(6.x.x only)
• NO NOUGAT SUPPORT YET (1/30/2017)
• >60% Battery charge
Additional suggestions and warnings:
• Make sure you know both your Samsung account info and your Google account info. You will need these, for Factory Reset Protection, if something goes wrong and you need to wipe your phone.
• I, also, recommend rooting a clean/wiped/reset phone. This rules out quite a few things that could cause failures or strange behavior during or after the rooting process.
• You WILL lose some speed and battery life. This is not an optimized root. If you are comfortable with that fact, then go ahead. You’ve been warned. Do not complain about it on this thread.
• Install the Samsung drivers even if your computer already seems to have them. Right click and run the .exe as administrator. REBOOT after install. This rules out another potential point of failure.
• MAKE SURE YOU ONLY HAVE YOUR PHONE PLUGGED IN. Make sure there are as few USB devices, as possible, plugged into your computer during the rooting process.
• DISABLE YOUR ANTI-VIRUS
Step 1:
Read EVERYTHING above. Twice.
Step 2:
Open Settings->About Device and scroll down to “Build Number”. Tap it repeatedly until it says you have activated “Developer Mode”.
Step 3:
Open Settings->Developer Options and turn ON both “USB Debugging” and “OEM Unlock”.
Step 4:
Turn phone OFF. Once off, hold (Volume Down, Center Home, and Power) until you see a blue warning screen.
Step 5:
Press Volume Up and plug your phone into your computer. You should have blue screen that says “Downloading”.
Step 6:
All of the files should be downloaded to your computer and be sitting in your “Downloads” folder. Un-zip the ODIN-modified.zip, right click the ODIN .exe, and run as administrator.
IF YOU DON’T SEE A BLUE BOX AT THE TOP LEFT OF ODIN THEN DO THESE STEPS AGAIN:
1. Run the Samsung USB Drivers .exe again.
2. Reboot your computer.
3. Make sure your data cable isn’t damaged and is plugged in all the way.
Step 7.
Select AP and choose the ENG Boot file ending in .tar. Then click “Start”. The blue box should eventually turn green and say “PASS”.
IF YOU GET STUCK IN A BOOT LOOP:
“If your phone ends up in a bootloop (which most likely will), you will need to do a factory reset. To do this, hold down Volume Down, Center Home, and Power buttons together until your phone resets then quickly switch the Volume Down to Up key while holding the rest of the buttons down until you see “Recovery booting” at the top-left of the screen. If you mess up, don’t worry you can keep trying until you get it right. Once in stock recovery, choose “Wipe data/factory reset” then “yes” to do a factory reset. THIS WILL ERASE EVERYTHING ON YOUR PHONE! Reboot and after 5-10 minutes, you should be welcomed by a welcome screen, go ahead and login.”
Step 8:
Go through the set-up screens until you can repeat Steps 2 & 3.
Step 9:
Unzip fastboot.zip to its own directory. Unzip the contents of SuperSU and copy them to the fastboot folder.
Step 10:
Shift-RightClick in the white space below the files in the fastboot folder. Click “Open Command Window Here”.
Step 11:
Type the following in the Command Prompt:
Code:
adb devices
Code:
root.bat
Watch your phone for any messages and make sure to tap OK. If it freezes, unplug your phone, plug it back in, and restart from Step 10.
Step 12:
Install BusyBox from the app store. Open the app and make sure it installs to “/system/xbin”. DO NOT INSTALL IT ANYWHERE ELSE. THIS WILL CAUSE PROBLEMS AND REQUIRE A FLASH AND RE-ROOT.
Step 13:
You are now successfully rooted. Read the rest of this post carefully to fix the following items:
WiFi password reset
SecurityLogAgent
General Lag and other issues.
TO UNROOT - CLICK BELOW
Link to Instructions Provided By (jembot)
WARNING:
DO NOT uninstall "SecurityLogAgent", DO freeze it using Titanium Backup. Uninstalling it seems to cause instability and random system crashes.
DO NOT attempt to update SuperSU BINARY UPDATE:You can update to v2.76 from v2.74 with the provided file (updating the app is also ok) after root. Other attempts to update will break WiFi, Cellular Data, Access to the Play Store, and will require a reflash in ODIN to regain functionality.
If you do accidentally do this, just reflash to PI2 firmware and check for OTA updates, or use the update packages, to bring your device back to PL1 Firmware. It will lag a lot, so be patient.
FIRMARE AND PACKAGE DOWNLOAD LINKS
PI2 Firmware Download Password: G891AUCS2API2_FULL_FSFD (Cost me $10 lol)
PG7 Firmware Download
PG7 to PH1 Update
PH1 to PI2 Update
PI2 to PK2 Update
PK2 to PL1 Update
PI2 to PL4 Update
PK2 to PL4 Update
PL1 to PL4 Update
SuperSU v2.74
SuperSU v2.76
Modified ODIN
Unlock boot.tar for PL1 or earlier (credit activefan01)
Original boot.tar for PL4 (use if updating to nougat)
imsservice.apk (use to remove VoLTE and RCS icons)
Fastboot (bundle used in the rooting tutorial)
Samsung Official USB Drivers v1.5.40
Other Issues and Solutions:
If you get and MD5 error:
Your download for the tar file was probably incomplete or corrupt. To fix, re-download and make sure it downloads completely before trying again.
If ODIN does not recognize the file or doesn't display it in the browser:
The file should end in a .tar extension, not a .MD5 extension. Use THIS tutorial to show file extensions in windows(if you can't see them), and make sure the file ends in .tar
If you still experience significant lag or battery usage:
1. Try any of the suggested CPU governor apps on this thread.
2. I, personally, noticed the biggest improvement with Device Control [root] from the play store
3. Enable - Power Efficient Workqueue
Enable - LCD power reduce
Core Limits - 1593 MAX - 307 MIN and Lock Frequencies
Governor - Interactive and Lock Governor UPDATE: "PERFORMANCE" seems to work significantly better at removing lag and, surprisingly, saving battery
Enable - Automatic FStrimming
Enable - Core Control and MSM-Thermal
Enable - Reapply on boot with a 15 second delay
4. Under developer options, consider setting all of the animation speeds to 0
5. As always, you are responsible for any damage to your device or data
For those of you who want Xposed:
1. Install Flashfire from the Play Store
2. Put these 2 files on your phone FRAMEWORK and APK
3. Use Flashfire to flash the zip to your phone.
4. Install the APK and Reboot.
5. Enjoy
6. Avoid these modules or risk bricking your phone:
- Gravitybox - Confirmed
- Xblasttools - Confirmed
For those of you who want to Tether/Hotspot:
1. Install XTether in Xposed
2. Activate and Reboot
3. The native hotspot/tether options will now work in settings
4. Enjoy more.
If you have issues with AT&T keeping you from setting up your phone:
1. Make sure you connect to WiFi on first step of the Samsung setup
2. Do the normal setup until you get to the AT&T Setup portion
3. Let the setup "scan" for connections on WiFi
4. Dismiss the warning about limited WiFi and turn the WiFi OFF
5. Proceed with the rest of the setup by hitting NEXT or SKIP when available
6. You should now be able to use your phone and should be able to setup all AT&T related software separately.
To fix WiFi password reset issue:
1. Install BuildProp from the Play Store
2. Change the value of ro.securestorage.support=false
3. Save, reboot, enter WIFI password for the last time!
How to remove the VoLTE and RCS(hurricane looking thing) icons: (tested by FtaWolf)
1. Install a file explorer like FX
2. Set Read/Write access to System Partition, use the 3 dot menu in the top right
3. (be careful not to touch anything else, I soft-bricked my phone twice on accident)
3. Navigate to /system/priv-app/imsservice
4. Rename file imsservice.apk to imsservice.apk.bak, tap and hold to rename
5. Copy THIS file into the same folder
6. Then set permission to 644, again, tap and hold to change permissions
7. Reboot and you should be good to go.
How to add HotSpot and MobileData toggles or remove unwanted toggles (credit slimshouki)
1. Install CSC Feature Expert from the PlayStore
2. Scroll down until you find "Config Def Quick Setting Item" (Do not search for it, you wont find it)
3. Add " ,WiFiHotspot,MobileData"
4. (OPTIONAL) Delete any toggles you don't want. Make you there is a single comma between all values
5. Open Settings->Personal->Backup and Reset->Reset Settings
6. After it reboots you should see the toggles.
COMPATIBILITY STATUS:
Galaxy S7 & S7 Edge Qualcomm Variant Root: Confirmed Successful On: PG7, PH2, PI2, PK2, PL1 || Fails On: PL4, Android 7.0 Update
Poot Debug APK Qualcomm Root: Incompatible
Dirty Cow Exploit: Temp/Partial Root
TO DO:
Determine Root Method/Source (activefan01, perhaps you can weigh in)
Custom Recovery (if possible)
Optimize Current Root Method (currently takes a decent toll on battery life)
7.0.0+ Root (currenty only works on pre-nougat systems)

If no one has any answers on the availability of a functioning root for the Samsung Galaxy S7 Active, can some one tell me why the Active series of phones seem to be actively ignored? Is there an extreme difference in hardware? Is it difficult for devs to get their hands on the device? Is there not enough interest?

The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.

br0adband said:
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
Click to expand...
Click to collapse
I'm only getting 4hrs of sot..... Hmm

I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.

I am also searching for root. I got some link in google search, but they are not working. I bought this unlocked device in India. While it works fine with old network, but it does not work with new network which are purely 4g and use voice over LTE for calls.
Sent from my SAMSUNG-SM-G891A using Tapatalk
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
I need to put Indian CSC on this phone.
Sent from my SAMSUNG-SM-G891A using Tapatalk

br0adband said:
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
Click to expand...
Click to collapse
Would you be willing to compile a list of all the packages you disabled? Maybe then I can get better battery life.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here's the list as XML and it's attached as well for import to Package Disabler Pro:
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.mobeam.barcodeService</string>
<string>com.monotype.android.font.rosemary</string>
<string>com.matchboxmobile.wisp</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.samsung.android.app.galaxyfinder</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.samsung.svoice.sync</string>
<string>com.drivemode</string>
<string>com.sec.android.app.clipvideo</string>
<string>com.sec.android.devicehelp</string>
<string>com.android.wallpapercropper</string>
<string>com.sec.android.app.wfdbroker</string>
<string>com.att.android.digitallocker</string>
<string>com.samsung.android.app.withtv</string>
<string>com.sec.android.app.safetyassurance</string>
<string>org.simalliance.openmobileapi.service</string>
<string>com.samsung.android.easysetup</string>
<string>com.android.externalstorage</string>
<string>com.sec.android.easyonehand</string>
<string>com.sec.factory</string>
<string>com.cequint.ecid</string>
<string>com.directv.dvrscheduler</string>
<string>com.samsung.android.qconnect</string>
<string>com.amazon.mShop.android.install</string>
<string>com.sec.android.app.tourviewer</string>
<string>com.sec.android.Kies</string>
<string>com.samsung.faceservice</string>
<string>com.monotype.android.font.foundation</string>
<string>com.sec.android.widgetapp.easymodecontactswidget</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.firmware.tsp</string>
<string>com.google.android.configupdater</string>
<string>com.sec.android.app.billing</string>
<string>com.sec.android.app.minimode.res</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.samsung.android.slinkcloud</string>
<string>com.dti.att</string>
<string>com.dsi.ant.service.socket</string>
<string>com.sec.android.AutoPreconfig</string>
<string>com.sec.android.app.soundalive</string>
<string>com.samsung.android.securitylogagent</string>
<string>com.android.carrierconfig</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.app.assistantmenu</string>
<string>com.locationlabs.cni.att</string>
<string>com.samsung.SMT</string>
<string>com.samsung.aab</string>
<string>com.samsung.vvm</string>
<string>com.sec.android.ofviewer</string>
<string>com.samsung.hs20provider</string>
<string>net.aetherpal.device</string>
<string>com.sec.att.usagemanager3</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.samsung.android.smartface</string>
<string>com.android.mms</string>
<string>com.android.backupconfirm</string>
<string>com.sec.android.app.SecSetupWizard</string>
<string>com.hancom.office.editor.hidden</string>
<string>com.sec.bcservice</string>
<string>com.android.calendar</string>
<string>com.samsung.android.providers.context</string>
<string>com.sec.android.preloadinstaller</string>
<string>com.sec.android.uibcvirtualsoftkey</string>
<string>com.samsung.android.sdk.professionalaudio.utility.jammonitor</string>
<string>com.android.sharedstoragebackup</string>
<string>com.yellowpages.android.ypmobile</string>
<string>com.samsung.android.app.colorblind</string>
<string>com.android.printspooler</string>
<string>com.android.dreams.basic</string>
<string>com.att.myWireless</string>
<string>com.sec.android.app.dictionary</string>
<string>com.samsung.android.app.talkback</string>
<string>com.samsung.android.game.gametools</string>
<string>com.asurion.android.mobilerecovery.att</string>
<string>com.sec.smartcard.manager</string>
<string>com.sec.allsharecastplayer</string>
<string>com.samsung.app.slowmotion</string>
<string>com.samsung.android.smartcallprovider</string>
<string>com.directv.promo.shade</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.samsung.android.personalpage.service</string>
<string>com.samsung.advp.imssettings</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.sec.android.app.clockpackage</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.sm</string>
<string>com.sec.android.widgetapp.locationwidget</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.samsung.android.controltv</string>
<string>com.samsung.mdl.radio</string>
<string>com.sec.spp.push</string>
<string>com.dsi.ant.server</string>
<string>com.samsung.android.gamepad.service</string>
<string>com.samsung.android.allshare.service.fileshare</string>
<string>com.synchronoss.dcs.att.r2g</string>
<string>com.sec.android.mimage.photoretouching</string>
<string>com.samsung.android.universalswitch</string>
<string>com.samsung.helphub</string>
<string>com.sec.android.app.sns3</string>
<string>flipboard.boxer.app</string>
<string>com.google.android.feedback</string>
<string>com.google.android.apps.photos</string>
<string>com.android.managedprovisioning</string>
<string>com.sec.android.providers.tasks</string>
<string>com.ubercab</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.android.dreams.phototable</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.samsung.app.highlightplayer</string>
<string>com.sec.android.app.vepreload</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.cleanmaster.sdk</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.android.wallpaper.livepicker</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.amazon.mShop.android</string>
<string>com.samsung.android.app.FileShareClient</string>
<string>com.facebook.system</string>
<string>com.sec.android.soagent</string>
<string>com.samsung.android.fmm</string>
<string>com.samsung.android.mdm</string>
<string>com.smlds</string>
<string>com.ws.dm</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.app.newtrim</string>
<string>com.samsung.android.spay</string>
<string>com.sec.hearingadjust</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.sec.android.splitsound</string>
<string>com.wssnps</string>
<string>com.samsung.android.app.watchmanagerstub</string>
<string>com.policydm</string>
<string>com.samsung.android.app.FileShareServer</string>
<string>com.enhance.gameservice</string>
<string>com.americanexpress.plenti</string>
<string>com.sec.svoice.lang.es_US</string>
<string>com.lookout</string>
<string>com.samsung.android.sm.provider</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.android.bluetoothmidiservice</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.voiceserviceplatform</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.android.app.mt</string>
<string>com.sec.knox.switcher</string>
<string>com.qualcomm.atfwd</string>
<string>com.sec.android.app.magnifier</string>
<string>com.samsung.android.video</string>
<string>com.amazon.kindle</string>
</disabledPackages>
</importExportSetting>

Thank you. I'm going to mess around with it later.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here first run with sot with S7 Active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-G891A using Tapatalk

FtaWolf said:
Here first run with sot with S7 Active.
Click to expand...
Click to collapse
That's awesome, really it is, but what does that have to do with this thread and rooting it?

br0adband said:
That's awesome, really it is, but what does that have to do with this thread and rooting it?
Click to expand...
Click to collapse
Not thing. What did disabled package pro have do with thread. You didn't ? It.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Back On Track
While I agree the S7 Active is a fantastic phone with fairly substantial battery life, those merits should be discussed in another thread such as HERE. The main goals of this thread are:
1. Determine if there is an available Root for the Samsung Galaxy S7 Active
2. Determine if any current exploits, for other models, could be modified to Root the S7 Active
- The Galaxy S7 (snapdragon model) Root
- Dirty Cow
- etc.
3. To offer help or a reward to anyone willing to make progress on this topic.
I personally am wiling to donate $50+ to anyone able to provide a legitimate root (or to a charity of their choice).
Please let me know if there is an official way of presenting a bounty or if there is any other way I can help progress this project.

I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system

-snip-

Poot
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?

NotSoMiniGun said:
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
Click to expand...
Click to collapse
Most likely not as that is an old method. You could try the method mentioned a few posts up.
Sent from my SAMSUNG-SM-G891A using Tapatalk

first of all, I apologize for my "English", I had to use google translator.
I am edu present, I'm from Argentina, and was looking for information on how to root the s7 active, no luck, but I found information that perhaps more experienced people can help them find a solution ....
Qualcomm Quadrooter Exploit
QuadRooter Android sounds like another serious security exploit. Which one can allow a malicious app Apparently to gain root access based on Qualcomm Android phones and tablets, enabling the app to do pretty much what Then it pleases. , According to Check Point, the research group discovered That QuadRooter, up to 900 million Android devices Qualcomm Could be AFFECTED. This exploit targets the drivers Qualcomm Which is why it is specific to this hardware. As of the 1st Augusts security update Google has patched 3 of the 4 will patch vulnerabilities and the last one in the September 1st update. To keep your device safe from bugs it is always in Original bests to stay on top of your security updates. One of the best ways to protect your phone from malicious software is to download apps only from trusted sources or google play.
If you want to check and see if your device can possible be vulnerable to this threat Then you can download and run QuadRooter Scanner by check point. Personally I am hoping That a developer can figure out this exploit and use it to get many android users root access. I am sure someone can create a app gets root then a INJECTS That SuperSU and their binary into the device. If you are hoping for the same I recommend not updating to new security patches and give the developers some time to get root access devices.
I would not be surprise to see this QuadRooter vulnerability Implemented into Kingroot app some time soon, as it would make there app on Android devices unstoppable. What do you think about this bug please comment below and let me know.
This information I found in rootjunky.
I hope you can serve something
---------- Post added at 01:58 AM ---------- Previous post was at 01:45 AM ----------
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
how did it go?

I tried it but not got success.

rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
That's awesome! Now, who is familiar with Linux... can dump boot.img and kernel.img from the phone...
I found that it's here:
cd dev/block/platform/soc/624000.usfshc/by-name/
dd if=/dev/block/sda6 of=/sdcard/efs.img
dd if=/dev/block/sdd10 of=/sdcard/aboot.img
dd if=/dev/block/sda13 of=/sdcard/fota.img
dd if=/dev/block/sda16 of=/sdcard/modem.img
dd if=/dev/block/sda17 of=/sdcard/boot.img
dd if=/dev/block/sda18 of=/sdcard/recovery.img
I don't know, will these comands work in linux?

Updating AT&T OTA issues; need help sideloading

Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.

This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!

So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse

westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.

Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.

despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?

Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.

New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot

omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.

despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !

Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade

I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.

Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...

bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it

wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk

despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143

Possible Brick - Flashing Unlock Not Allowed

I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!

So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?

Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).

I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?

ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.

That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk

ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.

I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?

Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.

ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.

Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk

I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?

Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.

ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:

0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk

Aiit.tnx

@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.

SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.