AT&T Samsung Galaxy S5 DeBloating - AT&T Samsung Galaxy S 5

Hello to all the fans of less programs/apps forced on the user.
To begin I'm listing what I have disabled/turned off from the stock rom, and I'm getting a better battery life and see less junk.
ANT Radio
ANT+ Plugins
AT&T FamilyMap
AT&T Hot Spots
AT&T Locker
AT&T Messages
AT&T Mobile Locate
AT&T Navigator
Beats Music
BlurbCheckout
Business card recognition
Caller Name ID
ChatON
Device Help
DriveMode
Flipboard
Google Play Books
Google Play Games
Google Play Movies & TV
Google Play Music
Google Play Newsstand
HP Print Service Plugin
Keeper
Mobile TV
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
My Magazine
myAT&T
Print Spooler
S Voice
Samsung Account
Samsung Apps
Samsung Galaxy
Samsung GALAXY Apps Widget
Samsung Link Platform
Samsung Print Service Plugin
Samsung Push Service
Travel wallpaper
Wallet (Isis)
Note: I'm not using any of the apps/services listed above, and I have not run into any problems. If you are going to use them then don't disable them.
Battery life has increased enough to be noticed, but not dramatically.
Next Project: Make an Odin flashable DeBloated stock ROM in both rooted and unrooted versions.
I got a full Stock ROM download from Samsung Kies to start Debloating and adding Root using Android Kitchen.
This file contains four files:
AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
Accomplished:
System folder is located and the apps listed above deleted from "AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5"
Also ran this through the Kitchen and got it rooted, signed, zipaligned, ... (Choosing the lazy option for now) and got my output .Zip
Stuck on:
1- the Android kitchen .Zip file is flashable using a custom recovery mod. e.g. CWM or it's PhilZ version, which isn't currently available for this phone.
I don't have previous experience that these .Zip files can be flashed through Odin. So I assume it won't work.
2- Cannot put the System folder I Debloated back together to get accepted and read by Odin.

Can u share the odin file that has been rooted. Without thw debloating
Sent from my SAMSUNG-SM-G900A using xda app-developers app

blkghost22 said:
Can u share the odin file that has been rooted. Without thw debloating
Sent from my SAMSUNG-SM-G900A using xda app-developers app
Click to expand...
Click to collapse
I'm sharing my Android Kitchen's Cygwin window screenshot of the file information.

Thx... i was askig so a dev or someone more knowledgable can take a look.
Sent from my SAMSUNG-SM-G900A using xda app-developers app

so what needs to happen now is the content inside that zip file need to get converted to "system.img.ext4" file, then I will put that file back into the tar ball "AP_G900AUCU1ANCE_.... .tar.md5" and load it up in the PDA section of Odin.
So that is where i'm stuck; in re-packing all those files back into "system.img.ext4" file. There is a delicate way to do this, also discussed in parts somewhere on the XDA forums. One has to know the final partition size to include it in the command used to pack those in to a "system.img.ext4" file.

That is awesome. I can't wait to see this finished. Seems you found a way to root it. Are you going to make it so that a "noob" like me can do it?
Sent from my iPad using Tapatalk

Commodore 64 said:
so what needs to happen now is the content inside that zip file need to get converted to "system.img.ext4" file, then I will put that file back into the tar ball "AP_G900AUCU1ANCE_.... .tar.md5" and load it up in the PDA section of Odin.
So that is where i'm stuck; in re-packing all those files back into "system.img.ext4" file. There is a delicate way to do this, also discussed in parts somewhere on the XDA forums. One has to know the final partition size to include it in the command used to pack those in to a "system.img.ext4" file.
Click to expand...
Click to collapse
even if you get it back in the tar your not going to flash it in odin, the AT&T bootloader is locked odin will not flash a file once you have rebuilt it because it does not contain the samsung signatures. i have already got a fully built flashable ROM for the AT&T just waiting for root and BL unlock.
your on the right path, so dont get discouraged but it just isnt that simple.
P.S. Before you even ask, yes i have tried multiple iterations of building the system.img.ext4 file and signing it.
P.P.S if you really want the best experience from building a rom build a linux box (either linuxmint or ubuntu) the kitchen is a great tool
but running under cygwin in windows there are many limitations including not being able to create a system.img.ext4 file or generate the correct md5sum.

Thanks cstayton for giving me a glimpse of what i'm dealing with here. From your comments a I searched further and found
http://autoroot.chainfire.eu/
Standing by for SM-G900A root release. I'm taking down my DropBox Dl link above since it is no use any more.

