Develop Bugs

[Q] Need Help changing to official version, totally new to this

Hi everyone, I just got my HTC One X today and I'm loving it, but since I got it here in New Zealand and the phone was on the Telecom network, it has all these preinstalled things inside, plus the logos on start up etc.
So I'm thinking of changing it to the official Taiwanese version? (is it called rom or something?)
I'm totally new to this, so is there anyone that can help me with it? like if possible provide me step by step instructions? or at least tell me where/which is the official rom i should download? I'm getting really confused by all the RUU's and OTA's out there, not sure what I should be getting.
Thanks a lot! Hope someone can help me

1) Head over here: http://onexroot.com/one-x-root/how-to-root-one-x/ to root your phone/unlock your bootloader. You'll wanna make sure you follow carefully and thoroughly. This will allow you to install custom ROMs ('versions' of the operating system I guess?)
2) Head over here and find a ROM that suits you: http://forum.xda-developers.com/forumdisplay.php?f=1536
If you want something feature rich, bloat free, and Sense-based you can't go wrong with Leedroid.
Go here http://forum.xda-developers.com/showthread.php?t=1587888 and download the zip linked in the first post.
3) Place the zip somewhere on your phone using your computer. You might want to create a new folder called "ROMs" or something to place it in.
4) Hold the power and volume down buttons on your phone till it boots into recovery mode, then select Recovery on the menu.
5) Go to backup/restore and select create backup. This will create a backup of the current state of your phone, which you can go back to in case anything goes wrong.
6) Select install zip from sdcard, then select the zip file you downloaded previously. It'll take you through a brief installer, then reboot your phone. You probably will want to select full wipe when given the option. This will erase all your contacts, settings etc.
Do all that and you should be good to go.

[Root] [CWM] Samsung Galaxy Discover (SGH-730G) Tracfone Variant ONLY

