Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
This Also Seemed to Work...
My root went through fine, but after the root my "n" buttom quit working and
I wound up in almost exactly the same place as above. I got out of it by:
1) Downloaded the "acclaim_update.zip" image found in the thread about Nook 1.4.0 from SDCard above, putting that on an SDCard and the rebooting to run and load it. When it first rebooted, the "n" worked but as is typical with Android
there were "leftovers" (files, etc.) still left from the previous installs.
2) So I went in to Settings and ran the "Erase and Deregister" option which seemed to clean out the leftovers and leave everything where it should have
been.
Hope this helps someone else.
Rev
albertwertz said:
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
Click to expand...
Click to collapse
This fix worked for me as well.
I had my tablet rooted and when the ota got pushed out it broke my root. So I went back to 1.4.0 and re-rooted. But the script died halfway through and had the same symptoms listed above. Not fully rooted, but not fully unrooted either.
I had to sideload the superuser app and then unroot. Then start the root process all over again.
Unroot NT but it stops in the registration
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
andrea89 said:
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
Click to expand...
Click to collapse
Albert Wertz posted a video showing how but I'm not allowed to post outside links yet. Go to youtube and search for this video: sAASnHPn4PM
albertwertz said:
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
Click to expand...
Click to collapse
Hi Albert
sorry to be bothering you , but i know your prolly the only one that can help me with this problem i have with my nook tablet
im replying to your reply :
so regarding this , im in need of your help here , same thing happend to me , didnt have superuser and was not fully rooted or not fully unrooted , but i did as you said i sideloaded superuser and unroot off this therd you posted and still the same probleam eco worked problem , what am i doing wrong ... the superuser doesnt seem to pop up when i run unroot ... how can i make superuser work properly ?
hope to can help
- Erik
Hopefully Albert has the answer for you. He's a clever one.
If this post helped click the thanks button!
Related
Up until today, I've been rooted. Used the SuperOneClick program. It was a piece of cake.
Today, I decide to check for new software updates..Two new ones.
I updated them and now I'm running 2.2.2 and ed05. Well I'm assuming that's the problem.
Because I've been going through the process today of backing up my ROM and stuff, to flash MIUI for the first time. Well, nothing seemed to work.
I tried to backup my current ROM, but nothing happened. (Should've rebooted and come back on, like normal after 'backup current ROM' was selected and a name was entered for it; Didn't happen. )
So I figured that the new software updates unrooted my phone.
So I go back into SOC and root my phone again, but during the process, it tells me that I'm already rooted. Finishes the process and I reboot my phone, etc.
Well the Superuser app is in my list now, but none of the root-required apps are working. They all tell me that I'm not rooted. I even used Root Check to see the status. It tells me as well, that I'm not rooted.
I go back to the SOC program and UNroot. Well that was successful. I reboot, etc.
No Superuser app. So far so good. So I go BACK again and root, everything went well, except when it said an 'su' command was sent to my phone, I never got one, but I still got the Superuser app. And still, the apps tell me I'm not rooted.
Any kind of help is great. I really appreciate all the time, spent reading this.
Sorry if I went on and on, but it's bugging me now and I really need some answers to what the problem might be. Thanks, guys. ;(
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
SOC does work with ED05.. I've used it several times, different phones.
Really? I thought quite a few folks were having trouble with soc after the ota ed05 update? If thats the case, then thanks for the clarification... although odin is still another option for the op since soc is not working.
droidstyle said:
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
Click to expand...
Click to collapse
I read most of the first page on that thread, mostly just read the latest replies about that method. I'll read the full directional tutorial once I'm clarified of questions.
I think I read a couple of users saying this does root your phone, but it will wipe all data as well? I'm not quite sure. I want my phone rooted, no matter if I install MIUI or not. I don't want a factory reset though.
Thanks droidstyle, I'm back to being rooted!
Now onward to flashing MIUI! Wish me luck.
:^)
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
lysdexik said:
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
Click to expand...
Click to collapse
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Fracta1 said:
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Click to expand...
Click to collapse
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
lysdexik said:
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
Click to expand...
Click to collapse
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Fracta1 said:
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Click to expand...
Click to collapse
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
lysdexik said:
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
Click to expand...
Click to collapse
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Fracta1 said:
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Click to expand...
Click to collapse
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
lysdexik said:
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
Click to expand...
Click to collapse
Yeah... Sorry about your luck
You could try sending it into Verizon still. They may fix it. Perhaps not for free. Even if not at all, at least it's just a side project?
That's about all I can think of :/
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Regain root access after JB update
weakenfalls said:
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Click to expand...
Click to collapse
I lost root on my TF201 after flashing Craig Gomez's us-tf201-jro03c-10.4.2.15-stock-deodexed.zip ROM. In addition to losing root access, I still had Superuser installed, and it would not grant superuser permission to anything I was trying to use to fix the problem, such as Voodoo OTA Rootkeeper, GooManager, etc. Also, Superuser did not even have superuser permission, but could not be deleted in the File Manager. Another big problem is that I could not boot into recovery, and I could not downgrade to ICS.
After trying a number of possible solutions that I found on this and other sites, I discovered Urkel's Fresh Start 1.0.zip. Here's the post:
<http://forum.xda-developers.com/showthread.php?p=32677560>
If you are at a dead end, I highly recommend that you give this a try! Your bootloader needs to be unlocked, but I had already done that when I was still using ICS. I'm not sure if the unlock tool available on the Asus site will work with JB. All you have to do is download the Urkel's Fresh Start zip file to your computer, unzip it to the same folder on your computer where you have adb and fastboot, add the JB ROM that you want to use to that folder, and rename the ROM file to system.blob. You'll also need to install the drivers on your computer so that it can send data to your TF201. I used the drivers that are on the Microsoft site, but there is a link to some universal drivers in the post above. Connect the cable from your TF201 to a USB port on your computer, and after deciding which option you want to try, double click Fresh Root.bat or Fresh Start.bat. Fresh Start.bat will first install the TWRP 2.2.2.1 recovery (that's what recovery.blob is). It will then install whatever JB ROM you decided to use. I went with the 10.4.2.15 ROM that's now on the ASUS site. The Urkel batch file may then restore root access, but that didn't work for some reason in my case. I think my problem was not mounting \System. You can do this by booting into TWRP recovery that you now have, select the Mount button, and put an X in the top box. In my case it seems that the box becomes unchecked during reboot. I tried it several times and gave up, but there is another simple way to regain root access if you have made it this far. Download Superuser-3.2-arm-signed.zip and flash that using TWRP, and you will at long last have root access once again. I see that this file has already been mentioned in this thread, and it worked like a charm for me.
So why did I want root access to being with? It's because of that stupid GPS problem. GPS isn't really needed on a pad in my opinion, but things like that bug me (pardon the pun)! When I was still using ICS, I unlocked the bootloader, rooted, and then used GooManager to flash TF201_External_GPS.zip. This file allowed the GPS function in my TF201 to work just as well as the GPS in my Samsung Galaxy S2. Also, I see no change when I attach the GPS dongle. What does that tell you? I think for most people with the GPS problem, it's a FIRMWARE problem, not a hardware problem. I'm not having a wifi problem, but I suspect that this is also a firmware problem. If Asus is smart, they have someone reading these blogs to get some ideas on how to fix their problems. Instead, they've spent money sending people a GPS dongle that, at least in some cases, is just a waste of time and money. So I've reinstalled the GPS zip file, and my GPS works...so now Google Maps can tell me where I am. Thanks, I already know that most of the time. Another thing that seemed to help with the GPS problem...disable the stock browser and use the Dolphin browser instead. I have no idea why that should make a difference.
Since I am a noob (whatever man), I tried to spell this out so that it can be easily understood by other noobs. Good luck, hope this works for you.
weakenfalls said:
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
Click to expand...
Click to collapse
Read this thread : http://forum.xda-developers.com/showthread.php?t=1911261 . It gives you two ways to try and get su/root back and working properly.
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Reroot I had no problems
Sent from my LT28i using xda app-developers app
defsix said:
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Click to expand...
Click to collapse
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
So do you think I could delete one of the systems?
I will stick it out until the next version is out if it's too much hassle.
Sent from my LT26i using XDA Premium HD app
Check out the all in one tool v5 when it comes out tonight my guess is itll fix ure problem!!
Sent from my LT28i using xda app-developers app
Will try at the wknd.
Sent from my LT26i using XDA Premium HD app
stifilz said:
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
Click to expand...
Click to collapse
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
[email protected] said:
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
Click to expand...
Click to collapse
Use AIO tool. 'Rescue back-door'. Then manually flash the file through recovery. Zip file link in signature and a FAQ including how to flash from recovery.
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
[email protected] said:
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
Click to expand...
Click to collapse
So after a few more days messing with this i'm still stuck. I booted into recovery , performed a factory rest, rebooted and did it again. Then I re-installed a full install of R5 , rebooted, factory reset. When I first boot I have (IRC) 30 apps, powercycle again I have 33 (IRC) apps, it appears I have extra ones that only appear in the vendor directory, again IRC. So rooted both partitions , double booting each time AIO said it was rebooting, I had root on both sides, however certain apps when started on the different partition were losing their settings. So with Root Explorer I decided to do a little trimming on one partition, I deleted the vendor and system folders and the tablet rebooted. So now I have one dead partition and one good. The good one works fine and is rooted, when I reboot it gets stuck in a boot loop at the Sony logo, press and hold the power button for a few secs and it reboots again , apps and settings unaffected.
So how do I have 2 partitions and how do i delete one ?
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
terrorist96 said:
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
Click to expand...
Click to collapse
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Hey, I PMed you.
Try uninstalling superuser and installing either supersu or the other superuser.
Sent from my HTC6435LVW using xda app-developers app
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
terrorist96 said:
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
Click to expand...
Click to collapse
I got your PM. I'll pick your brain about the ideal setup for your needs and how you use the DNA via gtalk. Then we'll make a plan of attack and you can update the thread with your solutions opinions etc.
As long as your opinion of me is good. Otherwise, it's prohibited. I have a green title and seniority rules
HTC EVO CyanogenMod Cant use BEATS AUDIO
CharliesTheMan said:
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Click to expand...
Click to collapse
I need help with rooting my HTC EVO to stock or CyanogenMod. With CyanogenMod my phone will not play audio/BEATS or will not open
PLAYSTORE.
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
cyaclone said:
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
Click to expand...
Click to collapse
Best to post such things in your device specific forum.
This forum is for the Droid DNA.
However, gaining root is as simple as downloading the latest SuperSu zip and flashing it in recovery.
Very simple to do on any rom.