[ROOT][S-ON/Locked BL][TUT]Simple Temproot tools for S-ON+Locked bootloader !!

Did this help ?


  • Total voters
    7

seaskyways

Senior Member
Feb 13, 2012
574
344
0
beirut
As you see in this post : http://forum.xda-developers.com/showthread.php?t=1162971 , a method to downgrade (or update) when having the error ... so the thing is Gingerbreak was patched in 2.3.5 , or other older versions so the only simple thing is to use another exploit , lets cut through into it , and please post your feedback :

For whoever wants temproot for the use of superuser , Option 1 is the only option for Locked BL+S-ON , but after finishing option 1 , your sdcard will be unmounted (mount it from settings) , and bluetooth won't work unless the phone is rebooted , which means when the root is gone , Option 1 can't allow you to flash CWM , or generally edit /system by any way , but stuff more like SetCPU , Titanium Backup , and similar root apps work ...
OPTION 1
IF you aren't seeing the # in the command prompt that is because you aren't rooted , so you have to use zergRush or Tacoroot , but zergrush is easier :
1. download the temproot.zip and extract it somewhere
2. enable USB debugging on your Wildfire S
3. go to market and download superuser ( doesn't root your phone but it may help )
4. plug your phone and run temproot
5. just watch it , if you see between the lines overseer found a path ,then it worked
6. now to make sure you gained root , try turning on bluetooth , if it did then you are not rooted , also when you open the command prompt , if you type in "adb shell" and seen # , then it worked , if you saw $ , type in the cmd "su" , it should change to # , if it didn't check your phone (superuser will ask to allow or not , just allow it)

This is what i got , please tell if it worked , because it worked for me so it should for you !
I am new to xda in posting and replying stuff , but i know how forums work , so if i asked a question of how this forum works , plz answer .

OPTION 2

I've Got feedback earlier that zergRush didn't work , then this method will state the second root option which is kinda harder and picky-er , so let's cut through into it ...

This exploit is called Tacoroot , and it is mostly used for adb shell root purposes , not for superuser purposes
1. Extract the Tacoroot simple.zip somewhere and enable USB Debugging at settings >applications>development
2. Enable USB debugging from Settings> Applications > Development
3. Now run Step1
4. After the phone reboots to recovery , press both vol + and power button in the same time until a menu of four shows up , then make sure you got reboot system is highlighted (it may not be called reboot system , but something similar) and press the power button
5. when the phone boots , run Step2
6. Redo step 4
7. Now after it boots run step3
8. That's It ! you got root ! now open up a cmd , cd to the adb directory , and type in adb shell , then su , and it should show # , which confirms the root
!
WARNING : you will have a bootloop now while you have the adb root , and if you have finished what you need with the root , to get unrooted and boot normally just run Undo .
 

Attachments

Last edited:

PeMo19946

Member
Oct 24, 2008
14
0
0
does not work for me: (

i have problem, look:

***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/boomsh, No such file or directory
running step 2...
rm failed for /data/local/tmp/sh, No such file or directory
running step 3...
397 KB/s (23056 bytes in 0.056s)
running step 4...
running step 5...

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
running step 6...
rm failed for -f, Read-only file system
mount: Operation not permitted
running step 7...
Unable to chmod /sbin: Read-only file system
running step 8...
 

seaskyways

Senior Member
Feb 13, 2012
574
344
0
beirut
Permanent root for S-off and unlocked bootloader WFS

s-off
bootloader locked ;/

i can't unlock bootloader but i have bad software

I must try tomorrow in Windows XP
hey , try removing the usb debugging and then re-enable it , it might help , also don't run temproot in cmd , just go to the folder and run it !

more over , you are s-off , meaning you can get permananet root ! go to shortfuse.org and download superoneclick ,extract it somewhere , and run superoneclick , all you have to do just click root ! and answer anything it asks you , then reboot the phone , you'll have perm root !!
EDIT : it is downloaded from http://depositfiles.com/files/n0dcxce3t
 

seaskyways

Senior Member
Feb 13, 2012
574
344
0
beirut
s-off
bootloader locked ;/

i can't unlock bootloader but i have bad software

I must try tomorrow in Windows XP
maybe i got your problem , look , when first choosing HTC sync , it might open HTC sync on the PC , so open up task manager(on PC) , and go to the processes tab , end every process that carries htc on it , then try redoing the thing !
 

seaskyways

Senior Member
Feb 13, 2012
574
344
0
beirut
are you following the instructions correctly

cuz it is a temproot that should work on any wildfire s , give your software info please , go to settings about and there find and tell me your software specifications
 

PeMo19946

Member
Oct 24, 2008
14
0
0
Android version 2.3.5
HTC Sense version 2.1
Software number 2.17.531.1

More:
Kernel version
2.6.35.10-g8409c43
[email protected] #1
Wed Nov 16 17:52:43 CST 2011

Baseband version
47.23b.35_3035H_7.53.39.11M

Build number
2.17.531.1 CL214145 release-keys
 

seaskyways

Senior Member
Feb 13, 2012
574
344
0
beirut
Oh, this is a way to give me all this work?
Tacoroot Gives you temproot access to any HTC phone , although you might not access the phone directly from the touchscreen , but you will only see a bootloop , while this loop is looooopppiinggg , you have root access through the adb shell , which will give you what is required "ROOT ACCESS" !