THIS THREAD IS ONLY FOR THE SGH-730G VARIANT OF THE SAMSUNG DISCOVER. USE OF ANY OF THESE GUIDES AND METHODS FOR ANY OTHER VARIANT OF THE PHONE IS AT THE RISK OF THE USER
This thread is a guide on how to root and install CWM recovery on the Samsung Galaxy Discover (SGH-730G) which is the Tracfone (Net10, Straight Talk) variant of the device. These instructions are for Windows users only. If someone knows how to do it through Linux distro or Mac, please let me know and we will add those instructions to this post.
IMPORTANT: THIS GUIDE ASSUMES THAT YOU HAVE A PRIOR KNOWLEDGE OF THE TOOLS AND TERMS USED. ROOTING YOUR DEVICE WILL VOID YOUR WARRANTY! STOP NOW IF THIS IS SOMETHING YOU ARE CONCERNED ABOUT! IF YOU PROCEED, FOLLOW ALL THE DIRECTIONS CAREFULLY. USE OF THIS GUIDE AND THESE TOOLS IS AT THE RISK OF THE USER! I AM NOT RESPONSIBLE FOR ANY DAMAGE OR NEGATIVE OUTCOMES INCLUDING BUT NOT LIMITED TO SOFT BRICK, HARD BRICK, EXPLODING BATTERIES, NUCLEAR WAR, GIANT SQUID PEOPLE, OR SPONTANEOUS JUSTIN BIEBER CONCERTS IN YOUR LIVING ROOM
***First let's get all the tools and files you will need to complete this process***
Samsung USB Drivers: Click HERE to download the USB drivers for the SGH-730G.
UnlockRoot Pro (Free Download) - Click HERE and scroll down to "UnlockRoot Pro" and click the "Free Download" button. *Note*: Your computer may tell you that this program is malicious. You may have to disable antivirus in order to download.
Odin3 v3.07 - Click HERE to download Odin. This program will be used to flash CWM recovery to your phone.
CWM Recovery (thanks to JohnnyGalto) - Click HERE to download CWM recovery for your phone.
***Now that you have all the tools downloaded let's get them installed and ready for use.***
1) Install the USB drivers (should be self-explanatory).
2) Click on UnlockRoot_downloader_by_UnlockRoot.exe to start the installation. You may have to grant it administrator privileges. I DO NOT RECOMMEND INSTALLING ANY OF THE SPECIAL OFFERS THAT FIRST COME UP WHEN YOU OPEN THE FILE. CLICK SKIP until the automatic download begins. This is the download for the program itself. Once that is finished, follow the instructions to install the program on your computer.
3) Extract Odin Files: I recommend creating a folder on the desktop named "Odin" simply for easy access. However, feel free to choose whatever directory you want. Simply extract all the files to a designated folder.
4) CWM Revovery Tar: Move this file into the same folder where you extracted Odin. This will make it easier to access in a little while.
***If you have followed all the instructions correctly, you are now ready to install CWM recovery and root your device! You will periodically see a yellow triangle on the Samsung boot logo screen throughout this process. But have no fear, we will take care of this later on.***
1) Put your phone into download mode by holding VOLUME DOWN + POWER. A warning screen about custom OS will appear. Press VOLUME UP to confirm this is what you want to do. You should then be showing a screen with the Android logo and the "Downloading... Do not turn off target!!" text.
2) Now connect your phone to the computer using the USB cable, and open Odin from the folder you extracted it to. If your phone is connected properly you should see something similar to "0:[COM10]" in the box under ID:COM in the upper left of the window.
**VERY IMPORTANT** MAKE SURE THE ONLY TWO BOXES CHECKED UNDER "OPTIONS" ARE AUTO REBOOT AND F. RESET TIME!! NO OTHER BOXES SHOULD BE CHECKED
3) Under "Files [Download]" click the PDA button. Navigate to where you placed the CWM tar file and click okay.It is important that you ONLY click "PDA" for this. If you have followed the directions carefully, Odin should check the MD5 sum of the file to verify validity. If the file comes back invalid or you get any errors, STOP, and report them in the thread.
4) Click "Start". DO NOT TURN OFF OR DISCONNECT YOUR PHONE DURING THIS PROCESS. If everything goes well, your phone will reboot automatically after install. To check if your install worked properly, follow the next instructions to boot into recovery and make a stock backup.
OPTIONAL BUT RECOMMENDED SAFETY STEP BEFORE PROCEEDING WITH ROOT (REQUIRES AN EXTERNAL MICRO SD CARD) - CWM recovery works without root permission. It is HIGHLY recommended that you make a complete backup of your stock image before proceeding. This will make it easier to recover from a soft brick, or to return your phone to stock in the future should you choose to do so. A)Power off your phone. To boot into recovery, hold VOLUME UP+POWER until the Samsung logo is displayed. After the logo displays, release the POWER button. Keep holding the VOLUME UP button until your phone boots into the CWM recovery screen. B) Using the volume keys to navigate the menu, scroll down to "backup and restore". Use the power button to select. C) Select backup using the power button. D) After your backup is complete, go back to the main menu and select "reboot system now".
5) Before using UnlockRoot Pro, go to your Settings menu and scroll down to "Developer Options". Be sure to select "USB debugging", "Allow mock locations", and just to avoid potential disaster, choose "Stay awake". After this is all done, you can go back and unselect these.
6) With USB debugging enabled on your phone, launch UnlockRoot (not the UnlockRoot PRO shortcut the program installs on the desktop). Click the big green "Root" button. **NOTE** During the process it will ask you if you want to install other apps. DO NOT INSTALL THEM. Once the program is finished, if all went well, you now have a rooted SGH-730G!
7) There are a number of apps available in the Play Store that check to see if you are rooted. Alternatively, this is how I check my devices. A) Download and install "Terminal Emulator" from the Play Store. This app is like using ADB on your phone. B) Once it is installed, open the app. Type in the command "su" (without the quotes) and hit enter. If rooting was successful, your phone should show a pop-up message asking you to grant it root privileges. Go ahead and say yes and rejoice in the fact you were successful. If you receive the error "permission denied", then the root was unsuccessful.
**Dealing with the pesky yellow triangle on the Samsung boot screen**
The yellow triangle on the Samsung boot screen is a visual warning that you are running custom software. To get rid of it, click the following thread link. "Triangle Away" is a paid app in the Play Store, but the awesome Chainfire has made it available in the forums. Read the thread carefully and follow all the instructions for using the app. Neither I, nor him, nor your pet are responsible for the misuse of the app. - http://forum.xda-developers.com/member.php?u=631273
THAT'S IT!!! If you followed all the directions carefully, you now have a rooted SGH-730G and the sky is the limit now. Currently there is no known custom roms for this device. However I am working on building a Stock+Root Deodexed version of the factory firmware, and will upload it when I can verify it is stable to be released. Following that, I will be developing a custom rom based on the stock firmware. But of course, if you have the experience and know-how, feel free to start developing your own roms for this phone. The more the merrier.
And as always, if you were successful using this guide, or it helped you in any way, please inflate my ego by clicking that thanks button.
I will try to answer as many questions as possible if you run into problems during the process, or if you have other questions about what you can do with this device now that it is rooted.
I CURRENTLY DO NOT KNOW OF A WAY TO MANUALLY UNLOCK THE PHONE. IT'S A LITTLE BIT BEYOND MY SKILLS. I HAVE HOWEVER SEEN PEOPLE IN OTHER FORUMS GETTING PEOPLE TO DO IT USING REMOTE ACCESS TO THEIR COMPUTERS WITH THE PHONE PLUGGED IN TO IT. I DON'T KNOW ALL THE DETAILS ABOUT HOW IT WORKS, BUT COMMON SENSE TELLS ME THIS ISN'T A VERY TRUSTWORTHY THING TO BE DOING. IT'S TOTALLY UP TO YOU IF YOU REALLY TRUST A COMPLETE STRANGER TO HAVE VIRTUAL ACCESS TO YOUR COMPUTER AND YOUR PHONE. BE I'D BE WEARY.
:good: Thanks (in no particular order) to andronald for the original thread about the 730M variant of this device, Without that thread, this thread would not be possible. FitAmp for his contributions to the project over there, JohnnyGalto for the CWM recovery image, cshmitt for his help in getting me started working on a custom rom for this device. :good:

