Related
This is a very simple device to root.
However if you root this device it will likely void your warranty.
There is no current method of obtaining S-OFF, so don't ask!
Requirements:
PC
Phone
USB Cable
External SDCARD (optional but highly recommended)
Internet Connection
HTC Drivers
Battery with a charge of over 50%
Ability to read
Ability to follow directions
Then you must view the following video!
If you meet these requirements then proceed to post #2.
Step #2 - Unlocking your bootloader
Copied from this thread by Revolution
Go to HTCDev.com
Make a account , here then go to this link and follow all instruction's , but make sure you go to this link , it don't show us as a supported device but this work's for all device's me & crackeyes have tried this .
Go to this link after that : here , follow all the step's , below will be my version .
1) Remove and reinsert the battery.
{
"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"
}
2) Press Volume Down and Power to start the device into Bootloader mode.
3) Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
4) Connect the device to the computer via a usb cable
5) Make a folder in c:\ called Android & then input the file's from your android SDK their , such as
adb.exe
AdbWinApi.dll
fastboot.exe
6) Open up command prompt. ( Start > Run > Type CMD,). The window that appears is called Command Prompt.
7) Navigate to where you unzipped the ZIP file and go to the folder you just created (For Example: If you created the folder in C:\Android, then you would type in Command Prompt: cd c:\Android).
8) Type in Command Prompt: fastboot oem get_identifier_token.
9) You will see a long block of text. Copy and paste this text into the the token field below (in the command prompt: Right Click > Mark > highlight the block of text > Right click to copy).
10) Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.
Example:
11) On the bottom of http://www.htcdev.com/bootloader/unlock-instructions/page-3 , please input your result's & if it say's failed keep on trying & it will go threw .
Straight from HTCDev.com , & NOTE : THIS WILL VOID YOUR WARRENTY
You are about to start the process of unlocking your device. Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty. HTC disclaims any and all liability for proper functioning of your device after the bootloader has been unlocked and for data lost in the unlocking process. To prevent unauthorized access to your data, unlocking the bootloader will delete all personal data from your device including applications, text messages and personalized settings.
Click to expand...
Click to collapse
Once you have unlocked your bootloader you can make changes to your /system partition.
The majority of you will probably never need to do this. This is because most developers use flashable zip files that will do everything for you. These files are flashed from Recovery Mode.
Let's move on to step #3
Step #3 - Installing Custom Recovery
Now that you have unlocked your bootloader you can now obtain root.
The easiest way to do this would be by installing a custom recovery.
I created a simple bat script that should update your recovery for you.
Boot up your phone and connect it to your computer by usb cable.
Go to Settings --> Applications --> Development.
Check USB debugging.
Unzip the attached file and run the Flash.bat file as Administrator.
Your phone should reboot and go to a white screen.
It should update the recovery for you automatically and reboot.
Now you should have yourself a custom recovery.
If by chance you decide that you would like to revert to the custom recovery then use the same technique with the STOCK_RECOVERY_FLASHER.zip file.
If a .bat script isn't your thing then try this thread: [TOOL] HTC Amaze 4G All-In-One Toolkit by Hasoon2000
Step #4 - ROOTING!
Now that you have your custom recovery installed it's time to flash root onto your phone.
Download a custom rom from the Development section or the HTC Amaze ROM Bible and store the zip onto your external sdcard.
If you do not want a custom rom but just want root simply download the attached Superuser-3.0.7-efghi-signed.zip file.
If you do not have an external sdcard then store it onto your internal sdcard.
The custom recovery from step #3 will default to an external sdcard if it's detected.
If the custom recovery from step #3 does not detect an external sdcard then it should default to your internal.
Now there are a couple different ways to reboot to recovery. The best way is to open the command prompt up and navigate to either directories from posts 1 or 2 that contains the adb.exe file.
For example this is from post #2.
If you stored it to your desktop directory then it would be something like:
C:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs
so you may have to enter:
cd Desktop\RecoveryInstallerForNoobs
Now enter "dir" into the command prompt and press Enter and you should see something like:
c:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs>dir
Volume in drive C has no label.
Volume Serial Number is 4850-996B
Directory of c:\Users\Binary100100\Desktop\RecoveryInstallerForNoobs
01/03/2012 05:04 PM <DIR> .
01/03/2012 05:04 PM <DIR> ..
11/08/2011 02:50 PM 366,661 adb
11/08/2011 02:50 PM 410,942 adb.exe
11/08/2011 02:50 PM 96,256 AdbWinApi.dll
11/08/2011 02:50 PM 60,928 AdbWinUsbApi.dll
11/08/2011 02:50 PM 127,435 fastboot
11/08/2011 02:50 PM 356,009 fastboot.exe
12/27/2011 12:37 AM 128 Flash.bat
12/27/2011 12:32 AM 5,187,584 recovery-cwm-ruby-5.0.2.7.img
8 File(s) 6,605,943 bytes
Click to expand...
Click to collapse
As long as you see adb, adb.exe, adbWinApi.dl and AdbWinUsbApi.dll you should be good to go.
Now without leaving the command prompt enter:
adb reboot recovery
Your phone should reboot and you should be looking at your recovery.
If for whatever reason you couldn't get access to recovery then go back to bootloader mode.
Remove the battery and put it back in. This is to make sure the device is completely powered off. Hold the Volume Down button while pressing power to get back to hboot mode. Just like step #1. Now if you don't see Recovery in the list then select BOOTLOADER. You should now see RECOVERY. Select that and your phone should reboot to recovery from there. Now that I know you're in recovery... let's move on.
From here you can flash your custom rom or root files.
Use the volume rocker buttons to move the highlight up and down the menu and highlight "Install zip from sdcard" then press the power button to select.
Now "choose zip from sdcard" then press power button again.
Highlight the downloaded custom rom or the Superuser-3.0.7-efghi-signed.zipfile and press power again. From here I think you have the idea.
Select the appropriate zip file and press the power button to install.
Now you can go back and then select "reboot system now" and let your device boot up.
Check the app drawer and make sure you have an app called SuperUser. If you have this app then you now have root.
If you followed the instructions like you were supposed to you should be fully rooted and unlocked the full potential of your HTC Amaze 4G phone.
Feel free to post your questions and comments here in this thread.
PLEASE! don't send me private messages asking for help. I just spent two hours making this as simple as I could to save me from all of the help requests. If you have problems then post in this thread and make sure to reference the step that you're having issues with.
Example:
Problem with Step #1 I can't follow directions. Someone do it for me. I'll be willing to pay $10,000,000 to have root.
Click to expand...
Click to collapse
Then I'm sure you will get plenty of help.
Remember to hit the thanks button to show your appreciation.
Thanks was wondering where the old sticky thread went!!! hopefully less questions with this one...It's much more clear.
seansk said:
Thanks was wondering where the old sticky thread went!!! hopefully less questions with this one...It's much more clear.
Click to expand...
Click to collapse
Which is exactly why I made it. Unfortunately the members that just got the device couldn't use the old PH85IMG.zip method because of the Main Version Older error and they couldn't use the tool that xboarder56 made because I had to remove it per request. I didn't want to make a tool that would do everything because then they would never learn for themselves. So I feel that this is a healthy balance.
Binary100100 said:
Which is exactly why I made it. Unfortunately the members that just got the device couldn't use the old PH85IMG.zip method because of the Main Version Older error and they couldn't use the tool that xboarder56 made because I had to remove it per request. I didn't want to make a tool that would do everything because then they would never learn for themselves. So I feel that this is a healthy balance.
Click to expand...
Click to collapse
good Idea I am having lots of flashing problems since 1.3 too, I didn't want to unlock it and I OTA'd...but then couldn't stand the bloatware and wanted more...now I'm having all kinds of problems, including kernel. so now If you could help me with the kernel, I posted question in general section, I'm kind of a semi-noob with kernels!!!!! lol
seansk said:
good Idea I am having lots of flashing problems since 1.3 too, I didn't want to unlock it and I OTA'd...but then couldn't stand the bloatware and wanted more...now I'm having all kinds of problems, including kernel. so now If you could help me with the kernel, I posted question in general section, I'm kind of a semi-noob with kernels!!!!! lol
Click to expand...
Click to collapse
Give me the link to your question and I'll do what I can to help.
Do you have access to fastboot and an unlocked bootloader?
Binary100100 said:
Give me the link to your question and I'll do what I can to help.
Do you have access to fastboot and an unlocked bootloader?
Click to expand...
Click to collapse
Yes, I'm familiar with all that stuff..unlocked and can get into fastboot. custom recovery is intact as well. here's the link: http://forum.xda-developers.com/showthread.php?t=1424757 post 8 and this almost the same http://forum.xda-developers.com/showthread.php?t=1328141&page=10 post 92....thanks you much in advance
Great job on this Binary!
IF PEOPLE HAVE PROBLEMS...you can always message me as well. BUT MAKE SURE TO READ AND FOLLOW DIRECTIONS FIRST...I'm am very familiar with all these procedures as well, just to take a load of binary and xboarder's backs...
seansk said:
IF PEOPLE HAVE PROBLEMS...you can always message me as well. BUT MAKE SURE TO READ AND FOLLOW DIRECTIONS FIRST...I'm am very familiar with all these procedures as well, just to take a load of binary and xboarder's backs...
Click to expand...
Click to collapse
Thank you very much! I don't have time to be 24/7 tech support.
jimczyz said:
Great job on this Binary!
Click to expand...
Click to collapse
Agreed. I wish this thread had been here when I rooted. It would have saved my hunting through 3 or 4 threads and trying to piece things together myself. Of course, I probably learned more that way.
marleyfan61 said:
Agreed. I wish this thread had been here when I rooted. It would have saved my hunting through 3 or 4 threads and trying to piece things together myself. Of course, I probably learned more that way.
Click to expand...
Click to collapse
I always encourage people to never stop learning.
When I see a script I like to open it up and see what's inside.
Knowing how things work is a great way to learn for yourself.
Before you know it, you'll be making guides like this! At the very least you'll be the A instead of the Q if you know what I mean.
Binary100100 said:
I always encourage people to never stop learning.
When I see a script I like to open it up and see what's inside.
Knowing how things work is a great way to learn for yourself.
Before you know it, you'll be making guides like this! At the very least you'll be the A instead of the Q if you know what I mean.
Click to expand...
Click to collapse
We both have the same curiosoty Binary...I alway open random files and probably break things before I fix them lol...my first computer was a packard bell 486 dx2 66 in 1993 I think. I learned everything I know by myself...including a lot of dos which we still use today for android . good old windows 3.1
Thanks a million!
I had lost my root to the most recent OTA update from t-mo, obviously I'm a noob when it comes to root only, everything else electronic wise I got the hang of. I'm not the type of person that likes things handed to me I prefer given the basic and expanding my knowledge from there, knowledge is a beautiful thing! I'm back rooted and again thanks for this post!
andyb0308 said:
I had lost my root to the most recent OTA update from t-mo, obviously I'm a noob when it comes to root only, everything else electronic wise I got the hang of. I'm not the type of person that likes things handed to me I prefer given the basic and expanding my knowledge from there, knowledge is a beautiful thing! I'm back rooted and again thanks for this post!
Click to expand...
Click to collapse
I'm glad that you found it helpful.
May be a Noob ? but I'm wondering since I use my phones hotspot to get internet on my laptop, if I can do this without the sim card in the Amaze, while using my other phones hotspot? I've searched and found no mention of this, thanks for the great guide.
Marquis63 said:
May be a Noob ? but I'm wondering since I use my phones hotspot to get internet on my laptop, if I can do this without the sim card in the Amaze, while using my other phones hotspot? I've searched and found no mention of this, thanks for the great guide.
Click to expand...
Click to collapse
As long as you have a PC connected to download the required files.
Sent from my HTC Amaze 4G using xda premium
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).
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
Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
1) Download KingRoot APK from here (the first one with the image of the phone if you are on the desktop site).
2) Install KingRoot and run it. It will restart the phone, and it will fail (or, if you have some Android God luck, it may succeed), this is supposed to happen.
3) Clear KingRoots cache and data (in that order) and power off the phone (not reboot). Then, power it back on again.
4) Now this is where things get... well complicated for this part. You are going to need to load your RAM with a bunch of processor heavy stuff. The person that made this method used CounterSpy and Final Fantasy Type-0 in the PPSSPP v1.0.1-411 emulator, but for those of you that don't have access to that, get creative and load up. Here is what I had running (all at the same time, mind you).
Note: Force Stop Task Manager in the app settings first or it will purge to free memory automatically and this won't work.
1. Next Launcher Lite
2. Apex Launcher
3. Nova Launcher
4. Cheetah Launcher
5. CM Launcher
6. Mi Launcher
7. 25 tabs on Google Chrome (No joke)
8. Both Temple Runs
9. Fruit Ninja
10. Google Play Store
11. Google Now
12. Google Play
13. Amazon
14. Google Play Music
Mine was definitely a bit extreme but I knew all of this stuff would guarantee a good memory hogging.
5) Run all of your apps at the same time. The TL;DR for this is that apparently it's some exploit that the app uses as a buffer overflow. Now, go to settings and Force Stop KingRoot. Then Run it again. If it works, you should go from 0 to 100 real quick (no pun intended). It shouldn't progess slowly or reboot the phone to do this, but your journey does not stop here.
Click to expand...
Click to collapse
If you did it correctly, the screen from a successful root will have a green checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
1) Plug phone into computer...
2) Open cmd type "adb shell" (without quotes, moving forward, type all commands without quotes). This will open a terminal for the phone.
3) While in ADB Shell, type "su" to gain root shell privileges
4) Type "getprop ro.build.fingerprint"
Output for that command should be...
zte/P892T57/draconis:4.4.2/KVT49L/20140804.141306.18686:user/release-keys (the part with P892T57 may be different depending on what model ZMAX You have). If you haven't updated that number will be different, this ok, just replace the number in the next command with whatever your output is.
5) type "setprop persist.sys.k P892T57"
6) type "getprop persist.sys.k" and your output should be your build number
7) type "cd /dev/block/platform/msm_sdcc.1/by-name/" to change directories so that we can back up your recovery image (remember I said something about that?) and set the boot to our recovery partition.
8) type "dd if=recovery of=/sdcard/recovery.img" to backup the recovery image.
9) type "dd if=boot of=recovery" to set recovery as boot. Another TL;DR is that this disables the write protection set by the stock recovery, allowing you to write to the system. It will mount the /system partition upon boot.
DELETE KINGUSER NOW
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
11) Reopene the adb shell (using "adb shell") in your command prompt or terminal (for OSX and Linux) and type "Id". If your output is "uid=0(root) gid=0(root) context=u:r:shell:s0" then It worked...
12) Remount system as writable "mount -o rw,remount /system"
13) Manual install for supersu you can get that here: http://download.chainfire.eu/supersu
14) Type "exit" into the terminal/command and it should drop you back to your normal cmd...unzip the su zip anywhere you want in your cmd switch to that directory...
14B) I advise taking the "su" binary and "install-recovery.sh" file from the superSU folder you downloaded and putting them in the same place (on the desktop or wherever your adb.exe is if you didn't set $PATH on your computer). su can be found in the "arm" folder and install-recovery.sh can be found in the "common" folder. It is important to note that where ever your files are, you will have to type that path (if it isn't in the same directory as your adb). So, as an example, I put mine on the desktop, so I have to type "adb push ~/Desktop/su /data/local/tmp/su". If you do not know how to do that, then stop what you are doing and research it, as that's just too much to explain.
15) "adb push su /data/local/tmp/su"
16) "adb push install-recovery.sh /data/local/tmp"
17) Reenter adb shell with "adb shell"
18) Make sure system is mounted writable with "mount -o remount,rw /system"
19) Move the so files into place with these commands
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/su > /system/xbin/daemonsu"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
20) Give them all permissions
"chmod 755 /system/xbin/su"
"chmod 755 /system/xbin/daemonsu"
"chmod 755 /system/etc/install-recovery.sh"
21) Reboot your phone to complete install with "reboot"
22) After rebooting go into the play store and install the supersu app. It's going to tell you the su binary is out of date to fix that we need to open the adb shell on our pc again with "adb shell"
23) Reboot into recovery (you're really rebooting the system with r/w privileges) using "reboot recovery"
24) Once rebooted open the app and update your binaries one finished reboot add your done 100% perm rooted
Click to expand...
Click to collapse
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
ADDITIONAL INFORMATION
If you by some chance flash the TWRP Recovery Image (found in post 2), and would like to revert back to root ability (being able to write to system). Please follow the steps below:
1. cd /dev/block/platform/msm_sdcc.1/by-name
2. su
3. dd if=/sdcard/recovery.img of=recovery
4. reboot recovery
Please make sure you have the recovery in your sdcard root folder.
Alternate Root Methods and ZTE Custom ROMs/Kernels/etc
If the above first part doesn't work for you, you can find alternative root methods
Alternate Method 1 HERE
Alternate Method 2 HERE
As I see more added, I'll add them here.
CUSTOM STUFF
TWRP Image for ZTE ZMAX
Q&A/Other [UDPATED MAY 13, 2015 @ 5:45PM]
If A question is asked and you feel like it needs to be here, please tag or DM me with the Q AND THE A so that I can do so.
OTHER:
Original Discussion Thread for the ZTE ZMAX
Please see fire3element's post on what each screen in the KingRoot app means
WHAT THE SCREENS MEAN IN THE APP
That's a whole lot to swallow but I'm glad to see y'all can finally get rooted. Definitely not a method for noobs or the faint of heart but its a HUUUGE step in the right direction. Thanks to everyone responsible for this.
Hroark13 has TWRP - http://androidforums.com/threads/zte-zmax-twrp.918537/
mingolianbeef said:
Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
If you did it correctly, the screen from a successful root will have a blue envelope with a checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
Click to expand...
Click to collapse
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Here is some more info for those of you wondering what the KingRoot app is doing.
Screenshots will follow.
Text ABOVE the screenshot is for the image directly under it.
Let's begin -------------->
FIRST SCREEN WHEN YOU OPEN KINGROOT
{
"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"
}
SECOND SCREEN
- CLICK BUTTON TO BEGIN ROOT -
ROOTING IN PROGRESS...
ROOT FAILURE
[Blue Button]: SUBMIT (submits the error report to KingRoot devs)
ROOT FAILURE
ROOT FAILURE
NO DATA CONNECTION (WiFi or cellular singnal required)
[Blue Button]: ANDROID SETTINGS MENU
SUCCESSFUL ROOT
IF YOU SEE THIS MESSAGE POP UP DURING ROOTING, JUST LEAVE IT ALONE. LET THE ROOT FINISH
SUCCESSFUL ROOT
[trash can]: [...]: [...]:
SUCCESSFUL ROOT
[Blue Button]: PURIFICATION (I believe this is similar to fixing permissions)
- CLICK IT AND LET IT RUN -
^ from clicking blue button above ^
PURIFICATION PROCESS
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=/sdcard/recovery.img of=recovery
reboot recovery
*edited to remove a potentially harmful commands per jcase's advice*
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=boot of=boot
dd if=/sdcard/recovery.img of=recovery
reboot recovery
Sent from my Z970 using XDA Free mobile app
Click to expand...
Click to collapse
even with just one slash I still have a problem
Sent from my Z970 using XDA Free mobile app
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Click to expand...
Click to collapse
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
fire3element said:
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
Click to expand...
Click to collapse
I would do a full root uninstall....
The backdoor keeps root for adb so installing the new su shouldn't be an issue
Sent from my Z970 using XDA Free mobile app
Got it. Will report back after this headache is done. *slams head on desk*
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Is there anyway to do it without a factory reset? Could I just remove kinguser? or it must be factory reset? and will I have to reroot with factory reset?
Sent from my Z970 using XDA Free mobile app
Sorry guys, kinda been running around all day, have a lot of catching up to do I see. I'll fix the thread with updated information that people have so generously contributed!
DroidisLINUX said:
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Click to expand...
Click to collapse
I know right!!! First hurdle... done... second hurdle, bootloader with no fastboot lmao...
a bit unclear on this
are we actually rebooting into recovery or its supposed to go straight back into the phone
i was never able to get into recovery
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
getting permission denied when running this.
"chmod 755 /system/xbin/su"
"chmod 755 /system/etc/install-recovery.sh"
as well as operation denied or something along those lines. any help would be nice. also and running id on adb. its showing.
uid=0(root) gid=0(root) context=u:r:init:s0
rather than
uid=0(root) gid=0(root) context=u:r:shell:s0
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
You have to exit adb shell to push files to /data/local/tmp, which does not require root. That was a major exploit in earlier android versions, as people would push scripts to /data/local/tmp without root, run the exploit in the directory, and it would root. That was patched of course, but that directory can be accessed without root. Once you use "reboot recovery" to reboot, then just plug your phone back up and type "adb shell" to which the phone should respond with a "#" instead of a "$". If you have the $, you are not root and need to go back. If you do, just be patient with it and make sure you are not just copying and pasting (I know this can be the root of the issue at times with command, just type it out). It should work, the second half is the easy part lol.
Q&A for [RECOVERY][ariel] TWRP 2.8.6.0 touch recovery [2015-06-07]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][ariel] TWRP 2.8.6.0 touch recovery [2015-06-07]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Edit: Well NM. I've gotten back into the bootloader. Just have to figure out how to get a working restore going. Is it possible to do one from the update-kindle-20.4.5.3_user_453011120.bin file from Amazon direct and just completely start over?
*************
I got TWRP Installed. and then after trying to clear some things I ended up where my device stays at the Amazon logo at startup.
Am I bricked? Or is there any way to force the thing to boot back into TWRP instead of loading the main OS?
Any chance of the recovery being added back to the app. When I try to get it from the app it says it's downloading, then goes to a cloudflare page that says "The page you are looking for cannot be found".
Fire HD 7 (ARIEL)
I was wondering is there any way to boot customs ROMS now with TWRP and unlocked bootloader because when attempting to flash CM12 with TWRP it fails... Plus, I heard about have a "second bootloader" but thats only for the second generation fire-hd tablets...
I'm having an issue restoring backups. The /system directory is failing to restore with the error "extractTarFork() process ended with ERROR=255" I checked the mounts before starting the restore, and /system is mounted rw. If I check the mounts after the error, /system is ro. I also made sure that I didn't have the "mount /system read-only" checkbox clicked under mounts on twrp.
If I save off the system log, I see entries like:
I:Unable to unlink '/system/app/Bluetooth.odex: Read-only file system'
and
lchown("/system//app/", 0, 0): Read-only file system
FAILED SETTING PERMS: -1
I'm on firmware version 4.5.4 on a Fire HD 7. I followed DoLooper's directions (http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10) to get there. Not exactly sure what could be going wrong.
So, I solved my issue. DoLooper updated the 4.5.4 update zipfile in his post on 7/20. I installed that update and suddenly everything started working right again. Not sure what was wrong with the original....
Fire HD 6 & TWRP (ariel)
Where can I download TWRP for a Fire HD 6? When I use the TWRP Manager and select the "Recovery Version to Install" option, the app just closes itself. There is a download link provided by jmz but I get this message when I try to download it:
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
Click to expand...
Click to collapse
It is also not listed on TWRP's website. My fire was downgraded using the 5.0 dev preview to 4.5.3 and rooted using KingRoot.
Where to get the newest TWRP manager
I don't have access to google play yet. I tried the older version of manager, it crashed when attempting to install TWRP. Hoping the new version will work so I can proceed to step #4 according to this thread:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
Thanks,
Em.
Emerald9 said:
I don't have access to google play yet. I tried the older version of manager, it crashed when attempting to install TWRP. Hoping the new version will work so I can proceed to step #4 according to this thread:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613.
Click to expand...
Click to collapse
You can try here: http://www.apkmirror.com/?s=twrp+manager&post_type=apps_post. Or use Flashify. (Can find apk at apkmirror.) Here's install info if you need it: http://forum.xda-developers.com/showpost.php?p=61769246&postcount=7
DoLooper said:
You can try here: http://www.apkmirror.com/?s=twrp+manager&post_type=apps_post. Or use Flashify. (Can find apk at apkmirror.) Here's install info if you need it: http://forum.xda-developers.com/showpost.php?p=61769246&postcount=7
Click to expand...
Click to collapse
Thank you for your quick reply. The managers there are all older than the one I tried earlier, so I'm going to try Flashify instead. I'll report back.
---------- Post added at 08:40 PM ---------- Previous post was at 08:36 PM ----------
Emerald9 said:
Thank you for your quick reply. The managers there are all older than the one I tried earlier, so I'm going to try Flashify instead. I'll report back.
Click to expand...
Click to collapse
Sorry, such a hurry to try that I don't even know how to sideload. So from the computer, the command is:
adb sideload flashifyfilename.apk
Emerald9 said:
Sorry, such a hurry to try that I don't even know how to sideload. So from the computer, the command is:
adb sideload flashifyfilename.apk
Click to expand...
Click to collapse
adb install flashifyfilename.apk. Open terminal/CMD window from the folder where the apk is. Don't hurry. Follow steps I linked before.
EDIT: @Emerald9 - That step 1 was for guy I wrote it for. By sideload there I meant copy from computer to device (and install with a file explorer). You need to adb install.
DoLooper said:
adb install flashifyfilename.apk. Open terminal/CMD window from the folder where the apk is. Don't hurry. Follow steps I linked before.
Click to expand...
Click to collapse
SUCCESS! A huge thank you for all of you that have worked on this.
When I tried the sideload command, it gave an error, so install did it. I do not know what I am doing, but I can follow step-by-step instructions .
So before upgrading to 4.5.4 and gapps, I should back up, correct? And Are the default backup options sufficient?
Emerald9 said:
SUCCESS! A huge thank you for all of you that have worked on this.
When I tried the sideload command, it gave an error, so install did it. I do not know what I am doing, but I can follow step-by-step instructions .
So before upgrading to 4.5.4 and gapps, I should back up, correct? And Are the default backup options sufficient?
Click to expand...
Click to collapse
There's not really anything to back up; /data is pretty clean. If you want step-by-step, try this: http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
EDIT: @Emerald9 Again steps were for someone who had file explorer. You'll need to adb install JMZ fire tool. At step 6, look at top of TWRP screen and be sure you're installing to system, not recovery.
DoLooper said:
There's not really anything to back up; /data is pretty clean. If you want step-by-step, try this: http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
EDIT: @Emerald9 Again steps were for someone who had file explorer. You'll need to adb install JMZ fire tool. At step 6, look at top of TWRP screen and be sure you're installing to system, not recovery.
Click to expand...
Click to collapse
DoLooper,
Thank you for your patience with me. I am at step #6, and I don't see the option to install to system/recovery? The file that I should select is the 454_update.zip, right?
{
"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"
}
[/URL][/IMG]
Yes. Wasn't sure if there were 2 options, so just install it.
Thank you so much for your clear instructions, DoLooper. My mom's Fire is rooted with working Google Play. I went through this whole journey just because she wanted a bible app that was not available in Amazone store. I notice Silk browser is not working...but will do some search here.
Have a great day,
Em.
Emerald9 said:
I notice Silk browser is not working...but will do some search here.
Have a great day,
Em.
Click to expand...
Click to collapse
This happened to someone else and they had to do a reinstall and had problems. I suggest you install a different browser app. (I use Dophin, but others like Firefox. Chrome will also work, but may be big.) After installing new browser, block Silk (named "cloud9"), which should make the icon disappear (I hope). Handy tool to easily block/unblock anything is gatesjunior Debloater. Alternatively, run following command from terminal/CMD window:
adb shell pm block com.amazon.cloud9
Please tell me where you got the 4.5.4 update file you used. I need link to the post that you downloaded it from. Thanks.
DoLooper said:
This happened to someone else and they had to do a reinstall and had problems. I suggest you install a different browser app. (I use Dophin, but others like Firefox. Chrome will also work, but may be big.) After installing new browser, block Silk (named "cloud9"), which should make the icon disappear (I hope). Handy tool to easily block/unblock anything is gatesjunior Debloater. Alternatively, run following command from terminal/CMD window:
adb shell pm block com.amazon.cloud9
Please tell me where you got the 4.5.4 update file you used. I need link to the post that you downloaded it from. Thanks.
Click to expand...
Click to collapse
The 4.5.4 file was from your link that you included in your step by step instructions.
I already installed Chrome, but per your advice, will replace with Dolphin. Is it possible to have 100% amazon experience with GooglePlay? Mom is used to Amazon Fire as she's been using it for awhile.
Emerald9 said:
The 4.5.4 file was from your link that you included in your step by step instructions.
I already installed Chrome, but per your advice, will replace with Dolphin. Is it possible to have 100% amazon experience with GooglePlay? Mom is used to Amazon Fire as she's been using it for awhile.
Click to expand...
Click to collapse
If Chrome fit in /system and works, keep it. Let me think about 100% Amazon experience. Will edit this shortly.
@Emerald9: I think using the stock launcher (carousel) should be fine, but can't say for sure because most folks want/use a custom launcher. If something doesn't work or crashes, post in Q&A explaining that she's running from Amazon launcher.
I need help
Is this compatible with fire os 5.3.3.0