No root = No dev on the ATT or VZW versions of the S5 this is because of the locked BL. Likely that there won't be a BL unlock or bypass like Loki. Eventually a root exploit will be found just a matter of time, but no one knows how long that will be. There likely down the road after root will be safestrap which will allow custom TW roms based on the stock TW kernel. What likely won't happen is AOSP.
CF-Root does not work and never will as long as the bootloader is locked due to how it obtains root (modified stock recovery to push root). /System cannot be modified to root the ATT/VZW S5, this has already been cofirmed by Chainfire. An exploit on Kit Kat has to be found. Sadly anyone who got the ATT S5 expecting great Dev support right out the gate picked the wrong variant.

Has anyone tried safestrape?

daraj said:
Has anyone tried safestrape?
Click to expand...
Click to collapse
I don't believe that the S5 is on his supported device list as of yet, and even then Safestrap requires root.

cstayton said:
I don't believe that the S5 is on his supported device list as of yet, and even then Safestrap requires root.
Click to expand...
Click to collapse
Duh Thats true. So first step is ROOT!

A friend of mine mentioned that the note 3 has a locked BL and Knox but is still able to be rooted. I am wondering if the root for the note 3 would work on the s5. Has it been considered or tried? I would try it but I do not have the knowledge necessary to undo it if something goes wrong. It seems like something that could really mess up the device if you don't know what your doing.
Sent from my iPad using Tapatalk

Don't try it @TheSheibs. Just wait for root to be announced. It'll be a big deal if and when it does.

@TheSheibs Try it! if it works youll be the man!
Just be aware of the issues.

I have the rom cooked and ready and it was ready to go in odin 3.07. Well the thing is if I'm willing to part with the one year warranty since it will advance the knox counter and at the end of the day that shouldn't matter anyways because even if a root solution/exploit is released, flashing it by odin will still advance the counter ...
Sent from my SAMSUNG-SM-G900A using xda app-developers app

Commodore 64 said:
I have the rom cooked and ready and it was ready to go in odin 3.07. Well the thing is if I'm willing to part with the one year warranty since it will advance the knox counter and at the end of the day that shouldn't matter anyways because even if a root solution/exploit is released, flashing it by odin will still advance the counter ...
Sent from my SAMSUNG-SM-G900A using xda app-developers app
Click to expand...
Click to collapse
Once root is achieved (hopefully soon-ish) will we see prior AT&T devs flocking to the device for things such as SafeStrap and TriangleAway. I assume once we have root we will have a way to trip the knox shortly after. Root is key.

My s5 is coming in a matter of hours! I'm looking forward to root but I don't mind staying stock for a while as long as I can disable apps! The part I'll have to get used to is no more "Greenify" app but oh well
Sent from my Nexus 5

So what at&t and verizon did was not only lock the phone's bootloaders but encrypt them. The encryption part is problematic for now.
If we can't flash with odin then we can't load custom recoveries like cwm/twrp then this phones becomes less attractive for developers. I have made a rooted version of stock ready with android kitchen but currently I don't have a way to load it on my device to test it.
I tried and Odin crashed, knox counter did not advance.
Sent from my SAMSUNG-SM-G900A using xda app-developers app

Commodore 64 said:
So what at&t and verizon did was not only lock the phone's bootloaders but encrypt them. The encryption part is problematic for now.
If we can't flash with odin then we can't load custom recoveries like cwm/twrp then this phones becomes less attractive for developers. I have made a rooted version of stock ready with android kitchen but currently I don't have a way to load it on my device to test it.
I tried and Odin crashed, knox counter did not advance.
Sent from my SAMSUNG-SM-G900A using xda app-developers app
Click to expand...
Click to collapse
Well your right, Odin will not flash any custom rom with locked bootloader, once you touch the stock img.ext4 you break the samsung signatures, nothing you can do will flash that file.
If it was as simple as re-creating the system.img.ext4 and flashing with Odin we wouldn't have to worry about locked BL.

Related

Active I537 having trouble with 4.3 upgrade after root/unroot.

