Develop Bugs

[Q] where'd my su go? [solved]

So heres the details. Did the unrevoked flash. Got superuser. Successful root, but wanted to flash CM6. Downloaded via Rom manager, when to reflash and got stuck in boot loader loop. Dragged and dropped eng boot loader package onto SD card from different thread (seen here: http://forum.xda-developers.com/showthread.php?t=752832). Now superuser is missing. Also, every time I reboot it reloads image from zip. Should I just remove zip from SD? Why did superuser disappear? S-off is still there. h-boot: 0.76.? Thanks for your help in advance!

Try downloading it from the market.
Sent from my PC36100 using XDA App

lol, did that, and none of my rooted apps recognize it. Rom manager said I need one in system/bin/su I tried to move via astro and root explorer but neither would let me saying it needed to be a read only file.

Remove the ZIP from your SD card, get ChainsDD's Superuser from the Market. Problem solved.

Thats the one I downloaded, however rom manager says I am not rooted and it cannot find file in system/bin/su or system/xbin/su

FIXED!!
Lol, apparently downloading from the market was the older version. I went ahead and downloaded zip file from dev original thread here:
http://forum.xda-developers.com/showthread.php?t=682828
flashed in recovery and presto chango I have my SU back.. Thanks guys!

where'd my su go?
This was ugly dude, good job on the recovery, sheez.

S-Off but not Root? Help!

i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.

djtoonjr said:
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
Click to expand...
Click to collapse
Have you tried using Rom Manager to install a recovery?

xNotta said:
Have you tried using Rom Manager to install a recovery?
Click to expand...
Click to collapse
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.

If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.

djtoonjr said:
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
Click to expand...
Click to collapse
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?

xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Click to expand...
Click to collapse
i cant get to recovery lol
i go to the bootloader, scans for a PC36IMG file but it donesnt find it, even tho the file is there! lol. maybe i shold format my sdcard. hmm.
but i scroll down to recovery, and it senss me to the default recovery, not clockwork or amen ra. the stock htc recovery. lol.

xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
Click to expand...
Click to collapse
lmfao. yeah i have S-off.

drmacinyasha said:
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
Click to expand...
Click to collapse
ive been trying dat but when it comes to the part to flash the first PC36IMG, it doesnt find it, i formatted my sdcard and trying it again.

I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.

xNotta said:
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
Click to expand...
Click to collapse
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol

djtoonjr said:
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
Click to expand...
Click to collapse
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.

t3project said:
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
Click to expand...
Click to collapse
lmfao. damn. now u tell me haha.
well i went ahead and re-rooted and got it woking now but thxs for the help.
if PC36IMG isnt getting picked up by boot loader, just format SDCARD and run it again lol

[Q] Unroot Desire Z (Regarding Recovery Image)

Hi I plan to unroot my phone for warranty purposes.
I'm using a Desire Z with
baseband: 12.28b.60.140eU_26.03.02.26_M
build: 1.34.707.5 CL273326 release-keys
I've rooted the phone using gfree method.
This is what I plan to do:
1) Restore back to stock ROM (done)
2) Restore stock recovery.
- i have extracted the recovery.img from this RUU:
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe
- Will be flashing using this guide:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
-Yet to flash that .img
3) S-on.
- Using this guide:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Turning_S-On
4) Restore factory settings.
I have extracted the .img from the RUU i mentioned. My question is whether that .img is flashable on all Desire Zs because it is the same RUU that was featured in the rooting procedure for build 1.72.
I understand that there has been a lot of unrooting threads, but none seem to deal specifically with the compatibility of the recovery image.
Any help is much appreciated.
I'm not sure that if I just skip to S-on then the custom recovery (CWM in this case) will not show up. Does it?

Can anyone help?
I just need to know whether recovery images from different Vision RUUs (except TMOUS ones) are identical and flashable on any Desire Z.
As mentioned I already have a stock recovery.img from a 1.34 RUU, but the location ID might not be the same. Are stock recovery images dependent on location IDs?

The recovery should be completely independent from the CID. If the partitioning scheme is the same (and you can check that by verifying if the sizes of the images that make up your original ROM and those of the RUU are identical) you should be fine.

