Cant remove bloatware? - Droid Incredible Q&A, Help & Troubleshooting

Seems i cant remove bloatware with titanium backup...it says the app in question is deleted, but it persists in the market and when I reboot its back. not sure what im doing wrong help is appreciated
rooted with unrevoked 3.22. s-on/ have not downgraded

I thought you needed to be s-off to remove system apps? Don't quote me on that, that's merely an assumption.

SlimSnoopOS said:
I thought you needed to be s-off to remove system apps? Don't quote me on that, that's merely an assumption.
Click to expand...
Click to collapse
You need root (su binary) and superuser app and a properly installed busybox (for mounting read-write and other tools with titanium backup). Titanium should ship with busybox tho. S-OFF just lets you flash unsigned code from HBOOT. Rezound just now got s-off but they could install custom roms and remove bloat.

it's running some weird/old superuser
try to update superuser from market - package file was not signed correctly
try to run update helper - force close
try to delete (any) apk from /system/app with root explorer get error
great. tried flashing superuser through recovery and now im stuck in bootloop. probably should have backed up with titanium when i had the chance

Shano56 said:
it's running some weird/old superuser
try to update superuser from market - package file was not signed correctly
try to run update helper - force close
try to delete (any) apk from /system/app with root explorer get error
great. tried flashing superuser through recovery and now im stuck in bootloop. probably should have backed up with titanium when i had the chance
Click to expand...
Click to collapse
Im sorry. It may have been better to let you assume s-off is required so you would back up properly.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
Im sorry. It may have been better to let you assume s-off is required so you would back up properly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah :/ anyways i did a backup from recovery to maybe save something...where does it save to?
is S-OFF needed to flash hboot and radio? or can that be done via recovery?
edit: ugh i got CM9 kang loaded and working great...only problem is i *still* cant remove system apps (movie studio, dev tools, etc) wtf

maybe try renaming the bloat .bak with root browser.

Shano56 said:
yeah :/ anyways i did a backup from recovery to maybe save something...where does it save to?
is S-OFF needed to flash hboot and radio? or can that be done via recovery?
edit: ugh i got CM9 kang loaded and working great...only problem is i *still* cant remove system apps (movie studio, dev tools, etc) wtf
Click to expand...
Click to collapse
Recovery backups save to your sdcard in a clockworkmod folder.
S-off is needed and the only way to flash hboots, radios, and splash screens. You also need s-off to flash recoveries thru hboot, but can also be done with unrevoked or rom manager.
Also you must be s-off to remove system apps, or anything from the /system folder or subdirectories, having root alone is not enough.

cmlusco said:
Recovery backups save to your sdcard in a clockworkmod folder.
S-off is needed and the only way to flash hboots, radios, and splash screens. You also need s-off to flash recoveries thru hboot, but can also be done with unrevoked or rom manager.
Also you must be s-off to remove system apps, or anything from the /system folder or subdirectories, having root alone is not enough.
Click to expand...
Click to collapse
yes I figured this out after I gained s-off and i was magically able to remove /system apps thank you

Shano56 said:
yes I figured this out after I gained s-off and i was magically able to remove /system apps thank you
Click to expand...
Click to collapse
I don't 100% buy that s-off is needed to disable/remove system apps. My understanding is that S-OFF is just at the bootloader level and would not affect system. Unless it has a deeper effect than that. Read/write access should be all that's needed and you need root for that for sure.
Just my 2cents. I could be wrong. Since it seems to be the case for you guys I may be wrong here.

tiny4579 said:
I don't 100% buy that s-off is needed to disable/remove system apps. My understanding is that S-OFF is just at the bootloader level and would not affect system. Unless it has a deeper effect than that. Read/write access should be all that's needed and you need root for that for sure.
Just my 2cents. I could be wrong. Since it seems to be the case for you guys I may be wrong here.
Click to expand...
Click to collapse
This is the case. At lease on the incredible
Sent from my HTC Incredible using Tapatalk 2

