Database Develop

[Q] SuperOneClick ROOT failing, please help

Hey guys - self-admitted n00b here : )
I've been trying for the past couple hours to follow ND1 Razors guide to root 2.3.4. NOTE: I tried to provide the link but I'm new to the forums so it won't let me
All was going well up to step 10...
When using SuperOneClick and following Razors detailed directions, I get the following failure:
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting manufacturer...
END:36496
OK
Getting model...
END:94500
OK
Getting version...
END:22067
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
1253 KB/s (1062992 bytes in 0.828s)
OK
Installing BusyBox (temporary)... - Step #2
END:8949
OK
Rooting device... - Step #1
1220 KB/s (585731 bytes in 0.468s)
OK
Rooting device... - Step #2
END:7192
OK
Rooting device... - Step #3
END:8007
OK
Rooting device... - Step #4
END:39931mmap() failed. Operation not permitted
FAILED
ANY help here would be AWESOME - I am VERY MUCH looking forward to root and using cyanogen.
I'll be purchasing an HTC Sensation pretty soon and from the research I've done, it sounds like root will be achieved sometime in September on that device once HTC unlocks the bootloader! I'm trying to root my N1 now so I am a bit more "seasoned" before I go bricking a purdy new and EXPENSIVE device
HELP!?!? lol please and thanks of course

Actually s-off on the sensation is going on right now, for the past few days even.
To answer your question, just passimg back to original and root from there, or even just fastboot oem unlock and root.

Thanks for the quick reply Evil - but like I said - I'm VERY n00bish when it comes to root.
I'm on FRG33 right now - superoneclick is failing at the point I mentioned above
My drivers are up to date (I believe) and have SDK
since its possible to root without unlocking - that was my first choice but I will do WHATEVER I CAN do.
Getting to step 10 out of 17 and then failing SUCKS.
Any SPECIFIC answers to get me root (using the above method or otherwise) would be appreciated

Have you tried the other methods in the wiki?
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root

Make sure your rooting with the rageagainstthecage method cause if you try to use the gingerbreak method it won't work.

I am having the exact same issues. I am also a total n00b at rooting, and SuperOneClick is failing at "Rooting device- Step #4 mmap() failed. Operation not permitted FAILED"

If you are running 2.3.4, there isn't any way to run an exploit and get root. The only way to root the phone is to: 1. unlock the bootloader and flash a custom recovery taht allows you to flash a zip containing the necessary files (which if you are want to install CM, it isn't necessary to root it at that point as you can just install CM from the custom recovery) --or-- 2. Use the passimg method to bring your phone back to a froyo version and use SuperOneClick's rageagainstthecage exploit to gain root access.

fre3vo might work for 2.3.4, but needs testing, and I don't have the time to test.
http://forum.xda-developers.com/showthread.php?t=1150006
How to run:
http://forum.xda-developers.com/showthread.php?t=1178912

How do I root the frk76 OTA update?

I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.

SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.

SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)

Don't know what the above means
Does 2.3.1 work without modification?

While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?

Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!

sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?

envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.

Pete has a stock rooted FRK76 Rom on his website, fyi

My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.

flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.

I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.

Is there a RUU i can run to unroot my phone?

YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.

stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one

YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site

[Q] How to root SGNote without Wiping/Changing FW

