root problem - One (M9+) General

I rooted my phone and it worked for a couple days but later root stoped working tried to re root still nothing
Unlocked and on marshmallow

It helped me to clear the cache from TWRP recovery

Related

[Q] Recovery Question/Trouble Rooting

Yesterday I tried to root my nexus 4 and I followed a tutorial. I unlocked the bootloader and was able to flash twrp 2.6.3.0 custom recovery. However, I forgot to factory reset my device before flashing the recovery. When I got to the twrp screen it asked me for my password. I entered the one for my device but I couldn't get in. I entered it in a couple more times, but still it wasn't unlocking. I pressed the back button and I randomly got into the recovery. From there I continued the rooting process but when I tried to wipe cache or dalviks cahce it always said that It failed (never got to the point of flashing SuperSU). I then tried to wipe the system but I stilled got the failed message.I had no choice but to exit out of twrp and turn off my device and when I did, I got stuck at the nexus logo. I was able to get my device back to stock and I want to root my device but I'm not sure what went wrong. Should I try using twrp 2.6.0.0 because a lot of guides I followed used that custom recovery. Also, if I use and old recovery will I be able to update it later? I also followed this guide : http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28 so I wouldn't lose my data. I tried including as much info as possible so sorry if I wrote too much.
neogamma said:
Yesterday I tried to root my nexus 4 and I followed a tutorial. I unlocked the bootloader and was able to flash twrp 2.6.3.0 custom recovery. However, I forgot to factory reset my device before flashing the recovery. When I got to the twrp screen it asked me for my password. I entered the one for my device but I couldn't get in. I entered it in a couple more times, but still it wasn't unlocking. I pressed the back button and I randomly got into the recovery. From there I continued the rooting process but when I tried to wipe cache or dalviks cahce it always said that It failed (never got to the point of flashing SuperSU). I then tried to wipe the system but I stilled got the failed message.I had no choice but to exit out of twrp and turn off my device and when I did, I got stuck at the nexus logo. I was able to get my device back to stock and I want to root my device but I'm not sure what went wrong. Should I try using twrp 2.6.0.0 because a lot of guides I followed used that custom recovery. Also, if I use and old recovery will I be able to update it later? I also followed this guide : http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28 so I wouldn't lose my data. I tried including as much info as possible so sorry if I wrote too much.
Click to expand...
Click to collapse
Hey man,
I followed this guide. I flashed CWM instead of TWRP.
http://forum.xda-developers.com/showthread.php?t=2018179
Here is the version of Recovery I flashed:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.6-mako.img
Here is the version of SU I flashed:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Then I just followed the instructions on that post and everything seemed to work well for me

[Q] Cannot re root after 4.4.3 upgrade