I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
Try this thread. http://forum.xda-developers.com/showthread.php?t=2611278
I think most issues related to the update have been covered pretty well. Best of luck to you.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
It sounds like you have quite a bit more reading to do so that you can understand exactly what you are trying to do. That said I'll try to answer your questions.
tweakedlogic said:
I rooted this phone for the sole purpose of using Titanium Backup. If the boot loader had been broken, I would have flashed a ROM from one of the very talented people that cook them.
Click to expand...
Click to collapse
Is TitaniumBackup the only root app you've used, have you frozen anything, installed any mods, or messed with any of the apps in your system/app folder? This will become important later.
tweakedlogic said:
That being said, I now want to flash the stock 4.3 upgrade. When I click the FOTA Upgrade button nothing happens, just a button click, nothing more (sound and tact). So I unrooted the phone and deleted every trace I could see. I ran 2 root checkers and verified. Then I called Tech Line. They got into my phone to try and push the upgrade, but told me that being still rooted blocked it from happening. I ran the SuperSU unroot and rebooted and pulled the battery. Again I have confirmation from boot checkers. So it should definitely be unrooted. But I haven't let Tech Line loose in it again. :fingers-crossed:
Click to expand...
Click to collapse
It sounds like you need to uninstall BusyBox. Normally SuperSU will uninstall this but it sounds like you tried a different method of unrooting that may have left bits in your system and since you weren't technically rooted anymore SuperSU didn't know what it needed to do.
tweakedlogic said:
Moving on...
I followed the instructions on the Samsung site using Kies. But Kies tells me my firmware isn't supported for Kies update. Really?!?
Click to expand...
Click to collapse
It sounds like you have the AT&T i537. This phone has a locked bootloader as you know. AT&T has required Samsung to lock down the i537 and will not allow them to release any firmware on Kies, this is why the software says your phone is incompatible. Basically AT&T is screwing us hard.
tweakedlogic said:
I followed the instructions on the Droid Magic site, I downloaded file OneClick_I537UCUBMI2.zip and fired up Odin. I have tried several different versions of Odin but none use .zip files. The phone does connect to Odin both in download and stock bootup.
Click to expand...
Click to collapse
The website you linked to is giving you bad information. The MI2 file is not technically "Official Firmware". This is a pre-release version of the firmware that DesignGears was able to get for the community. This will become important below.
tweakedlogic said:
Should I attempt to reformat the compression of the file to .tar or similar? Could I extract and run the lone .exe file in the .zip? Is there a switch to flip, or script to run, or app to install that will allow FOTA or Kies to work?
I would rather get the FOTA button to work, but I'll take any and all thoughts or suggestions offered.
I'm working on hosting the file unrestricted temporarily so maybe it can help someone. But it's kinda big.
Click to expand...
Click to collapse
As you've stated, this MI2 zip file that you've downloaded has a single exe file in it. This exe file should be run from a computer and it will allow you to flash new firmware to your phone. BUT, as I mentioned above this is pre-release firmware. What that means is you will forever be stuck on this firmware, you will not be able to take official updates from AT&T or Samsung. If you're ok with that, then go ahead and flash your phone with the pre-release of 4.3. If you want the official 4.3 update you have a little work to do. Above I asked you if you messed with any of the files in system/app, this is because the official update file can be downloaded and can even be flashed but it checks nearly every file in the system/app folder to make sure that it is the original file. If you've modified anything in there, the update is going to fail.
I'm going to post a few links of stuff you should read, but there is definitely a lot more that you should be reading.
How to flash stock MF3 - this is most likely the firmware you are on, but this thread will tell you how to get it back to stock, the way it was when you took it out of the box. This should allow you to take the official 4.3 update if other methods don't work.
MF1 Pre-release (4.2.2) - this is a pre-release of 4.2.2, you should read this.
MI2 Pre-release (4.3) - this is a pre-release of 4.3, read this thread to understand the benefits and drawbacks of flashing this pre-release firmware.
Official 4.3 Update Thread - this tell you what you need to do to try to update your phone to the official version of 4.3. Currently there is to way to root the official 4.3.
SafeStrap Thread - this will allow you to flash TouchWiz 4.2.2 based ROMs on your phone. Again, you need to read before you do anything. There's actually a lot we can do even though our bootloader is locked.
I can't stress enough how important it is to read. Once you've read everything and you think you understand what you're doing, READ MORE. There's always somebody who's done what you're trying to do and someone has more than likely given the answers you're looking for. Read as much as you can and you can avoid bricking your phone and ending up with a paperweight.
Good luck and us know if you have any questions, everybody is here to help.
You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.
tweakedlogic said:
You mentioned something I had forgotten, I did install app quarantine so I could remove the samsung and att apps from my drawer. So i went back and installed active root and app quarantine and unlocked the apps. But it seems I must have also deleted /system/apps/wssyncmldm.apk and .../KNOXAgent.apk. I can't believe that I deleted them instead of renaming them like I normally would, but it seems that's what I did.
So I'm hoping that some of you can copy these files to a google drive or something so i can reinstall them. pretty please?
If all else fails, i have insurance so my phone might get broken in a fall while doing some dangerous house work tomorrow.
Click to expand...
Click to collapse
You need to read the links I posted, all of this is explained including how to get the apps back that you deleted.
I so much miss being able to just flash with clockworkmod. Things were so much easier.
Sent from my SAMSUNG-SGH-I537 using Tapatalk

Samsung Galaxy S4 REFRESH Software Update - NC6