Cool. I went ahead with flashing the stock recovery and sure enough my phone isn't bricked and when I boot into recovery, it is of a red triangle.
Weirdly enough ROM Manager still tells me I have CWM 2.5.1.3 though...
Guess ppl can start using that recovery.img as a stock recovery.
Thanks a thousand times!
EDIT:
I tried to S-On using the guide on the Wiki but it did not work.
So i tried using terminal emulator to do the following:
# cd /data/local
# chmod 777 gfree
# ./gfree -s on
Click to expand...
Click to collapse
sure enough when i booted into (trackpad + power button) i see it say s-on.
Am i officially 'unrooted' now?
There was supposed to be a 'sync' command after './gfree -s on', but I forgot to do it. Am I still good to go?

You're okay. The sync command makes sure the caches are written to disk, but since you are S-ON it means they were written.

so if it so happened this phone gets returned to me after warranty claims, so I just
# cd /data/local
# chmod 777 gfree
# ./gfree -s off
to turn it s-off again? Or do I need to go through running rage again?
UPDATE: Got my phone back. Had to re-root the phone all the way from running rage.

weirdly enough, although the bootloader screen shows S-on, I am still able to use shootme? This means I'm still rooted, am I right?

Yup. Remove the Superuser app and it at least shouldn't be as obvious that you're rooted

hrmm superuser doesn't seem to be removable by conventional means... I don't remember installing it either. When I push it to the phone, I pushed it to the sdcard. Now i booted the phone without the sdcard, but superuser is still there...
Do I restore factory settings instead?
EDIT: nvm, Factory reset-ed. Everything looked factory. Wish me luck.

Nice, glad everything worked out...

djfoo000, glad it all worked out for you.
I have a Bell Desire Z, like yours and wanted to do something similar. While your steps are clear, i just wanted to confirm a few points:
1. In your very first post, when you said "Restore back to stock ROM (done)" i am guessing (99% sure) you meant that you restored back the ROM which you had backed up right after you installed ClockworkMod? Or did you use some other ROM image?
2. So even after you used gfree to turn back S-ON, you still had root privileges because of Superuser. How about after you did the factory reset, which presumably removed Superuser - did you still have root privileges?
3. Would it be possible for you to upload the stock recovery img file somewhere? If not, its okay as well.
Thanks

1) Yes. That stock ROM i mentioned was of a nandroid backup that restored everything prior to flashing a ROM that restored everything including apps and an unfinished Angry Birds (haha), instead of a clean one.
2) Yeah weirdly enough ShootMe still snaps screenshots. My guess is that root access is needed to install shootme as a system app and is not required beyond that. So even after s-on, shootme continues to operate due to it already being in the system app folder.
After I factory reset-ed, superuser and terminal emulator was gone. Since I was in a hurry to return the phone to the dealer I did not bother to download terminal emulator to input the 'su' command to check for root privileges. Sorry if it did not answer your question regarding root after factory reset.
3) Here's the file I extracted:
http://www.megaupload.com/?d=K8DVSNLX
I'm not 100% sure if it'll work on other Desire Zs since mine was not a carrier branded Desire Z.
Best of luck!

Excellent. Thanks djfoo000.
Couple of more questions -
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?

lol i'm a noob user just like you. I just happen to gather enough info to do what I wanted to do.
1) I have no idea of a way to backup the stock recovery. Maybe searching the phone for a recovery.img (if there ever is one in the phone) and pull that?
2) I dunno anything about CIDs...
Might need help from other senior users from the forums.

testerman123 said:
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
Click to expand...
Click to collapse
1. There may well be a stock ROM/RUU image that you can pull that stock recovery from, as you've mentioned above. Or if not, you could always "dd" the recovery partition to back it up, though I double that will be necessary.
2. Did you mean S-OFF ? No, it won't have any impact, the factory reset won't touch the radio config partition, which is where S-OFF, SuperCID etc are stored.

Thanks djfoo000 for trying - you have been helpful.
Steviewevie, thanks for responding.
I think dd would be the answer as well, now the only question is where is the recovery located? like the "if=" parameter.
After that off to the races with CwM (and a nandroid backup of my existing firmware, of course), and a custom ROM! Steviewevie and djfoo000 - didnt notice a mention of any custom roms you guys were using. any suggestions?
Edit:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.

BUMP!! anyone?

testerman123 said:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
Click to expand...
Click to collapse
The G2 does not use raw flash, so partitions will not show up as mtd devices. You should be able to do a
# cat /proc/emmc
if you are just trying to see the partition map...