Soft Brick Recovery
SOFT BRICK RECOVERY FOR SGH-730G
Right now, I am working on a tar Odin flashable system image to make it easier to recover from a soft brick of the device. Once it is completed and tested, I will update this post to include a download of it.
***This post will help you recover from a soft brick or bootloop error on your SGH-730G after rooting. This quick guide assumes that you still have access to CWM recovery and/or are able to boot into download mode. (See OP for instructions on how to boot into recovery and download mode.)***
If you followed the instructions and recommendations in the previous post, then you should have made a backup of the stock image using CWM recovery. This is what you will use to help recover your phone so you can start the process again, or not, depending on how gutsy you feel.
IF YOU ARE STILL ABLE TO BOOT INTO CWM RECOVERY
1) Power off your device. You may have to pull the battery to do this if you are stuck with a bootloop or other booting issues.
2) Boot into CWM recovery (see OP for instructions)
3) Scroll down to "backup and restore"
4) Select restore
5) You should then see a restore point to select. The format is usually "YYYY-MM-DD.HOUR". The hour is usually in 24h format.
6) Select the file then select "Yes".
7) If everything works correctly, your stock backup should be restored and you should be able to boot your phone again.
**Note** If you lose root while restoring your stock backup, just use the guide in the OP to try again.
**If you cannot boot into CWM recovery after installation and making a backup.**
Try to reinstall the CWM recovery image using the instructions in the OP.
Again, as soon as it is ready, I will upload a tar that can be flashed through Odin to restore the factory image to your phone, and instructions on recovering and returning to stock will be posted here.
As always, if this helps you in any way, inflate my ego by clicking that thanks button.