Hi,
I previously had purity rom on my nexus 10. I decided to back to stock and use the xposed framework. So with 4.4.3 I flashed the stock images (manualy so it didn't wipe my sdcard partition), wiped data, cache and dalvick.
Stock 4.4.3 works fine, no issues here, but in acquiring root by flashing supersu update (both 93 and 99r3) root doesn't seem to stick. I can adb in and su from terminal, but when booting android supersu days it couldn't acquire root. I have tried other clockworkmod recovery and team win recovery so see if it was a bug with recovery, but no dice. Clockwork did occasionally say it lost root and press Yes to put it back, it did this on my nexus 5 and I still kept root.
I have even tried the universal nexus toolkit but that didn't work either. All methods I have tried have run the zip output fine, saying success.
Any ideas what's wrong. I assume I have done something wrong but can't find much information about root not working like this.
Did you try chainfire 2.00?
Link to Chainfire page
Hi,
Some time ago I've faced the same issue as you, what worked for me was using an older supersu flashable zip and after flashing it I flashed the latest. Don't know if it was placebo or something, but always worked for me .
~Lord
I did the exact same couple days ago after running Omnirom. I used this odex stock image http://forum.xda-developers.com/showthread.php?t=2529492
After the initial factory wipe I wiped dalvik,cache,data, and flashed SU after flashing the ROM but before reboot. Using latest TWRP. Hope this helps.

[Q] Problem after flashing CF-Auto Root S5 SMG900F

Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Mike130784 said:
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Click to expand...
Click to collapse
Boot to recovery, wipe the caches, reboot, see how you get on then
*Detection* said:
Boot to recovery, wipe the caches, reboot, see how you get on then
Click to expand...
Click to collapse
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Mike130784 said:
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Click to expand...
Click to collapse
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
i used Odin3-v3.07
but after flashing the root everything worked installed superSU and updated it and its binaries and installed busybox,.
it all stopped working after i went into Stock Recovery and back
id prefer not to do a factory reset Wipe,. unless i really have to to fix it ,.
im going to try reflash with the latest version then,.
i have swapped SD card to galaxy tab to put the Flashable touch recovery on the SD card, and swapped back to the phone so i could Flash the Recovery when im in stock ,.
but ill try flashing Root with latest Odin first.. thank you
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
the new odin is a bit less informative (to me as beginner)
i managed to use AP to flash the root again
all goes fine , it reboots
and its now upgrading android as it says and opening app's
then Black screen again,. i klick a button,. and it shows me again all the STOPPED msg's of all internal apps that are crashing,. litterally all apps,
what can i do ?
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
*Detection* said:
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
Click to expand...
Click to collapse
i cant fix persmission in stock recovery and flashing the philz touch recovery didnt work something about not verify signature,.
al i can do i guess is wipe data factory reset ,.but im affraid it wont fix anything
Try TWRP recovery instead
http://teamw.in/project/twrp2/229
No reason a factory reset won't fix things, worst comes to worst, flash the whole ROM again from ODIN, that will fix everything as it wipes and reinstalls the lot
Grab a stock ROM from sammobile
Thank you for all your replys mate..
I managed to get it working again by doing a factory reset in stock recovery after I flashed root with latest odin
Even tho it was my last resort there was nothing else I guess .
I'm not sure tho if this will happen again when I go back to recovery like I did when this all happend the first time while I actually want to flash a more advanced recovery then stock recovery ..
But I'll take my chances and just leave it as it is
Again thank you for your help and suggestions .
This thread could be closed
Sent from my SM-G900F using XDA Free mobile app
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
*Detection* said:
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
Click to expand...
Click to collapse
i have actually ,. i installed the TWRP u mentioned,. by taking there app from the Playstore,. and flashed the new recovery, within android and without rebooting (just in case)
im used to the old CWM thats why i first wanted the Touch recovery as its based on it,
but always open for trying new things
Thank you
Good stuff
Id say the whole entering recovery / apps crashing thing was a problem with the ODIN version you used to root, too old for Lollipop is my guess, so I wouldn't worry about entering recovery again.

[root] 900w8 boc1

Has any one successfully rooted I just rooted mine but caused full system crash
LRX21T.G900w8vlu1boc1 [TELUS]
bulldog2000 said:
Has any one successfully rooted I just rooted mine but caused full system crash
LRX21T.G900w8vlu1boc1 [TELUS]
Click to expand...
Click to collapse
G900W8 TLS here too. No problem rooting by installing TWRP and then CFAutoroot through ODIN. The version of CF for 4.4.2 works just fine on 5.
after using CF-root on first boot it went MTP application could not start rebooted cleared the cache after that I got media has stopped and a a few other system errors, I did a Factory reset and issue was resolved and root was maintained
bulldog2000 said:
after using CF-root on first boot it went MTP application could not start rebooted cleared the cache after that I got media has stopped and a a few other system errors, I did a Factory reset and issue was resolved and root was maintained
Click to expand...
Click to collapse
Kingo root works too if you're lazy...

Am I doing something wrong? I've tried to find the answer. So please delete and refe

Trying to figure this out first off here's the details of the device in question.
Sgh-i377m Canadian koodo. Running stock ROM L 5.0.1
I've rooted with cf-autoroot and then flashified to Philz 6.14 I think. Just because I've never tried it. Then rebooted wiped cache/davlik then rebooted and flashified to the latest twrp 2.8.6 with f2fs support from the optimized 9105 cyanogen mod 12 thread. Everything was solid. I upgraded root to the beta copy in chainfire's supersu thread.
I rebooted several times and was fine. I went to bed and I woke up with my phone unrooted and factory reset asking me to start from the beginning of setting up my phone. So incredibly angry I didn't believe the situation and I setup the phone over again. Then rebooted into recovery and sure as fart that you shouldn't of trusted it was the factory oem recovery. So I attempted to root again and was successful and then upgraded the phone to what flashify lists as the latest twrp for the jfltecan as 2.8.4 and then upgraded to 2.8.6 f2fs from the thread mentioned earlier and sure enough not even 20 min later after I got out of the shower it factory reset itself and installed the factory oem recovery. I made sure this time software update was disabled and rooted again. I flashified to 2.8.4 only as per flashify reporting is the latest and everything seemed fine so I thought maybe the recovery being for the 9105 as the problem. I went to eat and the problem happened again. Am I the only one experiencing this?
Am I doing something wrong ? someone please help.
Signed sincerely,
Getting pissed off of flashing the same damn thing over and over.
Thank u.

Categories

Resources