Develop Bugs

A little help needed, Am I still rooted?

I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.

travazz said:
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
Click to expand...
Click to collapse
easiest way to know if you are still rooted is to download android terminal emulator from the market and type in su on the screen... if you get a # sign then you have root... if you get permission denied then you don't.
find that out first then we can answer the other questions.

Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it

travazz said:
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
Click to expand...
Click to collapse
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.

viccyran said:
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
Click to expand...
Click to collapse
Where do I get the custom recovery file and how do I install it/use it?
Sorry that these are really dumb questions, but now that I know I still have root, this is getting exciting again.

See the stickied thread recovery reflash tool.
-------------------------------------
Sent via the XDA Tapatalk App

Now I'm trying to follow the recovery steps and I'm having the following errors. Can anyone please help?
When I try to install the modified USB drivers I receive the following errors:
Error 0x80004005: Unspecified error on these specific dll files.
WdfCoInstaller01007.dll
WUDFUpdate_01007.dll
WUDFUpdate_01007.dll
When I go to install the reflash-bundle, everything installs, but it fails installing the reflash.exe saying that the file is corrupt.
I'm using Windows 7 Ultimate x64, if that helps out

This is a development sub-forum. Please post your questions in the General section. Thanks.

How to remove applications native HTC Desire?

ola staff, how are you all?
Firstly apologies if I'm creating a topic out of rules and with a subject ja discussed and case find necessary, moderation can delete without any problem!
I have a doubt: it would be possible to remove (uninstall) native applications of Desire?
What is the most appropriate way to do this?
I ask because ja had a motorola milestone and it managed to remove many native applications as the launcher, the music player, etc!
What do I need to do and which path to take to achieve this feat! Agradeceria if any of you, more experienced could help me, indicating the best way!
Thank you and peace!

- Root, flash a ROM with the apps removed.

Pajorve said:
ola staff, how are you all?
Firstly apologies if I'm creating a topic out of rules and with a subject ja discussed and case find necessary, moderation can delete without any problem!
I have a doubt: it would be possible to remove (uninstall) native applications of Desire?
What is the most appropriate way to do this?
I ask because ja had a motorola milestone and it managed to remove many native applications as the launcher, the music player, etc!
What do I need to do and which path to take to achieve this feat! Agradeceria if any of you, more experienced could help me, indicating the best way!
Thank you and peace!
Click to expand...
Click to collapse
Moved to Q&A as not development.
You can remove apks from /system/app, though I am not an expert on the desire. It's possible, perhaps someone can help with the specifics here.

Thank you very much, but I didn't really expresei correctly as it should.
I wonder if it is possible this procedure ja with Rom installed if having to another in order to withdraw flashear these applications!
with the root explorer is unfortunately not possible ...!
is how to do?
Thanks again for the quick response!

First of all please look over your English again, as some of it came out very bad/impossible to understand
But if i get you right, you want to remove some of the native apps. These are stored on the /system partition. If you want to remove some of those, you will first have to root your phone. Then you can remove them while in recovery mode using adb commands.
This might seem a bit difficult, but if you are rooted, i can easily guide you through it. Another way, if you are rooted is to install the new s-off hboot which will allow you to make the changes using root explorer

mortenmhp said:
First of all please look over your English again, as some of it came out very bad/impossible to understand
But if i get you right, you want to remove some of the native apps. These are stored on the /system partition. If you want to remove some of those, you will first have to root your phone. Then you can remove them while in recovery mode using adb commands.
This might seem a bit difficult, but if you are rooted, i can easily guide you through it. Another way, if you are rooted is to install the new s-off hboot which will allow you to make the changes using root explorer
Click to expand...
Click to collapse
Truth .... I know that my English is very bad ...! sorry!
Yes my Desire is totally root and could you please explain to me how to proceed in case extrans ABD to remove applications?
Know the method S-Off AlphaRev site, but I have to confess I didn't understand a lot about it, could tell me how to do this procedure correctly for non brickar my player?
excuse such noobs, but I'm just wanting to learn a little more ...!
Thanks for the great help