Fun with the SGH-730G
So far there are a few fun things I have found work for this phone so far.
For those who may want overclock features, check out this thread. The reason I didn't include it in the OP is because I didn't have success in changing the max value for CPU speed. It stayed constant at 1000 and produced a little too much battery drain for my taste.
SetCPU - This app only works to change the minimum allowed CPU speed of the stock kernel. I run the "ondemand" settings with a minimum of 600MHz and max of 800Mhz. This has helped to reduce some lag from the stock speeds the kernel likes to run and doesn't produce a noticeable battery drain.
Seeder - The seeder lag reduction app makes a huge difference in smoothness of the device.
Xposed Framework: If you don't know what this is, search the XDA forums and you will be able to learn just about everything you want about it. So far I have tested features of the XBlast module and Xposed Additions. Center clock and clock color change, 4-way reboot menu with screenshot, Volume button tweaks, all from Xblast. Xposed Additions can be used to remap the buttons for different functions. I was able to remap the back key to kill the foreground app on long-press. Very useful to limit the amount of running apps in the background.
Notification Toggle - This nifty little app allows you to place toggles for wifi, mobile data, brightness, etc, in the notification dropdown screen. Saves a little time from having to navigate through the settings on the phone, and saves home screen space by not having to use the power widget.
Rom Toolbox - Some features may work, but it is better to have the rom deodexed to take full advantage. (A deodexed version of the stock rom will be available soon).
Auto Killer Memory Optimizer: This is a personal favorite of mine. I own the pro version which is well worth the money. It allows custom settings to optimize RAM usage and free up memory. Makes the phone so much smoother.
If you find any other fun mods that work with this phone, pleas share!

Thank you very much. Been waiting for this for a while. Again thanks.

Nomad692000 said:
Thank you very much. Been waiting for this for a while. Again thanks.
Click to expand...
Click to collapse
My pleasure. I felt it was necessary to separate this phone version from the other versions to avoid confusion. I'll be (hopefully) updating the soft brick recovery in just a moment. Currently testing a new method. Glad you liked the thread. Stick around, things may start to get interesting soon

So far I haven't had any luck creating an Odin package of the factory system image. I have written to Tracfone to see if they could provide me with the factory image but I'm not going to have high hopes it will happen.
Hopefully this week I will be able to provide a deodexed and debloated version of the stock rom that will run a little faster and take up a little less space on the device.
A custom kernel is in the works for those interested in overclocking, though I think anything past the stock max speed will cause a good amount of battery drain.
Sent from my SGH-S730G

So you building a custom rom for the tracfone version (730G)?

(Dominix) said:
So you building a custom rom for the tracfone version (730G)?
Click to expand...
Click to collapse
Slowly but surely yes. Haven't gotten as much done this week as I had hoped but it is in the works.
Sent from my SGH-S730G

i need stock rom please
TheGeekyNimrod said:
Slowly but surely yes. Haven't gotten as much done this week as I had hoped but it is in the works.
Sent from my SGH-S730G
Click to expand...
Click to collapse
i mistakingly picked up the wrong phone..the discover and the centura are very similar....i accidently installed custom rom for the centura onto the discover...it is the 730g. i did not make a back up...do you have the stock rom and can you post or email it to me?? [email protected]
:crying:

j.nunez123 said:
i mistakingly picked up the wrong phone..the discover and the centura are very similar....i accidently installed custom rom for the centura onto the discover...it is the 730g. i did not make a back up...do you have the stock rom and can you post or email it to me?? [email protected]
:crying:
Click to expand...
Click to collapse
Right now I do not have a copy of the stock rom. I'm still trying to create an Odin flashable of the basic system partition files, recovery, and boot. Wish I could help you. This is why it's always important to make a backup. You might can try one of the 730M Discover threads and see if someone can send you a back up of theirs, but keep in mind that is the Canadian version of the phone. I'm not quite sure what all of the differences in them are.

Based on what I have been able to find out, other than the tracfone custom boot screen and sound, the android on this phone is just stock android 4. No touchwiz (thank God and all that it holy) no bloatware extras, no nothing. So you could probably take the stock Android 4.0.4 I think it is and work from that.
Sent from my SGH-S730G using xda app-developers app

