Losing root when nandroid restore. - Nexus One General

Ok guys, i think this is the best place to post this up as this post will get more appropriate replies.
In the last few days i've lost root 3 times for what i see as no apparent reason. I am running CM 5.0.2 with some morphs and nothing else different. I've heard over at IRC that some people on CM are experiencing the losing root problem as I have and only just now, have i pinpointed the problem.
Just now i did a fresh nandroid backup of my current config, and im not sure if anyone else does this - but i instantly do a restore with the 'new' backup just to verify that it backed up correctly and is not corrupt. If it is corrupt then it will not complete the restore and i can backup again. I do this because in the past I have gotten bad backups that dont restore and leave me with no backup at all. Anyways, after this restore I instantly checked my root and *drum roll* no root access.
Not sure if something is wrong with the Recovery (a bug), but i never had this problem in the past and not sure to the reason why. Im 100% sure i have root before the Nand Backup, so why would it lose root after a restore?
Thanks

I experienced this, I had made a backup, and wiped (to get protected apps working in market)... I then restored my backup, and noted that all attempts to access SU were given permission denied (without prompt). All you have to do is re-flash your current rom. I believe this has happened with Nandroid restores in the past, maybe Amon_Ra's thread is the right place for this conversation?

daveid said:
I experienced this, I had made a backup, and wiped (to get protected apps working in market)... I then restored my backup, and noted that all attempts to access SU were given permission denied (without prompt). All you have to do is re-flash your current rom. I believe this has happened with Nandroid restores in the past, maybe Amon_Ra's thread is the right place for this conversation?
Click to expand...
Click to collapse
Hi thanks for the reply,
I guess this does belong to Amons thread, but in a way im trying to inform those who are confused about the 'random' lost of root access. This was seriously baffling me before as it seemed really random at times, I wouldnt even know i lost root until i used certain apps. Therefore I couldnt pin point the actual cause. It is easily fixed with reflashing ROM/Gapps etc but i still do a superboot (not sure if this is necessary, although I dont see why not.), and for obvious reasons superboot you would need a computer.

m00moo said:
Hi thanks for the reply,
I guess this does belong to Amons thread, but in a way im trying to inform those who are confused about the 'random' lost of root access. This was seriously baffling me before as it seemed really random at times, I wouldnt even know i lost root until i used certain apps. Therefore I couldnt pin point the actual cause. It is easily fixed with reflashing ROM/Gapps etc but i still do a superboot (not sure if this is necessary, although I dont see why not.), and for obvious reasons superboot you would need a computer.
Click to expand...
Click to collapse
We appreciate the effort, but its just going to make people more confused when the information is all over the place and not in one clear, easy to find location.
Since it occurred when you performed the nandroid restore, then logically it belongs in that forum.

Fictionles said:
We appreciate the effort, but its just going to make people more confused when the information is all over the place and not in one clear, easy to find location.
Since it occurred when you performed the nandroid restore, then logically it belongs in that forum.
Click to expand...
Click to collapse
Sorry if thats the case then I should post in there and ask that a mod closes this thread. Although i think your post slightly contradicts itself lol The information is all over the place and by making this thread, I think it clears the mess up as people can see it clearly.
Like i mentioned before I was personally told over at IRC that people appeared to be getting this issue with CM roms, but to my finding seems to be Nandroid for me. Maybe even a combo of the both together? but whatever it is I hope both of the talented guys can look into it, although its not a huge huge matter to us (unless your an dev and nand frequently and lose root - now that would be annoying).
Regards
(if a mod does see this thread unfit please feel free to close )

i can also confirm when restoring cyan's latest stable rom with nandroid that i loose root. i can also confirm that re-flashing the rom and gapps restores root.

there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.

xkonni said:
there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.
Click to expand...
Click to collapse
solved the issue for me, thanks

xkonni said:
there's a problem with the restore currently.
the permissions of /system/xbin/su get lost.
fix it with:
Code:
adb remount
adb shell chmod 6755 /system/xbin/su
no need to reflash anything. besides if you rather reflash, no need for gapps then.
Click to expand...
Click to collapse
Thank you, sir! You just saved me a lot of time and aggravation!

Having the same issue as others in the thread although when i type in:
"adb remount" i get
"remount failed: invalid argument" thus i cannot get to the next step to restore root!
Cheers,
Vonapets

I've also been unsuccessful with this. Im on windows 64

I have attempted the same thing on XP 32bit as opposed to Win7 64bit. Still the same issue. Can someone post the su file for me to push onto my system via fastboot? I imagine you could probably pull it with root explorer?
Cheers,
Vonapets

The problem is fixed in my RA 1.6.2 recovery, just update and you'll not lose root again.

