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
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 ...
Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help
Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!
FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
kzoodroid said:
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
Click to expand...
Click to collapse
I can't seem to find a link to to superuser inside ROM Manager. Can you tell me where to locate it?
thanks,
John
under download rom > extras
kzoodroid said:
under download rom > extras
Click to expand...
Click to collapse
You can also get it from here
Thanks to you both. I didn't even click on the Download ROM because it's premium and I'm still getting my feet wet with the whole root thing. I'm off to try the GB RUU w/radio and then re-root.
What if you have s-on?
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
kzoodroid said:
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
Click to expand...
Click to collapse
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
deadsoulboy said:
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
Click to expand...
Click to collapse
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
kzoodroid said:
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
Click to expand...
Click to collapse
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Flash clockworkmod recovery first, then the superuser zip.
I tried that but it gives me an error saying: "An error occurred while attempting to run privileged commands!".
If you flashed the GB RUU and lost root and/or s-off.
Someone correct me please if I'm wrong but couldn't you download the froyo RUU and load it then root and s-off?
Sent from my ADR6300 using XDA App
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
deadsoulboy said:
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Click to expand...
Click to collapse
The Eris had a manual method (race method) for rooting the phone but I could never find one posted for the Inc. It involved having the phone connected to a pc with adb running and then taking out the sdcard and rebooting, at a certain point of the boot process you counted to 4 and then pushed the sdcard back in. If you did it correctly adb was able to connect to the phone and you could slip a custom recovery and su in. It was rather complicated and only a handful of people ever did it correctly myself included and it was eventually replaced by a one-click method. The one-click method still pretty much does the same thing you just don't have to manually remove the sdcard or have the phone connected to a pc. In some ways the Eris has a lot more support from its community than the Inc does probably because it was Verizons first android phone.
k_nivesout said:
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
Click to expand...
Click to collapse
I second this it has to be a flashable version (contains android-info text file + the recovery image) to work. I used the 3.0.0.8 file from doug pistons website which is already to go just needs to be renamed PB31IMG.zip and make sure it isn't being named PB31IMG.zip.zip as file extensions can be hidden especially if you are renaming it on a pc. I downloaded it directly to my phone and renamed it there so the extension wasn't hidden.
swskeptic said:
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Click to expand...
Click to collapse
I beleive that is becasue you stil have the stock recovery? Did you flash the clockwork recovery from dougpiston.com?
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
swskeptic said:
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
Click to expand...
Click to collapse
First thing are you getting into recovery from the hboot menu? And you can't get into recovery from ROM Manager because you need superuser installed to do it that way. It still sounds to me like you don't have ClockworkMod Recovery installed. Maybe only version 3.0.0.8 works I'm not sure but that version is for both amoled and SLCD screens. So either try reflashing your copy of 3.0.0.7 or try flashing 3.0.0.8. I do think I had to flash the recovery a couple times to get it to stick.
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium
Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.
irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.