little trouble
Ive downloaded everyting just fine, but when I try and install the unlockroot it keeps telling me Better installer host has stopped working. Is that something on my end or something on theirs? because i cant seem to figure anything out about better installer and have never seen it before downloading this. You have any suggestions on what is causing this problem?

[sgh-s730g] Discover Straight talk PR Rooted
I will reccomend you to start over as it is in [Root] [CWM] Samgsung Galaxy Discover (SGH-730G) Tracfone Variant ONLYthread, which is in the first page. Do a factory reset if it can be done, and wipe all the catches. format your sd card and be patient, because i followed all the instructions and mine works fine. the only thing i haven't done is get rid of the yellow triangle but I'll doit later on because I'm Working to find the unlocking code for mine. Wish you luck and do be afraid. Just be Patient :good:

Cristiandando said:
I will reccomend you to start over as it is in [Root] [CWM] Samgsung Galaxy Discover (SGH-730G) Tracfone Variant ONLYthread, which is in the first page. Do a factory reset if it can be done, and wipe all the catches. format your sd card and be patient, because i followed all the instructions and mine works fine. the only thing i haven't done is get rid of the yellow triangle but I'll doit later on because I'm Working to find the unlocking code for mine. Wish you luck and do be afraid. Just be Patient :good:
Click to expand...
Click to collapse
I am getting this error on my computer not on my cell phone, My cell is a discover from straight talk. when i downloaded unlockroot from their website onto my computer and go to run it it wont even install. just keeps saying better installer stopped working. Again this is on my computer not on my cell phone.

Uninstall then re-download UnlockRoot .. I had that problem first time I tried to run it. Also, there is the actual free program, amd another program file that pulls up an order and download program for the pro version. Maybe you clicked that one instead?
Sent from my SGH-S730G

I have a debloated, deodexed, zip aligned, rooted version of the stock rom completed. Working on the updater script which is being a pain in my ass. Soon as it is done and tested I'll post it.
I've been behind on it as my volunteer work and family obligations have been my primary focus. But it is something I still try to work on to give this phone a little boost.
Sent from my SGH-S730G

Here it's what you're looking for my Friend
pokesmot88 said:
I am getting this error on my computer not on my cell phone, My cell is a discover from straight talk. when i downloaded unlockroot from their website onto my computer and go to run it it wont even install. just keeps saying better installer stopped working. Again this is on my computer not on my cell phone.
Click to expand...
Click to collapse
Il' PM you the unlock root pro with the serial because I can't post it until I make 10 or more post. Download both items, install the software and then copy > paste the serial and start rooting your phone. Don't forguet to make a back up of your original not rooted rom and save it in your computer and sd card in case something goes wrong just restore it to it's original state.

TheGeekyNimrod said:
I have a debloated, deodexed, zip aligned, rooted version of the stock rom completed. Working on the updater script which is being a pain in my ass. Soon as it is done and tested I'll post it.
I've been behind on it as my volunteer work and family obligations have been my primary focus. But it is something I still try to work on to give this phone a little boost.
Sent from my SGH-S730G
Click to expand...
Click to collapse
I have a SGH-S730M that I bought unlocked off of ebay, and wound up giving it to my wife. After looking at the specs for the SGH-S730G it sounds like they are identical other than one being sold by Telus and the other being sold by net10. Is the SGH-730G unlocked by default? I'm interested in getting one to try my hand at modifying. One of my few key complaints about the SGH-S730M was that even though it didn't have the touchwiz launcher it still had the samsung style lock screen instead of the stock ICS lock screen. Would xposed or any of the other stuff you mentioned allow me to change that back to stock?
Also the battery issue you mentioned also seems to affect the S730M as well, it is more than a little annoying.

