I have my N7 on bone stock, rooted with superSU 1.60 installed. I flashed the .zip made by Chainfire, and no matter the recovery CWM non-touch , CWM, or TWRP after making a backup , I hit reboot system, and I get this message every time.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I've selecting option 1 multiple times and I still get the same message after a backup ,and before rebooting!! Root access works fine on all my apps and everything else I'm just curious as to why I'm seeing this via any recovery thanks. I'm sure its silly and an easy fix.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Try v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Jewveeski said:
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done this, i disable auto-update, flashed the v1.55 in CWM and rebooted. Now i cant use SuperSU anymore? tells me i have to update binaries. And i know that if i do the "root access possbibly lost" error comes again? any solutions?
In settings there is an option for reinstall as seen in the pic below click that then reboot your device , then reboot to recovery flash version v1.55 and make sure you still have the auto update feature in the play store unchecked. See if that works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Same issue on a Galaxy Nexus running 4.3 stock rooted... SU requires an update and then the recovery thinks root has been lost (this is not actually the case)... any ideas?
lost root and twrp
so i first discovered i lost root when it said no binary found then when i was going into twrp to reflash the zip all i get is a dead android on its back with a red triangle hovering over it. Went back into adb and flash recovery twrp.img and it says successful but i still get the same thing. any one know the correct thread to point me to? ive looked but cant find this problem. my device boots fine and i can get to the boot loader just not recovery.
Same thing happens with my Nexus 4, I always hit No because it says root may have been lost even if I just enter CWM without flashing any rom or doing any action but rebooting to system
Jewveeski said:
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same message on my SGS4 with stock Android 4.3 and SuperSU v1.80.
Same message with my GT-i9300, CWM 6.0.4.4 Touch (i've tried also with CWM 6.0.4.3 NO Touch) and SuperSU v.1.80
I have the same problem too on my Galaxy Nexus GSM 4.3 build JWR66Y with SuperSu by Chainfire v1.8.6 and CWM Touch Recovery v6.0.4.3
Is there a solution?
Thanks in advance
Happy Holidays and Merry Christmas
Same message, S4 mini GT-I9195 4.3 su 1.86
Same message here...
I am running CM 10.2 with CWM Touch and SuperSUv1.86
Is this a big problem?
I think CWM should work just fine regardless of this message right?
If anyone has truly found a "recent" fix please let us know.
Oh i tried reinstalling CWM Touch and that did not fix the problem..
Thank you all for your time and assistance.
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
kamikaze702k said:
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
Click to expand...
Click to collapse
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
droidshadow said:
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
Click to expand...
Click to collapse
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
maybe we should switch to TWRP?...
kamikaze702k said:
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
Click to expand...
Click to collapse
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
droidshadow said:
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
Click to expand...
Click to collapse
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
TWRP is the way to go!
kamikaze702k said:
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
Click to expand...
Click to collapse
So i just switched my Verizon SGS3 (d2vzw) from CWM Touch to TWRP Touch 2.6.31 and i go to error message/warning about the SU binary being corrupted. This seems to be just an isolated incident with CWM and Android ROM's running 4.3+
With all of the work I have been doing with my Nexus 7 FLO + TWRP Recovery I decided to go ahead and switch my phone to TWRP. It was kind of hard to switch because I started out with CWM but I have just quickly become such a fan of TWRP.
If you don't want to wait for CWM to fix this issue which i am sure they will in their next update try out TWRP i think you will like it!
If you want an easy way to install TWRP recovery manager use the app "GooManager" from the Google Play store and use the your menu button on your phone and choose the open install open recovery script.
Or you could just as easily download the recovery image file from the official TWRP website and flash it with the app flashify.
Don't you just love technology!?
-droidshadow
Related
Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??
forwardbias said:
Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??
Click to expand...
Click to collapse
Ok so I found some CWM tars that they they're v.6+ that I can get installed (at least I assume so since Odin says it worked) but when I get in there the version listed at the top is 5.5.0.4, should this number not match? I haven't even gotten around to trying to get it to install CM10 yet.
I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium
defnow said:
I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
By Rom Manager you are talking about the App you use from within the OS? So would I need root for this?
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium
defnow said:
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Awesome suggestion! Worked perfectly thank you!!
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium
nevetsgtI9100 said:
Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Get twrp does the same exact thing but a better ui and everything!!! Install goo manager and just choose a random rom to flash (you dont really have to flash the rom) its just so it prompts you to ask if you have a custom recovery say no and it will install twrp! Trust me on this one TWRP is one flawless custom recovery and always seems to work with me
Hey thanks for that reply. Just a couple of questions. I went ahead and installed twrp recovery and you're right its very easy to use. I tried flashing cm10 stable (at&t) on Rogers sg3 and I keep getting error 7. I factory reset the phone just like I would have with cwm.
Also, while in twrp when I select browse all compatible rims nothing comes up.
Any ideas?
Thanks again.
Sent from my SGH-I747M using xda premium
nevetsgtI9100 said:
Hey thanks for that reply. Just a couple of questions. I went ahead and installed twrp recovery and you're right its very easy to use. I tried flashing cm10 stable (at&t) on Rogers sg3 and I keep getting error 7. I factory reset the phone just like I would have with cwm.
Also, while in twrp when I select browse all compatible rims nothing comes up.
Any ideas?
Thanks again.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Wierd. CM10 always says Cwm is the only one that works to flash its rom .. but its wierd cuz i flashed cm10 perfectly with twrp many times before
Heres a thread to fix your error 7 though.. http://forum.xda-developers.com/showthread.php?t=1932975
Did you install ROM Manager from the market (Play Store)? EDIT: Just re-read your OP stating that you did a fresh install. At any rate, it should work fine, there is an option to select the AT&T version of the S3 (see attached screen shot).
TWRP is good too, I'm just more accustomed to cwm so I tend to stick with it.
nevetsgtI9100 said:
Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I had the same issue as you. I'm on a Rogers GS3 and the S3 ATT wasn't showing up in the Rom Manager menu.
I installed CWM using this toolkit: http://forum.xda-developers.com/showthread.php?t=1746665
I then had to update CWM to a more current version using these instructions: http://andr0idtech.blogspot.ca/2012/09/how-to-install-latest-clockworkmod.html
Once I updated CWM I was able to flash CM10 with no problems.
skrambled said:
Did you install ROM Manager from the market (Play Store)? EDIT: Just re-read your OP stating that you did a fresh install. At any rate, it should work fine, there is an option to select the AT&T version of the S3 (see attached screen shot).
TWRP is good too, I'm just more accustomed to cwm so I tend to stick with it.
Click to expand...
Click to collapse
That is weird!
The "S3 (AT&T)" shows up in your screenshot but it is nowhere in sight on my copy of CWM... (Bell S3)
I am running ROM Manager Premium v5.0.2.4 (current version, no?) and yet, the phone model list skips from the "Samsung Galaxy S Blaze 4G", to the "Samsung Galaxy S3 (MetroPCS)" and then on to the "Samsung Skyrocket"...
Could this be a regional lock sort of thing? or maybe CWM differentiates between the i747 and the i747m ? Either way, it is NOT showing up in the list...
Any thoughts??
kirkenshrir said:
That is weird!
The "S3 (AT&T)" shows up in your screenshot but it is nowhere in sight on my copy of CWM... (Bell S3)
I am running ROM Manager Premium v5.0.2.4 (current version, no?) and yet, the phone model list skips from the "Samsung Galaxy S Blaze 4G", to the "Samsung Galaxy S3 (MetroPCS)" and then on to the "Samsung Skyrocket"...
Could this be a regional lock sort of thing? or maybe CWM differentiates between the i747 and the i747m ? Either way, it is NOT showing up in the list...
Any thoughts??
Click to expand...
Click to collapse
If you really want cwm use this toolkit http://forum.xda-developers.com/showthread.php?t=1746665 Only for your att Galaxy s III though make sure its the right device that you flash it on !!!!
Well after ALOT of trial and error(which thankfully did not result in a bricked phone) and the helpful comments I finally got CM10 intalled!
Thank you for all the help and comments!
Steve
Cm10 has a check in it that looks for d2att, doesn't it? I think that's why you guys get that error when flashing.
Sent from my SGH-I747 using xda app-developers app
Only issue I have had with cwm is that fix permissions doesnt work. It just sits on it saying fixing for forever.
Sent from my A510 using Tapatalk 2
Hi all,
l tried to install DN3 v4 on my n7100 several times now, following exact instructions, but I always got stuck on this error: "Expecting 5 args got only 3". The installation is aborted at that point and the device is stuck in a bootloop . Only thing I can do is install stock rom using Odin , not really what I want.
Anyone else encountered this problem? Anyone knowing a solution? I would really like to use the wonderful DN3 rom, so if anyone has any idea how I can fix this, please... I would be very grateful...
Thanks in advance,
RuVaSky
Just read in another thread someone had a similar problem (on another device) and the issue would be related to Philz Recovery, not to the rom. He fixed the problem using twrp instead of Philz.
Don't know if that would be the solution for my problem too, I will give it a try and post the results as an update of this thread, so if anyone else would encounter the same problem they can find the solution here...
RuVaSky
(Belgium)
Sent from my SM-P600 with Tapatalk 4
My devices:
SM-P600 running stock Android 4.3
N7100 running stock Android 4.3
N8000 running stock Android 4.1.2
I9100 running stock Android 4.1.2
You can try this:
Download the ROM again
Get LATEST Philz recovery
Now after you do the full wipe in philz, go to install section and take off the x from the option says "verify something (can't remember the option name).
Then install the DN3 ROM from sdcard/extsdcard
Reboot
I think should work hopefully
Sent from my Galaxy Note II using Tapatalk
I did already try with latest version of Philz, but with the same results,
Now I used TWRP instead and after a few times it all worked out fine. So I really have to conclude the problem was indeed with the recovery. No idea why, but it seems I'm not the only one who experienced this.
So in the future I will always use TWRP instead of Philz... But I'm fed up for a while now, it will take some time before I will change my rom again ...?
RuVaSky
(Belgium)
Sent from my SM-P600 with Tapatalk 4
My devices:
SM-P600 running stock Android 4.3
N7100 running stock Android 4.3
N8000 running stock Android 4.1.2
I9100 running stock Android 4.1.2
Use PhilZ recovery and uncheck "Don't Allow Old Update Binary" under "Install Zip"
I've had the same problem with TWRP,
Hi guys, I have a problem flashing the Release Candidate ( RC)dn3rom, as it always got stocked at the first booting animation. I'm on v4.1beta2. I've search, red and followed almost all instructions b4 posting this.
Here are some things I've done,
I've flash rom with twrp v2.7.0, and wiped all except ext sd,
I also flashed the rom with Philz recovery v6.19, and I went further to flash my bootloader to mj5 according to the instructions I red at the Opening Page but still all to no avail.
I believe I should be able to install this rom successful by the help of the great E-TEAM and her families.
So guyz, PLEASE, what else can I do?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Can someone pls help me out
Sent from my GT-N7100 using XDA Premium 4 mobile app
Try latest philz version from here
http://goo.im/devs/philz_touch/CWM_A...25.0-n7100.zip
or with same version 6.19,
uncheck "Don't Allow Old Update Binary" under "Install Zip"
Clean wipe, clear cache and dalivk and flash,
joshjk said:
Try latest philz version from here
http://goo.im/devs/philz_touch/CWM_A...25.0-n7100.zip
or with same version 6.19,
uncheck "Don't Allow Old Update Binary" under "Install Zip"
Clean wipe, clear cache and dalivk and flash,
Click to expand...
Click to collapse
Thanks for ur effort to help, I flashed the rom this time with twrp v2.6.3 instead of v2.7 and everything works just fine. I guess the problem is with the version of recovery.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hello everyone, I've had and rooted a plethora of Android devices but none have given me as much trouble as the S3, I have tried every sprint method that there is all to no avail. I tried CF-Auto-Root, nothing, tried downloading SuperSU after using that, says no SU binary. I tried every option in the Android toolkit, and nada. I looked all over for a Rooted Restore cause thats what always saved me forever ago on the S2 but there's none for that. I'm running out of options, I'm on 4.3 MK3 and I could deff use some help please!
NOTE: On the Android toolkit, the process doesn't work because when it flashes TWRP and it boots to recovery the toolkit says "Recovery mode not detected", and when I check device manager it shows SPH-L710 with a yellow ! mark, I've already installed the Samsung USB drivers, I tried Kies, and even the PDANet drivers, none work for the device when its in recovery mode.
Flash the latest philz recovery via Desktop Odin, it will ask you if you want to root the phone when you reboot it, tell it yes, then update superuser through the play store
Sent from my SPH-L710 using Tapatalk 2
mattzeller said:
Flash the latest philz recovery via Desktop Odin, it will ask you if you want to root the phone when you reboot it, tell it yes, then update superuser through the play store
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Oh my god thank you so much, it worked like a gem! That should be the main root method, not CF-Auto-Root, that was a breeze AND gives you custom recovery!
If you could answer one more question for me that'd be great, I hate sounding so picky, and it's honestly no problem if there's no fix, I just have major OCD, when I boot to recovery and it shows the Cyanogenmod guy, is there anyway I can change/remove that? It bugs me cause I don't have CM or CWM so it seems very out of place.
Giston141 said:
when I boot to recovery and it shows the Cyanogenmod guy, is there anyway I can change/remove that? It bugs me cause I don't have CM or CWM so it seems very out of place.
Click to expand...
Click to collapse
I don't think you can change it, unless you were compiling a version of it yourself, but you would need to ask the dev for philz about how to go about that.
Sent from my SPH-L710 using Tapatalk 2
mattzeller said:
I don't think you can change it, unless you were compiling a version of it yourself, but you would need to ask the dev for philz about how to go about that.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
It's not a Philz thing tho, no matter what custom recovery you have, CWM, Philz, TWRP, it's always got the CM guy, Cid I think his name is? If you could change the boot screen you should be able to change that right?
Giston141 said:
It's not a Philz thing tho, no matter what custom recovery you have, CWM, Philz, TWRP, it's always got the CM guy, Cid I think his name is? If you could change the boot screen you should be able to change that right?
Click to expand...
Click to collapse
No clue, I only see it when I boot into recovery, so I rarely see it
Sent from my SPH-L710 using Tapatalk 2