Database Develop

[Q] I upgraded to FRG83D BIG MISTAKE. Want to get back FRG83

I update to FRG83D and I guess i lost root. I attempted to restore flash clock world mod again but .nothing happens when i confirm I tried to do a backup from Titanium backup and of course it says i'm not rooted. Then I tried to go into Superuser app and it asked me to update. I attempted to and I got an error the su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Sorry for the long winded explanation, but i'm totally frustrated. I've been trying to fix this for 2hrs. Oh yeah I originally got root using universal androot and it still says im rooted. I clicked unroot but it doesn't work. I'm confused cuz androot says i'm rooted, but Superuser and Titanium backup says i'm not.
PLEASE HELP MEEE!!! I would like to get back cmod 6.1
was this:
cmod 6.1 rc1-n1
clockmod 2.5.1
kernel: 2.6.35.7
Build num: frg83
Now i'm this:
Android ver: 2.2.1
Kernel ver: 2.6.32.9-27240
Baseband ver: 32.36.00.28U4.06.00.12_7
Build num: FRG83D

fastboot oem unlock

Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App

crachel said:
fastboot oem unlock
Click to expand...
Click to collapse
lol damn you evil bastards
Have some pity for the newbs

Newbs should start reading Wiki instead of wasting hours on irrelevant stuff

danger-rat said:
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thank you danger-rat. I'm back to stock frg83. It only took about 10mins. Now I'm trying figure out how to get back to root. None of the one click methods seem to be working. Superoneclick, z4root, androot. Once again Thank YOU

Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.

dls5375 said:
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
Click to expand...
Click to collapse
Is it the case for a Nexus One replacement unit that has never been rooted or altered in any way? I got it with FRG83 and installed FRG83D as soon as I received it. I tried SOC method but it was stuck on 'waiting for device' message. Not sure if it is because of an old XP machine or HTC Evo cable I was using.

Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.

Jack_R1 said:
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Click to expand...
Click to collapse
I tried both SOC 1.5.1 and 1.5.5 with .net 2.0.5x in the XP machine. I just used the files included in the zip, isn't it that it has latest Nexus One drivers too? Sorry, I am a Mac,Linux guy and not much experience with ADB stuff on Windows.

It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.

Jack_R1 said:
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Click to expand...
Click to collapse
Thank you! I guess I have no other option but to install Windows on my Mac. I was feeling lucky and I thought Linux or Mac can use SOC but it is proving difficult and I haven;t come across a single reply who stated success on Linux/Mac!

Uh, why SOC? Use any of the others you just run directly on the phone..

khaytsus said:
Uh, why SOC? Use any of the others you just run directly on the phone..
Click to expand...
Click to collapse
They don't exist for FRG83D just yet and I am not sure if we can downgrade to FRF91 or some other firmware without unlocking bootloader.

You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.

Jack_R1 said:
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Click to expand...
Click to collapse
Is it true for Mac too? My previous attempts with VMWare and Parallels failed while trying to use USB at low level. I guess it is worth a shot, thank you!

when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.

dls5375 said:
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
Click to expand...
Click to collapse
Tried that already, no go..

kkiran said:
Tried that already, no go..
Click to expand...
Click to collapse
With all the time wasted searching for other methods, you would have had root on your device already if you just did it manually. It is so simple, takes like 20 mins, and it doesn't require a Windows PC.
I really don't understand why people search for so long for a "1-click" when doing it manually doesn't take that much more effort.
Rooting so is simple with the binaries available:
1) Put rageagainstthecage on your device, change permissions to allow it to run, run it, and presto, it gives you a root shell.
2) Now that you have a root shell, all you have to do is put su in the /system/bin directory, change the permissions so that it can run, and presto, you have root.
And given that rageagainstthecage exploits a vulnerability in the way adb works, this method will work for all devices without a NAND lock.

Rageagainstthecage so easy a caveman can do it.
Sent from my Nexus One

[Q] How to Root Moto Droid running 2.2.3

I have looked around the forums and google searched this for the last hour. I've been trying to root it with SuperOneClick and Pete's Motorola Root Tools and have had no success. The build number is FRK76. My brother updated it and i can't root it anymore. Any help will be accepted.

I am having the same issue. Any rooting options out there for 2.2.3? Someone out there please help out.
Thanks...