doctor_evil said:
I have a SGH-S730M that I bought unlocked off of ebay, and wound up giving it to my wife. After looking at the specs for the SGH-S730G it sounds like they are identical other than one being sold by Telus and the other being sold by net10. Is the SGH-730G unlocked by default? I'm interested in getting one to try my hand at modifying. One of my few key complaints about the SGH-S730M was that even though it didn't have the touchwiz launcher it still had the samsung style lock screen instead of the stock ICS lock screen. Would xposed or any of the other stuff you mentioned allow me to change that back to stock?
Also the battery issue you mentioned also seems to affect the S730M as well, it is more than a little annoying.
Click to expand...
Click to collapse
They are pretty much the same device yes. The 730G I bought was through StraightTalk so it wasn't unlocked. I'm sure you could find one unlocked on Ebay or maybe Swappa or something similar. I do hate the Samsung stock lockscreen too. Stock, Xposed won't do the AOSP lockscreen style. Once I have the deodexed working and ready it should. There is another way to bring it up, but it's a little beyond my experience, but also requires a deodexed system.

TheGeekyNimrod said:
They are pretty much the same device yes. The 730G I bought was through StraightTalk so it wasn't unlocked. I'm sure you could find one unlocked on Ebay or maybe Swappa or something similar. I do hate the Samsung stock lockscreen too. Stock, Xposed won't do the AOSP lockscreen style. Once I have the deodexed working and ready it should. There is another way to bring it up, but it's a little beyond my experience, but also requires a deodexed system.
Click to expand...
Click to collapse
Cool I will be watching this thread for updates. I just bought a used SGH-730G that I am willing to do test flashes on the rom if you need a tester. I got it for a super super cheap price so I won't get upset if it gets bricked.

[Q] Need help unrooting. Need to return for warranty

I recently noticed a cluster of dead pixels in my screen and need to exchange it for a new device. To do this, I presumably need to unroot and revert to S-ON, even though this is purely a hardware problem. However I don't know where to start honestly, as this is my first phone I've ever rooted and am still learning (somewhat slowly). I made a backup of my stock rom, but I think I may have made it too far into the process, as the rom is already has supersu and cannot OTA update. I can't seem to track down a RUU, which is what I think I'm needing, but I'm not sure if those are released for this device yet.. I think I understand the process if I can simply track down a RUU or figure out what to do next. I'm sorry if this seems like an ignorant question, but honestly I"ve tried figuring this out for myself and I'm just needing a little help I think. Thanks in advance.

watchmuu said:
I recently noticed a cluster of dead pixels in my screen and need to exchange it for a new device. To do this, I presumably need to unroot and revert to S-ON, even though this is purely a hardware problem. However I don't know where to start honestly, as this is my first phone I've ever rooted and am still learning (somewhat slowly). I made a backup of my stock rom, but I think I may have made it too far into the process, as the rom is already has supersu and cannot OTA update. I can't seem to track down a RUU, which is what I think I'm needing, but I'm not sure if those are released for this device yet.. I think I understand the process if I can simply track down a RUU or figure out what to do next. I'm sorry if this seems like an ignorant question, but honestly I"ve tried figuring this out for myself and I'm just needing a little help I think. Thanks in advance.
Click to expand...
Click to collapse
Who said you had to revert to S-ON again? Before doing things like that rather read this thread first
SuperSU won't prevent the device from doing an OTA update, did you get the notification for it and tried to install it directly after downloading it? If you have a custom recovery then the OTA won't install, supersu on the other hand won't prevent it like I said. I did the OTA myself while having SuperSU :good:
You can just uninstall SuperSU from the application drawer, open the app and try to uninstall it. If it doesn't work then perhaps try point 6 in this thread "unsupersu". Though you need a custom recovery to do this.

BerndM14 said:
Who said you had to revert to S-ON again? Before doing things like that rather read this thread first
SuperSU won't prevent the device from doing an OTA update, did you get the notification for it and tried to install it directly after downloading it? If you have a custom recovery then the OTA won't install, supersu on the other hand won't prevent it like I said. I did the OTA myself while having SuperSU :good:
You can just uninstall SuperSU from the application drawer, open the app and try to uninstall it. If it doesn't work then perhaps try point 6 in this thread "unsupersu". Though you need a custom recovery to do this.
Click to expand...
Click to collapse
if I can simply uninstall super su then that shouldn't be hard to figure out. thanks. do you have any tips on how to remove the custom recovery? I'm pretty lost on that.

