[Q] Trying... and failing. - Xperia Z1 Compact Q&A, Help & Troubleshooting

Is there a clear and concise step-by-step guide to get root access for a sony z1c (for dummies)? I've been trying many things I've found on these forums; "newroot" doesn't even work ("Please wait" for 20 minutes indicates that something is wrong, I guess); "Flashtool" won't install properly (Windows won't let me install drivers even though I accept the "risk") and "Easyroot" simply won't do its magic (creating vm loljavasucks). I can't even get it to start in recovery mode (pressing power on and then up or down on the volume buttons when the led goes red / pink doesn't do anything).
I just want root access (want to remove some bloatware and get access to move apps from internal storage to SD card), I don't need to unlock the bootloader.
Can someone please point me in the right direction at least? Firmware is 14.4.A.0.157.

Sounds like you're getting really frustrated with yourself. Calm down, take a breath and research the process.
Start here
http://forum.xda-developers.com/showthread.php?p=49928704
You should find all you need to achieve root without having to unlock the bootloader. It really is very straight forward if a little time is taken to research first.

spudata said:
Sounds like you're getting really frustrated with yourself. Calm down, take a breath and research the process.
Start here
http://forum.xda-developers.com/showthread.php?p=49928704
You should find all you need to achieve root without having to unlock the bootloader. It really is very straight forward if a little time is taken to research first.
Click to expand...
Click to collapse
I see. There is none, then. Well, from what I've gathered part of the problem is probably that I'm on version 157, which appears to be "unrootable". If I manage to install Flashtool properly, I'll try to flash version 108 and root that instead.
While I really do appreciate the hard work from individuals here, I cannot but help suggest to clean some threads and perhaps split them according to topics. There's a load of useful information provided by eager enthusiasts here, but for a new user of these pages it apoears both a little chaotic and daunting, as it seems one is expected to know both abbreviations and "slang" expressions in order to be able to keep up when reading the tutorials.
When adding that much of the software advertised here is unofficial (though made with the best intent, I've no doubt!) and the OS and AV software on computers cry "alert!" the process becomes quite a challenge for those who don't want to brick neither their phone nor their computer.

I was quite the same when I first got my z1c. I spent days reading and googling all about it and like you say "struggling with abbreviations". I found the best way is to:-
1. Use flashtool to downgrade to .108
2. Use rootkitxperia to root and install supersu
3. Use Nuts dual recovery installer to install recovery
4. Don't upgrade to .157

spudata said:
I was quite the same when I first got my z1c. I spent days reading and googling all about it and like you say "struggling with abbreviations". I found the best way is to:-
1. Use flashtool to downgrade to .108
2. Use rootkitxperia to root and install supersu
3. Use Nuts dual recovery installer to install recovery
4. Don't upgrade to .157
Click to expand...
Click to collapse
Success.
Except that I don't understand what to download from NUTS. Or why I should install that, for that matter.
But I've managed to root the phone, install SuperSU and Titanium Backup, and everything works fine it seems (well, the 2nd time... The first time I uninstalled the Sony version of "Contacts" by a mistake, and that made the phone ....well, unusable as phone, since I only got "Contacts has stopped working" when I tried to make an outgoing call. A phone that can only answer calls is perhaps somewhat useless). I've also backed up my TA partition with TA Backup.
Now, on to my girlfriend's S3....

What if you do update to. 157?
Not sent by me!

Related

[Q] Problem after trying to root Arc S

Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
I had the same problem. First of all if you have bootloader unlocked it is still unlocked even if you had flashed another rom.
What rom did you exactly flashed? What OS do you use on your computer? When I started to flash different stock roms and then to root them then I unlocked my bootloader then the same problem appeared on Windows 8 (I could find no way to make my phone recognisable - don't know why). I tried to flash rom again on another one running on Winows 7 and after instaling drivers from flashtools and instaling sony companion phone started to be recognized.
So try to connect your phone to another Pc (if possible) and then flash any stock rom (for example ICS 4.04 build 4.1.B.0.587) and then (if you have unlocked you bootloader) flash any pre-rooted kernel (http://forum.xda-developers.com/showthread.php?t=2159411).
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something. If so, I'm sorry, feel free to point me to a fix, and then I'll try that.
So here's my problem,. While trying to root my SE Arc S I seem to have put it in some kind of situation I can't fix: I'm now stuck at running stock ICS 4.04 (4.1.B.0.431), lost my root (and looks like i also lost CWM recovery), can't flash anything and can't root the phone again.
So, would anoyone know how to fix this? Please, keep any instructions as easy and clear as possible. As you'll probably see in the rest of my post i'm pretty new/noob at this stuf.
Here are the things I did to get to this point (before all this I started out with ICS 4.04 build 4.1.B.0.587)
- First I unlocked my bootloader, that seemed to work. I followed the steps on the sony instruction page
- Second, I rooted the phone, by following a combination of the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1683957 and on another non xda page (the steps seemed similar, but the non xda page was a little clearer/easier/more noob friendly for me.) That also worked, since I could use Titanium Backup (can't now)
- Third, I installed CWM with RecoverX. That worked, since I could enter CWM.
- Fourth, I tried installing different ROM's (cyanogenmod) by storing it on my sd card and installing it via CWM. That's where the problems started.
First of all I couldn't install any of the ROM's i tried. CWM would start installing it and then gave a status 7 error and aborted the installation. After trying the same process a couple of times my phone got stuck on the Sony screen after rebooting.
To fix this i flashed a stock android thingy (not sure if it's a rom, kernel, or whatever, anyway it's the version i'm running now) That worked and my phone at least functioned again.
However, since I don't wanna run this version I looked for ways to flash/install a different one. That's when I noticed I lost my root (an app i dl'ed that needs superuser privilleges didn't work) I tried rooting the phone again, but found I couldn't even flash anything. If i tried that, flashtool would give an error about not recognising the phone and stopped the flashing process. Then i tried to unlock the bootloader again, to see if that might work. But that didn't work either cause again my pc didn't seem to recognise the phone. I also tried using the doomlord root app. That seemed to work, but somehow after finishing it i didn't end up with root priviliges (again, I checked this by trying to use a root required app)
So, now I can't unlock the bootloader, I can't flash anything and I can't root my phone. All I can do is use it. And thought that's obviously the most important thing, I would like to be able to do more with it.
So, does anyone know how to fix this? It all seems to boil down to my phone not getting recognised while in fastboot/flash mode. But I wouldn't know how to fix that...
A lot of thanks in advance for any help!
Click to expand...
Click to collapse
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた
Thanks both for the different bits of advice. I dunno how, but it finally works now! In the end I installed sony's pc companion, switched off antivirus and then all of a sudden i could flash things again. Then i just followed the steps to rooting the phone for the second time, and it finally worked. Got my root back and also managed to install a ROM from CWM.
Again, not sure how, maybe i should have just turned off my antivirus from the start, or maybe in retrying all the steps I somehow stumbled across the sollution, but at least it works now
popthosegaskets said:
1. Why did you use XParts? Unlocked bootloader means you can flash a stock kernel with CWM in it.
2. CM ROMs use different kernel, that's why you get status 7. Maybe you can Google a bit on CWM status 7 error? To install Cyanogen ROM, use the included kernel or look for a list of recommended kernels.
3. Flashtool should still work. Can you enter flashboot? Connect your cable to the PC, hold down the back button and connect your cable to it. A blue light means it's successfully connected in flash mode.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
What is XParts? I don't think i used that program. The steps i previously followed might have been redundant in part, but I wanted to be on the safe side and just try all options i could find.
I tried googling for the CWM status 7 error, but couldn't really find any sollution i could work with. And anyway, it's fixed now (i hope, didn't try CM again though)
Flashtool didn't work yesterday. Or at least, it did work but i just couldn't flash anything cause it didn't recognise my phone.
Anyway, thanks again. This is fixed now
ilporro said:
Hello,
First of all, I did try to look for other topics about this issue. However, working through sometimes a couple of hundred pages in a thread and to sift through all the topics here could mean I missed something.
Click to expand...
Click to collapse
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
XperienceD said:
Rooting:
UPDATE: One click root [4.1.B.0.587 /.431 /.562 ] All 2011 Xperias
- What is rooting and why should I do it? The pros & cons of Android rooting
Rooting methods for the XPERIA line of Phones has constantly changed from apps to Pre-Rooted ROMs and Kernels. A Google search of "root -insert device name-" should help to find the specific method for your Phone but the following link is well worth reading - [How-To] Rooting guide for 2011 xperia devices
References:
[Arc/S] [PRO] Root for 4.0.4 ICS Update [4.1.B.0.431+4.1.B.0.587]
Root MANY ANDROID! [Upd: 18.12.2012]
[ROOT+BB+CWM] ICS and non rootable GB build
[ROOT][NOOB GUIDE][for unlock BL] For Official ICS 4.0.4
[HOW-TO][FTF] Root and CWM with the latest 9.0.1.D.0.10 firmware
[ROOT&MORE]Xperia 2012 line Flashtool + prerooted system.img + Sony fw FTF + addons
[Tutorial]Root.Xperia 4.0.4 ROM [all h/m(dpi)] | 4.1.B.0.431
Click to expand...
Click to collapse
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.
XperienceD said:
Which is why senior members in all sections create guides like - [GUIDE] All Things XPERIA - Debranding - Rooting - BL Unlocking - Theming to make it easier for People like yourself, and in those guides you'll find things like...
...so when a new members start new threads about something that's been covered a gazillion times, it can be quite frustrating.
Click to expand...
Click to collapse
Well, I did follow the steps in at least one of those guides. And that worked. So the problem wasn't in working out how to root the phone, but in fixing what went wrong afterwards. The first attempt at rooting worked, but then flashing a ROM failed, the phone stopped working and after fixing that i lost the root and couldn't find a way to reroot it (even ater following all the steps in the guides i previously used, it just didn't work)
So, with all do respect to those guides and their usefullness, as far as I can tell my problem/question wasn't answered in them.

[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] Whats causing this problem?

Sup, so in my last post I was told to read some info, get a better idea of what to do and how to move forward.. Problem being is, Where do I start? There is no actual help for the situation I am stuck in.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe.
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off.
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along.
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again.
P.S in work, Will reply when possible.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe. As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop. Golden rule - Never Never Never take an OTA when running a custom recovery.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off. Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place??
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along. Samsung are completely different. I know as I've rooted my GF's and it was painful
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again No OTA's are safe to use with a custom recovery.
There are a couple of things I'm not sure on, I think you have done the following so far
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Is that correct?
Can you get into TWRP recovery?
Also you have a thread about this open already. Either delete that thread or this one.
As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2 - Nope, Upon taking out the box on day 1, there was an update required and did it straight away.. then a smaller one. Guessing thats 4.4.3 and 4.4.4.
Golden rule - Never Never Never take an OTA when running a custom recovery - hahah, Ive established this now >.< I originally saw rooting as a "inject" sort of methodology.. before the os booted.. Thats not the case!
Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place?? - I rooted following "TheUnlockr" video guide, It did say S-OFF, Bootloop and **** up with the OTA removed this I think. This was using the Hasoon2000 AIO tool.
Samsung are completely different. I know as I've rooted my GF's and it was painful - Good to know, I wont take too much advice from him, he did highlight a tool called Odin. Would that be any benefit to myself?
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Basically.. yes.
Yes I can get into TWRP, but as I say, when I boot to system, this is where the loop starts.. phone starts up normally.. gives me 1min before restarting over and over.
I am sorry, Im aware that another topic is open. I did try to close it, dont have permissions on account. havent used forums in a few years and its all over the shop now hahaha.
Sorry for late reply.. hectic couple of days.

Bootloop, how to download stock for TWRP

Hello, I recently tried to root my device, I succeed in doing so but it was systemless root, I didn't know anything at the time so I tried different versions of supersu, now my phone won't boot, only fastboot and recovery works,
I visited a thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but I don't know which one is my stock and I'm afraid to mess it up even more,
image uploaderG]
Can you please advise me how to recover my basic stock system :F
I remember that my installed android before it stopped working was 6.01 afaik
Your Stock is 6.12.111.4
option 1:
TWRP backup - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
on post #3
Make sure to use TWRP 3.x.x.x not your current one as it seems you use the outdated version.
option 2 :
RUU - https://www.androidfilehost.com/?fid=24399965296001026
follow this guide but use the above RUU - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you, my TWRP is the latest one now because my system sort of worked when I first rooted it but when I noticed that it's systemless I tried to flash system one and my phone didn't work as intended (couldn't download things on it and some other things didn't work) that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop. Downloading that recovery, wish me luck .
Edit: it works now, thanks
One additional issue arose - my folders seem to be really wrecked, can't download anything from updates to system apps to downloading apps from playstore and even downloading apps regularly, when I made sd card my internal card I was able to download opera and wanted to select default download folder but couldn't pick any/make any and the folders were not recognizable for me (no data folder for example)
edit 2: I probably fuked up permissions too last time, fix context in twrp seems to have fixed the issue
Radenz said:
that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop.
Click to expand...
Click to collapse
Couple words to the wise:
1) Always state exact versions numbers (TWRP, SuperSU, etc.) instead of just saying it the "latest". I've seen a lot of cases, where folks ensure us they are on the "latest" and it turns out when prompted for the actual version number, they are using something from 2 years ago!
In general when posting here, it's always best to give as much detail and specific info as possible. Vague descriptions, lack of details, and assumptions are always going to hinder more than help.
2) Always make a TWRP backup of your stock ROM before doing any mods like root or custom ROM. As you now see why, things don't always go as intended. Luckily, ckpv5 maintains a collection of stock backups. But you should already know how to revert to stock and be equipped to do so, before doing the mods. Not waiting for that "panic" moment when you need it, and can't figure it out.
I'm surprised how many folks here jump into rooting, flashing custom ROMs without leaving themselves an "escape plan" of knowing how to get back to stock. Maybe it's just my personality, but I can't fathom doing any of these things without knowing beforehand how to fix them, restore stock, etc.
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Radenz said:
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Click to expand...
Click to collapse
Yeah, completely understand if you are new to this; and we all had to start somewhere, at some time. Consider it lessons learned for next time.
A lot of folks skip the step of making a backup (before root, etc.). And also a lot of guides, YouTube tutorials, etc. neglect this step (which is something I cannot understand). So it's an honest mistake, and I'm definitely not saying that it's your fault that it wasn't done.

Newbie rooting/backup thread (groan...)

In my defence, m’lud, I spent about 6 hours yesterday reading through a great many threads before posting this one. It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
I expect it's just the terminology… when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…? Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
My main reason for wanting to root my M8 is to remove all the bloatware HTC put on it. I can read the instructions for rooting here, but I don’t like blindly following anything I don’t understand, for obvious reasons!
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
I’ve read through several tutorials, and they’re easy to follow, but not easy to understand, if you get me… they’ll say things like download this, flash that… but I don’t really know what’s going on when you flash something – what am I over-writing etc.
Is there a thread anywhere which explains what these various things actually ARE?
Oh, and I’ve been playing various King games for years, and have got a long way. I’ve tried to figure out how to back them up – the King website is possibly the most unhelpful I’ve come across. People mention various utilities (I think maybe Titanium etc), but if they only work on a rooted phone, they presumably can’t be used to back the games up prior to rooting…
Sorry about all this guys – not asking you to re-invent the wheel, but f there are specific threads that already answer my questions to get me started, I’d be VERY grateful
Thanks
Roger
Roger465 said:
In my defence, m’lud, I spent about 6 hours yesterday reading through a great many threads before posting this one. It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
Click to expand...
Click to collapse
Aye, it takes a bit of time to learn all the things and understand them.
Me, after being really familiar with a Sony device had to spend XX hours reading about HTC and after few years there are still things that I don't know
Roger465 said:
I expect it's just the terminology… when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…? Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
Click to expand...
Click to collapse
I'd rather say recovery is closer to bios., but bootloader matches too.
Recovery is a partition that all android phones have and it can be accessed in case when the system dies to factory reset and things. Stock recovery is good, but it can't be used to flash things like roms and kernels, so we use TWRP - a custom recovery with many options.
Original recovery is overwritten, but can be restored.
As for bootloader it's kinda like a gate - a locked one prevents booting and flashing of any unauthorized files, like custom recovery for example. Unlocking it removes this restriction. That's one fuction of bootloader, another one is starting up the system - like a bios - and can be accessed by a button combination durning boot up, it's also called hboot. In it you can see some essential info about phone software and boot to recovery.
Roger465 said:
My main reason for wanting to root my M8 is to remove all the bloatware HTC put on it. I can read the instructions for rooting here, but I don’t like blindly following anything I don’t understand, for obvious reasons!
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
Click to expand...
Click to collapse
ROM is the android itself, drivers, kernel and manufacturer's interface, apps, tweaks, settings. and probably something else I've missed. I think it would be somewhat correct to call this operating system. Rooting is gaining superuser access on the phone - it can be used to give extended functionality to apps, like making modifications in system itself. Pretty similiar to "run as administrator" in windows. Rooting itself won't remove the rom.
Roger465 said:
I’ve read through several tutorials, and they’re easy to follow, but not easy to understand, if you get me… they’ll say things like download this, flash that… but I don’t really know what’s going on when you flash something – what am I over-writing etc.
Is there a thread anywhere which explains what these various things actually ARE?
Click to expand...
Click to collapse
Those should give you a basic knowledge:
https://www.androidcentral.com/dictionary
https://android.gadgethacks.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
Roger465 said:
Oh, and I’ve been playing various King games for years, and have got a long way. I’ve tried to figure out how to back them up – the King website is possibly the most unhelpful I’ve come across. People mention various utilities (I think maybe Titanium etc), but if they only work on a rooted phone, they presumably can’t be used to back the games up prior to rooting…
Click to expand...
Click to collapse
Titanium backup is an app used to backup other apps, but it requires root. To get root you need a custom recovery and for it you need an unlocked bootloader.
Unlocking the bootloader will wipe all data from the phone. I'm not aware of many working methods to backup apps and their data.
There's an app called Helium, but there are many complaints that it doesn't fully work. You can try syncing all data to your google account or adb backup.
A lot of the basic terminology is explained here: https://forum.xda-developers.com/showthread.php?p=52484527#post52484527
My responses below in red font:
Roger465 said:
when you guys talk about a bootloader, I’m thinking that’s roughly the same as a BIOS on a computer…?
I'd say that is a pretty good analogy. It's responsible for loading the OS, same as BIOS does on a PC. And as long as you can get into bootloader, the phone is recoverable almost regardless of what else you did (within some limits).
Then there’s the “recovery” thingy… is that like a recovery partition on a Windows machine? But then some threads seem to suggest you over-write that when rooting, so is the original factory image lost forever?
Recovery is the tool for making or restoring backup (and also flashing ROMs and other mods like root). And not the actually backup itself. So that is one important distinction to remember.
Installing custom recovery (TWRP) will overwrite the stock recovery, that is true. You can only have one recovery at a time.
Stock recovery is easy to restore; and the stock recoveries are available on this forum. But stock recovery is close to useless. The only reason you would need stock recovery, is to install an official OTA (over-the-air) upated. And HTC was done updating this phone a long time ago (with Marshmallow) and there will be no more updates. Therefore, no need for stock recovery.
Since you've decided to do to the dark side and root; custom recovery TWRP as vastly more useful than stock recovery (as also mentioned in the previous response). To be honest, I can't say I've booted to stock recovery on this or any HTC device I've owned (and it's been several) even once. Never used it, and never needed to.
I kind of gather that the “ROM” is the operating system… if I root the phone, does that automatically obliterate the existing one, necessitating a new one, or can I just gain the access I need to delete the horrible factory apps, and keep everything else?
Depending on root method (SuperSU or Magisk), root will make changes to the system and/or kernel (which comprise the OS or ROM). It's still the stock ROM, just with some minor changes to allow superuser access. You can and should make a backup or your stock ROM, before rooting, using TWRP custom recovery. This gives you an easy way to restore to stock unrooted ROM, if you ever want to. And also gives you an easy "escape hatch" if anything goes wrong while trying to root. There are other tools on this forum for restoring the stock ROM. But best practice (and just plain common sense) is to make a backup in TWRP.
Click to expand...
Click to collapse
---------- Post added at 10:33 AM ---------- Previous post was at 10:24 AM ----------
Phalangioides said:
There's an app called Helium, but there are many complaints that it doesn't fully work. You can try syncing all data to your google account or adb backup.
Click to expand...
Click to collapse
All backup methods are far from perfect, especially before/without root. I'll agree that Helium is probably the best bet for the OP to backup things like game saves.
---------- Post added at 10:36 AM ---------- Previous post was at 10:33 AM ----------
Roger465 said:
It’s amazing how hard it can be to pick up a slightly unfamiliar technology when it’s not the one you're used to… I spent the latter half of my life in IT (Windows), but really struggle with this phone stuff.
Click to expand...
Click to collapse
Stick with it. Every technology has its own lingo and nuances. Even from one Android device to another, there is a learning curve. I've found myself wondering: "WTF is a blob, or Odin" when switching to other Android devices.
With your IT experience, it shouldn't take much to pickup the necessary knowledge.
Thanks guys, kind of you to go to so much trouble to explain for me. Wish I had two phone,s then I could play around messing one up... will read a bit more, then give it a go in a day or two I think. But just to clarify again, can I give myself the rights to remove stock bloatware, while maintaining my familiar Android environment, the apps I use at the moment etc, or do I have to install a custom ROM if I root?
Cheers
Roger465 said:
can I give myself the rights to remove stock bloatware, while maintaining my familiar Android environment, the apps I use at the moment etc, or do I have to install a custom ROM if I root?
Click to expand...
Click to collapse
Yes, the OS will remain the same.
Whether you can remove bloat apps after root is a little complicated to explain. You would normally expect to be able to delete system apps (which bloat apps are) with root. However, for whatever reason, HTC decided to write-protect the system partition, even with root. This means that if you try to delete apps when the phone is booted to OS, (depending on what method you used to delete the apps) you will find they return when the phone is rebooted.
You can flash a kernel mod to disable the write protection, or install a custom kernel. Or you may find the easiest work around (after root) is to use the file manager within TWRP to delete the bloat apps.
---------- Post added at 12:43 PM ---------- Previous post was at 12:11 PM ----------
Vomer's guide is a good one, for unlocking the bootloader, custom recovery and root:
https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
It's a bit outdated, so some words of advice:
- Only follow parts 0 and 1 of the guide. The sections after that aren't needed (s-off and SuperCID) for root, and the s-off method no longer works.
- Use an updated version TWRP from what is in the guide. If you are currently on Marshmallow, the current version TWRP 3.2.1.0 should work. Or basically any version 2.8.7 or later. You can get TWRP here: https://dl.twrp.me/m8/
- Similarly, use current version SuperSU 2.82 (use TWRP flashable zip from here): https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Or alternately, you can use Magisk to root, instead of SuperSU. Honestly, Magisk is really cool, and has lots of features that SuperSU doesn't. So I suggest checking it out: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
redpoint73 said:
Vomer's guide is a good one, for unlocking the bootloader, custom recovery and root
Click to expand...
Click to collapse
Hhmmm, not getting very far with that procedure. Difficulties so far:
- Enable USB debugging in your phone's Developer options - DONE
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
- Install ADB and Fastboot on your computer - DONE
- Make sure to back up all of your app data using either ADB or HTC Sync, because you will be wiping your phone – JUST PLAYING AROUND WITH CONNECTING TO THE PHONE AT THIS STAGE
- Install the HTC One M8 drivers on your computer (if you have HTC Sync installed, then you already have them) - DONE
Enter Fastboot (bootloader) Mode
Place your device into fastboot mode by plugging in your HTC One to your computer,
then powering it down by holding both the Power and Volume Down buttons until you see the screen below – WHEN I DO THAT, IT JUST TAKES A SCREENSHOT
Roger465 said:
Hhmmm, not getting very far with that procedure. Difficulties so far:
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
Click to expand...
Click to collapse
It was only available back on 4.4. It was removed in 5.0 and above, no need to worry about it now.
Roger465 said:
Enter Fastboot (bootloader) Mode
Place your device into fastboot mode by plugging in your HTC One to your computer,
then powering it down by holding both the Power and Volume Down buttons until you see the screen below – WHEN I DO THAT, IT JUST TAKES A SCREENSHOT
Click to expand...
Click to collapse
The guide is a bit inaccurate in this one. Turn off your phone, then press power and vol down - you should get into bootloader. Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
My phone refuses to boot up after I turn it off. Have to help it with a soft reset and then hold vol down so it gets into bootloader, so I can't fully confirm.
Roger465 said:
- Un-check "Fast boot" on your phone by going to Settings -> Battery Manager – NO SUCH OPTION
Click to expand...
Click to collapse
As mentioned in the previous response, this doesn't apply anymore. The feature doesn't exist (hasn't since Kitkat) and therefore does not need to be turned off.
Also note, this option is not to be confused with the fastboot/adb interface (virtually the same name, for different things) which is still fully working, and required to unlock the bootloader and flash custom recovery. The power option "Fast boot" was just a feature used by HTC to make the phone turn on faster. It was merely a "deep sleep" trick which was not a true "power down" and would interfere with accessing bootloader/fastboot mode if you tried to it from a "power off" condition (since in fact it wasn't truly powered off).
Again, it's irrelevant now, and you don't need to worry about that step at all.
---------- Post added at 09:14 AM ---------- Previous post was at 09:00 AM ----------
Phalangioides said:
The guide is a bit inaccurate in this one. Turn off your phone, then press power and vol down - you should get into bootloader.
Click to expand...
Click to collapse
Agreed, the guide is a little incorrect on that step, and I hadn't caught that (error in the guide) before. Power+vol down to access bootloader, will only work when the phone is powered off.
To the OP, another method/trick to access bootloader:
1) While the phone is on, reboot the phone by holding down the power button, and select "reboot" (or restart, I forget exactly what it says)
2) Once the screen goes dark to reboot, but before the white HTC logo screen appears, hold down the vol down button. Don't let go until you see the white bootloader screen.
3) If the phone simply restart to OS, you simply got the timing wrong. You either started pressing vol down too late, or let go too early. Just repeat steps 1 and 2 until you get it right.
Another alternative, is to force a reboot by holding power+vol up. Again, once the screen goes dark to reboot, but before the HTC logo screen appears, hold the vol down button only. In this case, you simply let go of the power button, and slide your finger down to the vol down button, and don't let go until the bootloader screen appears. This method is handy to know, since it works in all cases when the phone is powered on, even of the phone is "frozen" or stuck not loading the OS.
Phalangioides said:
Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
Click to expand...
Click to collapse
If the phone is already connected to the PC by USB cable before going to bootloader, it should default to fastboot mode once the bootloader is accessed.
Not sure if it will automatically switch to fastboot mode if you are in bootloader, then plug in the USB cable. But that may well be true (and would make sense).
In either case, if it's not in fastboot mode, simply select "fastboot" by using the vol buttons, and confirm the choice by pressing the power button. You should see "fastboot" highlighted in red near the top of the screen.
Phalangioides said:
Turn off your phone, then press power and vol down - you should get into bootloader. Select fastboot and when it gets into fastboot, plug in the usb, it should change to "fastboot usb" - or at least I think it was like this.
Click to expand...
Click to collapse
Wahay! That worked fine, thanks both. Hope you can appreciate, though, how scary it can be for somebody like me following instructions I don't really understand, when the expected thing doesn't happen – visions of bricks keep coming into my mind
OK, will practice these steps a few times till they’re 2nd nature. I have managed to retrieve my phone identifier thingy though
Roger465 said:
Hope you can appreciate, though, how scary it can be for somebody like me following instructions I don't really understand, when the expected thing doesn't happen – visions of bricks keep coming into my mind
Click to expand...
Click to collapse
Don't worry, you won't brick this device with what you are doing (unlock bootloader, custom recovery & root). In fact, this device is very hard to brick. As long as the screen comes on, it can almost always be recovered.
Worst case, is that something goes wrong, and you can't boot the phone. Maybe you did something wrong, or maybe just some random event that was not fault of yours. And maybe it takes you an (hairpulling) hour to find the answer, and figure out what went wrong (or how to recover from the problem). But that pretty much happens to everyone who mods these devices from time to time. If you work IT, you've been there. Stressful, but hardly ever catastrophic.
Woo hoo! Got my unlock code. Now time for some more studying before I do anything drastic - specifically how to back up.
I think the HTC Sync Manager will handle most of it? My contacts are all on Google anyway... main worry is 2 years' progress on various King games
Roger465 said:
Now time for some more studying before I do anything drastic - specifically how to back up.
I think the HTC Sync Manager will handle most of it? My contacts are all on Google anyway... main worry is 2 years' progress on various King games
Click to expand...
Click to collapse
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).
redpoint73 said:
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).
Click to expand...
Click to collapse
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it
Roger465 said:
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it
Click to expand...
Click to collapse
The first unlock bootloader will restore your phone. Cross your finger if the game data has been backed up. :fingers-crossed:
redpoint73 said:
I don't use HTC Sync, personally. So I really don't know. I typically root my devices pretty soon after getting them, and therefore never had to use any no-root backup solutions (Titanium Backup is my go-to backup app, but requires root). A number of folks around these forums have suggested Helium for backing up app data when no rooted (and it was mentioned before on this thread).
Click to expand...
Click to collapse
I don't play games so I can't really confirm all games are same.
On my experience transfering games data from one device to another (for nieces & nephews), the data is stored in internal storage android\data\games folder & android\obb\games folder. I copy these two out and transfer them to new device.
(Also check sdcard android folder)
Roger465 said:
Yeah... it doesn't fill me with confidence. I'm sure I'd do exactly as you if it was rooted. I'll probably do it with several different backup apps, and hope that one of them will do it
Click to expand...
Click to collapse
I agree with the approach, make different backups and hope one or more works properly. Games and other apps don't all save data the same way, so no single approach will work in all cases.
Me again, sorry… shortly after that post, I dropped the thing and broke the screen. For one reason or another, I ended up getting a Samsung S6, which I’m quite happy with.
But I want to use the HTC as a spare/emergency phone – trouble is I can’t remember what I’ve done to it, apart from installing something which was recommended as part of my attempted rooting process.
When I switch it on I get the screen below – but no matter which option I select, it just seems to either switch it off or loop back to this screen.
I didn’t go any further than install whatever software it was that gives me this boot menu screen.
I’m no longer interested in rooting it etc – just went to restore it to factory settings and leave it.
Can anybody tell me how please…?
Thanks
Roger465 said:
I can’t remember what I’ve done to it, apart from installing something which was recommended as part of my attempted rooting process.
Click to expand...
Click to collapse
Obviously, if you don't know what you did, it's hard for us to figure out as well.
The "LOCKED" banner at the top of the bootloader screen means the bootloader was never unlocked. So really, no actual mods were done to the phone by you.
All I can think, the "something" what you installed was possibly the Helium app (recommended by another user back up on this thread) which can be used to backup/restore your app data.
Roger465 said:
I didn’t go any further than install whatever software it was that gives me this boot menu screen.
Click to expand...
Click to collapse
I don't know what you're trying to say here. You'll need to be more specific (at least try) than "whatever software". Did you flash something to the phone? Or only installed something to your PC (drivers, fastboot, etc.).
We need to properly understood what you've done, before we can assist further.
redpoint73 said:
Obviously, if you don't know what you did, it's hard for us to figure out as well.
The "LOCKED" banner at the top of the bootloader screen means the bootloader was never unlocked. So really, no actual mods were done to the phone by you.
All I can think, the "something" what you installed was possibly the Helium app (recommended by another user back up on this thread) which can be used to backup/restore your app data.
I don't know what you're trying to say here. You'll need to be more specific (at least try) than "whatever software". Did you flash something to the phone? Or only installed something to your PC (drivers, fastboot, etc.).
We need to properly understood what you've done, before we can assist further.
Click to expand...
Click to collapse
Yeah… sorry, I’m aware how unhelpful my post is. Unfortunately, it was a while ago now, life went tits up for quite a while, and the phone lay in a drawer, being a very low priority. I used to take it out occasionally and charge it up – it started normally.
The other day, I realised I hadn’t charged it in many months, so took it out, and sure enough it was completely dead – so I plugged it in, and it came up with the screen as posted. I let it charge for a couple of hours, then rebooted, and it came up that way again. No matter which option I select from the menu, it either just shuts down, or reboots to that screen.
I’m virtually certain I didn’t do anything other than enable the mode which lets you get to that boot screen, and that I didn’t get as far as flashing the phone or anything. Don't think I installed Helium - if I did, I didn't actually use it.
So it may just be that the phone has died from being left flat for so long… is that likely do you think?
Thanks and sorry again for the lack of info – I completely understand if you can’t help!
Roger465 said:
I’m virtually certain I didn’t do anything other than enable the mode which lets you get to that boot screen, and that I didn’t get as far as flashing the phone or anything.
Click to expand...
Click to collapse
Okay, so it was somewhat confusing, as you said previously (twice) that you "installed" something. But I think you are just confused, thinking that installing something is necessary to get to the bootloader screen. Which it isn't, that screen is part of the bootloader, without which your device would be a paperweight. It will sometimes default to this screen by virtually no action of yours (except powering it on) in cases when the Android Operating System (OS) is missing or damaged. Or you can simply access the bootloader screen by holding the button combo power+vol down.
Roger465 said:
So it may just be that the phone has died from being left flat for so long… is that likely do you think?
Click to expand...
Click to collapse
We've seen it a number of times, actually. The OS was probably corrupted or damaged by being powered off (battery dead) for so long. This condition is over recoverable, as long as the phone can power on, and you can get to bootloader (which you can).
You can restore the OS with the RUU (ROM Update Utility) tool. You can get the RUU, and instruction how to flash it from here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note: there is no need to lock the bootloader as the first part of the instructions say (your bootloader is still locked).

Categories

Resources