Thanks ianmcquinn! That worked great.
Got my hboot, recovery and boot backed up just in case.
The curious thing, though, is that the stock unbranded recovery from 1.34.405.5 RUU that djfoo uploaded is only 3.85MB, while my backed up recovery is 8.5MB. whats up with that?

i can confirm that when I flash the recovery.img i uploaded, the unrooting works fine. And it is 3.85MB as mentioned.

[Q] G2 HELP Bootloop with S-on

I am having an issue and although it is similar to others i haven't been able to solve it through the suggestions that others have posted
I have rooted my phone and installed CM7 and ended with an issue. I decided to unroot my phone and go back to stock. Stupid move. I am now stuck in a boot loop and the HBOOT was reflashed.
This is my set up
VISION PVT S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010, 17:59:38
Also I have CWM 3.0.2.4 Installed
I cant install a froyo image right... Due to the CWM and i cant install an unsigned gingerbread image right due to the S-ON am i stuck or is there something that i can do.
I Think That a signed gingerbread rom would work but the one post of it that i can find i can't download from for some reason.
Any Help is Awesome.

You custome recovery? You could flash a new rom on there s-off jus take sign checks in bootloader, not recovery, a simple wipe and reflash of cm 7 would brring phone bacl

ilostchild said:
You custome recovery? You could flash a new rom on there s-off jus take sign checks in bootloader, not recovery, a simple wipe and reflash of cm 7 would brring phone bacl
Click to expand...
Click to collapse
Close, but not quite. From what I've been told (haven't tested myself) but when you s-on it will say its flashing, but boot.img will not flash.
Now you could try wiping and reflashing same exact cm rom you had and is a small chance will work, but if it doesn't you can do this:
You will need a wpthis.ko specfic to whatever kernal is currently installed. You will also need adb installed and working.
put wpthis.ko in sdk folder
Have phone connected to comp.
Boot into recovery.
Goto advanced mounts and mount /data
Then type:
adb remount
adb push wpthis.ko /data/local/wpthis.ko
adb shell should bring up #
insmod /data/local/wpthis.ko (should get function not implemented error)
Then go back to advanced mounts and unmount /data
Now wipe and flash rom of choice.
Once your up and running, rerun gfree.
Good luck, let me know how it goes.

fastludeh22 said:
Close, but not quite. From what I've been told (haven't tested myself) but when you s-on it will say its flashing, but boot.img will not flash.
Now you could try wiping and reflashing same exact cm rom you had and is a small chance will work, but if it doesn't you can do this:
You will need a wpthis.ko specfic to whatever kernal is currently installed. You will also need adb installed and working.
put wpthis.ko in sdk folder
Have phone connected to comp.
Boot into recovery.
Goto advanced mounts and mount /data
Then type:
adb remount
adb push wpthis.ko /data/local/wpthis.ko
adb shell should bring up #
insmod /data/local/wpthis.ko (should get function not implemented error)
Then go back to advanced mounts and unmount /data
Now wipe and flash rom of choice.
Once your up and running, rerun gfree.
Good luck, let me know how it goes.
Click to expand...
Click to collapse
If that's true then at first attempt at root would fail and couldn't install cm at all?
Also if that's the case look in the forums how to get s-off and eng-boot on from the help guides
But if anythinf do some real good reading b4 attempting so don't hose your phone

Fixed
Thanks to all i knew that it had been posted. I ended up reflashing with the Gingerbread Official Rom Leak and it worked perfectly. Thanks to Football and ilostchild.

compgeek13 said:
Thanks to all i knew that it had been posted. I ended up reflashing with the Gingerbread Official Rom Leak and it worked perfectly. Thanks to Football and ilostchild.
Click to expand...
Click to collapse
But can you root now? I didn't suggest the offical gb because I haven't looked into if there is a root method for it.
I guess you could replace the misc.img to downgrade and re root if all else fails.
And ilostchild, I'm not understanding your question. You go s-off before ever flashing a custom rom like cm.

fastludeh22 said:
But can you root now? I didn't suggest the offical gb because I haven't looked into if there is a root method for it.
I guess you could replace the misc.img to downgrade and re root if all else fails.
And ilostchild, I'm not understanding your question. You go s-off before ever flashing a custom rom like cm.
Click to expand...
Click to collapse
there is no root or temp root for the new rom, once flashed kinda stuck on there, gignerbreak wont work either
im asking how is he running recovery/rom and still s-on i seen a few ppl with this, and im askin how he do that?

