Hi i just update to 2.3.4 and try to root it and work fine with me
Download this file and move it to your NS
http://www.mediafire.com/?0a4abln7x3gjgrv
after your flash the recovery then ..
On your phone, use the volume key to highlight "recovery". Press power to boot into recovery.
in the recovery screen, select mounts and storage
mount /system
mount /data
go back, and choose install zip from sd card
choose "choose zip from sd card"
pick the su package zip file you copied over earlier
choose Yes
when done, reboot.
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
it is for the i9023??
So after I flash 2.3.4 update, all I have to do is reboot and flash SuperUser again, and then Nexus S is re-rooted again?? Thanks!
amjad_2020 said:
Hi i just update to 2.3.4 and try to root it and work fine with me
Click to expand...
Click to collapse
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
I have a custom kernel. How do I Install 2.3.4
Sent from my Nexus S using XDA App
italia0101 said:
I have a custom kernel. How do I Install 2.3.4
Click to expand...
Click to collapse
You have to go back to stock GRI40, i.e. with a Nandroid restore?! But this will be the correct thread for you: http://forum.xda-developers.com/showthread.php?t=1055591&page=12
kevin_ngckk said:
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
hehe how on earth can someone provide real feedback on battery life 2 seconds after installation?
Thanks for sharing, I'll wait for Team Douche to implement this on CM7.
Trouble
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
smlmn said:
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
Click to expand...
Click to collapse
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
jungbum said:
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
Click to expand...
Click to collapse
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
Yes, same here SuperUser ist still available, but without any function
on nexus s 9023 ??
what about it ?
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
jamallj said:
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
Click to expand...
Click to collapse
No sorry. It's not possible to install busybox without root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
That means you're not rooted.. you have to root again.
bolabola118 said:
That means you're not rooted.. you have to root again.
Click to expand...
Click to collapse
I've tried to reroot again and totally get result
But I also done that:
!Once you are in recovery mode, select the relevent mounts and storage by Mount / System and Mount / data.
(I can not post links)
Thx
Handymeister said:
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
Click to expand...
Click to collapse
Same situation/problem
For those stock rooted but bootloader locked 2.3.3 users that previously rooting using CWM recovery to update and superuser root method.
You can root the same way...but save the trouble of fastboot recovery step via PC which novice users could be stuck on getting fastboot usb driver to work properly.
0) Just installed ROM Manager (From Market) into your phone
1) Store both 2.3.4 update.zip and SuperUser.zip into SDCard
2) Run ROM Manager
3) Activate CWM Recovery
=> Make sure recovery is installed succesfully..check ROM Manager screen which tell whether the installation is successfully done.
4) Reboot recovery from ROM Manager App
5) Follow thread #1 on the rest
6) After applying update.zip..do not reboot...do a system mount from CWM Recovery then apply SuperUser.zip ..after completing all steps..do a reboot..
Voila your 2.3.4 is installed and rooted..
Thanks, but this way comes to late for me and some other users. We've flashed the update without rooting.
And now we need another way for root ...
Related
So I got gingerbread, updated from rubix 2.01. Question is would z4root would to root it. Or do I absolutely have to sbf to 2.2 and get rooted gingerbread file? Thanks
the rageagainstthecage exploit doesn't work on 2.3 (z4root) so right now you will have to sbf and flash the prerooted one.
tried running sbf app and it didnt like me.. clicked start nothing happened... had all drivers as well.. i dont know
Droid2kev said:
tried running sbf app and it didnt like me.. clicked start nothing happened... had all drivers as well.. i dont know
Click to expand...
Click to collapse
the gb file is flashable through clcokwork recovery
Sent from my DROID2 using XDA App
And you don't have to wipe. It's signed as an update so all your apps and settings will be the same.
Sent from my DROID2 using XDA App
so i can grab the sbf and stick it through recovery as if i would with any other file update and put it on root of the sd card?
Droid2kev said:
so i can grab the sbf and stick it through recovery as if i would with any other file update and put it on root of the sd card?
Click to expand...
Click to collapse
Yes. What they did was they took the .sbf file, and converted it into an update.zip format so we can flash it in recovery.
So just get the file in sbf format and stick it on sd card and go from there correct... thanks
Is Clockwork ROM Manager the same as Recovery? I looked in the Market, but it only brings up Clockwork ROM Manager in the search.
I would install ROM Manager on my phone, put the update.zip file in the root directory of the SD card and then run it with ROM Manager?
silverfang77 said:
Is Clockwork ROM Manager the same as Recovery? I looked in the Market, but it only brings up Clockwork ROM Manager in the search.
I would install ROM Manager on my phone, put the update.zip file in the root directory of the SD card and then run it with ROM Manager?
Click to expand...
Click to collapse
Yes clockworkmod is the same as the custom recovery. You need to get Droid 2 bootrstrap recovery app from the market. The droid 2 bootloader is locked, preventing us from completely flashing a custom recovery. the bootstrapper is the only way to get to clockwork.
hey OR, i got the bootstrap recovery unfortunately its not working. i got the correct one for the droid 2 but it keeps saying error running exec(). command and it list a lot of other writing as well. i also tried rom manager to reboot into recovery with the result of it saying error while trying to run privileged command.. what shall i do
Droid2kev said:
hey OR, i got the bootstrap recovery unfortunately its not working. i got the correct one for the droid 2 but it keeps saying error running exec(). command and it list a lot of other writing as well. i also tried rom manager to reboot into recovery with the result of it saying error while trying to run privileged command.. what shall i do
Click to expand...
Click to collapse
Uninstall bootstrap and reinstall, be sure to give it su permission.
how do i assign it superuser again?
Is your phone rooted?
no i cant root it, cause it has the 2.3 leaked update on it... i put super user on it and it wont give me access to bootstrap until i install an update it said it put on my sd card but i cant reboot into recovery to even alow the superuser update... frustrating
Download SuperOneClick to computer, link to phone with USB debug on, click "root".
Voila!
Edit: Flash back to Froyo, root with SuperOneClick, bootstrap clockwork recovery, then install .zip file with rooted Gingerbread.
hey man i cannot ind a link to it, u got one? and it will work on 2.3 droid 2? thanks
figured it out
I have a Nexus S(I9023) and used the full Rom to update from 2.3.3 KB3 GRI54 to the 2.3.4 KD1 GRJ22 version, except I can't get my clockworkmod recovery to stick, I unlocked the bootloader and flashed the recovery with clockworkmod 3.0.2.5, and installed the superuser file, except each time I boot into the OS, and then boot back into recovery, the clockworkmod is gone, and I'm stuck with the stock recovery again.
What I did was the following procedure:
Odin flashed back to stock 2.3.3 - KB3 - GRI54
installed the full update 2.3.4 with the recovery
unlocked bootloader
flashed clockworkmod recovery 3.0.2.5
installed superuser
reboot
checked if superuser app was installed successfully - yes
reboot to recovery
And to my surprise the clockworkmod recovery was gone, and I was stuck with the stock recovery again.......
How do you make the CW stick and not have it reverted to the stock recovery?
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Matridom said:
There is a script that resets it. Been like that for a while. Look in the root threads on how to make it permanent
Sent from my Nexus S
Click to expand...
Click to collapse
Tried looking in the Root threads, but can't find the solution, the funny thing is that I never had this before, only started after updating to 2.3.4.
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Yep. Also if you use this method you will still have to flash CWM one more time after you do what this poster says (the script runs when the phone boots) .
Sent from my Nexus S using XDA App
I had same problem..it worked for me..now should I back up that Tom so I don't gotta do it again??
Sent from my Nexus S using XDA App
pullermann said:
There's a file in the system's /etc folder named install-recovery.sh. You need Root Explorer to rename it in order to prevent further installs. Mount the "etc" directory as writable using Root Explorer and rename the file (to for example: install-revocery.sh.old).
This will prevent the stock recovery from being installed in the future...
Click to expand...
Click to collapse
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
RISHI-O said:
Thanks for the solution, I did what you described, and things are working now
You just saved me a lot of frustration........
Click to expand...
Click to collapse
Guides for rooting had the solution for this problem.Dont frustrate just search )
Sent from my Desire HD using Tapatalk
Hey all,
So I've managed to upgrade to FW 4, Doom's latest kernel, & Doom's autoroot also. Thanks Doom
I still can't seem to get root working. When I go in to Superuser to try to update, I get the following:
su-2.3.1-bin-signed.zip
reboot into recovery and flash it
I can't reboot into recovery (not sw cuz it's not rooted, hitting back key when powering on ignores me).
Anyone else know what I could try?
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Cat_On_Droid said:
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Click to expand...
Click to collapse
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Rixter757 said:
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Click to expand...
Click to collapse
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
AndroHero said:
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
Click to expand...
Click to collapse
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Rixter757 said:
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Click to expand...
Click to collapse
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
azuell said:
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
Click to expand...
Click to collapse
Rixter757 said:
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
Click to expand...
Click to collapse
WooHooo glad your sorted
some help is really needed the problem is down below
AnAndroidLover said:
Hello guys,
let me tell you i am a complete noob and this is my first post.
i updated to ics 4.0.4 official and rooted the device with CWM
and the samsung_galaxy_tab_10.1_root.zip or similar name
i open superuser to update and it cannot gain root access.
the system dir is read only and i cant change permissions or ownership.
tried to install su.zip with adb and terminal app, failed.
no app gets su permissions. tried remounting it failed too.
even root explorer and titanium backup dont work zt all
please help me, any contribution will be appreciated.
also, please put links to another root file or method which
does not involve losing the camera.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Try this,it's supersu with su binary.hope it helps:
http://forum.xda-developers.com/attachment.php?attachmentid=1296159&d=1346514922
so do i have to install it by cwm on recovery mode?
Sent from my GT-P7510 using Tapatalk 2
AnAndroidLover said:
so do i have to install it by cwm on recovery mode?
Click to expand...
Click to collapse
Yes.sorry for not mentioning that...
The original root.zip also installs a version of Superuser that doesn't work with stock ICS. You can go to the Superuser site and download the 3.1.3 ARM zip...that's what I ran when I rooted. Either way!
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Srsly? Please go back and root it manually. It will work.
Mart360 said:
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Click to expand...
Click to collapse
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
simms22 said:
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
Click to expand...
Click to collapse
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Mart360 said:
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, reboot. that is all.
all you need to do is have the drivers and fastboot installed http://forum.xda-developers.com/showthread.php?t=1741395
If you go to terminal emulator and type in su, does the $ change to a #?
Sent from my Nexus 7
If you have access to directories like /system and /dev, you're rooted. If not, you're not. Skipsoft's Nexus 7 Toolkit works well. Just redo the root steps, watch for error messages, and use Super SU (not SuperUser), and you'll be fine.
This happened to me too so I re rooted it manually. I just followed this link:
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
Wow this is getting confusing... ive got two or more guides open both with varying methods and files to install..
if i download the new SU files and reroot, then it wipes all files ? so how does having the SU work
As to reflashing a new binary, thats what i dont want, i just want a stock set up thas rooted.
Also re terminal? it that putty ? and go into the device that way?
Mart
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
simms22 said:
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
Click to expand...
Click to collapse
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Mart360 said:
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Click to expand...
Click to collapse
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
simms22 said:
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
Click to expand...
Click to collapse
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Mart360 said:
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Click to expand...
Click to collapse
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
simms22 said:
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
Click to expand...
Click to collapse
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Mart360 said:
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Click to expand...
Click to collapse
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
simms22 said:
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
Click to expand...
Click to collapse
Again Many thanks sometimes we can be a bit slow on the uptake lol
cheers for sticking with me and seeing it through
Mart