watchmuu said:
if I can simply uninstall super su then that shouldn't be hard to figure out. thanks. do you have any tips on how to remove the custom recovery? I'm pretty lost on that.
Click to expand...
Click to collapse
Download stock recovery from this thread just select the correct recovery that matches your software version.
Unzip the recovery and move it to the adb folder where you have fastboot.exe in(By default this is platform-tools). Hold shift then right click in the folder, select open command prompt/window here.
1) Connect device to computer
2) Type: adb devices to check if device is being picked up, should show you your serial number
3) Type: adb reboot bootloader
4) Type: fastboot flash recovery name_of_recovery.img
5) Type: fastboot reboot
6) Done.

BerndM14 said:
Download stock recovery from this thread just select the correct recovery that matches your software version.
Unzip the recovery and move it to the adb folder where you have fastboot.exe in(By default this is platform-tools). Hold shift then right click in the folder, select open command prompt/window here.
1) Connect device to computer
2) Type: adb devices to check if device is being picked up, should show you your serial number
3) Type: adb reboot bootloader
4) Type: fastboot flash recovery name_of_recovery.img
5) Type: fastboot reboot
6) Done.
Click to expand...
Click to collapse
Just for clarification, are flashing my stock rom backup and removing the custom recovery along with SuperSU all I need to do for it to be in a returnable condition? I really appreciate the help.:good:

