I used to have root on my optimus v. When I purchased my nexus s I decided to unroot it and try and sell it. I had a few problems unrooting due to superoneclick freezing but when I tried to get root permission in the terminal I was denied, so I figured I was unrooted. However I recently went to factory reset the phone, so it would be back to it's original state, to sell it. Well, now my phone doesn't load anything but the RA recovery I had installed when I rooted. So I tried to install the stock recovery and rom again, but it keeps giving me verification and script errors. I can't get to USB debugging mode to root it again, so I'm kind of stuck in a loop. Anyone have any advice? Very frustrating since I'm rely on this phone until my nexus s get's activated.
Well, after hours upon hours I finally got adb and fixed it. Now I'm off trying to figure out how to stop this from happening again.
Next time try disabling signature and script verification.
Sent from my LG-P509 (Optimus T) with Void Gear using XDA App
Related
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!
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.
@stifilz
I ****ed up. Badly.
A few months ago, I got an AT&T Sony Tablet P (SGPT211US/S) which I tried to root, and somewhat succeeded. KingRoot seemed to work fine, except that I couldn't actually open the damn app (it would close right after launching it). Nothing else seemed to work (I tried flashing TWRP, CWM, SuperSU and Magisk via recovery but they all gave me an error), until I found KingRoot and that sort of worked. Because I didn't have much time on my hands when I got it, I called it a day after that. Now that I do have more time, I decided to look into it a bit more (namely getting a higher firmware version) and found out about that S.onyTablet.S All in One tool, the FLASHER and some other stuff and decided to unroot the tablet and get as close to stock as possible.
Nothing really seemed to work. After just bashing myself against various commands on the various tools (neither "root" or "unroot" or any flashing option worked in the AiO tool and the FLASHER just closed itself whatever I did) and getting fed up by getting errors whenever I tried to flash anything through recovery, I decided to install a root uninstaller app and removed KingRoot with it, then I got the SuperSU app from the Play Store. That in its turn stated that the SU binary was occupied, so I decided to do a factory reset through the recovery menu. Which resulted in the tablet getting stuck in a screen with a looping AT&T logo. After that, I just can't get anywhere. I get errors whever I try to flash any updates or anything else.
I hope I can do something to eventually fix it. Preferably running Android 4.0.
So here's my recovery log, which I hope is useful to someone.
i own a sprint slate 8 aqt80 i recently rooted it with king root. and after about a week of it routed everything started freezing up on it. so i came here to see if i could find a solution and a post i had found gave me instructions on the removal of kingroot using an app called super sume. once run it needed another program to aid in the removal and the first time failed and error messages popped every second pretty much so thought my only option was to reboot into recovery and do a full wipe . so i did . attempted to install magisk in place and as i was accepting permisions for magisk in a very quick popup kingroot pops up as im pressing the approval button for magisk. wrll long story short king root made itself a sysyem app and there was no uninsyalling that without root now. ran supersume again followef instructions to a t. and it seemed like it worked after the third phase said king root was uninstalled to restart. so i did . now im stuck in boot loop usb debugging not enabled cannot find recovery for life of me . been to hp website downloaded their update.zip and have tried adb sideload numerous times and aborts somewhere between 40 & 50% evertime . plz can someone help . i dont know where else to look. it would be greatly appreciated
Don't use kingroot. Ever.
Sent from my LM-V350ULM using Tapatalk
Yeah I get that now I'm still very new at all this. I'm working on a moto e5 plus now. really having a problem decrypting seems it works faster than I can type and twrp won't stick so I have to flash Everytime I want to get into recovery.