I have a White Galaxy Note which came with Gingerbread 2.3.6 N7000DXKL2 preinstalled. However, since Chainfire does not support KL2 firmwares, I've opted to upgrade it to N7000DXLC1 via Kies. When I tried the Chainfire CF-Root flasher method (including the correct zImage) here's what happened:
---------------------------------------------------------------
Initial CF-Root flasher, by Chainfire
Credits:
Easy rooting toolkit by DooMLoRD
zergRush by Revolutionary Team
Gingerbreak/Honeybomb by The Android Exploid Crew
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) flash CF-Root
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
(7) !!! PUT A CF-ROOT zImage FILE IN THE zImage FOLDER !!!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
2251 KB/s (23052 bytes in 0.010s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android E
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---------------------------------------------------------------
We should have (temporary) root now
We will try to flash CF-Root kernel now
Please watch for any errors beyond this point!
---------------------------------------------------------------
Press any key to continue . . .
--- pushing zImage
2650 KB/s (8387840 bytes in 3.090s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
---------------------------------------------------------------
If all is well, CF-Root should be flashed
Your device should be rebooting now
Please check if you have root and CWM after boot completes!
---------------------------------------------------------------
It still isn't rooted. Is there another method? I don't want a full wipe of the phone and I don't want to change to Custom ROMS because my sole purpose of rooting the device is to backup its current firmware since there's been a lack of pure stock roms for the SGN in my country and I wish to provide an unadulterated ROM to my fellow countrymen. Plus I need something to get back to since SamFirmware isn't a very reliable source.
Details
Samsung Galaxy Note White
Version 2.3.6
Baseband Version N7000DXLC1
Build Number GINGERBREAD.DXLC2
Region: XTC (Philippines: Open Line)

Your decision was wrong, you didn't fully understood the chainfires advise OR you have not read it completely. Here what you have missed in chainfire's thread.
-Your previous ROM was likely rootable,b'coz upto KL3 most of ROM is directly rootable it is not necessary to have same kernel to use.
Read this
chainfire have clearly said :
Don't worry too much, just find the matching download and use it. What if there is no matching download ? You can ask me to make one, but I can tell you right now, I very very rarely make CF-Root's for kernels on request, unless it is the very latest kernel that has been released by Samsung. In the latter case, be sure to let me know. If there's no match and I'm not making one, try finding the closest match. You should treat "KJ4" as a number, but instead of 1-9, we have 1-9, A-Z (where A would be 10, and Z would be 35). "KJ3" is really close to "KJ4", "KF1" is not close to "KG4" at all. I hope that makes sense.
Click to expand...
Click to collapse
So it is clear that you need to use Kl1 kernel to root your ROM
Another thing you have missed is.
Read this from chainfire
1.2. If you are not rooted yet: Using the zergRush exploit This method no longer works on KL* and newer firmwares!
Click to expand...
Click to collapse
So hear again you did wrong, you have updated to LC1
That is non rootable, Cf have provided kernel for LC1, but it can't root your ROM LC1. it is for updating kernel, but you need to have root.
So Now you have option to root is
Downgrade to any directly rootable ROM, Root it, then update to latest ROM with Mobile odin/CWM
You can dowload guide form last link on my signature to get detail assistance for total procedure.

dr.ketan said:
Your decision was wrong, you didn't fully understood the chainfires advise OR you have not read it completely. Here what you have missed in chainfire's thread.
-Your previous ROM was likely rootable,b'coz upto KL3 most of ROM is directly rootable it is not necessary to have same kernel to use.
Read this
So it is clear that you need to use Kl1 kernel to root your ROM
Another thing you have missed is.
Read this from chainfire
So hear again you did wrong, you have updated to LC1
That is non rootable, Cf have provided kernel for LC1, but it can't root your ROM LC1. it is for updating kernel, but you need to have root.
So Now you have option to root is
Downgrade to any directly rootable ROM, Root it, then update to latest ROM with Mobile odin/CWM
You can dowload guide form last link on my signature to get detail assistance for total procedure.
Click to expand...
Click to collapse
Well, it's not easy to read and it's very easy to misunderstood on what he said. Contrary to what you said, it's not even close to clear and what you said about the previous firmware is rootable contradicts to what chainfire said about KL firmwares.
Please don't say that "it is clear", It's insulting my intelligence. I read it a lot of times and I also read some comments (that's how I got the idea of upgrading to get root availability). I've already upgraded it to ICS so the topic is now irrelevant. Now I'm trying to figure out how to backup the firmware without rooting and sending it to the community so that at least our country has an entry on samfirmware.com. I lost hope in rooting the Note and since it's not mine (it's my sister's) and most apks just run fine even without root, I don't think I'd pursue having it rooted unless it can enable me to format the microSD card to a better file system aside from FAT32.

Why you are asking Questions If You are that much intelligent....???
Dr. Ketan is one of Most Respected Senior member Of XDA.. Look his Thanks meter.... You are very lucky that Dr.Ketan was Replied You.
Now Don't be angry with me... I am posting this becouse We Respect him...
No Need to Reply... I am not going to visit This Thread again...

[Q] bionic jb 98.72.22 su binary help! root access?

So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )

You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium

linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?

MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/

Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T

To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium

toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.

Installing rooted ROM on a phone that's not rooted

Hello guys! I have Xperia T 9.2.A.0.295.
I've tried a couple of methods of rooting my phone and all failed:
- rooting via flashtool, when "make it ra1n" appears, phone just restarts
- rooting via first method listed in this subforum, when running .bat file it gets stuck @ *daemon started successfully*
- rootin via towelroot, when I try to install it, it simply says "App not installed".
My idea was following, but I'm afraid to execute it without you guys having my back or I know it will be broken (back or phone or both hehe)
I wanted to try to push CWM via fastboot (already got drivers installed and all options defined correctly, unknown sources, debugging etc.)
I wanted to follow this tutorial with this CWM: http://forum.xda-developers.com/showthread.php?t=1918966
1. So, if I install rooted ROM, is my phone going to be rooted or not? Or is installation going to fail? (some people were mentioning it's very likely phone is gonna end up bricked...)
2. If I install this CWM (since it's from 2012) am I going to have problems installing ROMs developed in 2015 (eg. 4.4.4 or 5.x?)
3. Is there a way I could back my current software up just in case something goes wrong so I could restore it in case of a fail?
Thanks guys!
If anyone has FB and maybe would like to add me just so I could contact him if things go south, feel free to send it to my PM, I'll add you

OK, I found older firmware on XperiFirm (9.2.A.1.199) from the vendor I bought the phone from. Later the phone was unlocked, I sure hope it doesn't lock again or something.....Since I moved to another vendor.
I'm downloading now, but I'm thinking about sleeping through the night 'till someone answers because I'm having a feeling I'm gonna wreck something...

Did you tried THIS ?
It works for me

Sorry for replying so late, didn't work for me, but I'm working on it with Olivier, he helped me