watchmuu said:
Just for clarification, are flashing my stock rom backup and removing the custom recovery along with SuperSU all I need to do for it to be in a returnable condition? I really appreciate the help.:good:
Click to expand...
Click to collapse
Well your bootloader screen will still show "Tampered" and "Unlocked" (IF you haven't fixed these yet) so you might want to reset those flags as well before doing the unroot.
Remove Tampered banner
Reset lock status flag
Just follow those 2 guides made by Scotty. If you don't have the flags anymore and you have stock recovery in place, you can just uninstall SuperSU and you're good to go.

[Q&A] FireTV Boot Menu 1.0

Q&A for FireTV Boot Menu 1.0
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 FireTV Boot Menu 1.0. 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!

Missed a step...
Well, as careful as I was trying to be, I managed to screw up the steps!
1) I have no way to block OTA updates via the router (I don't have access), but when I booted up the first time I was able to go into system settings and cancel the update it was downloading. Phew. Still on 51.1.0.1_user_510055620.
2) Sideload towelroot and SuperSU. Success.
4) Root and install BusyBox. Done.
3) Block OTA updates. Now I'm safe!
4) Unlock the bootloader and install CWM 6.0.5.1.4a. Version check. Verified.
5) Install 51.1.4.0_514006420 updated via CWM. Now we're making progress!
6) Install BusyBox again. I guess it wasn't included in "51.1.4.0_514006420 updated."
7) I see to update further, I need to install RBox Boot Menu, so I press forward. I was being SO careful. I verified md5sums, read back through the instructions, and tried to follow line-by-line. I finish installing RBox and reboot.
Success, I think, as RBox loads!! I watch the countdown go from 5 to 0, and then... well, nothing. It just sits there. I read back through the instructions and realize I missed one very crucial step. Yup, I missed copying the original boot.img to /system/boot/. So of course now, it just boots to RBox, but doesn't know where to go from there. And I can't do anything else about it tonight because I don't have a USB keyboard -- I did all the stuff above using ADB and recovery-input.
Sooo, I think all I have to do is hook up a USB keyboard, go into recovery (which I can't do right now with no way to select recovery in RBox), reflash "51.1.4.0_514006420 updated," and start over with the RBox install process -- this time making sure I don't miss any steps. Tomorrow I'll bring home a USB keyboard from work and hopefully have better success!

adgriffi said:
Well, as careful as I was trying to be, I managed to screw up the steps!
1) I have no way to block OTA updates via the router (I don't have access), but when I booted up the first time I was able to go into system settings and cancel the update it was downloading. Phew. Still on 51.1.0.1_user_510055620.
2) Sideload towelroot and SuperSU. Success.
4) Root and install BusyBox. Done.
3) Block OTA updates. Now I'm safe!
4) Unlock the bootloader and install CWM 6.0.5.1.4a. Version check. Verified.
5) Install 51.1.4.0_514006420 updated via CWM. Now we're making progress!
6) Install BusyBox again. I guess it wasn't included in "51.1.4.0_514006420 updated."
7) I see to update further, I need to install RBox Boot Menu, so I press forward. I was being SO careful. I verified md5sums, read back through the instructions, and tried to follow line-by-line. I finish installing RBox and reboot.
Success, I think, as RBox loads!! I watch the countdown go from 5 to 0, and then... well, nothing. It just sits there. I read back through the instructions and realize I missed one very crucial step. Yup, I missed copying the original boot.img to /system/boot/. So of course now, it just boots to RBox, but doesn't know where to go from there. And I can't do anything else about it tonight because I don't have a USB keyboard -- I did all the stuff above using ADB and recovery-input.
Sooo, I think all I have to do is hook up a USB keyboard, go into recovery (which I can't do right now with no way to select recovery in RBox), reflash "51.1.4.0_514006420 updated," and start over with the RBox install process -- this time making sure I don't miss any steps. Tomorrow I'll bring home a USB keyboard from work and hopefully have better success!
Click to expand...
Click to collapse
As long as bootmenu and recovery is working, you can just flash to 51.1.4.1 and it'll be fine.

rbox said:
As long as bootmenu and recovery is working, you can just flash to 51.1.4.1 and it'll be fine.
Click to expand...
Click to collapse
Success! Thanks for the advice about not having to start over with RBox. Hooked up the keyboard (which worked flawlessly), installed the latest pre-rooted image and I'm back up and running!

few questions
hello,
Just so I will learn few things
When I power up the machine it start by loading from /boot partition, Then it decide whether to go to /recovery or /system ?
I saw somewhere that the /boot include the kernel and that the /system the OS ?
I saw from the guide that bootmenu is copied into the /boot
and that the original /boot to /system/boot.
Why do need to save the original /boot ?
I guess that the bootmenu does not include the kernel ?
If so - the pre-rooted roms include this /system/boot ?
also - installing a stock rom will fail because it doesn't built this way or will it also overwrite the /boot ?
Sorry for asking a lot - Interested in וnderstanding.
Thank you

Fire TV Menu 1.0 Question
I have the same issue this person this person has, would appreciate any thoughts or ideas, thanks:
After installing bootmenu I get stuck at the boot screen where the count runs to 0 and am unable to choose launch recovery.
The device does boot into the kernel automatically with no issues.
For some reason my keyboard doesn’t allow me to change it to recovery and I have tried several keyboards. However, if I do ctrl-alt-del the unit reboots so it seems the keyboard commands are working. Any way to recover from this?" Have tested with both pre-rooted 51.1.40 and 51.1.41

Today I installed the app following the instructions but after a reboot it won't go past the Amazon Logo. Does anyone have any tips on how to fix it?
I don't have ADB access to the device via the network have not tried via USB

Problem downloading firetv-bootmenu-1.0.img
No matter what i do this file wont' downlaod from mediafire. Can somene PLEASE upload it to another location. It should have a mirror anyways right? I've been attempting to download it for hours.
Thanks guys

FTV now goes to Wired network on reboot
I've got 2 FTVs that I've updated to the latest CWM, Boot Menu, and pre-rooted firmware. Everything works great except on reboot, sometimes instead of joining the wireless network, the units report that they can't find the network and show that they are wired, which they are not. Forgetting the wired network solves the problem only until the next reboot. Is it possible that the latest custom rom has wired as the default instead of wireless?
Thanks for all your great work.

[root] [ZS570KL] Asus Zenfone 3 Deluxe fast rooting method. Despite TWRP

Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75

Your links do not work.

jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!

You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...

Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app

Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA

You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat

Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!

I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).

Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??

Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.

Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry

Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.

Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website

This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!

Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files

Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.

Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.

Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname

Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.