For 720T owners
Coming our way taken from sprint commnuity forum:
Samsung Galaxy S4 REFRESH Software Update - L720TVPUBNC6
Enhancements/Fixes
- Wi-Fi Calling
Important Notes
- Software version is L720TVPUBNC6
- This update will roll-out in a phased manner from 4/9 - 4/22
- Refer to the Samsung Galaxy S4 Software Update article in Support for install instructions
And these threads begin
... One already closed regarding this update. Please move your discussion to the 4.4.2 update thread that covers both regular and T model. There's also the everything for Triband version in the Q&A section.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 08:55 AM ---------- Previous post was at 08:54 AM ----------
Actually I just saw that you already posted in one of those threads so why start another thread?
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
And these threads begin
... One already closed regarding this update. Please move your discussion to the 4.4.2 update thread that covers both regular and T model. There's also the everything for Triband version in the Q&A section.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 08:55 AM ---------- Previous post was at 08:54 AM ----------
Actually I just saw that you already posted in one of those threads so why start another thread?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Because it's on general section and It's information that should be available to all.
The thread you referring to is exclusively for 720T so I asked the question there first but since no one responded I searched and I thought It would be useful to let know the others on the thread!!
If the information about 4.4.2 update thread is already there provide the link.
Before posting I searched and wasn't able to find any OTA info.
So remove threads and pardon my ignorance but my intent was to help!!!
I really do think it is about time to add a SPH-L720T section, it is already quite difficult to find post about this phone, they are mixed in with the standard SPH-720.
Anyone agree?
I wouldn't mind a subform.....It is hard, but a little reading and searching will get you to where you need.
NC6 On a custom recovery.
Does anyone know how to apply this update using a custom recovery?
sarcigon said:
Does anyone know how to apply this update using a custom recovery?
Click to expand...
Click to collapse
You can't. have to be unrooted to apply the update.
Sent from my SPH-L720 using Tapatalk
I believe you can be rooted, but you have to run the stock recovery
Sent from my SPH-L720T using XDA Premium 4 mobile app
VandyCWG said:
I believe you can be rooted, but you have to run the stock recovery
Sent from my SPH-L720T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To clarify his post. You can be rooted but you have to be running pure stock with no mods of any kind. No deleted system apps and also be running stock recovery.
Awesome "Samsung Experience"
I hadn't noticed until last night that since I got this (NC6) update on my phone, that several things were screwed up. Namely, the Hotspot Toggle was gone from the "Connections" settings tab, Sprint Zone was replaced by something called Mobile Zone that always errored out when you tried to open it. And lastly, the Tethering and Roaming settings were completely missing - as in gone, as in not there. After much frustration I tried a factory reset, but to no avail. Nothing changed. Same problems. On a whim, I decided to see what the guys at the Samsung Experience at Best Buy could do for me. I was pleasantly surprised to be helped by a sharp, knowledgeable guy who really knew his stuff. He was a fellow geek and was familiar with XDA and all the ins and outs of Samsung/Android phones. He did not have the NC6 version available to flash, but he did have NAF (KitKat update). So he flashed NAF to my phone with Samsung's SMART firmware tool (a glorified Kies that I would love to have access to!). And unlike going to the Sprint store, I didn't have to wait 30 minutes to be helped and my phone didn't disappear to the back room for another 30 minutes to be abused and mishandled by an overworked and probably under-trained and underpaid sprint employee. I stood right there beside the guy at his laptop while he showed me the software and flashing process. Totally awesome!
This fixed all the above issues plus another interesting thing too. Some of you are probably familiar with a little quirk in the S4 (and S3 too) in the stock recovery - when you reboot, it would show "Error!" under the little android robot. This always bugged me because I knew it shouldn't do that. Well my newly flashed S4 no longer says "Error!" when you reboot from recovery. I have no idea why it did it before or what changed to make it go away, but I feel better now that it's gone. It's probably major placebo effect but my phone seems snappier and smoother than ever.
So to make a long story short, "Samsung Experience" is totally awesome compared to going to the Sprint store. I will be going back when they get the NC6 (and possibly every future update as well) to have it flashed properly to my phone. I know I probably could have done the same thing myself with Odin and the firmware packages from Sammobile.com, but having them do it makes them responsible if anything goes wrong. And since I'm still under warranty, I don't want to do anything to void my warranty.
Amazing when things actually work the way they're supposed to...
Upon further investigation, it looks like I actually can re-initialize my phone using Kies now. I had tried doing it before going to the Samsung place at Best Buy, but when I tried the "Firmware Upgrade and Initialization", it said is was unsupported or something to that effect. That was because I already had NC6 on my phone, which wasn't available in Kies yet - just like even the Samsung guys didn't have it yet. But now that I have NAF, when I try "Firmware Upgrade and Initialization" it does give me the option to actually do it. The message says it will delete all user data and write the current software to the device - which is what I think they did for me at Best Buy. Only Kies couldn't load NAF for me while I had NC6 on my phone. So once NC6 makes it to Kies (if it ever does) I should be able to do a pristine flash using Kies instead of going to Best Buy if my phone starts acting up again.
You guys probably know all of this already, but I'm still learning...
Cooljb said:
Upon further investigation, it looks like I actually can re-initialize my phone using Kies now. I had tried doing it before going to the Samsung place at Best Buy, but when I tried the "Firmware Upgrade and Initialization", it said is was unsupported or something to that effect. That was because I already had NC6 on my phone, which wasn't available in Kies yet - just like even the Samsung guys didn't have it yet. But now that I have NAF, when I try "Firmware Upgrade and Initialization" it does give me the option to actually do it. The message says it will delete all user data and write the current software to the device - which is what I think they did for me at Best Buy. Only Kies couldn't load NAF for me while I had NC6 on my phone. So once NC6 makes it to Kies (if it ever does) I should be able to do a pristine flash using Kies instead of going to Best Buy if my phone starts acting up again.
You guys probably know all of this already, but I'm still learning...
Click to expand...
Click to collapse
So You can flash NAF over NC6 Is that what you're saying or I misunderstood?
frukyyy said:
So You can flash NAF over NC6 Is that what you're saying or I misunderstood?
Click to expand...
Click to collapse
No, you CAN'T. That was my original problem. Kies still thinks NAF is the latest version so it can't do anything with NC6 - it doesn't recognize it as the latest verstion - in fact it doesn't know NC6 exists at all. It will only initialize with what it thinks is the latest version. But since I have NAF now, Kies can do the full initialization with NAF. Like if I ever hosed my phone while it had NAF, I could fix it by doing a clean flash of NAF with Kies. And eventually I would think NC6 would become available in Kies. Then you should be able to do a clean flash of NC6 using Kies too.
frukyyy said:
So You can flash NAF over NC6 Is that what you're saying or I misunderstood?
Click to expand...
Click to collapse
So you never tried to Odin NAF over NC6? Thanks.
Sent from my SPH-L720T using xda app-developers app
ROMANTiC KiD said:
To clarify his post. You can be rooted but you have to be running pure stock with no mods of any kind. No deleted system apps and also be running stock recovery.
Click to expand...
Click to collapse
It makes sense.
Thank you!
frukyyy said:
So you never tried to Odin NAF over NC6? Thanks.
Sent from my SPH-L720T using xda app-developers app
Click to expand...
Click to collapse
No I didn't. I thought about it, and it probably would have worked, but everything I read said that would trip the Knox warranty flag. However now that I see the Samsung guy was able to do it - and it DIDN'T trip the Knox flag - I checked afterwards. And I even asked him if it would before he flashed my phone. So assuming the Samsung SMART firmware tool uses Odin at it's core, maybe I could have done it myself and not tripped the Knox flag. Or maybe the Samsung software has something that Odin doesn't that keeps it from tripping Knox. I just didn't want to use my phone as a guinea pig to prove or disprove whether or not downgrading firmware would trip Knox. Again, everything I read indicated that even flashing official Knox-enabled firmware that was a lower version than what was currently on the device would trip Knox.
My phone has downloaded this update automatically, and when it boots into stock recovery gives me an Error and aborted message. I'm assuming that's because I am stock rooted. So, can I download the zip and flash it myself through recovery? I honestly don't recall what recovery I'm running. It's been a couple months, and as a recovering flashaholic, I haven't gone beyond stock. I only wanted root to get rid of the bloat.
AuGmENTor said:
My phone has downloaded this update automatically, and when it boots into stock recovery gives me an Error and aborted message. I'm assuming that's because I am stock rooted. So, can I download the zip and flash it myself through recovery? I honestly don't recall what recovery I'm running. It's been a couple months, and as a recovering flashaholic, I haven't gone beyond stock. I only wanted root to get rid of the bloat.
Click to expand...
Click to collapse
You have to completely be unmodified. I think root has not stopped it, but you'll likely lose it afterwards. If you stripped the Rom, themed, or installed a custom recovery, you have to revert back to stock.
Sent from my SPH-L720 using xda app-developers app
krnfrk6663 said:
You have to completely be unmodified. I think root has not stopped it, but you'll likely lose it afterwards. If you stripped the Rom, themed, or installed a custom recovery, you have to revert back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Blech. Really? And then I can reroot?
AuGmENTor said:
Blech. Really? And then I can reroot?
Click to expand...
Click to collapse
i believe you can re-root once you take the update.
Mine has yet to get the update. Anyone have the NC6 zip up?