Same problem here. It got updated to FRK76, cant find any support to root it.

I found that using Superoneclick v1.7 works when you use the rageagainstthecage method. This was the latest version I found that included this method; it has been removed in later versions.

Root 2.2.3 (FRK76)
I had the same problem:
Current version of SuperOneClick could not root my Droid (2.2.3 FRK76)
Downloaded SuperOneClick 1.7,
ran it (selecting rageinthecage option)
and it succeeded in rooting my phone.
Thank you!
- michael
PS: I got v 1.7 here
jaymode said:
I found that using Superoneclick v1.7 works when you use the rageagainstthecage method. This was the latest version I found that included this method; it has been removed in later versions.
Click to expand...
Click to collapse

slsmag said:
I had the same problem:
Current version of SuperOneClick could not root my Droid (2.2.3 FRK76)
Downloaded SuperOneClick 1.7,
ran it (selecting rageinthecage option)
and it succeeded in rooting my phone.
Thank you!
- michael
PS: I got v 1.7 here
Click to expand...
Click to collapse
hi my virus scanner says there is a virus in the .zip file is that normal and will it do no harm?

eaglesfan398 said:
hi my virus scanner says there is a virus in the .zip file is that normal and will it do no harm?
Click to expand...
Click to collapse
I can't vouch for that zip file but yes version 1.7 will get flagged by your virus scanner. I posted in the other thread where I got my version of 1.7 from and the link has a description of why it gets flagged by your virus scanner: http://forum.xda-developers.com/showthread.php?t=1406287&page=2

Root Droid using 2.2.3 with Mac OS X
Can someone point me to step by step instructions on how to root my Droid 1 running 2.2.3 using my Mac running Snow Leopard 10.6.8? I've searched quite a bit so far and have not come across what I need. I have not rooted before, and I'd like some help. Everyone here seems to be the most helpful I've seen on most forums so I figured this would be the place to ask. All assistance is greatly appreciated.
I tried using mono and running SuperOneClick v 1.7 with the rageinthecage option and it failed, also failed using all other exploits in both the 2.3.3 version on SOC and the 1.7 version of SOC.
Each time I try I get "Automatic version checking failed, Is your OS 2.0 or higher?" with options of YES, NO, OR CANCEL. No matter what i choose, the process stops.
Is using mono the problem? I am willing to try anything manually or otherwise, I just need some guidance. Thanks in advance!
Nate

Never mind, I've got it taken care of

How did you get it taken care of?

I am officially a sap. I download all excited thinking "hey, maybe wireless will finally work on a wpa2 encrypted network." But of course we should not fix a serious usability issue. Instead lets take away root making it even harder to use the device.
Err.. I simply meant to say, "hey, thanks for the tip on getting superoneclick 1.7 to do the jpb!"

UniversalAndroot is what you looking for.

I was able to use the latest SuperOneClick w/ my Droid @ 2.2.3 and it worked the first time on Win7 64-bit. I don't remember my build number (it seems to have changed since installing CM7), but I got it in January of 2010.

so ive been at this all day reading and searching these forums with no luck.
i have a droid one, running 2.2.3 FRK76, bought the phone used. says it has kernel version 2.6.32.9-g68eeef5. no clue what this is.
have tried to root with superoneclick with rageagainstcage option clicked. also tried the one click some one had posted on this site in one of the forums. Sd card is unmounted. debugg mode is selected. and i cant get past first time it says waiting for device. what do i do? im usign windows xp