Finnaly S-OFF Tnx guys !
I ended up making the procedure of S-off and now I am with my desire in full swing!
Thank you for your strength and pela great help!
I removed all native applications that they had no use for me. ..
Thank you!

Hehe great to hear it worked out for you It was probably also easier to go the s-off road right away. Issuing adb commands is a bit more difficult.
And sorry for not answering on you request, but i have had a busy day

friend I thank you for the tips
mortenmhp said:
Hehe great to hear it worked out for you It was probably also easier to go the s-off road right away. Issuing adb commands is a bit more difficult.
And sorry for not answering on you request, but i have had a busy day
Click to expand...
Click to collapse
friend I thank you for the tips
thank you very much!
Are people like you goodwill that make all the difference!
hug and sits on God's peace!

If you want to remove apps after you have flashed the ROM you can boot into recovery mode, connect device to pc in debug mode and use adb:
adb shell remount /system/
adb shell cd /system/app
adb shell ls
adb shell rm [application name.apk]
Blame me if I'm wrong, sending from my phone so I can't check atm.
Sent from my HTC

Tanx man...great ! Thank you !!
shoemeistah said:
If you want to remove apps after you have flashed the ROM you can boot into recovery mode, connect device to pc in debug mode and use adb:
adb shell remount /system/
adb shell cd /system/app
adb shell ls
adb shell rm [application name.apk]
Blame me if I'm wrong, sending from my phone so I can't check atm.
Sent from my HTC
Click to expand...
Click to collapse
Now I'm trying to change the boot animation but simply can't .... ja tried in ADB follow in the footsteps of the link corresponding to the subject in thread: http://forum.xda-developers.com/showthread.php?t=648555
somehow can help me ... thanks!
ja tried everything, all commands and nothing ... the appliance makes the reboot and when I think he will ride the bootanimation, I get the old boot!
swear I don't know how do I change my boot animation?
I'm using the Rom Froyo 2 with Root Version 2.12.911 .1 any tips on how to do this procedure work?
Thank you very much!

Now I have S-off with my desire and downloaded root manager from market place can I mount r/w goto to system apps and add and remove apps? Or am I being a totall noob

Pajorve said:
Now I'm trying to change the boot animation but simply can't .... ja tried in ADB follow in the footsteps of the link corresponding to the subject in thread: http://forum.xda-developers.com/showthread.php?t=648555
somehow can help me ... thanks!
ja tried everything, all commands and nothing ... the appliance makes the reboot and when I think he will ride the bootanimation, I get the old boot!
swear I don't know how do I change my boot animation?
I'm using the Rom Froyo 2 with Root Version 2.12.911 .1 any tips on how to do this procedure work?
Thank you very much!
Click to expand...
Click to collapse
It can depend on where the bootanimation.zip file is.
In some ROMS they're at a different location.
cheekystew said:
Now I have S-off with my desire and downloaded root manager from market place can I mount r/w goto to system apps and add and remove apps? Or am I being a totall noob
Click to expand...
Click to collapse
I never used root manager but I suppose it's the same as root explorer.
But it can indeed remove files from your system, sometimes need to reboot system afterwards to see the effect. It's a paid app.

Thanks buddy shoemeistah ... Any tips of where to find this file on your system
Thanks for the explanation friend, why I can't change the bootanimation my Desire!!!
The paths that follow to try to change the bootanimation on my Desire were as follows: With the Root Explorer threw the image date/location and nothing!
After reading lots found a different way to play the file bootanimation that was as follows: System/media nor gave nothing!
Have any tips of where it could be this file bootanimation so I can make the procedure and get definitely?
Once again I'm very grateful!
Thank you!
USING FROYO 2 WITH ROOT ROM Version 2.12.911.0.1