Amon_RA said:
The problem is fixed in my RA 1.6.2 recovery, just update and you'll not lose root again.
Click to expand...
Click to collapse
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers

vonapets said:
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers
Click to expand...
Click to collapse
Did you make a new nandroid backup AFTER flashing the new recovery? Using a corrupted backup will still make you lose root.

vonapets said:
I understand completely, i have already done so pretty much the minute i saw there was an update, although as i still dont have root and the commands dont work im guessing that i have to reflash? I have tried commands on 3 diff pc's and still no luck. Do i flash superuser then Cyanogen or?
Cheers
Click to expand...
Click to collapse
Yes, flash superuser again to gain root.

prettyboy85712 said:
Yes, flash superuser again to gain root.
Click to expand...
Click to collapse
Attempted this morning, when i flashed the superuser over the top of cyanogen, launcher and phone constantly force close! Maybe should just start again haha. Just hate downloading all the apps again and market db, cant backup because i dont have root!

thank you adb shell chmod 6755 /system/xbin/su saved me some reflash
thank you for your post save me some headaches

I entered the game starting with the 1.6.2.
First thing i did was make a nandroid backup of the stock rom, with root.
then went on flashing random roms , with nandroids.
as i switched from modoco to stock rom, i lost root.
when i try the adb stuff, i get
'Unable to chmod /system/xbin/su: No such file or directory'
I understand that.. but what do I do now then?
Superuser permissions doesnt do much for me here.. but ill be honest and say i dont know how to work it. I highlight the 1 item that was there, and it deletes itself.
-resets phone. opens ti backup-
it gave me the allow stuff, and i said Allow Always,
but it still says no root, I tried Metamorph, always gave me allow questions, and i approved, and no go.
-
---
restoring to a CM nandroid gave me root back.
I wonder if i wipe and format will i still have root, but i can start fresh?

Related

Possible to Unroot without RUU?

I was just wondering if it was possible to Unroot without the RUU? With all of my problems with the RUU and the error 110. I am a little hesitant to root again, not so much to root, but if I ever needed to unroot I don't know that I would want to run the RUU. BTW I have searched many places and all the unroot methods I have found use the RUU.
I dont believe that it is!
Although you can still be stock and be rooted like I am, and I don't think anyone would be the wiser if you had to take your phone in for something!
Could pull the recovery image from the ROM.zip in the ruu, then chmod everything back.
abcdfv said:
Could pull the recovery image from the ROM.zip in the ruu, then chmod everything back.
Click to expand...
Click to collapse
That is kind of what I was wondering if was possible. Thanks
crash447 said:
That is kind of what I was wondering if was possible. Thanks
Click to expand...
Click to collapse
All that will do is return your recovery image back to stock image. That doesn't unroot your phone.
If you want to unroot your phone, there are several things you need to do including, remove su, change adbd to start in restricted mode, blah blah blah. If you've loaded a custom ROM, you would have to RUU to be sure you got rid of everything. If you removed stock apps, you'd need to copy them back on. If you added anything to /system/app, you'd have to remove those apps (and clean up the cache and data areas in /data). If you did apps2sd, you'll need to move your apps and app-private directories back into /data.
There are many things you would need to do based on what you have already done after you got root access to your phone. The easiest and simplest way is to RUU your phone.
jmanley69 said:
All that will do is return your recovery image back to stock image. That doesn't unroot your phone.
If you want to unroot your phone, there are several things you need to do including, remove su, change adbd to start in restricted mode, blah blah blah. If you've loaded a custom ROM, you would have to RUU to be sure you got rid of everything. If you removed stock apps, you'd need to copy them back on. If you added anything to /system/app, you'd have to remove those apps (and clean up the cache and data areas in /data). If you did apps2sd, you'll need to move your apps and app-private directories back into /data.
There are many things you would need to do based on what you have already done after you got root access to your phone. The easiest and simplest way is to RUU your phone.
Click to expand...
Click to collapse
I do not disagree that RUU is easiest, but if it bricks your phone that is not worth it.
lol yeah i hear ya, i still have a phone that reads rev. 0 and it bugs me but hearing about all the bricks with the .56 RUU that is supposed to fix the glitch. it really isnt worth it to me >.<
but i want to get rid of it badly, hopefully the 2.1 update does the same...
This might be off topic but I saw your other thread too.
Iv used RUU on my phone like 6 times and never had a problem, it even reflashes the stock radio. I have a Google branded phone. I wouldn't turn away from just yet. Idk, just throwing it in here..
Well ive used the .29 RUU once before.
But again. im too afraid of bricking by the .59 RUU. no one knows why the error 110 happens or what makes it click.

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.
jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!
xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.
I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.
It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on
vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.
mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.
Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...
Please post questions in Q&A section.
just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.
Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App
Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