How can i root after flashing a ROM?

So here is what i did step by step:
1.Installed the Kindle Fire Utility v.0.9.6 drivers
2.Connected Kindle and waited for all drivers to install
3.Started the utility (ADB Status: online)(Boot Status: i dont remember)
4.Chose option 2 and got stuck on a "Please Wait" after the utility said it was trying to remove root checker, meanwhile my kindle was already in TWRP and stopped booting, so i figured why not just install a custom ROM, so i flashed CM10 by lithium76, the tablet edition rom, then flashed gapps.
5.When it finished i chose reboot system and it didnt reboot system it just kept going back to the Recovery so i got very scared(note: I formatted everything before flashing, dalvik, cache, factory reset, and system)
6.I kept trying to run the utility again but it would always get stuck saying that it cant rename root and telling me to wait and the phone would just stay in the recovery( i cant remember this part at all)
7. So i chose reboot and chose bootloader and held down the power button and from there chose "boot normally", it booted normally and now i'am running cm10 on the kindle
8.BUT.... i dont have root access at all, superuser is installed but i dont have root access, i tried going back to the utility but it doesnt recognize my device at all, it is always offline now.
How can i get root access now, I'am completely lost and dont know what to do, also i cant reboot from the recovery, i have to go to the bootloader and reboot normally from there.Please help me, i know i should't have done things the way i did but i wasnt thinking, i know you dont need root access for a custom rom but i think you wont have the full android experience without root, please somebody help me.

All of the ROMs here (Unless it says they don't, correct me if I'm wrong.) should give you root. I'm not sure about your problem. Er, There isn't anything I can do to help, sorry.

Jared631 said:
All of the ROMs here (Unless it says they don't, correct me if I'm wrong.) should give you root. I'm not sure about your problem. Er, There isn't anything I can do to help, sorry.
Click to expand...
Click to collapse
yeah they all should but if you dont have the root binaries installed you dont have root even if you have an apk installed.

iraiderx said:
yeah they all should but if you dont have the root binaries installed you dont have root even if you have an apk installed.
Click to expand...
Click to collapse
All custom ROMs (except maybe 2-3 you'll never use) come with Superuser.apk and the su binary already packaged in the flashable ROM.zip. Not only that, but custom recoveries like TWRP already have root access, so going through the "rooting" process only to install a custom ROM is absolutely pointless.
Who knows why you don't have root access. It could be your recovery's fault or you may have a bad ROM download (did you check the md5?). Either way you should start all over from the beginning and skip all the unnecessary steps like installing su and Superuser.apk
Access fastboot (you've done it once, so I'm sure you can figure it out)
Download custom recovery and check md5
(Re)Install custom recovery (via fastboot)
Download FFF1.4a.zip
Use recovery to flash FFF1.4a.zip (checksum is automatic)
Download a custom ROM and check md5
Transfer ROM to sdcard
Wipe System & Factory Reset
Install ROM
Reboot System
Enjoy your fully rooted ROM

soupmagnet said:
All custom ROMs (except maybe 2-3 you'll never use) come with Superuser.apk and the su binary already packaged in the flashable ROM.zip. Not only that, but custom recoveries like TWRP already have root access, so going through the "rooting" process only to install a custom ROM is absolutely pointless.
Who knows why you don't have root access. It could be your recovery's fault or you may have a bad ROM download (did you check the md5?). Either way you should start all over from the beginning and skip all the unnecessary steps like installing su and Superuser.apk
Access fastboot (you've done it once, so I'm sure you can figure it out)
Download custom recovery and check md5
(Re)Install custom recovery (via fastboot)
Download FFF1.4a.zip
Use recovery to flash FFF1.4a.zip (checksum is automatic)
Download a custom ROM and check md5
Transfer ROM to sdcard
Wipe System & Factory Reset
Install ROM
Reboot System
Enjoy your fully rooted ROM
Click to expand...
Click to collapse
Thank you so much, i didnt do extacly as you said but what it did worked! i flashed a stock rom which came with busybox and su and then went to the recovery and flashed the rom i already had in my internal storage and now i have root access