shoemeistah said:
If you want to remove apps after you have flashed the ROM you can boot into recovery mode, connect device to pc in debug mode and use adb:
adb shell remount /system/
adb shell cd /system/app
adb shell ls
adb shell rm [application name.apk]
Blame me if I'm wrong, sending from my phone so I can't check atm.
Sent from my HTC
Click to expand...
Click to collapse
True but it's so much easier with S-OFF and Root Explorer...

Discovered a simple way how to change the bootanimation on my Desire!
shoemeistah said:
It can depend on where the bootanimation.zip file is.
In some ROMS they're at a different location.
I never used root manager but I suppose it's the same as root explorer.
But it can indeed remove files from your system, sometimes need to reboot system afterwards to see the effect. It's a paid app.
Click to expand...
Click to collapse
Thanks to all of XDA, ja I S-OFF and tbm discovered a simple way how to change the bootanimation on my Desire!
Thank you to all of you for the great discussion here in this thread!
=]
=]

[Q] Have I managed Perm Root with this much ease? Visionary+ Question

About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?

Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App

I should have mentioned that I did that and got the # symbol, am I good to go?

Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).

redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.

That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App

Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.

Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?

OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.

Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?

Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?

There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App

Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.

shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.

Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.

New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?

Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.

Excuse my ignorance, but what exactly do you mean by that? What should I do?

[HOW-TO] [GSM & CDMA] How to root without unlocking bootloader (for ITL41D to JRO03O)

[HOW-TO] [GSM & CDMA] How to root without unlocking bootloader (for ITL41D to JRO03O)
As of Oct 10, 2012: Google has patched this vulnerability starting with JRO03U. That is to say, this works on versions of ICS and JB from ITL41D to JRO03O inclusive. It will not work for JRO03U or newer. (My previous guide found here only worked on Android versions 4.0.1 and 4.0.2, i.e., ITL41D/F and ICL53F.
Once you have root, you can use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it. All credit goes to Bin4ry and his team. I just isolated the parts required for the GNex, modified it slightly and eliminated the script.
So, it looks like Bin4ry (with the help of a couple of others) has managed to find a way to exploit a timing difference in the "adb restore" command. See source here. (Although this may be old news to some, I hadn't seen it before a few days ago.) This is more for informational purposes, as having a Nexus device, we are able to backup our data, unlock the bootloader and restore the backup, so this is guide is not really that useful for most, but you still have those users who are scared to unlock their bootloader. It is useful however, for those with a broken power button, as it allows them to unlock their bootloader without the power button.
How this works
The way this works is as follows: the "adb restore" command needs to be able to write to /data to restore a backup. Because of this, we can find a way to write something to /data while this is being done. Now, Android parses a file called /data/local.prop on boot. If the following line exists in local.prop, it will boot your device in emulator mode with root shell access: ro.kernel.qemu=1. So, if we can place a file called local.prop with the aforementioned line in /data, once your device boots, it will boot in emulator mode and the shell user has root access, so we now can mount the system partition as r/w.
So what does this all mean:
You can now root any version of ICS and JB released to-date without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) Please read the entire post before attempting this.
2) This does not wipe any of your data, but I take no responsibility if something happens and you lose your data. Maybe consider doing a backup as per this thread before attempting this.
3) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
4) This obviously needs to be done over ADB, as you cannot run adb in a terminal emulator on-device. If you do not have ADB, I've attached it in the zip (Windows and Linux versions). Unzip all files.
Step-by-step:
1) Download the attached files to your computer and unzip them;
2) Open a command prompt in that same directory;
3) Copy the root files to your device:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
8) Once it is rebooted, open a shell: adb shell
Note: Once you do step 8, your should have a root shell, i.e., your prompt should be #, not $. If not, it did not work. Start again from step 4. (It may take a few tries for it to work. Thanks segv11.)
Now we can copy su and Superuser.apk to the correct spots to give us root.
9) Mount the system partition as r/w: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
10) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
11) Change permissions on su: chmod 06755 /system/bin/su
12) Symlink su to /xbin/su: ln -s /system/bin/su /system/xbin/su
13) Copy Superuser.apk to /system: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
14) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
15) Delete the file that the exploit created: rm /data/local.prop
16) Exit the ADB shell: exit (May have to type exit twice to get back to your command prompt.)
17) Type the following (not sure if this is needed for the GNex, but it shouldn't matter): adb shell "sync; sync; sync;"
18) Reboot: adb reboot
19) Done. You now should have root without having to unlock your bootloader. If you want to unlock now, you can without wiping anything. See segv11's app linked at the beginning of this post.
Note: If you still do not have root access after doing these steps, redo them and add this step between 10 and 11:
10b) Change the owner of su: chown 0.0 /system/bin/su (Thanks maxrfon.)