First, it's but joined up as mass storage it's it? Also run one chick as admin if you aren't
Sent from Tyler`s Tweaked Charge

I know I'm kinda late to the party but my brother brought me a Droid and I was finally able to root with unlockroot.com I tried everything else suggested and this finally worked first try. It's funny but I don't remember it ever being that difficult before.
Sent from my SPH-D710 using XDA

I have an old Droid 1. I would like to root it and assume the 1.7 is what I need. After that where can I find roms. I only could find a thread for the Droid 2.
life is better with root.

links for rooting
I am having the same problem. I have been at this for 2 days now trying to root my droid 2.2.3. I tried
psouza4 method
it didnt work. I got the error message:
ERROR: adb could not be granted root access via local.prop method
Try again from the start, but if the problem continues, check your version
of Gingerbread -- hopefully you don't have a version where this exploit
was fixed.
then I tried to download super one click and I couldnt find the link....
I need help... anyone??
THANKS!

HTC VIVID Super User Problems....

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.

Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.

Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App

Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.

Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.

Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?

*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.

slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...

Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?

slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated

Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4

Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....

Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.

slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help

Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

[Q] Incredible S (2.3.5) refuses to root!?

Hey,
For the past 6 hours i've been trying to root my Incredible S so i can install ICS 4.0.3 and i've just had no luck!
I have absoloutly no 'rooting' experience (jailbreak experience, yes) and i have no idea how to install custom firmware/images/roms ect.
For the first 4 hours i just tried to get rid of S-on, after reading through about 50 articles i gave up and was told to go to htcdev.com and unlock my bootloader, which is done but i can't root the phone!
I've tried the following:
HTC Supertool v3 - Unlocked my bootloader but failed with 'S-on', said my phone was rooted but is not...
SuperOneClick - Looks like it worked but didn't...
Unlock Root - 'Failed to access Shell root'
Universal Androot - Incompatible
z4root - First time, got stuck on 'Running exploit in order to obtain root access'
Second time, got to 'Attempting to apply root' and stayed like that forever (tried removing battery and restarting)
My phone may (MAY!) be rooted, i was told to download ConnectBot and if it had '$' i was not rooted but if i had '#' i was, nevertheless it came up with '$'....
Please help! I am desperate to get TRUE ICS (and none of that ****ty HTC ICS thats coming soon...)
Thanks, Danz207

UPDATE!!
I had z4root version 1.10, so i upgraded to 1.30 and this time the second step was called 'Acquiring root shell' or something like that and then it closed, but it wasn't a crash, it faded out within half a second. Anyway i opened 'Rom Manager' and it told me that i needed to root first and ConnectBox still has '$'.......

Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate

Have you tried the two links at the top of the dev forum? Read through them and you should be fine

Thank you markj338
markj338 said:
Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate
Click to expand...
Click to collapse
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!

danz207 said:
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!
Click to expand...
Click to collapse
LOL seems you're happy

[Q] PASSIMG.ZIP Really Screwing Me Up

I've rooted my Nexus One a long long time ago, and eventually reverted to it's original state. Let's skip ahead a year..
I wan't to use my Nexus One again until I can get my hands on a Nexus 4. I'm trying to root this bad boy, but run into a problem with every method. I got the one click method to work, but it wouldn't boot up. And when I try to go into Bootloader for recovery, it checks for the PASSIMG.ZIP file and then updates. If I click no, it makes no difference, it doesn't let me do anything. Updating will restore the phone to stock(unrooted). So I deleted PASSIMG.ZIP from the SD card. Ever since, I can actually click on Recovery, but I run into trouble(see further below). S is ON btw, I don't remember what this was, but I'm sure I had it OFF before? I have been using an iPhone for the past year and a half, so I apologize for being a noob. I'm not to tech savvy when it comes to these terms, either.
Short explanation:
One Click Root - I can root it, but when I go to Bootloader Recovery it shows the Android guy and a triangle around !
Using the old school method using Windows terminal, recovery-clockwork-5.0.2.0-passion.img was flashed without problem.
But I can't access Recovery!
In the end I'm trying to at least have an ICS ROM, or Jellybean(Really wanna try Google Now or whatever) if possible.

Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.

tommert38 said:
Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.
Click to expand...
Click to collapse
The unlock padlock icon means the bootloader is unlocked, correct? I've done that. And I actually went through that, and flashed the custom Recovery, still the same result. I'll retry it again.

I figured it out, but I don't get it...
I did this in kind of a different route, so just incase someone runs into a similar problem some how:
I rooted the phone using the one click root software on a windows PC, the N1 was successfully rooted.
However, same error recovery, even after adb flashing recovery(followed wiki and unlockr tutorial).
What I did different to fix the issue, was after the root, I downloaded Rom manager(yes I've done this before too, but...), I flashed the recovery via Rom Manager. After it didn't work(sadface).
I tried it again, but just out of frustration I re-flashed it after flashing. So I flashed the recovery twice, back to back. And poof, I check bootloader, go into recovery, and there it is(just like it used to be).
Close this I guess, (an embarrassing)problem has been solved.