After being scared to do it, I flashed my Samsung Galaxy S 4 Active (I537) to KitKat

This is my first post and I'm going to try my best to not break a rule. If I do, I apologize in advance.
Thread thread is a sort of, "This is how I updated my phone from 4.2.2 to 4.4.2 and rooted it but your mileage may vary."
First, thanks goes to Sunderwear for his directions on how to push KitKat to the Samsung S4 Active as well as ROOT it. I rooted my 4.2.2 phone a few months ago and didn't realize doing so would prevent OTA updates. I went to the AT&T store to have them put 4.4.2 on the phone only to be told that the store didn't have the image (or whatever they said) and couldn't put it on my phone. Instead, they put 4.3, which turned out to be great because the directions pretty much have you going back to 4.3 in order to root.
BTW, if you are uninitiated, you may want to read this glossary page.
After having root in 4.2, I knew I wanted it in 4.4.2!
For the most part, I've been hesitant to flash the phone. I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Anyway, I started in the thread above only to find that I now needed to download Odin. This, surprisingly, was difficult. I found this site (http://odindownload.com/) which I am convinced is some sort of hacked version of Odin because when I tried to install from there, my Symantic warned me. When I disabled it, the file tried to install a bunch of bloatware/spyware. It EVENTUALLY gave me Odin.
FYI, this thread was of no use. No download links.
Later on, after searching for something unrelated, I got to a "better" site. Unlike the link above, this site has a zip file compared to the bloat-ridden executable.
I learned that I had to use Odin 3.07 and NOT Odin 3.09. Odin 3.09 did not have the PDA button that would be central to me flashing the ROM to the phone.
I started my journey on the thread for the Stock AT&T Firmware Collection. I learned that the thread uses the last three characters of the build name to identify the build. For example, 4.3's build name is I537UCUBML2 but was referred to as "ML2". This was a bit confusing but I got the hang of it. I then went over to the 4.4.2 rooting thread. It was there that I read Sunderwear says that you need to downgrade to 4.3 to root 4.4. I was grateful that AT&T only updated me to 4.3!
Sunderwear's second post described how to root 4.4.2 if you had a rooted 4.3. Since I hadn't done that yet, I proceeded back to the firmware collection and found the thread to root my 4.3 phone.
I downloaded the files and loaded up the first file to flash. I made the mistake of keeping my phone plugged in while trying to put it in download mode. It was when I stumbled upon this page that gave me the clue that my phone had to be disconnected first before going into download mode.
Once done, I clicked Start and Odin flashed my phone! It took about 2-3 minutes.
The next step was to do saferoot. The thread didn't link it so here it is.
SafeRoot requires your phone to be in USB debugging mode. Directions were found by googling. You go to Settings, About Device, and click Build Number until you get a message saying you have enabled developer mode. Then go back out one screen and go into Debugging options and enable USB debugging.
One installed I rebooted the phone and everything worked...except for wifi and "some other stuff". The thread warned you about this so I didn't worry. I flashed the next file and rebooted. Updated SuperSU and everything worked!!
I verified that I had root by installing Root Checker.
All was great with 4.3! Now for what turned out to be the more agonizing part: Upgrading to 4.4.2.
Going back to the 4.4.2 rooting thread, I learned that all I needed to do was install SafeTrap to update to KitKat and then flash a couple more files. I downloaded pwnedkitkat.zip (link in the thread) and then installed SafeTrap. I presume that SafeTrap is some sort of bootstraping method of updating the firmware.
I copied the SafeTrap apk file, along with pwnedkitkat and the updated superSU zip files to my external SD card. Once everything was copied, I installed SafeTrap and then opened it. SafeTrap then offered me the option to install Recovery Mode. Once done, I restarted my phone.
I noticed a new splash screen after the Samsung splashscreen. I clicked the Menu button (left of home) to start the recovery process. I clicked "Install" and pointed it to the pwnedkitkat.zip file. This took the longest. Probably took 15 minutes but felt like an eternity. I wasn't sure if my phone bricked when the screen turned off! But upon turning it back on, it was still going.
The bar moved very slowly. But remained patient. After a long 15-20 minutes, it updated! SafeTrap gave me the option to reboot there but I followed the directions and installed SuperSU from the SD card. It was a quick install.
I restarted the phone! I was done!! Right?
My phone got stuck on the AT&T splash screen! I started to panic! What did I do wrong?!
I missed Sunderwear's step five:
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Click to expand...
Click to collapse
Goes to show you to read everything. I missed it due to the line break. I downloaded the boot.tar.md5 file and put the phone back into download mode and push it via PDA in Odin (I presume PDA. It wasn't explicit.)
After a few hours of chewing my nails and wondering if I bricked it:
http://imgur.com/a/UFg6u#F5qFTdq
So thanks to everyone! Now if I could only unbrick my Skyrocket!
Outstanding instructions! Thank you for this. I wish all the instructions were as clear and detailed as this is.
:good:
I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Click to expand...
Click to collapse
do you mean it vibrates every 2 seconds and doesn't turn on?
:good:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
jimmietilt said:
do you mean it vibrates every 2 seconds and doesn't turn on?
Click to expand...
Click to collapse
Yup. The last time I looked into this was almost two years ago. It just sits in my drawer now.
dajabec said:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
Click to expand...
Click to collapse
I think what got me was all the new terminology and unfamiliarity of flashing. Jailbreaking an iPhone (which I've done before I had an Android) is pretty simple. It's pretty much point and click. But ROMs, flashing...these all have definitions which can be a bit overwhelming, even to a technical person such as myself. I've compiled Linux kernels from scratch!
But there's something about making your phone unusable. Something that I cannot live without, especially as I'm searching for a job.
It's nerve-wracking and I especially got nervous when I was putting KitKat on since it took so long. But overall, I'm glad I did it.
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Agent. said:
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
rdh28 said:
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
rdh28 said:
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
Devo7v said:
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
Click to expand...
Click to collapse
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Agent. said:
I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
I took mine to the AT&T device support center. I called before going in and they pretty much told me it was going to be destructive. I had previously wiped my phone earlier that day in the hopes that it would receive the OTA update.
I'm not going to lie: it's nerve-wracking, but straight forward. I know sometimes it helps to have someone hold your hand while you do it. And for me, it was definitely in the camp of, "What am I going to do if my phone craps out on me?"
But like what someone else said: you can back up your settings within Keis. I didn't. I just did a wipe. I backed up my photos but that's about it. Everything else was in the cloud. The one thing I should have done was transfer my Authenticator keys to another device because I couldn't log into AWS (which does not give out backup codes like Google). I did end up switching to Authy (I can't link to it since I'm such a new user but you can find it in the Play Store) which allows you to have more than one device. It shares your secret key between devices so it's technically less secure. But I needed the flexibility in case my phone crapped out on me again.
Pro Tip: to install all your apps again, go to the Google play store on your device and click "My Apps". Long hold one of the apps and then select the check boxes of the apps you want to install.
And hey if you run into anything there's plenty of people who check this forum regularly. I've managed to root 4.2.2 , 4.3, and 4.4.2 while retaining full functionality, just from this forum...the information is out there good luck!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Click to expand...
Click to collapse
What system apps need to be reconfigured? I can't really see that many that it would take you more than 15 to 20 minutes.
Thank you guys, I need to get my phone serviced anyway as there is a yellow dot in the top left of the screen that won't go away. So if AT&T sends me a new phone I can do all of the dirty work and then transfer everything side by side from the old device. If they won't for whatever reason I will do what you guys suggested. So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Agent. said:
So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Click to expand...
Click to collapse
I personally thing this is better since if you have 4.4.2 already, you have to downgrade to 4.3, root it and then put 4.4.2 on it.

[Q] Flashed TWRP Idiotically! :P && KNOX Tripped

Hey guys,
I flashed a TWRP recovery through flashfire and got this security error probably caused by a flagged KNOX. I found that the param.bin contains alot of of the POST/BOOT stuff including the boot logo. Digging deeper though found compiled stuff . I am posting the stuff maybe someone might be able to help that way we can get rid of that check and have a recovery. Don't get me wrong flashfire is awesome ,but at times you just need a recovery. As far as the KNOX stuff goes should I keep the phone?(since I may not be able to use MST, I still have 5 days to exchange it.)
See what att can do and if nothing then exchange it for a more customizable phone att locked bootloader caused this so if u still want the s6 get a tmobile varient and put the att chip in. It works and tmobile lets you do whatever you want with the phone so enjoy custimization.
Sent from my SM-N910V using XDA Free mobile app
madchainsawer said:
See what att can do and if nothing then exchange it for a more customizable phone att locked bootloader caused this so if u still want the s6 get a tmobile varient and put the att chip in. It works and tmobile lets you do whatever you want with the phone so enjoy custimization.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
FYI the phone is up and running a custom rom. Even on T-mobile I would still have to be careful with knox tripping after a recovery is flashed. Thanks for your reply man appreciated. Also if I could get some help on cracking the param.bin it would benefit every one that is not on T-mobile .
It's crazy to think that people can post the exact same mistake in the exact same forum because they aren't reading before performing impossible steps:
http://forum.xda-developers.com/showthread.php?t=3105398
[Q] PingPong Root -> TWRP -> Brick! Help!
KryptosXLayer2 said:
It's crazy to think that people can post the exact same mistake in the exact same forum because they aren't reading before performing impossible steps:
http://forum.xda-developers.com/showthread.php?t=3105398
[Q] PingPong Root -> TWRP -> Brick! Help!
Click to expand...
Click to collapse
Hey KryptosXLayer2 ,
I did read I just wanted to do it anyway to see. That how I had found the param.bin in the official rom. I am actually trying to get help on fixing this issue. My thinking is that if we can remove the secure_error.jpg from the bin and repackage it correctly. I should just resume booting. Because there is nothing to be done.

How to Unlock/Root Your Galaxy SM-G920T 5.1.1 without Tripping the Knox

Hello Everyone,
Today we'll be unlocking the Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung, which both required you to root your Galaxy S6 SM-G920T. I will guide throughout the steps to root your phone without tripping the knox counter, which will allow us to use one of the programs above. We will use the (sboot.bin) which allows their service centers to do flashing and repairs to the device without tripping the Knox counter. The modified bootloader also disables write protection on the device. Once you are done rooting and unlocking the Galaxy S6 SM-G920T, we will restore the official firmware 5.1.1. Don't worry, your phone is unlock permanently regardless of the times you restore the phone.
The steps to root your Samsung Galaxy SM-G920T 5.1.1
1. Install Samsung USB Drivers
2. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
3. Plug phone in and wait for drivers to install if necessary.
4. Download Odin
5. Download sboot.bin for Galaxy S6
6. Open odin and then you should now see phone’s modem port highlighted in blue.
7. Click on BL tab and select the correct sboot.bin that you downloaded above. Then click start.
8. When phone comes back on, power it off again and put into download mode.
9. Download UniBase_BOG8_v2
10. Open odin again and this time select AP tab and select UniBase_BOG_V2 file and click start.
11. You're Done!!!
When the phone turn on, it will be rooted. To verify that knox has not been tripped go back to download mode and it should still say KNOX WARRANTY: 0 (0X0000). Now you can go ahead and unlock your Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung. The sboot.bin isn’t playing very well, causing issues with Calls and Fingerprint sensor, but it is only for the meantime until you restore your phone back to the stock firmware.
Restoring your Samsung Galaxy SM-G920T to the stock firmware 5.1.1
1. Download the SM-G920T stock firmware
2. Open and extract the firmware file, then you should get the a file in .tar.md5 format.
3. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
4. Open odin and then you should now see phone’s modem port highlighted in blue.
5. Click the AP button tab and select G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
6. Make sure Re-partition checkbox is NOT selected, under the Options tab. Click start and wait for it to finish completely.
7. Enjoy!!! The G920TUVU2COF6 Android 5.1.1 firmware on your Galaxy SM-G920T.
I hope this guide helps everyone who wants to unlock their Samsung Galaxy SM-G920T, but needs their phone rooted first temporarily.
Will this work if I'm on the G920TUVU2COF8 build?
It may work!
yoderz said:
Will this work if I'm on the G920TUVU2COF8 build?
Click to expand...
Click to collapse
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Any chance we could get links to the files you reference? Thank you in advance.
ron.cabanillas said:
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Click to expand...
Click to collapse
Can confirm it works. Went my own route on some things but Knox is 0 and SuperSU and TWRP are installed and working
Use the Search Engines!
LPoirierIV said:
Any chance we could get links to the files you reference? Thank you in advance.
Click to expand...
Click to collapse
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Anyone with some credibility willing to try this? Or have tried it... No offense but the two people that posted have a combined 7 posts...
Sent from my SM-G920T using Tapatalk
So at the end of the step I'll end with stock of6 with root?
Will this deleted my saved data and apps?
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
ron.cabanillas said:
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Click to expand...
Click to collapse
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
It should work without problems
noodlev1 said:
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
Click to expand...
Click to collapse
These link should work fine with your galaxy s6 SM-G920t
You have to Root, unlock and restore
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock.
It should work fine
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
Regardless of the firmware COF8 or COF6, you must have the full stock firmware to restore your phone after it rooted and unlocked.
I can't post the link Yet!
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: this seems to be a much better guide
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
edit: and here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
I more than glad to post the link, I don't have any problems. The forum rules don't allow me yet to post the links. The guide you found have the link everyone needs too.
It should work Too!
LPoirierIV said:
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
Click to expand...
Click to collapse
The latest Tmobile is COF8, regardless COF8 or COF6 build you can unlock it. The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock. Now you can also flash to metro pcs, but you have to stay with the metro pcs after you unlock it with the code.
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
True i posted there a compilation to root without triping knox and on cof8. Must be on page 24 i think. And the md5 of sboot number to compare from ones in google
rooted but issues
both methods worked for my phone. got my phone rooter and unlocked. but i keep getting security threat warning if i stay rooted

Categories

Resources