I've done all. It installs supersuser app but the phone is not really rooted and apps that requires it doesn't work

Lorenzo_9 said:
I've done all. It installs supersuser app but the phone is not really rooted and apps that requires it doesn't work
Click to expand...
Click to collapse
Did you try opening the Superuser app?
What happens when you open an app that requires root? Do you get the request for su access?

You can open the app but whith apps that requires root there are no requestes and they don't... Even using root checker you see that you're not rooted

Lorenzo_9 said:
You can open the app but whith apps that requires root there are no requestes and they don't... Even using root checker you see that you're not rooted
Click to expand...
Click to collapse
Re-run the entire procedure again (including pushing the su and Superuser.apk files). When I had done it, I used the latest version of su and Superuser.apk, but when I uploaded the files in the attachment in post #1, I used the files that Bin4ry had in his package, which I assume are older. Regardless, re-download the attachment in the first post and try it again.

efrant said:
Re-run the entire procedure again (including pushing the su and Superuser.apk files). When I had done it, I used the latest version of su and Superuser.apk, but when I uploaded the files in the attachment in post #1, I used the files that Bin4ry had in his package, which I assume are older. Regardless, re-download the attachment in the first post and try it again.
Click to expand...
Click to collapse
Ok I'll do it and then I'll report you what happens. So now have you updated su and superuser.apk?

Lorenzo_9 said:
Ok I'll do it and then I'll report you what happens. So now have you updated su and superuser.apk?
Click to expand...
Click to collapse
Yes, I put the latest versions in the zip in the first post.

I can confirm that this works, and also that step 10b was not needed for me. This is the first time I have not used a toolkit so if I can do it, anyone can.
Running a Verizon Galaxy Nexus, this allowed me to update to the leaked Jelly Bean OTA with a locked bootloader. I first flashed stock 4.0.4 and locked the bootloader. I then used the exploit to gain root access, allowing me to apply IMM76Q and JRO03O OTA updates via stock recovery. (Rebooting between updates.) Thank you for creating a guide that this newb could easily understand and follow.

serty4011 said:
I can confirm that this works, and also that step 10b was not needed for me. This is the first time I have not used a toolkit so if I can do it, anyone can.
Running a Verizon Galaxy Nexus, this allowed me to update to the leaked Jelly Bean OTA with a locked bootloader. I first flashed stock 4.0.4 and locked the bootloader. I then used the exploit to gain root access, allowing me to apply IMM76Q and JRO03O OTA updates via stock recovery. (Rebooting between updates.) Thank you for creating a guide that this newb could easily understand and follow.
Click to expand...
Click to collapse
Thanks for confirming that step was not needed.

Thanks!
Bookmarked for future reference :good:

does it work on nexus 7 ?

dacc said:
does it work on nexus 7 ?
Click to expand...
Click to collapse
Yes, it should.

thans for quick response

Works fine for my GNex, big thanks! How about putting it into a script for non-advanced users here?