Unlock Problem: Permission Denied??

I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
If I root the phone, will that work?
Also, what are some good programs to copy the EFS folder?
Sorry for all the questions.
I'm fairly certain you have to be rooted
I am rooted as of 10 mins ago.
I tried to unlock it and I still got the same thing.
It says Permission Denied
Anyone have any ideas?
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
molson24 said:
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
Click to expand...
Click to collapse
in Terminal?
type:
su
(and hit enter)
before the command that needs superuser permission.
Also you probably would be better off just pulling the whole efs folder.
molson24 said:
I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
Click to expand...
Click to collapse
for permission denied try this:
open terminal emulator on your phone (download it from the market if you dont have it yet)
or you can type "adb shell" without quotations into the dos prompt and do it from there.
and type:
su
chmod 777 /efs/nv_data.bin
exit
exit
then in the dos prompt try:
adb pull /efs
or if you just want nv_data.bin:
adb pull /efs/nv_data.bin
if you need further help, this was written for the 19000 but it should help you anyways.
http://www.communityhosting.net/sgsunlock/i9000.html
You need to copy your nv_data.bin from your phone to your pc
You should see a folder made in the repair_nv_data folder like this Sauverarde_efs_apres_reparation
Move your nv_data.bin there along with nv_data.binvierge and repairation_nv_data.jar and Step2 and Step 4
Run Step 2 again and then Step 4 after its done creating the new nv_data.bin
I can't remember but I think you have to delete nv_data.md5 and a few others from your phone first
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
molson24 said:
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
Click to expand...
Click to collapse
lol yeah I can see that happening
I've accidently denied su permission a few times myself even when I do notice the pop up
well congrats!
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
molson24 said:
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
Click to expand...
Click to collapse
Unlocking should not break your downloads (At least I've never heard of it happening) but you'll be fine flashing any rom you like, without having to unlock again.
are you still on t-mobile just unlocked?
orare you on a different carrier now that your unlocked?
the main things to be careful of when flashing roms is:
be careful going from froyo (2.2 JK2/JK6) back to eclair (2.1 JFD/JI6) its a little tricky, but not too bad.
and be careful with lag fixes, if you use one always disable it before flashing. (I never found them very useful myself anyways)
going from JFD to JI6 and back should be fine though.
if you want a completly clean slate then you can use Odin and it still wont re-lock your phone.
you might even find that you like some of the roms out there better than the stock one
I know I did.

[Q] 3.2.1 rooted stock rom?

I currently have stock 3.2 rooted (US 7.006.01_COM_GEN2). I got an ota notification for 7.014.01. Is there a rooted version of the ota I can flash via cwm?
From searching around, it's also looking like another ota ( 7.014.02?) Is right behind the 7.014.01. Is that true, and if so, is that available in rooted cwm-flashable form?
Neither available yet. (I'm waiting too. They were just released, so give them some time)
I wouldn't be so quick to update something, without first knowing what it is
Old saying "if it ain't broke, don't fix it"
A little more info on the update;
http://www.androidcentral.com/syste...ia-brings-market-update-and-improved-ui-speed
Yes, the 01 and 02 will break root. But, never fear, I rooted it for you. Here's the link
http://forum.xda-developers.com/showthread.php?t=1307539&page=12
Very cool
Although I don't need it, it's nice to know some people are still doing some neat things for stock 3.2.
update without wiping?
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
There are some roms currently in the works for 3.2.1. I'd expect them to come out fairly soon, keep an eye on the development forum. A few guys working on them right now.
mpkrcl said:
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
Click to expand...
Click to collapse
Ok, if I hear you correctly, you are already rooted and want to use CWM to run the updates and keep root? Therefore you don't wipe out everything?
Piece of cake, just grab the update.zip and change it not to wipe your permissions. Then rebuilt it.
If you don't know how to do that, then put a backdoor into your device therefore you can get back into the device as root. Updates (normally) are not evil un-rooting tools. They don't seek and destroy root and rooting tools. Updates just reset the permissions on all files in /system removing the 'sticky' bit. The 'sticky' bit is how you get root.
What is a 'sticky' bit you ask? Well, in Linux (Unix) you can set a permission on a file so that any time it is run, it runs as the user that owns the file. This would be like setting a shortcut in Windows to say always run as 'Administrator'.
So, when you apply an update, the last thing it does is resets all the permissions back to their default. Since they recursively do this on the /system directory they remove the sticky bit on your su program.
So, all you have to do is set up a root backdoor outside the /system folder. My favorite is to set the ro.kernel.qemu = 1. This makes adb run as root. Now after your OTA resets permissions, you can just adb shell and you get #(root). Now you just reset your 'sticky' bits.
TD

Categories

Resources