• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root super user with no root access

also in the superuser app both "-rwxr-xr-x" and "rootshell" have always been highlighted red.

and /system/bin/su is highlighted green
 
@grashan why don't you just flash a rooted rom? It is by far the easiest if you already have cwm.
 
ah, sorry, just read through the entire post. Have you tried this on a different computer? If the machine is old it may have usb 1.1 ports and i vaguely remember junkie having a problem with those. Even if it's a newer machine it might help to start with a clean slate.
 
it sounds like you are somewhere in the middle of the root process without having root. you should be able to type su in terminal emulator and you should get the superuser popup asking for root permissions.
 
also in the superuser app both "-rwxr-xr-x" and "rootshell" have always been highlighted red.

and /system/bin/su is highlighted green

they should all be green. try "tap to check for updates". prolly won't work but it's worth a shot.
 
k ive updated my modular tool to HOPEFULLY work right, dont see why it wouldnt work at this point. but at the same time how you could have gotten the su binary or superuser.apk without root in the first place is beyond me. that would require root privlidges
 
just wyi, i fixed two potential problems, one i dont think is a problem because it got as far as it did but who the hell knows... the other is that instead of using file names in the push command it used .s so i changed that. other than that i have no idea why it would get stuck pushing busybox unless there is something seriously wrong with your tmp partition
 
how long ago was the update because i tried three days ago using the very first aio tool at the top of the page in yourlink for the root, unroot tool
 
how long ago was the update because i tried three days ago using the very first aio tool at the top of the page in yourlink for the root, unroot tool

he updated it yesterday, so you probably don't have the newest one.
 
can you give me the link please because i think im using the wrong one

edit*
and also tell me which one to use if theres more than one option
 
yea that one i updated like yesterday. might work might not, not sure really. i cant figure out where the problem would be
 
why is my phone so sucky.

so the root did exactly what doomlords script from 2011 did, basically i got superuser without root access and my phone got really studdery, like 7 fps.

and the recovery didnt work either in fast boot.


is anyone else having this prblem or just me???
 
Are you able to issue other fastboot commands like "fastboot devices"? Just trying to establish whether fastboot is functioning a little bit or not at all.
 
its just you im sorry to say. and fastboot needs the proper drivers, check your device manager with it on the black screen with the green android guy
 
i m still running the stock rom

On stock rom, get into fastboot by typing "adb reboot bootloader" in terminal.
once in fastboot, type "fastboot devices" in terminal. The terminal is on your computer, not the phone
 
I can't able to register in Xperia flash tools. It must need before start unlocked bootloader. there is no option for skip. I can not make password where I was followed the instructions. Plz help me.
 
I can't able to register in Xperia flash tools. It must need before start unlocked bootloader. there is no option for skip. I can not make password where I was followed the instructions. Plz help me.

I apologize in advance if this sounds rude, but I have no idea what you are referring to. If you are trying to root your phone please see Junkie's AIO Tool thread
 
edit*

ok,
can you do me a favor so i can make sure im not wasting my own and everyone elses time, because i think i have everything but im not 100% sure.

please if you have the time take screen shots of the drivers that im supposed to have and the location the drivers are in so i can see if anything is identical.

because at this point im thinking my phone is just useless or its just my computer
 
actually im not even sure thats the right phone hes talking about. first of all what kind of phone do you have birenregmi? if its not the zte warp sequent you are in the wrong section, if it is then you have the wrong tools, dont just go download some random xperia tool set, use my tool or the specific doomlord script built for the xperia but posted on this section and proven to work for us. other ones wont work and may break your phone

also, if you are trying to unlock the bootloader on a warp sequent you should just give up now kuz ur gonna break something. the sequent doesnt have a locked bootloader and youre heading the right direction for a bricked phone

general rule, dont use stuff from other phones unless specifically instructed. you broke rule #1 and thats a good way to end up with a phone you cant even turn on anymore. only use things you find on this section of the forum, never use tools designed for other phones, never install kernels or roms or cwms for other phones, even using things from the warp will completely destroy your phone, after that you cant fix it
 
please if you have the time take screen shots of the drivers that im supposed to have and the location the drivers are in so i can see if anything is identical.

Can't help you with drivers as i am a linux user. I believe Junkies AIO Tool has a link to the drivers you need though.
 
fastbootdriver_zpsa8deff6b.jpg


that is the fastboot driver as seen in the device manager. youll notice mine is broken, i fixed it by updating the driver manually. if it has that little yellow warning sign like mine, or if its named something else, youll have to follow the directions ive given to manually update the driver to the correct one
 
side note, for that to show up youll have to try the fastboot method of installing a recovery, that will put you into fastboot mode, once in fastboot mode with just andy sitting there staring at you check your device manager and if it isnt correct youll have to look at my posts about manually forcing the drivers earlier in this discussion
 
Back
Top Bottom