wictor1992 said:
Works fine for my GNex, big thanks! How about putting it into a script for non-advanced users here?
Click to expand...
Click to collapse
Glad you got it working!
As for putting it into a script, I could but I'd rather not. As with most of the guides that I have written up, I purposely do not put things into a script so that people would actually go through all the steps and, by doing so, maybe get an understanding of what they are actually doing, and hopefully learn something in the process. If I would have packaged it up into a script, a lot of the less experienced users would not even try to go through the steps -- they would just use the script, and no one learns anything yet again. See here for some discussion on one-click scripts. Granted, blindly following a step-by-step is not much better, but I have tried to put comments and explanations throughout to facilitate learning. It's about the journey...
P.S.: I would appreciate it if no one else posts a script in this thread.

efrant said:
P.S.: I would appreciate it if no one else posts a script in this thread.
Click to expand...
Click to collapse
can i make a script that just puts in big text "STOP USING TOOLKITS AND 1 CLICKS"

Zepius said:
can i make a script that just puts in big text "STOP USING TOOLKITS AND 1 CLICKS"
Click to expand...
Click to collapse
LOL! Yes, sure, that's one script I don't mind being posted. LOL!

Heh, fair enough. I think I'm learning a bit about adb
One question: I can't replace system APKs by installing them, it tells me that there is a signature conflict. How can I fix that? I thought it shouldn't happen after rooting. (I'm trying to install the "international" velvet.apk).

wictor1992 said:
Heh, fair enough. I think I'm learning a bit about adb
One question: I can't replace system APKs by installing them, it tells me that there is a signature conflict. How can I fix that? I thought it shouldn't happen after rooting. (I'm trying to install the "international" velvet.apk).
Click to expand...
Click to collapse
Let's try to keep this thread on-topic please.
But to answer your question, don't install the apk. Using a file explorer that has root access, copy it to /system/app (after making sure that system is r/w) and make sure the permissions are set to match the other apks in that directory.

when running adb after running the command where i tell it to restore fake restore and then while the "exploit" is running ikeep getting , in cmd, link failed, no such file or directory, and it just keep doing that. is this normal or did i do something wrong.
efrant said:
Let's try to keep this thread on-topic please.
But to answer your question, don't install the apk. Using a file explorer that has root access, copy it to /system/app (after making sure that system is r/w) and make sure the permissions are set to match the other apks in that directory.
Click to expand...
Click to collapse

Rooting Hell Since 4.2.1

So I usually use the toolkit to root, in fact I have been for many versions now.
However with the installation of 4.2.1 I haven't been able to root at all. I use the toolkit in the same way but it simply doesn't root the phone.
So today I tried the manual way. I downloaded and installed SDK tools from google navigated to the adb folder and went through the commands. Everything seemed to go okay apart from when I typed adb shell chmod 06755 /system/bin/su. The command window did nothing.
I carried on and typed adb shell chmod 06755 /system/app/Superuser.apk, when it said "bad command" or something similar.
Rebooted the phone, no root... still.
However the Superuser app is there. So:
1) How do I delete the superuser app, bearing in mind it has system permissions. I'd like to simply start again.
2) I don't have CW recovery installed and would prefer not to bother with it if I can.
3) Just to confirm, when I root the phone, does that allow me to delete files in the /system/app folder?
4) Following this guide on rooting manually. Is that all alright?
5) In a couple of sentences, can someone explain rooting to me? From what I understood, rooting simply opens up the phone to allow access to everywhere, where you can copy and delete files, or apks.
6) If 5 is true, when following the rooting guide (4), which command am I actually telling the system to run as root? Is it simply the "root" command?
7) If 6 is true, how come when I re-boot, the phone won't let me delete things from the system/app folder?
Thanks for any help.

1) stop using a toolkit, and no you didnt root the manual way.
2) download this: http://forum.xda-developers.com/showthread.php?t=1538053 - its supersu, superuser is unreliable on 4.2+
3) fastboot flash a recovery
4) flash the supersu.zip
5) done.

Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Don't these superuser apps just manage app permissions? They don't actually enable the root access do they?
Thanks

anotherxdauser said:
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Thanks
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showthread.php?t=1529058

Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.

anotherxdauser said:
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
Click to expand...
Click to collapse
it replaces anything in /system... basically the OS.