easy removal of some sys apps -"Covert to User App"
Shano56 said:
Seems i cant remove bloatware with titanium backup...it says the app in question is deleted, but it persists in the market and when I reboot its back. not sure what im doing wrong help is appreciated
rooted with unrevoked 3.22. s-on/ have not downgraded
Click to expand...
Click to collapse
I finally was able to get rid of oem swype, then reinstall swype beta through the installer. I was not able to "force remove app (by recover/exploit)", i don't know what I was doing wrong. Maybe I just don't know how to use Titanium Backup well enough.
I used Titanium Backup, went to "backup/restore", scrolled down to Swype, long hold, clicked on "convert to user app", then I was able to remove it through the "Application Manager".
I haven"t tried this with other System App but it should work. I hope this helps. Good luck.

I agree with tiny, S-off shouldn't be required to delete system apps. I understand that you switched to s-off and you saw then light but is there any chance you may have changed something else while you were changing to s-off? reflashing the su-binary? switching ROMs? updating your ROM? Many of these things can also have an effect on your superuser position in life. Most ROMs are pre-rooted which means that the su-binary is already implemented into the ROM. If you updated or switched your ROM while you were in the process of switching to s-off, it is likely that you also updated the binary and gave yourself lovely superuser permissions once again. Also note that when you update using OTA and you are using stock rooted with S-ON that your phone will lose it's superuser binary in the process of updating and you wont notice the change until the next time you try to do something that involves SU. Just a few thoughts. Glad you got it fixed

You might also poke around the TB settings. I believe there's one near the bottom that removes the market link, although it should be enabled by default.

Related

[Q] How the heck did I Unroot?

OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.
So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.
MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828
_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.
OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha
Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds

[Q] stuck at white htc evo 4g screen - not flashed anything yet

hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App
ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App
ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App
What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).
dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.
Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.

