Anyone else having issues with bugs after root and twrp installation?
I'm experiencing lag spikes here and there, freezing but rarely, and problems with sd card. So far all I've done to the phone is rooted it and installed twrp..
Love roots of all kinds
~N3
vizi0nz said:
Anyone else having issues with bugs after root and twrp installation?
I'm experiencing lag spikes here and there, freezing but rarely, and problems with sd card. So far all I've done to the phone is rooted it and installed twrp..
Love roots of all kinds
~N3
Click to expand...
Click to collapse
I have immediately experienced force closes often. Right after root/twrp. I also noticed there isn't a "fix permissions" option in the boot menu.
Borii said:
I have immediately experienced force closes often. Right after root/twrp. I also noticed there isn't a "fix permissions" option in the boot menu.
Click to expand...
Click to collapse
wasnt aware their was a TWRP yet....where did you get and how to install?? Thanks for any help...
rockinandroid said:
wasnt aware their was a TWRP yet....where did you get and how to install?? Thanks for any help...
Click to expand...
Click to collapse
Sorry. I get in a habit of typing TWRP for every recovery. I used CWM Recovery (http://forum.xda-developers.com/showthread.php?t=2469955)
rooted and twrp are both fine on my MI5 stock rom.
There is a known SD card issue WITH twrp but it shouldn't affect stock. Only affects when inside the TWRP recovery.
No FC on anything for me after rooting.
Did you by any chance install/restore anything through Titanium backup? If you restore anything through TB, you'll get FC's because of selinux. http://forum.xda-developers.com/showthread.php?t=2473113
Compusmurf said:
rooted and twrp are both fine on my MI5 stock rom.
There is a known SD card issue WITH twrp but it shouldn't affect stock. Only affects when inside the TWRP recovery.
No FC on anything for me after rooting.
Did you by any chance install/restore anything through Titanium backup? If you restore anything through TB, you'll get FC's because of selinux. http://forum.xda-developers.com/showthread.php?t=2473113
Click to expand...
Click to collapse
If I flash to mI5 rom, would I need to wipe everything? I've been wanting to do that since I've heard so many good reviews.. I'm assuming I'm on mI3 stock rom? I'm not sure lol.. Kinda new to this stuff
Love roots of all kinds
~N3
Related
Are there any clear benefits of one recovery over the other? I'm a fan of TeamWin but I'm comfortable with CWM... Is either recovery clearly superior?
Preference is the deciding factor.
Appreciate my help? Thank me
Not sure which one is better, but i've been using ClockworkMod 4.0.1.4 that came with Revolutionary S-OFF tool and it's worked flawlessly so far.
Do CWM work with Rom Manager
I personally like TWRP for the customization options plus the race horse is kinda cool too.
Nope...
Sent from my PG86100 using XDA App
bluediablito said:
Do CWM work with Rom Manager
Click to expand...
Click to collapse
Yes. I just updated to 4.0.1.5 with it today. Fixes charging bug while OFF with Fastboot off.
mswlogo said:
Yes. I just updated to 4.0.1.5 with it today. Fixes charging bug while OFF with Fastboot off.
Click to expand...
Click to collapse
Yep, I was curious and used rom manager to flash the recovery... worked perfect. I enjoy being able to go into rom manager and select "reboot to recovery" instead of having to hold down button combination (i know, lazy).
mswlogo said:
Yes. I just updated to 4.0.1.5 with it today. Fixes charging bug while OFF with Fastboot off.
Click to expand...
Click to collapse
How? Where?
Thank you!!!!
karikian said:
How? Where?
Thank you!!!!
Click to expand...
Click to collapse
You can just click on the first option in Rom Manager, which is "Flash ClockworkMod Recovery". That's pretty much it.
mswlogo said:
Yes. I just updated to 4.0.1.5 with it today. Fixes charging bug while OFF with Fastboot off.
Click to expand...
Click to collapse
I can confirm that 4.0.1.5 fixes the charging bug as well.
I'm a big fan of Rom Manager. I use it to organize my backups. I've used since day one of the OG Evo and never had a problem with it. If anyone is having any bugs, go into the market and download rom manager and update clockwork mod recovery. Mines working flawlessly!
I remember a long time ago, people claimed that clockwork recovery had a problem with wiping cache and dalvik cache. Is that still an issue? Thats the only reason I stopped using rom manager back in the day.
knlmwq said:
I remember a long time ago, people claimed that clockwork recovery had a problem with wiping cache and dalvik cache. Is that still an issue? Thats the only reason I stopped using rom manager back in the day.
Click to expand...
Click to collapse
It did on the OG EVO, but so far on the EVO 3D I haven't had any problems.
knlmwq said:
I remember a long time ago, people claimed that clockwork recovery had a problem with wiping cache and dalvik cache. Is that still an issue? Thats the only reason I stopped using rom manager back in the day.
Click to expand...
Click to collapse
Funny. That was just a year ago. I am not laughing at you. I am laughing with you.
Sent from a 3VO. Long live the EVO.
Im using twrp and it wrks amazing very quick and stable my fone failed to let me use cwm when i first rooted my fone
htce3d said:
Im using twrp and it wrks amazing very quick and stable my fone failed to let me use cwm when i first rooted my fone
Click to expand...
Click to collapse
Punctuation is your friend. Use it. Not just to make yourself sound more intelligent, but to help the eyes of those reading it. =D
there shouldnt be any issues when flashing the newest clockwork right? say, making a backup in the CWM that came with REVO and then trying to restore it with the newest clockwork? i feel like that is an issue simply because i made a backup of my stock rom with the newest recovery and i got the MD5 error, and i cant restore it. im doing a full backup and restore test right now, ill report back.
EDIT:alright so i was able to do a full restore with the newest clockwork. i guess i just got a bad NAND on my stock rom. and the funny thing is the same thing happend with a stock rom on my G2. what causes this damn MD5 error?
That would be appreciated by many here... Don't want to get stuck with no way to restore
PatrickHuey said:
there shouldnt be any issues when flashing the newest clockwork right? say, making a backup in the CWM that came with REVO and then trying to restore it with the newest clockwork? i feel like that is an issue simply because i made a backup of my stock rom with the newest recovery and i got the MD5 error, and i cant restore it. im doing a full backup and restore test right now, ill report back.
Click to expand...
Click to collapse
Sent by Logo the turtle
I installed TWRP, but I'd like to be able to use the CWM Rom Manger. Can I download Rom Manager from the Market, and have it install CWM over my TWRP install?
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
XAlexander_AlexanderX said:
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Phone randomly shuts down. I get a black screen and can't reboot unless I pull the battery. It usually won't fully boot unless it is plugged into a charger or PC. I had a problem with battery drain and overheating. I did S-Off and went through all of R3v3nt3ch's procedures to return to stock and reload all signed RUUs and OTAs. Then flashed TACHYON. The battery drain/overheating problem seems much better. There were no FCs at first, but they are getting more frequent. Just had one and my battery is at 80%.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
If your recovery is the "cause" of your force closes, then after you install the new recovery, you need to do a complete wipe and reinstall the ROM and setup manually... If recovery is the "cause" of your issues, it is in the flashing of the ROM that is problem, not the actual recovery itself, that is the issue.
To be honest, those issues sound more like you need to S-OFF and clean flash everything from first RUU forward... it is not the most logical approach, but it seems to work for people having "weird" issues that don't seem to have a real cause.
I just did all of that.
Thanks
Sent from my Rezound on Tachyon using xda app-developers app
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
mjones73 said:
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
Click to expand...
Click to collapse
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
REV3NT3CH said:
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
Click to expand...
Click to collapse
As far as a I know those all in one kits still run the same fastboot flash command under the covers so I don't know how that could cause an issue. It's basically a GUI that runs the commands for you, not a big fan of them because you never learn the actual commands.
I tried JB's KitKatKiller v4 and decided to go back to my previous version of NABD. I did the TWRP Recovery and attempted to restore back to NABD. It is stuck on Restoring Modem. I am not sure if I should power cycle the phone or wait. It has been on the modem portion for probably 10 minutes.
Did you ever get around this? I am having the same issue
Hmm, my phone is in this situation now. Trying to go from CM11 back to stock when I made the backup.
Never used a backup before so hoping it works, but it is just sitting at Restoring Modem for a while now..
Not sure if it restart and try again or wait.. but for how long.
EDIT: Restarted and tried again and it went through the restoring modem bit like instantly.
I had nothing but issues trying to restore with TWRP, I only use Philz now. I wonder if it's also that KitKat Killer is a NC5 ROM not NABD, that could be messing up the restore
12gage said:
I had nothing but issues trying to restore with TWRP, I only use Philz now. I wonder if it's also that KitKat Killer is a NC5 ROM not NABD, that could be messing up the restore
Click to expand...
Click to collapse
+1 I had nothing but issues trying to restore with TWRP, I only use Philz .
TWRP looks nice but performs terrible
Same thing. I had nothing but trouble with TWRP. My advice: don't rely on TWRP backups!!!
metooo said:
Same thing. I had nothing but trouble with TWRP. My advice: don't rely on TWRP backups!!!
Click to expand...
Click to collapse
That's not fair to say. I've had Philz fail more then T.W.R.P. But I'm not going to say at use them. Every1s phone is different..
I am currently rooted with TRWP recovery installed and have been testing out the CM11 Beta for the Sprint LG G3. I have experienced this HW reset twice, which was when i first installed this ROM it had trouble going through the setup process. I ended up going back to my recovery to try a reinstall which worked until tonight. There was an update for a few apps that i had installed from the play store and decided to allow them to update. The phone froze which led to the HW reset screen and gave me the option to either enter DL mode or simply reboot. I chose the reboot option to get it to my custom recovery so that no more havoc can be caused. What should i do to stop this HW reset from occurring? Any help would be greatly appreciated. Please note that i would like to continue using CM11 as my daily. Thanks.
WoodenDiamond71 said:
I am currently rooted with TRWP recovery installed and have been testing out the CM11 Beta for the Sprint LG G3. I have experienced this HW reset twice, which was when i first installed this ROM it had trouble going through the setup process. I ended up going back to my recovery to try a reinstall which worked until tonight. There was an update for a few apps that i had installed from the play store and decided to allow them to update. The phone froze which led to the HW reset screen and gave me the option to either enter DL mode or simply reboot. I chose the reboot option to get it to my custom recovery so that no more havoc can be caused. What should i do to stop this HW reset from occurring? Any help would be greatly appreciated. Please note that i would like to continue using CM11 as my daily. Thanks.
Click to expand...
Click to collapse
Since you are already in recovery, why don't you try recovering a stock backup and then clean-flashing one of the older builds instead of the same one that was giving you problems?
R2DeeTard said:
Since you are already in recovery, why don't you try recovering a stock backup and then clean-flashing one of the older builds instead of the same one that was giving you problems?
Click to expand...
Click to collapse
I have tried that already but i cant seem to find my backup. I have even renamed it to "Stock Backup" but no luck. Is there another way to return to stock rooted?
R2DeeTard said:
Since you are already in recovery, why don't you try recovering a stock backup and then clean-flashing one of the older builds instead of the same one that was giving you problems?
Click to expand...
Click to collapse
NEVERMIND! I found the stock back up. Derp...wrong SDCARD.....Derp lol
Have you tested CM12 by any chance?
WoodenDiamond71 said:
NEVERMIND! I found the stock back up. Derp...wrong SDCARD.....Derp lol
Have you tested CM12 by any chance?
Click to expand...
Click to collapse
I am running it right now. It still has its issues, but it does what I need it to do.
R2DeeTard said:
I am running it right now. It still has its issues, but it does what I need it to do.
Click to expand...
Click to collapse
Might give that one a try. Thanks for your help!