Related
Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.
Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.
Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..
Still reboots to cwm... it won't flash stock recovery. Any ideas?
xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
OP updated for the new packages from mtmichaelson
xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.
Just reinstalled busybox... got it!
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?
Hi,
I have just performed the revone s-off on my phone, then rooted it using PaulOBrien's simple method then finally flashed clockwork recovery.
Everything seemed to work fine and my phone booted perfectly.
Now i have just come to reboot it and it after trying out clockwork recovery has just been non stop boot looping. I can get into recovery fine still but im not really sure how best to proceed with the least pain possible. Im quite happy on the stock rom so dont really want to start again on the phone with a new rom if i can avoid it.
Any suggestions?
Thanks,
radeonorama said:
Hi,
I have just performed the revone s-off on my phone, then rooted it using PaulOBrien's simple method then finally flashed clockwork recovery.
Everything seemed to work fine and my phone booted perfectly.
Now i have just come to reboot it and it after trying out clockwork recovery has just been non stop boot looping. I can get into recovery fine still but im not really sure how best to proceed with the least pain possible. Im quite happy on the stock rom so dont really want to start again on the phone with a new rom if i can avoid it.
Any suggestions?
Thanks,
Click to expand...
Click to collapse
Reboot to bootloader
Connect to pc in fastboot mode
Using adb <fastboot erase cache>
Reboot.
Try and see if it works
rider5512 said:
Reboot to bootloader
Connect to pc in fastboot mode
Using adb <fastboot erase cache>
Reboot.
Try and see if it works
Click to expand...
Click to collapse
Thanks for that!
Just given it a shot and it doesnt seem to have made a difference.
Any other ideas?
radeonorama said:
Thanks for that!
Just given it a shot and it doesnt seem to have made a difference.
Any other ideas?
Click to expand...
Click to collapse
Does your phone happen to be a sprint version?
Not quite sure why you followed Paul's method as it is pretty redundant these days. All you have to do is flash the Superuser.zip from CWM for root access...
Can you still get into CWM? If so, flash this via adb sideload:
http://download.clockworkmod.com/superuser/superuser.zip
EddyOS said:
Not quite sure why you followed Paul's method as it is pretty redundant these days. All you have to do is flash the Superuser.zip from CWM for root access...
Can you still get into CWM? If so, flash this via adb sideload:
http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
I guess it seemed like a good idea at the time. Regreting it now tho! :-/
Just tried the adb sideload and all flashed fine but still now working
Any more ideas?! Feeling stupid now!
So I'm assuming CWM recognised the adb sideload and flashed the ROM file and said success afterwards? Might be worth trying CM 10.1 instead of a ROM using Aroma (seeing as it's crap and keeps crashing)
EddyOS said:
So I'm assuming CWM recognised the adb sideload and flashed the ROM file said success afterwards? Might be worth trying CM 10.1 instead of a ROM using Aroma (seeing as it's crap and keeps crashing)
Click to expand...
Click to collapse
Yeah, it all flashed fine. As for cm an aroma, you lost me a little there, im just tr to keep stock, i havent flashed an aroma rom or anything? Sorry if i have confused things somewhere.
Any more ideas?
Oh and its just a unbranded orange, not spirit. Sorry i missed your comment there tws101
I've seen one or two threads that were in the same vein as this, but no clear resolution. Every time I open SuperSU, I get the message, "The SU binary needs to be updated. Continue?" I select "Continue," and am given the message to install it normally or through TWRP/CWM. If I try through TWRP, the phone restarts into TWRP, but does nothing. If I select "Normal," I get the "Installation failed!" message. I tried uninstalling/reinstalling SuperSU, but that didn't do anything.
In a related problem, I only have root access pretty much immediately after I reboot. Only immediately after I restart the phone can I use apps like WiFi Tether or Titanium.
I'm on stock, rooted 4.1.2. Any help would be great, thanks!
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
eyeisdasteve said:
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for responding! Just to clarify, should I follow that readme file’s instructions, even though I’m already rooted and have TWRP? If simply choose “install” in TWRP and select this zip, will I have the option to just install SuperSU, or should I extract one of the following 3 zips in that file first?
SuperSU-v1.41.zip
superuser.zip
Superuser-3.2-RC3-arm-signed.zip
I assume this won’t wipe my phone, but of course, I’ll do a nandroid backup first.
Well, I went into TWRP, went to "install," and selected the whole .zip, but it didn't look like it was going to give me the option to flash just SuperSU.
Agh... I should do this stuff more often so I'm not so clueless each time I need to do stuff in recovery...
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
SuperSU
subhumanderelict said:
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
Click to expand...
Click to collapse
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
rwilcher said:
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
Click to expand...
Click to collapse
So er.. what's your problem exactly? I could try to help you out.
not updating
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
limehedd21 said:
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
Click to expand...
Click to collapse
TWRP is a recovery not a ROM. If Normal doesn't work, select the other one. Assuming you have a custom recovery (I recommend TWRP for this phone), it should restart into recovery and flash the update there.
Hello, im new here and if you can please answer me on German
My problem is when i start to update SuperSU Binary it is failing on Normal mode and TWRP is happening nothing.
When i rooted first everything was glad, but there was no button to update the Binary and when i used apps like Xmodgames it says, my root is maybe no succesfull, so i rooted again without deinstalling the SuperSU blabla. And now is nothing working, if i go in Root Checker it cant find my root. Pls Help, sry for bad Grammar etc.
still have the problem
I did the flashing of the latest su update zip on my recovery reboit and ny supersu still prompts me to update binary just like before...HELP!!
my samsung galaxy s duos 2 is not updating binary in any modes
what should i do please help me
Is there any other way to update the binary other than through TWRP or CWM. I can't for the life of me find a CWM or TWRP recovery for my Hannspree Titan.
Hey guys, I have a problem here...
I had rooted my tablet and installed SuperSU, I choose the normal mode for binary update but it said it failed. Then I tried in TWRP/CWM but it just restarted my tablet and there it stayed.
When I power it on, it just keeps restarting every 5-7 seconds and it doesn't do anything else.
What should I do?
ViperROM 1.1.0 on Sprint.
So, I everything was working fine, until I decided I wanted to put a new tweak on in the MoDaCo toolkit. I did it, and then rebooted the phone. Bootloop. Well, maybe we can just reboot it, and the bootloop will be fixed! Bootloop. Well, we can clear the cache, from TWRP and a cmd propt! Bootloop.
Now, me being the idiot that I am, I didn't keep a backup on my device. It's on my computer. So, is there a way I can get it back on the device from the off state, bootloader, or recovery? Is there a fix for this, even after clearing the cache? I guess wiping the data isn't an issue since I have the backup on my computer, but then how do I get it on the phone?
Help please, as I currently am without a phone!!!
EDIT: WAIT WAIT WAIT... I just booted up after 20 minutes of bootloop. I guess these MoDaCo mods take forever to apply! I now know that for future reference! Jeez I got freaked out! Everything seems to be working fine, but thanks to everyone for their replies if this ever actually does happen!
Bseagull said:
ViperROM 1.1.0 on Sprint.
So, I everything was working fine, until I decided I wanted to put a new tweak on in the MoDaCo toolkit. I did it, and then rebooted the phone. Bootloop. Well, maybe we can just reboot it, and the bootloop will be fixed! Bootloop. Well, we can clear the cache, from TWRP and a cmd propt! Bootloop.
Now, me being the idiot that I am, I didn't keep a backup on my device. It's on my computer. So, is there a way I can get it back on the device from the off state, bootloader, or recovery? Is there a fix for this, even after clearing the cache? I guess wiping the data isn't an issue since I have the backup on my computer, but then how do I get it on the phone?
Help please, as I currently am without a phone!!!
Click to expand...
Click to collapse
how everything was fine when THERE IS NO VIPERONE for sprint?
but anyway....hold power button and vol down so this will take you to bootloader and then you can go to recovery....can u do that?
Bseagull said:
ViperROM 1.1.0 on Sprint.
So, I everything was working fine, until I decided I wanted to put a new tweak on in the MoDaCo toolkit. I did it, and then rebooted the phone. Bootloop. Well, maybe we can just reboot it, and the bootloop will be fixed! Bootloop. Well, we can clear the cache, from TWRP and a cmd propt! Bootloop.
Now, me being the idiot that I am, I didn't keep a backup on my device. It's on my computer. So, is there a way I can get it back on the device from the off state, bootloader, or recovery? Is there a fix for this, even after clearing the cache? I guess wiping the data isn't an issue since I have the backup on my computer, but then how do I get it on the phone?
Help please, as I currently am without a phone!!!
Click to expand...
Click to collapse
I would just adb sideload/push a rom to get a working phone, once the phone is working transfer your backup from your PC into your TWRP/clockworkmod folder on your phone then restore it in recovery...
Sent from my HTC One using xda premium
99piotrek said:
how everything was fine when THERE IS NO VIPERONE for sprint?
Click to expand...
Click to collapse
I'm using ViperROM. The one for Sprint devices. There's ViperROM (Sprint) and ViperONE (Everything else).
Here's the link to the ROM if you don't believe me: http://forum.xda-developers.com/showthread.php?t=2241016
Bseagull said:
ViperROM 1.1.0 on Sprint.
So, I everything was working fine, until I decided I wanted to put a new tweak on in the MoDaCo toolkit. I did it, and then rebooted the phone. Bootloop. Well, maybe we can just reboot it, and the bootloop will be fixed! Bootloop. Well, we can clear the cache, from TWRP and a cmd propt! Bootloop.
Now, me being the idiot that I am, I didn't keep a backup on my device. It's on my computer. So, is there a way I can get it back on the device from the off state, bootloader, or recovery? Is there a fix for this, even after clearing the cache? I guess wiping the data isn't an issue since I have the backup on my computer, but then how do I get it on the phone?
Help please, as I currently am without a phone!!!
Click to expand...
Click to collapse
Did you try the steps to disable the xposed framework to get you out of the boot loop and then disable the module that caused it. From the xposed support page:
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-CWM.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
You could also create a file /data/xposed/disabled, which causes Xposed to be bypassed as well.
Try that. If no luck then you can sideload with twrp recovery from this guide:
http://forum.xda-developers.com/showthread.php?t=2325853
If you have troubles, give a shout.
Bseagull said:
I'm using ViperROM. The one for Sprint devices. There's ViperROM (Sprint) and ViperONE (Everything else).
Here's the link to the ROM if you don't believe me: http://forum.xda-developers.com/showthread.php?t=2241016
Click to expand...
Click to collapse
ok ...can you go to bootloader? and then recovery?
WAIT WAIT WAIT... I just booted up after 20 minutes of bootloop. I guess these MoDaCo mods take forever to apply! I now know that for future reference! Jeez I got freaked out!
Everything seems to be working fine, but thanks to everyone for their replies if this ever actually does happen!
Okay, so at this point I have no idea what to do, and am hoping for some help.
I was able to unlock with Sunshine via temproot with Kingroot (was on the latest stock 5.1 OTA) last night, and pretty much everything was fine. I attempted to install Supersu via TWRP, but the binaries were out of date (this was after uninstalling Kingroot from in app). After a few attemts to update (within Android and in TWRP), I attempted to uninstall SuperSU to start over, no dice, wouldn't go. After that I went rooting around TWRP (not a good idea if you're new) and used the 'Fix Permissions' feature. Not only did that not fix SuperSU, but after that all hell broke loose within the OS, with Google Play Services crashing all the time. I tried clearing the cache, updating after diabling Services, no dice. Infally I tried a Factory Restore, and that still didn't help. Tried two more times, evebn without restoring my app data, it still would crash. I attempted reflashing TWRP through ADB a couple times, but it wasn't having an effect.
Then, the really bad part, I attempted flashin in TWRP, and accidently selected BOOT instead of RECOVERY, now either one brings me to TWRP. I tried restoring to stock firmware in RSD Lite, no dice, tried running the batch file that came with the firmware, nothing, it apparently tried loading the parsechunks, but had no effect.
I can still get into both TWRP and Fastboot on the phone, and it will connect via USB (shows up as a fastboot device in adb), but other than that my phone is stuck.
Anyhelp would be VERY appeciated, I should have just left things alone.
Why not just try installing cm12.1 and see what happens?
Wonder if entering twrp needs to be done via vol down and power so to not be on the boot side... If that makes sense...
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Why not just try installing cm12.1 and see what happens?
Wonder if entering twrp needs to be done via vol down and power so to boy be on the boot side... If that makes sense...
So you've tried flashing stock ?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Tried flashing the stock frimware, and it didn't work.
Was able to find a clean copy of the boot.img from computerfrrek and it has allowed me to get back into Android, however, play services still appears to have issues.
At least the phone is operational again.
Odd problems.
I'm thinking rsd now?
Sent from my XT1254 using XDA Free mobile app
---------- Post added at 01:45 AM ---------- Previous post was at 01:45 AM ----------
You have a system directory problem it sounds a clean flash should fix it.
Sent from my XT1254 using XDA Free mobile app
Just go get one of my mofo imgs unzip it and fastboot the .img all but recovery and the big system img. Then fast boot twrp. And then you can flash my new rom that is ready to download now.
the thing that messed you up was the fix permissions. find out how to "fix"/ "undo" the fact that you hit fix permissions and then flash stock and start over
computerfreek274 said:
Just go get one of my mofo imgs unzip it and fastboot the .img all but recovery and the big system img. Then fast boot twrp. And then you can flash my new rom that is ready to download now.
Click to expand...
Click to collapse
Thanks, I ended up flashing the boot.img you uploaded yesterday and all I'm back in Android again, not just figuring out the SuperSU/GPlay Services issue, do you thing the ROM would help with that?
diabl0w said:
the thing that messed you up was the fix permissions. find out how to "fix"/ "undo" the fact that you hit fix permissions and then flash stock and start over
Click to expand...
Click to collapse
Yeah, it's a matter of fixing the damage done by the 'Fix Permissions' command now.
CtrlAltConstruct said:
Yeah, it's a matter of fixing the damage done by the 'Fix Permissions' command now.
Click to expand...
Click to collapse
I uninstalled and then reinstalled Play Services a couple times. Mostly because I had to force stop Titanium Backup after it sat for 15 minutes without completing the uninstall. For me, everything seems to be working, except my old texts didn't show up in Hangouts. I just searched around here and found a thread with all the Play Service apks and grabbed the right one from there. I'm about to try installing computerfreek's ROM, so we'll see if that does anything else for me.
Everything seems fixed after installing the ROM.
AVELLIN said:
Everything seems fixed after installing the ROM.
Click to expand...
Click to collapse
Flashed the ROM, still have issues, do you recomend uninstalling via Titanium and re-flashing?
CtrlAltConstruct said:
Flashed the ROM, still have issues, do you recomend uninstalling via Titanium and re-flashing?
Click to expand...
Click to collapse
Yeah, I'd give it a try. Mine's still going strong, got all my stuff set back up and it's smooth.