Related
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
So I have screwed up pretty bad and now tried fixing the problem myself before asking for help.
Earlier I flashed Android Revolution HD 12.3 to finally realize that I didnt work with sprint, however I forgot to make a back-up for my phone. I have tried using adb sideload to install viper's rom v1.1.0 via TWRP. After the flash is complete and I click reboot, I get an error saying "No OS installed! Are you sure you want to reboot?"
If I swipe to reboot, I end up with a black screen with a toolbar at the top. I am totally lost and have been searching to forums for hours on end. Any help would be greatly appreciated.
Edit: I have been able to get viperROM to boot to the startup screen, however with a minute or so I get an error which states "Precess system is not responding, would you like to close it?" Then my phone restarts to the black screen.
You messed up your partitions by flashing that rom. From bootloader select factory reset to get your partitions back and then sideload your sprint rom and you should be set.
Or this method will work too.
http://forum.xda-developers.com/showthread.php?t=2321685
Konfuzion said:
You messed up your partitions by flashing that rom. From bootloader select factory reset to get your partitions back and then sideload your sprint rom and you should be set.
Or this method will work too.
http://forum.xda-developers.com/showthread.php?t=2321685
Click to expand...
Click to collapse
I tried the first method and didnt have any luck. I did notice that when looking through the install folder, the .zips are no longer listed. However, when the phone turns on for a few seconds and I am able to open files through my PC, they are listed there.
Second method got me to the startup screen. As I attempted to connect to wifi, I had no phone service and also there was an error connecting to wifi due to "temporarily avoiding poor connection". Then the phone instantly restarted back to a black screen.
[SOLVED]
I followed instructions on:
http://forum.xda-developers.com/showthread.php?t=2390821
followed by
http://forum.xda-developers.com/showthread.php?t=2250904
Which fixed all of my problems. Now im back to square 1
You're lucky the partitions aren't aligned in a way that your hboot was overwritten. Otherwise you'd have a brick instead of a phone.
CNexus said:
You're lucky the partitions aren't aligned in a way that your hboot was overwritten. Otherwise you'd have a brick instead of a phone.
Click to expand...
Click to collapse
I know, I really lucked out. Took a solid 14+ hours of research and trial and error to figure out how to fix it. I had rooted my old evo 4G a few times thinking I still knew what I was doing, but that was a while ago. I should have definitely took some extra time to do some more research before I flashed.
This is why i don't flash roms from another section even though some have sprint version i just don't trust them
YoungCorruptionV2.0 said:
This is why i don't flash roms from another section even though some have sprint version i just don't trust them
Click to expand...
Click to collapse
I flashed viper's sprint version of his ROM and havent been receiving text messages or phone calls. I think its time to just give up on keeping my phone rooted. I havent had any favorable results yet.
So I ran a RUU to get everything back to stock as described above, however I am no longer receiving text messages or phone calls. I can send them though. Would anyone know why?
message deleted
flsurf7 said:
So I ran a RUU to get everything back to stock as described above, however I am no longer receiving text messages or phone calls. I can send them though. Would anyone know why?
Click to expand...
Click to collapse
did you try to update the profile and PRL? otherwise you might have to call sprint and manually program using your MSL through the ##DATA# menu
http://forum.xda-developers.com/showthread.php?p=29331038
Sent from my HTCONE using xda app-developers app
I'm having a similar problem but I can't sideload anything because adb can't find my device.
Jay227 said:
I'm having a similar problem but I can't sideload anything because adb can't find my device.
Click to expand...
Click to collapse
PM me teamviewer id (I'm bored. Gonna fix as many people's phones as I can
http://teamviewer.com/download
Indirect said:
PM me teamviewer id (I'm bored. Gonna fix as many people's phones as I can
http://teamviewer.com/download
Click to expand...
Click to collapse
You should add the teamviewer link to your sig
Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.
Reinstalling ROM from scratch and if that doesn't work then running ARU.
EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app
thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk
This is my first post and I'm going to try my best to not break a rule. If I do, I apologize in advance.
Thread thread is a sort of, "This is how I updated my phone from 4.2.2 to 4.4.2 and rooted it but your mileage may vary."
First, thanks goes to Sunderwear for his directions on how to push KitKat to the Samsung S4 Active as well as ROOT it. I rooted my 4.2.2 phone a few months ago and didn't realize doing so would prevent OTA updates. I went to the AT&T store to have them put 4.4.2 on the phone only to be told that the store didn't have the image (or whatever they said) and couldn't put it on my phone. Instead, they put 4.3, which turned out to be great because the directions pretty much have you going back to 4.3 in order to root.
BTW, if you are uninitiated, you may want to read this glossary page.
After having root in 4.2, I knew I wanted it in 4.4.2!
For the most part, I've been hesitant to flash the phone. I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Anyway, I started in the thread above only to find that I now needed to download Odin. This, surprisingly, was difficult. I found this site (http://odindownload.com/) which I am convinced is some sort of hacked version of Odin because when I tried to install from there, my Symantic warned me. When I disabled it, the file tried to install a bunch of bloatware/spyware. It EVENTUALLY gave me Odin.
FYI, this thread was of no use. No download links.
Later on, after searching for something unrelated, I got to a "better" site. Unlike the link above, this site has a zip file compared to the bloat-ridden executable.
I learned that I had to use Odin 3.07 and NOT Odin 3.09. Odin 3.09 did not have the PDA button that would be central to me flashing the ROM to the phone.
I started my journey on the thread for the Stock AT&T Firmware Collection. I learned that the thread uses the last three characters of the build name to identify the build. For example, 4.3's build name is I537UCUBML2 but was referred to as "ML2". This was a bit confusing but I got the hang of it. I then went over to the 4.4.2 rooting thread. It was there that I read Sunderwear says that you need to downgrade to 4.3 to root 4.4. I was grateful that AT&T only updated me to 4.3!
Sunderwear's second post described how to root 4.4.2 if you had a rooted 4.3. Since I hadn't done that yet, I proceeded back to the firmware collection and found the thread to root my 4.3 phone.
I downloaded the files and loaded up the first file to flash. I made the mistake of keeping my phone plugged in while trying to put it in download mode. It was when I stumbled upon this page that gave me the clue that my phone had to be disconnected first before going into download mode.
Once done, I clicked Start and Odin flashed my phone! It took about 2-3 minutes.
The next step was to do saferoot. The thread didn't link it so here it is.
SafeRoot requires your phone to be in USB debugging mode. Directions were found by googling. You go to Settings, About Device, and click Build Number until you get a message saying you have enabled developer mode. Then go back out one screen and go into Debugging options and enable USB debugging.
One installed I rebooted the phone and everything worked...except for wifi and "some other stuff". The thread warned you about this so I didn't worry. I flashed the next file and rebooted. Updated SuperSU and everything worked!!
I verified that I had root by installing Root Checker.
All was great with 4.3! Now for what turned out to be the more agonizing part: Upgrading to 4.4.2.
Going back to the 4.4.2 rooting thread, I learned that all I needed to do was install SafeTrap to update to KitKat and then flash a couple more files. I downloaded pwnedkitkat.zip (link in the thread) and then installed SafeTrap. I presume that SafeTrap is some sort of bootstraping method of updating the firmware.
I copied the SafeTrap apk file, along with pwnedkitkat and the updated superSU zip files to my external SD card. Once everything was copied, I installed SafeTrap and then opened it. SafeTrap then offered me the option to install Recovery Mode. Once done, I restarted my phone.
I noticed a new splash screen after the Samsung splashscreen. I clicked the Menu button (left of home) to start the recovery process. I clicked "Install" and pointed it to the pwnedkitkat.zip file. This took the longest. Probably took 15 minutes but felt like an eternity. I wasn't sure if my phone bricked when the screen turned off! But upon turning it back on, it was still going.
The bar moved very slowly. But remained patient. After a long 15-20 minutes, it updated! SafeTrap gave me the option to reboot there but I followed the directions and installed SuperSU from the SD card. It was a quick install.
I restarted the phone! I was done!! Right?
My phone got stuck on the AT&T splash screen! I started to panic! What did I do wrong?!
I missed Sunderwear's step five:
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Click to expand...
Click to collapse
Goes to show you to read everything. I missed it due to the line break. I downloaded the boot.tar.md5 file and put the phone back into download mode and push it via PDA in Odin (I presume PDA. It wasn't explicit.)
After a few hours of chewing my nails and wondering if I bricked it:
http://imgur.com/a/UFg6u#F5qFTdq
So thanks to everyone! Now if I could only unbrick my Skyrocket!
Outstanding instructions! Thank you for this. I wish all the instructions were as clear and detailed as this is.
:good:
I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Click to expand...
Click to collapse
do you mean it vibrates every 2 seconds and doesn't turn on?
:good:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
jimmietilt said:
do you mean it vibrates every 2 seconds and doesn't turn on?
Click to expand...
Click to collapse
Yup. The last time I looked into this was almost two years ago. It just sits in my drawer now.
dajabec said:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
Click to expand...
Click to collapse
I think what got me was all the new terminology and unfamiliarity of flashing. Jailbreaking an iPhone (which I've done before I had an Android) is pretty simple. It's pretty much point and click. But ROMs, flashing...these all have definitions which can be a bit overwhelming, even to a technical person such as myself. I've compiled Linux kernels from scratch!
But there's something about making your phone unusable. Something that I cannot live without, especially as I'm searching for a job.
It's nerve-wracking and I especially got nervous when I was putting KitKat on since it took so long. But overall, I'm glad I did it.
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Agent. said:
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
rdh28 said:
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
rdh28 said:
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
Devo7v said:
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
Click to expand...
Click to collapse
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Agent. said:
I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
I took mine to the AT&T device support center. I called before going in and they pretty much told me it was going to be destructive. I had previously wiped my phone earlier that day in the hopes that it would receive the OTA update.
I'm not going to lie: it's nerve-wracking, but straight forward. I know sometimes it helps to have someone hold your hand while you do it. And for me, it was definitely in the camp of, "What am I going to do if my phone craps out on me?"
But like what someone else said: you can back up your settings within Keis. I didn't. I just did a wipe. I backed up my photos but that's about it. Everything else was in the cloud. The one thing I should have done was transfer my Authenticator keys to another device because I couldn't log into AWS (which does not give out backup codes like Google). I did end up switching to Authy (I can't link to it since I'm such a new user but you can find it in the Play Store) which allows you to have more than one device. It shares your secret key between devices so it's technically less secure. But I needed the flexibility in case my phone crapped out on me again.
Pro Tip: to install all your apps again, go to the Google play store on your device and click "My Apps". Long hold one of the apps and then select the check boxes of the apps you want to install.
And hey if you run into anything there's plenty of people who check this forum regularly. I've managed to root 4.2.2 , 4.3, and 4.4.2 while retaining full functionality, just from this forum...the information is out there good luck!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Click to expand...
Click to collapse
What system apps need to be reconfigured? I can't really see that many that it would take you more than 15 to 20 minutes.
Thank you guys, I need to get my phone serviced anyway as there is a yellow dot in the top left of the screen that won't go away. So if AT&T sends me a new phone I can do all of the dirty work and then transfer everything side by side from the old device. If they won't for whatever reason I will do what you guys suggested. So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Agent. said:
So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Click to expand...
Click to collapse
I personally thing this is better since if you have 4.4.2 already, you have to downgrade to 4.3, root it and then put 4.4.2 on it.
I recently rooted my HTC a few days ago. I downloaded Titanium Backup to get rid of the Sprint bloatware. Did it and everything was fine. However, a few hours ago I turned my phone off as I had a speech to deliver. Turned it back on and now it is rebooting every 15-30 seconds. Also, my text messaging is weird. I use hangouts and the messages stay on "sending" and yet apparently they are sent since I am getting replies. I am using Google Hangouts. I can still make calls and all that so I know I still have service. Any help would be greatly appreciated. Also, I DO NOT have S-Off. Just a standard root, if that helps. My guess is that I most likely uninstalled something I shouldn't have. If so, could anyone provide a stock HTC rom or app package I can flash? Is this even possible since I don't have S-Off?
Goofy317 said:
I recently rooted my HTC a few days ago. I downloaded Titanium Backup to get rid of the Sprint bloatware. Did it and everything was fine. However, a few hours ago I turned my phone off as I had a speech to deliver. Turned it back on and now it is rebooting every 15-30 seconds. Also, my text messaging is weird. I use hangouts and the messages stay on "sending" and yet apparently they are sent since I am getting replies. I am using Google Hangouts. I can still make calls and all that so I know I still have service. Any help would be greatly appreciated. Also, I DO NOT have S-Off. Just a standard root, if that helps. My guess is that I most likely uninstalled something I shouldn't have. If so, could anyone provide a stock HTC rom or app package I can flash? Is this even possible since I don't have S-Off?
Click to expand...
Click to collapse
i believe the standard messaging app is still required for texting even if hangouts is handling it. did you uninstall stock messaging? also as a rule of thumb i tend to freeze instead of uninstall the apps that way i dont have to hunt down a flash if it messes up. this is also why you always make a nandroid anytime you mess with your phone's software.
reinaldistic said:
i believe the standard messaging app is still required for texting even if hangouts is handling it. did you uninstall stock messaging? also as a rule of thumb i tend to freeze instead of uninstall the apps that way i dont have to hunt down a flash if it messes up. this is also why you always make a nandroid anytime you mess with your phone's software.
Click to expand...
Click to collapse
Nope, I did not uninstall the stock messaging app. And yeah, I forgot to do a nandroid backup. Do you know where I can find a stock ROM to flash? Do I need S-Off to flash roms?
What version of SuperSU do you have installed? I recall seeing an issue awhile back where some other folks were having reboot issues and flashing the newest version of SuperSU fixed their issue. If that doesn't fix your issue you'll need to reflash your ROM. You can take a look at the thread in the link below, also. It has stock backups that you can load and install via recovery. You can also run the RUU that's the equivalent of what you're currently running.
Stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
RUU's:
http://forum.xda-developers.com/showthread.php?t=2729173
Once you get things running again, make sure you make a backup in TWRP.
Magnum_Enforcer said:
What version of SuperSU do you have installed? I recall seeing an issue awhile back where some other folks were having reboot issues and flashing the newest version of SuperSU fixed their issue. If that doesn't fix your issue you'll need to reflash your ROM. You can take a look at the thread in the link below, also. It has stock backups that you can load and install via recovery. You can also run the RUU that's the equivalent of what you're currently running.
Stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
RUU's:
http://forum.xda-developers.com/showthread.php?t=2729173
Once you get things running again, make sure you make a backup in TWRP.
Click to expand...
Click to collapse
Wow thanks a bunch man. Quick question: Do I need S-Off to flash ROMs?
Goofy317 said:
Wow thanks a bunch man. Quick question: Do I need S-Off to flash ROMs?
Click to expand...
Click to collapse
No, but it makes life with the M8 easier. Hit the second link in my sig for more info.
Magnum_Enforcer said:
No, but it makes life with the M8 easier. Hit the second link in my sig for more info.
Click to expand...
Click to collapse
You da real MVP
Magnum_Enforcer said:
No, but it makes life with the M8 easier. Hit the second link in my sig for more info.
Click to expand...
Click to collapse
Alright man I'm not able to get the files onto my phone since, like I said, it reboots an all that. Ideally, I'd like to simply flash a 100 percent stock ROM and I just won't **** with the damn thing ever again. If you could help me with this, I'd be eternally grateful.
Goofy317 said:
Alright man I'm not able to get the files onto my phone since, like I said, it reboots an all that. Ideally, I'd like to simply flash a 100 percent stock ROM and I just won't **** with the damn thing ever again. If you could help me with this, I'd be eternally grateful.
Click to expand...
Click to collapse
I replied to your PM.
I had this happen to me as well. I just SuperSU app, got a message about updating binaries, chose to do it over TWRP and all has been good.
PartimusPrime said:
I had this happen to me as well. I just SuperSU app, got a message about updating binaries, chose to do it over TWRP and all has been good.
Click to expand...
Click to collapse
How do I do this? I managed to get the phone stable but now none of my radios are working. Cell, data, WiFi, GPS, none of them work or even turn on. Will doing what you said fix this?