Help!!! No apps reporting root!!! :(

So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Check other apps that need root, like titanium backup. Still no root message? What ROM are you running? Did you do a full while when you flashed?
I always wipe data before restoring a NAND backup. You could try clearing data for superuser.
Superuser
Do you have the Superuser application?
The superuser app is still there just not working i guess and no app that uses root is working I don't know what to do. Will I have to re-root my device
Did you do what I suggested and do a full wipe then reinstall the backup? Did you try clearing your data for the superuser app?
MeNaCe2s0cieTy said:
So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Click to expand...
Click to collapse
It happened to me today after I had done what you did. I dont have setcpu. Titanium on my Unity said it doesnt have root. tried everything the guys mentioned here, apart from clearing the data of superuser.
Anyway I did a full wipe, with system format as well, and reflashed Virtuous Unity. All seems fine now.
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
michael_duvalle said:
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I'd sure love to have it...you never know when you get hit by another no-root issue.
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
There you go mate. This always worked for me. Flash in recovery.
mak3040 said:
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
Click to expand...
Click to collapse
Did not work for me. I lost root again when I restored a different rom.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
Worked like magic.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
i have a similar issue. i rooted my sensation using revolutionary
towards the end it kept restarting the phone and going into the boot screen, and then restarting it again. it did this about 3 times, and then it said it failed. i restarted my phone to the boot menu, and it shows s-off. i tried running the revolutionary program again to make sure, and it confirmed this.
i then got the leedroid mod and flashed that to my phone. the leedroid mod works well, just whenever i try to access superuser it crashes. i tried accessing titanium backup and adfree and when these request for permissions, i get an android notification that superuser has crashed and the request times out.
i tried using this fix, but this errors as well...
any assistance in resolving this will be greatly appreciated
thanks
hi
i had the same problem with trying some new roms and restoring nandroid.
i fixed this problem with: Rom Manager -> correct permissions -> reboot
best regards

[Q] Need EVO 4G rooting help, issue with Hboot 6.16

I have reas for hours on these forum post, nothing I have tried has worked. I have tried all the ways I could follow on here. I have an issue with the device showing an HBoot of 6.16 but the device is not rooted. The Last way I tried was with , but it gives me an error that the firmware is too new. The software is version 2.3.5. What are my options and can someone please give this elementary minded person a step by step guide how to fix this.
THANKS in advance!
Pull battery out reinsert battery then press power button +volume down. Does it say s-off and revolutionary at the top or just hboot 6.16 s-on?
Sent from my PC36100 using XDA
hboot 6.16 is the modified hboot from revolutionary. Meaning you ate rooted, you may need to do a couple more steps... Make sure you have the newest version of su binaries and superuser.
Sent from my Evo using xda premium
imheroldman said:
hboot 6.16 is the modified hboot from revolutionary. Meaning you ate rooted, you may need to do a couple more steps... Make sure you have the newest version of su binaries and superuser.
Sent from my Evo using xda premium
Click to expand...
Click to collapse
The hboot 6.16 means he might have been nand unlocked at one point. But in the process to s-on you have to flash the hex edited hboot to turn s back on then run the ruu to get 2.16 hboot back. Sometimes people are to lazy and just turn the s back on and leave the 6.16 hboot from revolutionary
Sent from my PC36100 using XDA
The s-on hboot is v6.17 so he should still be s-off which means he just needs to flash an Amon RA PC36IMG.zip and then flash su and su bin or a rooted ROM
We are legion, for we are many
more info for my problem
Here is what my phone shows
Revolutionary
Supersonic E V T 3 ship S-OFF
H-Boot 6.16.1002
Micro P-041F
Touch Panel ATMEL 224_16a b
Radio 2.15.00.12.19
March 8,2011
Thanks for the replies, and can one of you kind folks give me a step by step of what to do here as I am new at this.
Thanks again
http://forum.xda-developers.com/showthread.php?p=7226 Here is a link to the recovery Evil suggested and I would check out the stickys in development thread. Lots of helpful links. Biggest thing is read,read,read and search (i use google instead of xda search). Your bootloader is unlocked so your options are endless.
Mezmerized TSM EI20 LeanKernel ADW Launcher Antique CM theme
kimber45 said:
http://forum.xda-developers.com/showthread.php?p=7226 Here is a link to the recovery Evil suggested and I would check out the stickys in development thread. Lots of helpful links. Biggest thing is read,read,read and search (i use google instead of xda search). Your bootloader is unlocked so your options are endless.
Mezmerized TSM EI20 LeanKernel ADW Launcher Antique CM theme
Click to expand...
Click to collapse
link doesnt work...
this is what shows up in my bootloader... is the hboot 6.16 not good to use or something?
You need a recovery, your hboot is fine recovery will be renamed PC36IMG.zip placed on sd card without being in a folder then when u boot into hboot it will ask you to update volume up to accept the update this will install recovery. Next you will go to androidsu.com and download the zips for superuser-efghi and the matching su-binary-efghi, then boot into recovery make a backup just the preselected options plus wimax to start when the backup is complete back out to the menu and select wipe, in wipe clear cache and then dalvik cache, back to main menu, now select install zip from sd card, might be flash zip from sd depending on your recovery version then locate the superuser zip and install it, back out to main menu go to wipe repeat cache and dalvik wipe the back to main menu then install again now select the binary zip and install, now reboot your phone you are now rooted
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
Sorry apparently didnt work from my phone. Ill give it another shot from the pc. http://forum.xda-developers.com/showthread.php?t=705026
Another question, sorry
On the backup, do I choose Nandroid backup or do I choose baxck Google Proprietary system files??
Thanks for helping this newbie
Nand Backup
I think I am rooted??
Thanks for the help, got through the backup and all the steps you guys and evil gave me. I think I am rooted. I have this new icon that says Superuser, I guess I am lost from here, whats next??
emsdoc911 said:
Thanks for the help, got through the backup and all the steps you guys and evil gave me. I think I am rooted. I have this new icon that says Superuser, I guess I am lost from here, whats next??
Click to expand...
Click to collapse
if you have superuser download a app that needs superuser permissions like wireless tether for root users or you can explorer and start flashing roms
a little more info
When you say to start flashing roms?? tell me more. The Superuser kind of directs me to buy the elite version, but I am sure that I am just new and green to this. I saw a rooted device that allows more rows of icons on the screen, processor management, take off unwanted programs that are preinstalled. Any suggestions on these??
I guess I just need more direction, You all have been a great help.
Thank you, thank you!!
emsdoc911 said:
Thanks for the help, got through the backup and all the steps you guys and evil gave me. I think I am rooted. I have this new icon that says Superuser, I guess I am lost from here, whats next??
Click to expand...
Click to collapse
If you have superuser access i would download app Titanium Backup Root and under settings choose Batch and backup all user apps before flashing anything new. Then after u flash (a new rom) u can re-download titanium (tb) and restore your apps. A few other apps i would suggest are ES File Explorer or Root Explorer, AdFree, and my fav. Boot Manager.
---------- Post added at 08:14 PM ---------- Previous post was at 08:01 PM ----------
emsdoc911 said:
When you say to start flashing roms?? tell me more. The Superuser kind of directs me to buy the elite version, but I am sure that I am just new and green to this. I saw a rooted device that allows more rows of icons on the screen, processor management, take off unwanted programs that are preinstalled. Any suggestions on these??
I guess I just need more direction, You all have been a great help.
Thank you, thank you!!
Click to expand...
Click to collapse
I could write a book on ur questions. You should go over to the EVO 4G Development Thread and start reading. Start at the Stickies!
There is no need to buy the elite version of superuser, as far as i'm concerned. With being rooted(superuser) u can uninstall any app(program) on ur phone, but u need to be careful cause un-installing some apps will cause ur main phone functions not to work properly. Do some reading first.
I spent 2 months reading threads before i even rooted for the first time, let alone flashed a new rom.
-EViL-KoNCEPTz- said:
You need a recovery, your hboot is fine recovery will be renamed PC36IMG.zip placed on sd card without being in a folder then when u boot into hboot it will ask you to update volume up to accept the update this will install recovery. Next you will go to androidsu.com and download the zips for superuser-efghi and the matching su-binary-efghi, then boot into recovery make a backup just the preselected options plus wimax to start when the backup is complete back out to the menu and select wipe, in wipe clear cache and then dalvik cache, back to main menu, now select install zip from sd card, might be flash zip from sd depending on your recovery version then locate the superuser zip and install it, back out to main menu go to wipe repeat cache and dalvik wipe the back to main menu then install again now select the binary zip and install, now reboot your phone you are now rooted
We are legion, for we are many
Sent from my Anonymous DeathStar in the depths of GalaXy S2
Click to expand...
Click to collapse
It works perfect for me...Thanks alot...
roms
ok i had the same problem and followed all the stepps. i was rooted untill i updated my phone and was getting the hang of flashing roms and trying them out but i kinf of forgot how to do so. what are the steps i take when flashing roms. i did the nandroid back up but kind of forgot what to do when installing roms. do i clear catche and just install from sd card?
same issue
I had the same issue. hboot 6.16 revolutionary s-off but i was not rooted and on the stock recovery. i thought i was a goner because no pc36img i downloaded would flash in bootloader and ruu's wouldn't flash. I just recently started revolutionary and when i plugged my phone in revolutionary said 'you are already s-off, do you want to flash revolutionary clockwork recovery?' Once I hit Y (yes) it flashed the recovery and i was rooted again. this took a whole lot of guessing and checking so hopefully this helps someone

Re-installing su on Jelly Bean after removing it with Smelkus

Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Edit: Sorry, earlier it was in the dev section.
connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.
Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available

Categories

Resources