I need someone to try this. I pulled the libs from Sprint HTC One 4.1.2 ROM and I need a tester. Can't answer for 4.2.2 yet. I did not make the zip but i placed the correct files in the zip.
If it doesn't work after the flash, you can use Root Explorer too push the individual files to the exact folder locations that are in the zip. See instructions below
BEFORE YOU START....DO A NAND BACKUP SO IF ANYTHING DOES GO WRONG, YOU CAN JUST RESTORE AND NOT HAVE TO FLASH AND SET YOUR WHOLE PHONE BACK UP.....I DEF RECOMMEND NOT SKIPPING THIS, BUT HEY SOME PEOPLE ARE COWBOYS TO INCLUDE ME.
NOTE: If you are on a 4.1.2 Sprint Based ROM like OMJ you can also try Trial Method 2 without flashing the libs to see if it will work. The 4.2.2 based ROMS from the HTC One FORUM may have the secure element already enabled and may not require the libs to be flashed, however I don't have any 4.2.2 libs I can pull and it may not be necessary. I need some testers. Your Secure element is not enabled or you need a lib fix if you get this Insufficient Secure Element Privileges for system image (release-keys).
Trial Method 1 - Patched Wallet - Sprint libs - Universal for 4.x.x Stock Sense Based ROMS - Need Confirmation
1. Download This Patched Version of Google Wallet
2. Use root explorer to push the Wallet.apk to system/app
3. Change permissions to rw-r-r
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot to Recovery
6. Install Sprint NFC Libs Test 1 fo 4.1.2 and 4.2.2 Test Ignore the name of the zips. We are in DEV phase need feedback before this begins to matter. (ALWAYS WIPE CACHE AND DALVICK BEFORE FLASHING ANY ZIPS).
7. Reboot Phone
8. Open and Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
9. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
10. Reboot Phone
11. When Phone Boots up, Enjoy!
Trial Method 2 - Modaco Toolkit - Universal for 4.1.2 and 4.2.2 Sense Based ROMS like ViperOne ROM, Android Revolution HD, InsertCoin ect... - Need Confirmation
1. Install XposedFramework 2.1.4 (hit "Install" in the installer app afterwards). Xposed Framework Forum Found Here
2. Install MoDaCo Toolkit v26
3. Open Xposed Settings and Enable MoDaCo Toolkit Module
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot
6. Open MoDaCo Toolkit (Takes 5-10 Seconds Don't Touch Screen)
7. Click Google
8. Click Check Box to disable Root and Supported Locale Check of Google Wallet
9. Click Download Wallet APK or You can install from Google Market
10. Install APK you just downloaded unless you chose the Market Place (DO NOT OPEN AFTER INSTALL)
11. Reboot For Modaco Toolkit changes to take place
14. Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
15. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
16. Reboot Phone
17. When Phone Boots up, Enjoy!
Screen Shots
Picture 1 - Step 6-7. / Picture 2 - Step 8-9
{
"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"
}
Trial Method 3 - Modaco Toolkit - Sprint libs - Universal for 4.1.2 Stock Sense Based ROMS - Need Confirmation
1. Install XposedFramework 2.1.4 (hit "Install" in the installer app afterwards). Xposed Framework Forum Found Here
2. Install MoDaCo Toolkit v26
3. Open Xposed Settings and Enable MoDaCo Toolkit Module
4. Change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
5. Reboot to Recovery
6. Install Sprint NFC Libs Test 1 fo 4.1.2 and 4.2.2 Test If you get any force closes or issues after reboot....Do a nand restore of your Rom and do the process again but Download and flash Sprint NFC Lib Test 2 this time. Ignore the name of the zips. We are in DEV phase need feedback before this begins to matter
7. Fix Permissions in Recovery and Reboot
8. Open MoDaCo Toolkit (Takes 5-10 Seconds Don't Touch Screen)
9. Click Google
10. Click Check Box to disable Root and Supported Locale Check of Google Wallet
11. Click Download Wallet APK or You can install from Google Market
12. Install APK you just downloaded unless you chose the Market Place (DO NOT OPEN AFTER INSTALL)
13. Reboot For Modaco Toolkit changes to take place
14. Set Up Google Wallet to 100% completion where you are ready to make a purchase. If successful move to next step
15. Change build.prop back to Stock upon successful set up of Wallet to Completion. At this point Wallet sets up all the way and you can make purchases.
AT&T HTC One
ro.product.device=m7
ro.product.model=M7
ro.product.name=m7
16. Reboot Phone
17. When Phone Boots up, Enjoy!
The stock AT&T HTC One build.prop (Case Sensitive) so before you change your build.prop, record the current config for your device to ensure it matches what I have...The same 3 lines you change to the Galaxy Nexus you need to write down because after Wallet sets up Completely, you will need to go back to stock.
If you extract the ZIP files from the NFC Lib test because I am not 100% sure the files will flash to the correct directory, but you can manually push them and it may be a pain in the butt unless someone is great at making zips
Here is how you would manually push. DO THIS IF YOU FLASHED THE ZIP AND YOU GET INSUFFICIENT RSA KEYS OR SECURE ELEMENT MISSING ERRORS
1. Extract Zip to Desktop
2. Place folder on SD Card of Phone
3. Open Root Explorer and navigate to Folder on SD Card
4. Inside that folder on SD card will be a system folder, go Inside that system folder
5. You will see an "etc" and "lib" folder
6. Copy the nfcee_access.xml and navigate to the phones system/etc folder and copy it in there
7. Rename the current one you have to nfcee_access.xml.bak and then paste this one in the folder and change permissions to rw-r-r
8. Navigate to the Folder you copied to your SD Card
9. Go inside that system folder then look for the lib folder
10. Repeat the same steps but now you will navigate to the phones system/lib and copy the files
11. Rename the 3 individual files that are already there and add .bak like you did previously
12. Repeat the same step for the individual file thats on the SD Card in the system/lib/hw folder
13. Make sure the files all have rw-r-r permissions
14. Once all are copied then you can reboot and follow the Trial instructions above to install Wallet
THIS WAY IS A PAIN IN THE ASS BUT IF IT WORKS IT WORKS
Troubleshooting And Development
reserved
Thought people would be more all over this, its perfectly safe to try, need some feedback because I would like to have working Wallet for everyone.
I would love to test it but I'm on 4.2.2
Looking forward to seeing the progress. Would love Google Wallet on my HTC. =/
Hoping to see that it will work on 4.2.2, 4.3, etc.
Taking donation?
Sent from my HTC One using Tapatalk 4
greenrocks said:
I would love to test it but I'm on 4.2.2
Looking forward to seeing the progress. Would love Google Wallet on my HTC. =/
Hoping to see that it will work on 4.2.2, 4.3, etc.
Taking donation?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
You can give it a try on 4.2.2, just do a nandroid backup so if you have an issue you can restore like nothing ever happened
Okay, will give it a try later. Will let you you know.
Sent from my HTC One using Tapatalk 4
greenrocks said:
Okay, will give it a try later. Will let you you know.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Ok, I am adding an aditional zip to try....Do the first one still, but if you get any force closes or error flash the 2nd one after you do a nand restore.........
I am also on a Sense based 4.2.2 rom (CleanROM to be exact) but I'll give this a whirl!!!
K.AuthoR said:
I am also on a Sense based 4.2.2 rom (CleanROM to be exact) but I'll give this a whirl!!!
Click to expand...
Click to collapse
Ok I updated OP, just have to ignore the names of the zip files....
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
K.AuthoR said:
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
Click to expand...
Click to collapse
I have had that happen before, next time don't fix permission I am not a cwm fan. If you get the same results next time then try zip 2. It won't hurt the phone
Sent from my SGH-T889 using xda premium
Something else I just noticed, now when I reboot my phone or cold boot, the HTC logo has the "this build is for developmental purposes only" red text printed at the bottom. That was not there before I made this attempt.
Any idea what causes that?
edit: I don't recall if I had the 'fast boot' option enabled or not so my device might have been just doing fast boots before and skipping the HTC logo. Regardless, I have not seen this before unless I was entering recovery.
K.AuthoR said:
Something else I just noticed, now when I reboot my phone or cold boot, the HTC logo has the "this build is for developmental purposes only" red text printed at the bottom. That was not there before I made this attempt.
Any idea what causes that?
Click to expand...
Click to collapse
That happens when you flash a custom recovery
I believe once you go s-off, there are ways to get rid of that message, but it does no harm....
K.AuthoR said:
I got all the way to step 5, installed zip and fixed permissions which took a good 5 minutes, clicked reboot in cwm, then my phone rebooted into a black abyss of the backlight blinking and the buttons blinking with and without the backlight blinking. Needless to say I'm a bit scared right now, this is my first non-Nexus phone. I lost all faith until I got to Hboot for a few seconds so I sent it back to CWM where I'm now restoring my backup. I feel like as long as Hboot is safe I'm good, but that really bugs me.
Putting the brakes on for tonight, I'll give it another shot tomorrow. If I didn't require my phone for work I wouldn't be as cautious about anything, I've honestly even been reluctant to S-Off the thing.
tldr - I am using CleanRom, not stock, so that could have also caused my issue. Will keep checking this thread out and offer future testing if necessary.
Click to expand...
Click to collapse
I have had that happen before, next time don't fix permission I am not a cwm fan. If you get the same results next time then try zip 2. It won't hurt the phone.
For the red text, this won't touch the bootloader, that has been there you haven't noticed it, that is binary and you can fix that only in bootloader. Flashing zips will not make that happen. This happens as soon as you unlock your bootloader and run custom Roms
Sent from my SGH-T889 using xda premium
Gotcha. I was just running with the 'fast boot' power option enabled and never happened to see my HTC logo again after incorporating S-Off into the picture. lol
K.AuthoR said:
Gotcha. I was just running with the 'fast boot' power option enabled and never happened to see my HTC logo again after incorporating S-Off into the picture. lol
Click to expand...
Click to collapse
Their is a fix for it in the HTC One international thread I used it before but I don't know if the bootloader version has updated since
Sent from my SGH-T889 using xda premium
bdorr1105 said:
Their is a fix for it in the HTC One international thread I used it before but I don't know if the bootloader version has updated since
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Interesting - do you have a link for the specific thread in the forum?
I'll give this Wallet fix another goaround tomorrow when I'm home from work.
K.AuthoR said:
Interesting - do you have a link for the specific thread in the forum?
I'll give this Wallet fix another goaround tomorrow when I'm home from work.
Click to expand...
Click to collapse
Go here
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my SGH-T889 using xda premium
So for 4.2.2 roms, there are no libs to download?
Tried based on method 2 and same results as always, just sits and spins at Setting up Wallet, this may take up to 5 min and then terminates.
The issue that has been previously address is the belief that we will not be able to have Google Wallet because we don't have a secure element(this is why the GE, DEV and US variant phones) can't get or install.
I'm willing to be a tester but I think the results are always going to be the same, fail due to no secure element.
nest75068 said:
So for 4.2.2 roms, there are no libs to download?
Tried based on method 2 and same results as always, just sits and spins at Setting up Wallet, this may take up to 5 min and then terminates.
The issue that has been previously address is the belief that we will not be able to have Google Wallet because we don't have a secure element(this is why the GE, DEV and US variant phones) can't get or install.
I'm willing to be a tester but I think the results are always going to be the same, fail due to no secure element.
Click to expand...
Click to collapse
I have seen instances where it has worked on viper with screen shots....
The Sprint One has the secure element it's not blocked by the carrier and my boy has it. You can try trial 1 and flash the zip it has the libs from sprint off a 4.1.2 based Rom. I would do a nand back up incase it puts you in a boot loop. Give trial 1 a try.
Sent from my SGH-T889 using xda premium
Related
[Custom Touchscreen Recovery & ROOT!][Port][UPDATE! 7/13/12] TWRP 2.2.0 for Fireball
I have successfully ported TWRP Recovery to the Droid Incredible 4G LTE (Fireball). It is an unofficial port and all credit goes to teamwin & eyeballer for the original One S version this is based on.
Screenshot:
{
"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"
}
Installation:
Method 1: "Easier," Doesn't require fastboot!
0) Unlock via HTC Dev.com
1) Download TWRPDroidIncredible4G.zip Here
2) Verify the MD5 with mine: 6B0756E20FF11B593C6EC2291B5A38CF
3) Rename TWRPDroidIncredible4G.zip to PJ53IMG.zip (make sure you don't get PJ53IMG.zip.zip in windows!)
4) Place the zip file on the root (not in any folders) of your EXTERNAL sd card.
5) Boot to hboot by holding Volume-Down and Power
6) Green text will scroll and will ask you to press Volume-Up. Do that.
7) You are done! Press Power to reboot back into Android. Delete the PJ53IMG.zip off your SD card immediately or you won't be able to get into recovery with the Volume-Down & Power combo.
8) You can now boot to recovery by holding Volume-Down and Power to boot the phone and navigating to "Recovery" in HBOOT with the volume keys. Select it with the Power button.
Method 2: Fastboot (probably faster for "advanced" users)
0) Unlock via HTC Dev.com
1) Download TWRPDroidIncredible4G.zip Here
2) Verify the MD5 with mine: 6B0756E20FF11B593C6EC2291B5A38CF
3) Extract the zip file. Ignore the android-info.txt file.
4) Place the recovery.img file in your fastboot folder & boot the device into fastboot mode. You know how to get here since you unlocked.
5) Send the command "fastboot flash recovery recovery.img"
6) When complete, restart your phone. You can now boot to recovery by holding Volume-Down and Power to boot the phone and navigating to "Recovery" in HBOOT with the volume keys. Select it with the Power button.
To Revert To Stock Recovery:
1) Download the StockRecoveryDroidIncredible4G.zip from HERE!
2) Verify the MD5 with mine: 624365D2F5F44FDF2583EE8C619592C7
3) Follow the directions to flash the custom recovery, but substitute this zip file.
Permanent Root
Info: The Droid Incredible 4G LTE is capable of permanent root. It is very simple and safe. If you want to unroot, flash the RUU supplied by HTC.
Install Instructions:
1) Download PermaRoot.zip from HERE!
2) Place on SD card
3) Make a nandroid backup in TWRP.
4) Flash in TWRP custom recovery
Known Issues (Minor issues only):
1) Can't copy things from computer over USB to the internal sd card. External card is fine and you can use the file manager to copy it over if you want.
2) I have experienced the occasional random restart before a rom install starts on my Rezound port. This can be fixed by rebooting the recovery and is not dangerous. May not happen on this port.
Zip Install Failed? Restart recovery by powering off fully and booting in from HBOOT. If that doesn't help, make sure your zip file isn't corrupted (check MD5). If you made the zip, make sure it is packed correctly and the updater-script has correct syntax & you have an appropriate update-binary.
Thanks to maqsur for testing!
Changelog for this recovery only (not official twrp changelog):
7/13/2012 - Updated to latest TWRP 2.2.0
7/11/2012 - Corrected Debug and Secure flags in the default.prop. This fix is for development purposes and was NOT a safety issue on previous versions! New MD5 reflected in OP.
TWRP Team Changelog:
2.2.0
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
2.1.x - Original Fireball Release
Numerous small bug fixes and improvements
con247 said:
I have successfully ported TWRP Recovery to the Droid Incredible 4G LTE (Fireball). It is an unofficial port and all credit goes to teamwin & eyeballer for the original One S version this is based on.
Installation:
0) Unlock via HTC Dev.com
1) Download FireballTWRP2Alpha2.img attached to this post.
2) Verify the MD5 with mine: D0BD138A5B56AFB109846576E2D953FE
3) Place the .img file in your fastboot folder & boot the device into fastboot mode. You know how to get here since you unlocked.
4) Send the command "fastboot flash recovery FireballTWRP2Alpha2.img"
5) You are good to go. The original recovery is also attached if you need to revert.
Known Issues (Minor issues only):
1) Can't copy things from computer over USB to the internal sd card. External card is fine and you can use the file manager to copy it over if you want.
2) I have experienced the occasional random restart before a rom install starts on my Rezound port. This can be fixed by rebooting the recovery and is not dangerous. May not happen on this port.
Thanks to maqsur for testing!
Click to expand...
Click to collapse
Thank you very much for this.
Worked like a charm, tyvm Con.
Working good except I cant see the external SD within recovery. I also try to mount it by hitting the checkbox but it never works (the box never gets checked). I tried multiple SD cards of different sizes. Both were Fat32, perhaps I can try HFS, not that it should make it better...
hmmm
no problems here. Thank you so much. did this then the 3 button remap. Now i'll i need it to remove the dumb wifi icon, then it'll be close enough to perfect for me.
Dude... exactly what I need. You are awesome.
JDMpire said:
Working good except I cant see the external SD within recovery. I also try to mount it by hitting the checkbox but it never works (the box never gets checked). I tried multiple SD cards of different sizes. Both were Fat32, perhaps I can try HFS, not that it should make it better...
hmmm
Click to expand...
Click to collapse
The external card is called /sdcard and it worked for my tester.
I'm sort of new to the process now with android devices, haven't owned one since my Xperia X10. I have the recovery flashed to my DInc4g and now I'm trying to root it. Where exactly do I do that? I get it to the bootloader, which is unlocked now, and I don't know what to do exactly after that.
Thanks in advance.
JDMpire said:
Working good except I cant see the external SD within recovery. I also try to mount it by hitting the checkbox but it never works (the box never gets checked). I tried multiple SD cards of different sizes. Both were Fat32, perhaps I can try HFS, not that it should make it better...
hmmm
Click to expand...
Click to collapse
I can see my 32GB external with no issues.
Nevermind, I got it running and rooted. Also, my SDcard shows fine. Thanks again.
Hey Con, If you are planning to dev a little on the Inc4g (which I hope) I'll would be happy to be your test bed if you need one. Would love to see this phone get some dev'in love.
*Madmoose* said:
Hey Con, If you are planning to dev a little on the Inc4g (which I hope) I'll would be happy to be your test bed if you need one. Would love to see this phone get some dev'in love.
Click to expand...
Click to collapse
I can't get the deodexed roms to boot so I am dropping all my support for now since there isn't much I can do & my upload is too slow to send out test builds all the time.
I feel your pain on the upload situation. I was working a little with Hasoon2000 today and I think he has the deodex working. Just had a force close on a file or two. I appreciate your efforts though man, you took us into root and recovery which was half the battle. My offer still stands though, if you come back, hit me up for testing. I'd be glad to help. Enjoy your GNex, I have one as well, just cant get past the horrible battery life
*Madmoose* said:
I feel your pain on the upload situation. I was working a little with Hasoon2000 today and I think he has the deodex working. Just had a force close on a file or two. I appreciate your efforts though man, you took us into root and recovery which was half the battle. My offer still stands though, if you come back, hit me up for testing. I'd be glad to help. Enjoy your GNex, I have one as well, just cant get past the horrible battery life
Click to expand...
Click to collapse
I might sell it and my Rezound and pickup a SG3. I would like the inc 4g but I need a large screen!
con247 said:
I might sell it and my Rezound and pickup a SG3. I would like the inc 4g but I need a large screen!
Click to expand...
Click to collapse
It's a bummer to see you moving on but it sure is understandable. Thanks for porting the recovery and getting everything moving in the right direction. Have fun with the SG3 if you get one.
blazingwolf said:
It's a bummer to see you moving on but it sure is understandable. Thanks for porting the recovery and getting everything moving in the right direction. Have fun with the SG3 if you get one.
Click to expand...
Click to collapse
Jellybean source & new radios dropped for the Nexus so I'll see what happens with that before I do anything drastic. Plus, if the GS3 ends up being stuck with Touchwiz I won't be happy about that. I like Sense but not TW.
I will see about building a new recovery from source (possibly today/tomorrow ??) which would hopefully allow dual SD mount.
Sorry to double post, but I re-wrote the entire OP. If you believe there are errors, shoot me a PM and I will fix ASAP. Hopefully it will clear up any questions you and others might have.
I also added a fastboot-free install method I pushed with kernels & recoveries on the Rezound despite the semi locked bootloader.
You can use my base if you want.
http://forum.xda-developers.com/showthread.php?t=1762537
@con
just wanted to say thanks for helping out! (sans phone)
makes life easier for the rest of us :highfive:
Hey Con, any idea what happens with the zip failing to install? I ran into it earlier and was just curious. Easily remedied with a restart of the phone though.
Figured I would share this just because once I found the right pieces to the puzzle it's gone beautifully. Instruction steps match URL list #'s. I put the downloaded files into my external SD in a folder called 00-CWM so that it always shows up at the top of the listings.
First off, the pieces:
CWM upgrade steps
CM10 download
Google apps package
CM Flash Instructions
Steps:
0 - BACKUP YOUR DATA: Duh. this is a sanity check step really, make sure you've taken efforts to protect anything you want to keep should the worst happen. At the very least do a CWM backup to the external SD card prior to flashing.
1 - Install the appropriate CWM recovery image (AT&T - 'quincyatt' - in this case). This is critical because without it, the CM10 flash step fails with 'error 7'. Root is required to follow the steps at this page, you can go here to find the means to do so if you haven't done it already.
The actual DD command did not match my own file location, so I had to modify it slightly. To figure out where to go for this run the android terminal emulator. The first command you run will be 'su' - you'll get prompted by superuser, hit allow. Next type 'df' (hit enter) and you'll see a list of mounts, mine was something like /mnt/external_sd/ when I did this step - look for something that makes sense, then get over to it via 'cd /path/to/your/external_sd/CWMfolder' (hit enter). Next run 'ls' and make sure you see the recovery-cwm-touch-5.8.4.3-whatever.img file like you're expecting. Now, start typing 'dd if=./' and DO NOT hit enter yet, go to the page mentioned above and copy from the filename all the way to the end of the line and change back to the emulator and paste (long press on the screen, paste), and hit enter. It will take a few seconds and then give an 'ok' with a few lines of output at the end if all goes well. Congrats! you now have CWM for CM10 (btw, grab the TOUCH version, it's free when doing it manually, only updating to it through rom manager costs money).
2 - I grabbed the M2 at that page, but if you click 'nightly' on the top left section you can grab whatever the latest build is.
3 - Strictly speaking you don't need Google apps to boot your phone and have it be useable.. but come on. An Android-based phone without Google apps? Pfft.
4 - The next thing is to get into that new shiny recovery you just installed. Jump straight to the 'flashing cyanogen mode' link on the wiki (hey, item 4 there too!). You can do it the traditional way with the power+vol+home buttons, but since you've got root installed I'd suggest just grabbing 'quick boot' or rom manager from the market and using their methods to go directly to it from your launcher. However you go about it, get to recovery.
Once again, if you haven't done so already: BACKUP YOUR DATA.
Your external SD card should be fine, but these steps tell you flat out to wipe/reset your phone which will nuke all internal memory. I went even farther than part 5 and 6 on this URL and next went to advanced and told it to wipe dalvik cache as well. Considering they don't tell you to it's probably not a mandatory step but in the interest of a totally barebones start, I did it.
Now you get to the moment of truth - flashing that lovely CM10 file. If you've followed me through this it should go nice and easy, though not much scrolling by on the screen to tell you how it's going. It will just say 'installing' for a while and then be done with no particular errors. Next, flash the google apps zip file. You'll get a little more output there but again it should be fine and have no issues.
Once that's done, press back until you see 'reboot phone' and hit it. Now wait while it boots up and enjoy.
ADDITIONAL NOTES ON THE EXPERIENCE:
Why am I writing this? It all seems trivial, right? Yep. Except that for two days straight I couldn't find any information whatsoever on the current release install instructions. Everything was saying to go to CM9, then do this, then do that, etc. Then I found URL #4 and thought 'GREAT!'... until the cwm recovery they link to didn't match the md5 checksum and I had to start digging for that piece independently.
The best part so far has been that after booting up CM10 and putting in my Google credentials, I got told about updates - so I fire up the market and was floored when all of my previously installed apps came flooding in. All 84 of them. Google profile backup was a beautiful thing. It didn't get my settings, so if you did a TiBkp of your stuff you can probably take advantage of it, but this was a huge basic help for me.
CM10 runs well so far and I'm half tempted to leave the trebuchet launcher as primary rather than nova like I'd been on ICS.
All in all it's a positive experience once things got rolling, and I am just trying to help by gathering up bits of info so that others won't go through the headache I did to get to this point.
Can I only flash with cwm. Can I use twrp?
The aim of this guide is to enable you to install a custom firmware on your Optimus G while being as clear, accurate and succinct as possible. This guide is intended for use by Windows users with an AT&T Optimus G (AKA LGE970).
I've presented the following sections in a specific order for a reason: you need to root to unlock, and you need to unlock to install a custom firmware. If you're currently running what the manufacturer gave you, you need to start with rooting, then unlocking, then trying other firmwares. Be careful, good luck, and have fun!
How to "root" your Optimus G
(Optional if you have another means of un-RARing) Download and install 7-zip from here. You need this to open certain types of archives (specifically .rar, but you might also want to open .tar, .bz2, or other types of archives in the future). This program is supremely awesome in its ability to open almost any archive you throw at it. It's also unobtrusive and efficient.
Download and install LG USB Drivers from here. Without these drivers, your computer won't be able to effectively communicate with your phone. This is vital for the steps we will be taking.
Enable USB debugging by going to Settings->(General)->Developer options" and checking the box next to "USB debugging." You will get warnings. You can probably ignore them. This setting will allow you to run commands on your phone from your computer (via USB). For more info on the Android Debug Bridge, click here.
Download and extract (using 7-zip (or whatever)) the root exploit from here.
Connect your phone to the computer with your USB cable.
Put the phone into "Charge Only" mode at Settings->General->PC connection->USB connection type
Open CurrentRoot.bat and follow its prompts. You will need to change from "Charge Only" to "Media sync (MTP)" mode. The setting is in the same place.
Run SuperSU (now in your apps drawer) it and make sure it works. This program allows others to gain access to superuser privileges. For more info on rooting and what kind of stuff it lets you do, click here and/or use Google.
If that didn't work for you, try following instructions from the thread where this root method came from.
How to unlock the bootloader
The bootloader is the first program your phone runs and its main job is to load the operating system. The stock bootloader is locked and will only run versions of Android that LG and AT&T want it to. Since our goal is to install and run custom firmwares, we must circumvent this locked bootloader. Luckily, thecubed and Shellnut2 have found a way to do this for us. What you want to do is buy Shelnutt's app. There are several reasons you should throw down some cash on this:
It's way easy to use
It'll make backups of your stock recovery/bootloader for you, it'll also make restoring these backups easy
The money is for a good cause
If you're still confused, visit thecubed's thread. He is the man, thank him a billion times. Then thank him again for being a nice guy.
For the convenience of those interested, here is the more laborious/error prone/manual way to unlock (NOTE: this method does NOT work if you've updated to Jelly Bean, you need to use the app):
If you haven't already, download and install 7-Zip and the LG USB drivers, and make sure you have USB Debugging turned on (see above).
Download the latest version of the bootloader unlock here (latest version has the highest version number).
Ensure that your screen is on and unlocked (I'd go to "Settings->Display->Screen timeout" and set the timeout to never to make sure the screen doesn't go off during this process). Your screen must remain on because SuperSU will ask you to grant superuser privileges to the unlock script and you want to be able to tap "Yes" when the time comes.
Connect your phone to the computer with your USB cable, and run the freegee.bat script in extracted files on your computer. Do NOT run this script as administrator. The install will fail if you do. Follow the prompts. You can ignore "No space left on the device" errors, but "adb.exe not found" or "tar: invalid magic" errors are not negligible and indicate either you skipping a step, a funky download, or something very bad.
Once the script finishes, make sure you have a populated "backups" folder in the folder where freegee.bat lives. The backups folder contains your original stock/locked bootloader, which you might want if you ever want to revert to stock.
If you're sure the script ran successfully, power off the phone. Next, hold down the power and volume up keys simultaneously to enter fastboot mode. You should see a screen that looks like this:
{
"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"
}
In fastboot mode, there is a menu, but it's hidden. To navigate it, remember that volume up moves the cursor up, volume down moves it down, and power selects the currently highlighted option. The options are, in order:
Start - boot the phone normally [highlighted by default]
Restart Bootloader - reboot into bootloader
Recovery Mode - enter ClockworkMod recovery (more on this later)
Power Off - (duh)
Here is a video of thecubed showing you how to get to ClockworkMod from the bootloader (like a boss):
Using Team Win Recovery Project
Team Win Recovery Project (AKA TWRP) is a recovery, which basically allows you to install new firmwares and apply updates/modifications to already-installed firmwares (and a bunch of other things, like mounting and formatting portions of your phone's memory). It is the default recovery option when you use the Freegee app to unlock your phone (the other is Clockworkmod, which is so similar I won't be writing a separate guide on how to use it). Navigating TWRP is fairly self explanatory. Many great guides on how to use TWRP have been written and can be found via Google. Here is the first search result that came up for me. It's a pretty good guide.
One thing I will vehemently recommend is that you make a backup every time you install a new firmware. Personally, I backup apps and texts with Titanium Backup and my current firmware via TWRP (the linked guide explains how to make a backup in TWRP). Backups are a good idea and people should always make them. ALWAYS.
Installing custom firmwares
Follow the firmware author's instructions EXACTLY. These guys know what they are doing, certainly more than you or I. Check out the development threads for ROMs to try out.
Note: Be sure that if you are installing ROMs that require the Jelly Bean OTA update that you have taken that update.
There are two ways to do this: receive the update as intended (Over The Air) or use LGNPST (guide on using that under FAQ 3.a of this post) or autoprime's awesome tool, TeenyBin.
FAQs
How do I upgrade FreeGee? The easiest thing to do is simply install the new version of FreeGee the way you did the old one. It will work. Make sure you keep your original locked bootloader in a different, safe place though, just in case you ever want to revert to stock (if you try to return your phone, for example).
How do I disable that pesky OTA update notification? This comes courtesy of shawnchalfant and adfurgerson (visit ad's thread for more details): go into Titanium Backup and freeze the following programs: com.lge.lgfota.permission 4.0.4-91f513f88d AND com.lge.omadmclient 3.2.21
How can I re-lock and un-root my phone?
How to LGNPST to restore a factory image.
Obtain the following files: AutoLGNPST-tSilenzio.zip (available on IRC), and the firmware. Unzip AutoLGNPST-tSilenzio.zip and follow the instructions in "READ ME FIRST.txt" (mad props to tSilenzio for automating this process).
Here's the laborious/error prone/manual method for LGNPST-ing back to stock.
You need to obtain the following files: LGNPST-PhantomPhreak53.zip, LGNPST_ACG_2.2.3_Lab.zip, and the firmware. Follow the following steps (please note: I am less experienced with this process and find it much more tedious. Also, IMHO, I don't think the people you're returning the phone to will care if you leave some minor traces of your unlocking shenanigans. I think the process above this is more than sufficient and simpler). Credits go to Jhoopes517 for this process, he showed me how to do it in his thread.
(Install LG USB drivers)
Extract LGNPST_ACG_2.2.3_Lab.zip, run the installer. Open file explorer to C:\Program Files\LG Electronics\LGNPST and replace the current LGNPST_ACG.exe with the one in the extracted folder (if you are on a 64-bit version of windows, go to C:\Program Files (x86)\LG Electronics\LGNPST)
Extract LGNPST-PhantomPhreak53.zip and run LGNPST_GenericModels_Ver_5_0_12_0.exe and then run LGNPST_Components_Ver_5_0_20_0.exe
In file exlorer, navigate to C:\LG Electronics\LGNPST and copy over the "Models" folder from the extracted Phantom zip folder
Run cmd as administrator and execute the following
Code:
regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
Extract LGE970AT-01-V20j-310-410-MAR-08-2013.zip and change the extension of the .tot file to .bin
Connect phone to computer, power off, and then power on, holding down the power button and both volume buttons
Run the newly replaced LGNPST_ACG.exe from step 2. Select the DLL from step 5 and the .bin from step 6.
Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release. DO NOT disconnect the cable before LGNPST is done doing its thing. Your phone may reboot. This is OK.
(If you are using Shelnutt's app, simply use the button in the app to re-lock and install the stock stuff).
Here's the laborious/error prone/manual method for re-locking the phone and installing the stock recovery/bootloader/kernel.
Remember the backups of the locked bootloader that you kept? You're going to need them. Obviously, you'll need USB Debugging enabled and LG USB drivers installed. Copy them to your phone's "Internal Storage" in a folder, in this example it's called "backups." Connect the phone to your computer via USB, open a command line (cmd) and type the following:
Code:
cd C:/some/folder/where/you/have/adb.exe/eg/your/freegee/download
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/backups/aboot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/recovery-att-backup of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd basically copies from the if= location and writes to the of= location. The first three dd steps write a bunch of zeros to the recovery, boot, and aboot partitons, the last three write the backups to aboot, recovery, and boot. If you want to know more, read all about dd here and/or Google. If you lost your backups, you can try writing mine.
Now you've restored the stock bootloader and recovery, but your phone is still rooted. To unroot it, open SuperSU, go to its settings, and tap "Full unroot." Do a factory reset (Settings->General->Backup & reset->Factory data reset) and you should be good to return the phone to AT&T (or whatever).
Be careful with these last two methods if you have removed any bloatware or installed a custom firmware, you may prefer to LGNPST back to stock (LGNPST is almost always a safe way to return to stock).
blenkows said:
Haha I wish I had seen this earlier. I had screenshots before and after so I could see exactly what was removed but I had just deleted them. From memory, it doesn't seem like too much was removed. All the AT&T apps are gone but it appears LG's apps are still here.
Click to expand...
Click to collapse
Here is a list of apps I had shortly after factory reset on stock for people to compare with theirs. I have struck out the ones I was able to remove without my phone blowing up. Let me know if you safely removed one and I'll strike it out. Also let me know if I missed any or included an app which isn't part of stock. Thanks!
AAT
Adobe Flash Player 11.1
Adobe Reader
Amazon Kindle
Android keyboard
Android live wallpapers
Android system
Aspect ratio correction
AT&T address book
AT&T code scanner
AT&T family map
AT&T hot spots
AT&T locker
AT&T messages
AT&T navigator
AT&T ready2go
AT&T smart wi-fi
Bluetooth share
Browser
Bt/wifi test
Bubbles
Calculator
Calendar
Calendar storage
Calendar widget
Camera
Car home
Certificate installer
City ID
Clock
com.android.backupconfirm
com.android.providers.partnerbookmarks
com.android.providers.settings
com.android.sharedstoragebackup
com.lge.lgdrm.permission
com.lge.lgfota.permission
com.lge.lockscreen
com.lge.omadmclient
Contacts
Contacts storage
DeviceHelp
Download manager
Downloads
DRM protected content storage
DRM service
Email
Email widget
EmailServices
Face unlock
Facebook
Favorite contacts widget
File manager
File networking
FileShare
Finance
Gallery
GestureOverlayService
Gmail
Google account manager
Google backup transport
Google calendar sync
Google contacts sync
Google partner setup
Google play books
Google play magazines
Google play movies & tv
Google play music
Google play services
Google play store
Google search
Google services framework
Google text-to-speech engine
Google+
Home
Home selector
Home theme - Biz
Home theme - cozywall
Home theme - marshmallow
HTML viewer
Key chain
Lg keyboard
Lg tag+
Lg voicecommand speechpack
Lgapduservice
Lgatcmd service
Lgsmartcard service
Lgsystemserver
Live tv
Live wallpaper picker
Local search
Lock screen settings
Maps
Marionette
Market feedback agent
Media home
Media storage
Messaging
Multi-photo live wallpaper
Music
Music
Musicfx
My uploads
MyAT&T
Network location
News
NFC service
Nfsservicemanager
Note pad
Note pad widget
On-screen phone
Package access helper
Package installer
Phone
Phone/messaging storage
Photo frame
Playready cert test
Polaris office 4.0
Power control widget
Quickmemo
Search applications provider
Settings
Setup wizard
Shutdown monitor
Sim toolkit
Smartshare
Social+
Streaming player
System ui
Talk
Task manager
Today+ widget
Tom's diner
Twitter
User dictionary
Usermode
Vidclip
Video wiz
Videos
Voice command
Voice search
Voicemail
VPN client
Vpndialogs
Wap service
Weather
Widevine keybox test
Wiper app
Wise screen
World clock widget
YouTube
Yp mobile
I can't root. What do I do?
Double check that you have followed all the steps in this guide (USB drivers, correct settings, etc.) If your software version ends in "c," you need to LGNPST to the version that ends in "o" (see the section on LGNPST in this post).
Why shouldn't I run the Nexus 4 conversion?
See this post by thecubed. Don't be impatient, a legit, safe ROM is forthcoming here. Messing with partition tables is needlessly risky.
My shiny new firmware has no APNs and I don't get mobile data! What do I do?
Use the APN settings in this post. They have always worked for me. If they don't try setting the "APN" variable to "pta" instead of "Phone."
... (ask me more questions!)
I hope you found this useful. Obviously this is a work in progress. I am way open to suggestion, please leave a comment below! If you liked this post, hit the thanks button and/or rate this thread so that others know this guide is legit. Thanks!
Very nice, man. This is great for people who don't want to have to hop between threads for all the different information.
I recommend we sticky it.
this is definitely appreciated. i was looking for a guide when i first rooted and unlocked, just to read along with making sure i was doing it right. more just to double check my process than actually needing it.
This is the best root/ROM guide I've ever seen. Excellent job.
Sent from my LG Optimus G
anyone try this on E97110d
should it work?
cpus456 said:
anyone try this on E97110d
should it work?
Click to expand...
Click to collapse
I haven't so I can't recommend trying it.
Awesome work! someone please sticky
all worked great!
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
karelson said:
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
Click to expand...
Click to collapse
Both of those requests are covered in the OP. Specifically, look at FAQ #2...If you can't understand that, I can't help you.
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
martyotaku said:
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
What files do you have exactly? The easiest way to do it, in my opinion, is to follow the steps in FAQ #2.
i have the stock rom(i deleted some bloat) and i went on thecubed's irc and got some dlls and and a lg program but no clue what to do
Is there a way to restore? I totally messed up. My phone won't turn on at all. Help would be appreciated thanks.
i need a step by step for LGNPST back to stock if possible please
martyotaku said:
i need a step by step for LGNPST back to stock if possible please
Click to expand...
Click to collapse
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
carrett said:
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
Click to expand...
Click to collapse
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
aznracer62 said:
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
Click to expand...
Click to collapse
The folks in IRC know much more about lgnpst than I do. There's no secret that's being withheld, and unfortunately my best guess is that the lgnpst experts in IRC are right and it is a hardware issue. The good news is that you don't have to tell Best Buy the events leading up to your phone's demise and they probably won't be able to tell what they were either (we're talking about Best Buy employees here; most don't give two craps about their job).
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
carrett said:
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
Click to expand...
Click to collapse
I've tried something similar to that. Basically that's just an older version of LGNPST but when you use it, it says verizon wireless on it, well the one i downloaded at least. And you're right, took it to best buy and they didn't ask about it. I have up to January 24 to exchange it again in case it happens again. If the guys on IRC say it's hardware after explaining exactly what i did, it's the hardware. Gotta admit, i'm new to LG. I came from a line of Samsungs. Usually if anything goes wrong id just reflash with Odin or Heimedall and everything's back to normal again. LGNPST does the same function? From what i've read it serves the same purpose.
Anyway, take 2 on this guide. Deleting everything LG from my computer and starting fresh. One thing that i did notice when rooting, cmd gave me an error saying i'm missing backup_restore.apk (or something of similar name).
AT&T
I am not responsible for anything that happens to your device by doing this! If you break it, brick it or just plain blow it up. it is your phone and your responsibility for what happens to it.
Here it is. Full AT&T With Root - since this is AT&T based all bands should work as well
This is Based On AT&T PH1 Firmware and is Completely Stock and Unmodified
To Avoid Repeat Questons. READ! READ IT AGAIN! and then READ it once more! if you do not Understand any part of this. Do Not Continue!!!
This Guide assumes you have some basic knowledge and can at least copy and paste for the most part! It is Intended for advanced users!!!!!!!!
This Guide also Assumes you have an sdcard inserted in your phone(however some of you may not and this will not work.)
This Does NOT Trip Knox.
Read this entire post before doing anything to avoid issues and FOLLOW Directions - if you don't things will not work right.
Note! if at anytime during the following steps you see the samsung boot animation before step 11. start over cause you screwed up!
Step 1. Initial PreSetup Requirements and Downloads
Make Sure your ExtSDCard(the one you put in your sim tray) is formated exfat(backup your card before you do this in windows or linux(whichever you use))
https://www.androidfilehost.com/?fid=24651430732237653 bbx.rar
https://www.androidfilehost.com/?fid=24723785898787049 ATT_System.rar
https://www.androidfilehost.com/?fid=24713784966775407 AT&T Bootloader
https://www.androidfilehost.com/?fid=24713784966775395 AT&T Modem
Step 2. extract system.rar and bbx.rar and then copy system.img and bbx to your extsdcard(the sdcard you inserted into your phone)
Step 3. odin sprint userdebug firmware available here. http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
Step 4. Directly after odin is done with the sprint file you will immidiatly be presented with an update screen
Step 4a when this process of erasing your phone is finished it will reboot(this is the point you want to do the next step)
Step 4b. press and hold power, home and vol up to enter recovery
Step 4c If you see the samsung boot animation. you did NOT do this right and i would suggest you start over
Step 5. open a command prompt in your adb folder and do the following steps 1 at a time(these are case sensative)
Step 5a. adb shell
Step 5b. su
Step 5c. setenforce 0
Step 5d. export PATH=$PATH:/sbin
Step 5e. mount -o remount,rw /
Step 5f. on your phone, go to apply update from sdcard(this will mount your extsdcard as /sdcard and you should see the system.img file and the bbx file) do not select anything, go back to adb and continue(it is not a big deal if those files don't show. we just needed the extsdcard mounted as sdcard - the files exist, just continue to the next step)
Step 5g. cp /sdcard/bbx /sbin/bbx
Step 5h. chmod 777 /sbin/bbx
Step 5i. cd /sbin
Step 5j. ./bbx --install /sbin
Step 5k. umount -l /system
Step 5l. /sbin/dd if=/sdcard/ATT_System.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
Note. you will see a blinking cursor. just be patient
Step 7. when it is done you will see something similar to this
11161600+0 records in
11161600+0 records out
5714739200 bytes (5.3GB) copied, 268.668086 seconds, 20.3MB/s
Step 8. if all went well you should be at your prompt and not in adb anymore
Step 9. from your command prompt simply type
Step 9a. adb reboot bootloader
Step 10. open odin and click the bl button and select this file - BL_N930AUCS1APH1_CL8706614_QB10526661_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930AUCS1APH1_CL8706614_QB10526661_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10c. now click start. it will reboot when done let it fully boot this time.
Step 11. once booted and you have setup your phone, we need to add the root files or supersu as most of you know it
Note! pertaining to Step 12. these instructions were taken Explicitly from @freeza thread which is listed in step 3
Step 12. Now we need to add supersu and the needed files for it to work
Step 12a. download this file - https://www.androidfilehost.com/?fid=24651430732236679
Step 12b. Extract the sun7 file to your adb folder making sure the files are in a folder called sun7(mine looks like this - c:/adb/sun7 and contains 4 files)
Step 12c. Open a command prompt where your ADB executable and sun7 folder are.
Step 12d. adb shell
Step 12e. su - Note! if your adb prompot changes from a $ to #(you are good and have root access)
Step 12f. type exit twice to get back to the command prompt. - Your Phone should be fully booted when you do this
Step 12g. adb push sun7 /data/local/tmp/su
Step 12h. adb shell chmod 0777 /data/local/tmp/su/*
Step 12i. adb shell
Step 12j. cd data/local/tmp/su
Step 12k. su
Step 12l. ./root.sh - Note. this command begins with a . do not leave it out
Step 12m. Your Phone will now reboot
Step 13. when booted back up go to playstore and install busybox on rails or a similar app and install busybox to /system/xbin(if your given an option of where to install it)
Step 14. Thats Pretty Much it. most of all enjoy it
Additional Notes!
If for any reason you do a factory reset. you will break root and need to redo this method to get it back
If you use shealth do not update it or allow playstore or galaxy appstore to auto update it or it will break it
Enjoy and FOLLOW Directions - if you don't things will not work right.
thank you to the following:
@freeza - for posting the original userdebug file
@ted77usa - for testing
@bajasur - for the initial idea which ultimately led to this
@Surge1223 - for the busybox installer and the adb help and android commands that make this work
@galaxyuser88 - for testing this and pointing out some flaws
@Hashcode - for inspiration
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
TY to @jmahaffey for testing and the following screenshots
{
"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"
}
This Method Completely replaces the Sprint files with AT&Ts. with exception to the kernel, recovery and the su binary. so everything once complete is now AT&T and not sprint with AT&T touchs thrown in to make it work.
as we don't have an unlocked bootloader, there is no twrp recovery. but flashfire takes it place. so any changes you want to make are basically done the same way as they would be for twrp except they are now flashed through flashfire.
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
reserved 2
and 1 more just in case
Nice job OvrDrive! Can't wait to get my replacement.
---------- Post added at 11:19 PM ---------- Previous post was at 11:11 PM ----------
So if you want to go back to stock rom all you have to do is flash the stock firmware again?
borijess said:
Nice job OvrDrive! Can't wait to get my replacement.
---------- Post added at 11:19 PM ---------- Previous post was at 11:11 PM ----------
So if you want to go back to stock rom all you have to do is flash the stock firmware again?
Click to expand...
Click to collapse
yup. this does not trip knox. just odin stock firmware and samsung pay and android pay will work again. yes they are broken by root, blame samsung. but stock firmware they work fine
enjoy all. i can go relax now that i got everyone taken care of.
@OvrDriVE
Finally we got att root method published too..... great job as always Bud[emoji106] hint @Venom0642 test your note 7 Bro before u return it.....haha
Sent from my SM-N920T using Tapatalk
Thank you for making this root method happen, can't wait for replacement note 7s to come out. Already got my case and other accessories coming soon in the mail next week.
I will definitly try this, as soon as I get home from work, before the new replacements come, just in case.
@OvrDriVE Thanks man and sorry I couldnt been much help.
Since I use Samsung pay most of the time, I think I will wait until my Gear S2 is able to use SSPay before I root.
But def cant wait to get my N7 rooted!
Thanks!
Awesome. I really wanted to be a tester, but it is impossible to get a replacement for now. Sorry.
Does all samsung stuff work
Does samsung health still work? I've read somewhere new version doesn't on rooted devices..
dvtmg704 said:
Does all samsung stuff work
Click to expand...
Click to collapse
[email protected] said:
Does samsung health still work? I've read somewhere new version doesn't on rooted devices..
Click to expand...
Click to collapse
This is a short thread as of right now. Please read it~
But short fed answers.
It was stated S Health works on the older version and to not update it.
OvrDrivE also stated that Samsung Pay and Android Pay will work.
Made it so it kinda sticks out like a sore thumb
sixk said:
This is a short thread as of right now. Please read it~
But short fed answers.
It was stated S Health works on the older version and to not update it.
OvrDrivE also stated that Samsung Pay and Android Pay will work."
Made it so it kinda sticks out like a sore thumb
Click to expand...
Click to collapse
I've cut and pasted overdrive's response about Samsung Pay and Android working from post #6. "yup. this does not trip knox. just odin stock firmware and samsung pay and android pay will work again. yes they are broken by root, blame samsung. but stock firmware they work fine."
So got my replacement n7 and have software ver 1APH1, is it rootable? I know this root process is based off of the PH1 but justed wanted to make sure.
Currently trying this on my replacement Note 7, which I just got from AT&T. However, when I try to odin the Sprint file from step 3 odin is giving me a " SHA256 is invalid" error.
The file is an md5 file rather than a tar file too; I don't know if it should be
rogerandgina said:
So got my replacement n7 and have software ver 1APH1, is it rootable? I know this root process is based off of the PH1 but justed wanted to make sure.
Click to expand...
Click to collapse
Yes, I wanted to make sure this worked before trading it in. It does work on this software version.
Could someone recommend a good app that will allow tether for us Unlimited users? Perhaps there's a way to unlock the provisioning?
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
Although root is working, I'm getting security warnings. "Threat Found" Unauthorized actions have been detected. Restart your device to undo any unauthorized change"
I realize I have to freeze the Security Log Agent with titanium backup.... but what exactly is the security problem and will I be at harms way by disabling the log agent?
What is it, and how to avoid?
JameyS said:
Although root is working, I'm getting security warnings. "Threat Found" Unauthorized actions have been detected. Restart your device to undo any unauthorized change"
What is it, and how to avoid?
Click to expand...
Click to collapse
From the second post:
OvrDriVE said:
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
Click to expand...
Click to collapse
Luigiman765 said:
From the second post:
Click to expand...
Click to collapse
Thanks... I was just wondering if it will cause other "Real" security issues in the future by not detecting a real problem once turned off?
Also, Wifi tether?
**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?