Related
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Anyone got any ideas?
I even installed fresh, LeeDroid last night and still it wont let me select OK to go in to ROM Manager?
Maybe something on my SD card?
CodeJACK said:
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Click to expand...
Click to collapse
You are better off without the latest version of CWM if you have no plans of flashing CM7.
Damn, I just purchased the full Rom Manager in the hope that it would work.
What a waste of 4 Euro.
So I guess I wanted it for the ease of ability to manage ROM's as i use my phone more as a gadget rather than a phone. I like messing with all the great work chefs produce
Ill continue to flash via clockwork recovery and continue to upgrade clockwork recovery with the SDK.
I have a 16Gb Class 10 card on the way so when it arrives, ill do a full wipe and flash with a blank card to see what i get.
Any other suggestions greatly appreciated.
Going to bring this post back up as i was wondering if anyone had anything similar since?
I have gone totally back to stock now and done a fresh root and Eng and radio s-off but still Rom Manager opens but wont let me slect OK to continue.
I think its almost cetainly related to root access as I'm not able to choose allow when apps pop up requesting root. i have to deny them, close the app, then swap them to allow in Superuser and then run them again!
This is a real pain in my ass at the moment.
Is your superuser the latest version?
Yeah, have tried both the one in ChainsDD's thread which I know is very old.
Also tried the patched version that works properly with the later froyo build.
Have tried flashing LeeDroid and Revolution ROM's but still the same problem persists.
I went back to stock today, thinking it might have been a step i missed/screwed up. Still this problem persists.
I'm stumped. Could it be some hardware issue?
Well Damn crap n balls to it anyway!
Turns out after all this time, all I had to do was touch the search button at the bottom right of my HD to bypass the disclaimer of Rom manager.
I feel so dumb now. Still having issue with superuser allow button but I can work around that for now.
Sent from my Desire HD using XDA Premium App
I think the problems started ever since I rooted the device. That's the only thing I can think of. I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Is it possible the root made my system unstable? What do you guys suggest I do to try and fix this problem?
Thanks
Sent from my GT-N5110 using xda app-developers app
have you tried un-rooting? Anytime you mess with the system it has the potential to make it unstable.
Sent from my GT-N5110 using Tapatalk HD
I installed software on mine which changes color balance and runs as a service.
When it was running, the device crashed occasionally.
Once I uninstalled it, the behavior stopped.
Rooting probably doesn't create a problem, but try uninstalling any software you've added, then stepwise walk through adding in apps.
I've also seen some apps create lockups for the camera app.
theraker007 said:
I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Click to expand...
Click to collapse
Then why did you root? Just waiting for the development to come around?
I'm rooted and haven't seen this issue. Its rebooted once, maybe twice on its own in the 2 weeks or so since rooting.
Yeah I thought we'd have custom roms by now. How do I safely uproot and get back to factory. I would like to wipe everything and start from scratch
SuperSU
Using framaroot.apk with Aragorn exploit, I noticed that the SuperSU option is more stable that Superuser.
I ran into problems with my first Note 8 after I installed XMBC. It would lock up within 10 seconds or so of reboot. I would highly recommend that you take advantage of the root toolkit in this forum, install CWM recovery and make a full backup once you get it behaving again. It is good to have something to go back to if you have unexpected problems!
EDIT: You can flash back a stock image using the toolkit: http://forum.xda-developers.com/showthread.php?t=2251033
well i dont know what the heck is going wrong with the toolkit, but i did everything correctly, installed all the drivers, serial # shows up in the toolkit, checked off developer debugging mode. I tried to flash CWM from toolkit in PDA and everytime i try to go to recovery it just has the stock recovery there not CWM.
Hello all, my First post so please bear with me, Been using these forums for quite a while and all answers have been allready given, so no need to post... till now.
I have a Samsung Galaxy s3 i747 running android 4.1.2 OTA update and used CF-Autoroot. No problems there,
installed Rom manager, and cwm recovery touch. no problem
When I restart in recovery mode, also everything seems fine...
When I try to backup the phone however using cwm recovery it starts backing up everything including system but the just as it starts data the phone restarts.
Tried reinstalling cwm over and over different versions.. nada same result..
went into the settings to mount the various options as suggested to another user. same problem nada...
To be completely clear, I am trying to make a backup of my stock / rooted only Galaxy s3 i747 onto it's own storage NOT SDcard.
as I also could not figure that out either.
Any help would be greatly appreciated. -Erdericks1976
Sorry about misleading Subject. This is about making my first backup successfully..
Followup.
Well seems there are/were more problems here than I thought, it has begun randomly? restarting,..
Well. not Ramdomly. Whem specific apps are run it would restart.
I did a titanium backup and it would backup alot of the apps. but them would restart the phone when it got to 1 specific app.
I think I figured out what I did wrong here.
I have a Galaxy Note 2, and I may have flashed something from it by mistake......
so I have restarted my Gs3 From scratch Re-Following all instructions.. waiting to test and see if CWM works to back it up now..
It sure was faster with the Note2 rooted Kernel though. (if that was in fact what happend)
I'll update soon as its done..
Followup 2
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Erdericks1976 said:
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Click to expand...
Click to collapse
good for you, yu got it solved fast and easier than expected, XDA is your place for Android and root but also every kind of OS there is
anywz am not that old in XDA i joined in April and officially started rooting and modifying my phone since May and it has been great, bricked my phone 1st time but all in all i got the S3 in case for the loss. yu'll get used to this place and ROOT/custom roms
I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik
metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.
I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!