So i attempted the mac root method found on the general forum, had a couple flags come up in the terminal while rooting and now I have no cellular reception.
AT&T SGS3. Only a slashed circle in place of cellular bars. Here's the terminal log:
results of terminal root:
waiting... If you get stuck here, try another USB port.
Start Rooting...
3174 KB/s (1862336 bytes in 0.572s)
2975 KB/s (91980 bytes in 0.030s)
42 KB/s (142 bytes in 0.003s)
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 2098
debugfs: debugfs: debugfs: debugfs: reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
RootMac.sh: line 40: unexpected EOF while looking for matching `"'
RootMac.sh: line 42: syntax error: unexpected end of file
What did i do? how do i fix it?
I am by no means a mac user but looking at your terminal output it appears the file you were trying to flash was incomplete, or was disconnected before the flash was completed....hence the 'unexpected end of file' error. I would suggest redownloading whatever you used and run it again. Worst case scenario you can always flash back to stock using whatever the preferred method on mac is, not being a mac user i am at a total loss what this might be so maybe some of the other mac users can lend a hand in that department.
Related
now i know this is pretty basic i couldnt find anywhere that tells you how to root on linux or any other unix os but here it is. Thanks goes to bubby!!! PLEASE check out his original post and HELP HIS EFFORTS
FOR bubbys ONE CLICK ROOT BUSYBOX INSTALLER SAMSUNG CONTINUUM V0.1!!
Finally, i after days of searching and trying to execute the commands for this root Manually i pulled my sd, and Formatted my phone and then Found the command to run the one click root on my continuum.
MAKE SURE YOU BACK UP YOUR FILES!! ITS A MUST,, ALSO DEFINATELY ODIN BEFORE THE ROOT.
Next, Open terminal Locate your Unzip folder i recommend you place the folder near your sdk folder Ex. CD ~/android-sdk-linux_x86/oneclickroot
since we've located the destination Check to make sure your in the right place ls. Look at the list make sure you see the run.sh Ok Now Type in the terminal
sh run.sh you should then see
One Click Root v 0.1 for the Samsung Continuum
Scripted by bubby323
read: 11: Illegal option -n
[: 18: Linux: unexpected operator
-e
Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
-e
Copy and run the exploit (may take up to two minutes)
74 KB/s (5392 bytes in 0.070s)
0 KB/s (43 bytes in 0.075s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2961
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
it comes to adb connection will reset, restart adb server on desktop and re-login.
unplug your phone and wait 10sec and plug it back in
then you should see
Wait for phone to reconnect...
run.sh: 77: [[: not found
Mount system as r/w, cleanup old files, do some basic configuration
rm failed for /system/bin/playlogo, No such file or directory
failed on '/system/bin/playlogo-orig' - No such file or directory
Unable to chmod /system/bin/playlogo: No such file or directory
63 KB/s (4793 bytes in 0.073s)
Copying files onto phone...
361 KB/s (26264 bytes in 0.070s)
1120 KB/s (196521 bytes in 0.171s)
1219 KB/s (978414 bytes in 0.783s)
1207 KB/s (486948 bytes in 0.393s)
9 KB/s (483 bytes in 0.051s)
Setting permissions...
Installing busybox...
Waiting for phone to reboot...
run.sh: 117: [[: not found
Cleaning up files...
read: 129: Illegal option -n
now your rooted to check go to the market and try installing Titanium back-up
if all goes well you have root access
Hi people.
I realize that the usual response to threads like this is "read the forum" but I honestly have, I've tried several guides but I get no luck.
So if anyone would please help me out, it would be much appreciated and maybe helpful for others.
The way I've understood things is that I need to
1. Temproot
2. Downgrade using a goldcard.
Using this guide
HTML:
http://forum.xda-developers.com/showthread.php?t=1152233
I think I've managed to temp root;
1. Temproot:
C:\DHDDowngrade>root
C:\DHDDowngrade>adb push fre3vo /data/local/tmp
1195 KB/s (9796 bytes in 0.008s)
C:\DHDDowngrade>adb shell chmod 777 /data/local/tmp/fre3vo
C:\DHDDowngrade>adb shell /data/local/tmp/fre3vo -debug -start FBB00000 -end FFF
FFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region fbb00000...
Potential exploit area found at address fbb7f800:1800.
Exploiting device...
I do get kicked back to the command prompt, but if I type "adb shell" I do get the "#" that I'm supposed to be getting.
Right - so far so good, right?
2. Downgrade
As instructed in the guide, I run the commands as follows
C:\DHDDowngrade>adb push misc_version /data/local/tmp
1288 KB/s (15837 bytes in 0.012s)
C:\DHDDowngrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\DHDDowngrade>adb shell /data/local/tmp/misc_version -s 1.31.405.3
--set_version set. VERSION will be changed to: 1.31.405.3
Patching and backing up partition 17...
Error opening input file.
C:\DHDDowngrade>adb reboot bootloader
There is an error here, but I haven't found anyone else having this problem, and don't even know if it really is a problem.
So I've ignored it, and continued on creating a coldcard.
I've tried using Goldcard manager from the market, I've tried retrieving the reverse CID manually. I've pasted the data from the generated image file onto the card and saved. A few times I've not been able to paste PD98IMG.zip on to the card afterwards, giving me the error that the card must be formatted to work, but lastly it would let me copy. If I try reading the card, I do get the error that the card has to be formatted. My HTC also tells me theres something wrong with the SD card. I've ignored this, and booted into the bootmanager. For a split second theres a green text saying something i along the lines of "PD98IMG image not found".
And so it ends, I can't get any further.
So the questions summarized are;
1.Is this the correct order?
2.Am I rooted, even if I have to type "adb shell" to get the "#"?
3.When dowgrading, is the "Error opening input file" fatal?
4.Is the card supposed to be unreadable after pasting the hex data onto it?
Sorry for the neverending post, but getting a custom rom onto my Desire HD has been very, very hard. Unsuccesful so far. Please help me out
Best regards from Norway.
Hi there noticed no one has replied I have plenty of time to help you out the best I can. I recently did this last week and had no problems. Im still learning myself so sorry if i am not the best of help.
wow long post
After skimming your post I did notice something. I pretty sure that you need to create a gold card first. If you still have problems creating a GoldCard get back to me but here is the link:
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
I then followed this tutorial to downgrade:
http://forum.xda-developers.com/showthread.php?t=905003
and then use the s-off tool :
http://forum.xda-developers.com/showthread.php?t=857537
hope that helps, get back to me if you need help.
I used these two guides when rooting my DHD, I also had to use a goldcard but the link for that is in the downgrade page below.
1. Downgrade
http://forum.xda-developers.com/showthread.php?t=905003
2. Root + Radio installation + Rom installation
http://forum.xda-developers.com/showthread.php?p=11557769
As far as I know, the two links above are the correct order, as long as you get the # its safe to proceed and the card should be usable after you make it into a goldcard, at least I still use mine. Oh, and you shouldn't receive any errors throughout the process, it might not be fatal but why take a chance.
ace hack kit
use the ace hack kit to steps you can't get wrong
http://www.google.com/url?sa=t&sour...sg=AFQjCNFFmKIBniFFp-RmQV7lN2Ma-n9dzQ&cad=rja
TheJokah said:
use the ace hack kit to steps you can't get wrong
http://www.google.com/url?sa=t&sour...sg=AFQjCNFFmKIBniFFp-RmQV7lN2Ma-n9dzQ&cad=rja
Click to expand...
Click to collapse
Thanks to all of you for replying.
My head was spinning after going through different tutorials and problem solutions - and I had frankly given up the whole thing.
But TheJokaH's one-click method seemed intriguing so I decided to give this one.last.shot. And it worked!
I don't know why this isn't posted as the only sticky thread at the Q&A section - because is definitely the only way to get one started with custom roms.
Thanks again!
I am trying to root my quad core MX, (mainland running flyme 1.0.3) using Adam's Casual [http://forum.xda-developers.com/showthread.php?t=1885789]
I click "Do it" in causal, and it prompts me to click again, when the screen has gone black. (Is this when it starts to reboot? When I do that I get an error message:
Rebooting...
Step 2 - Rooting...debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 921
debugfs: debugfs: debugfs: debugfs:
Cleaning up...
Restoring tmp...error: device not founderror: device not found
...done restoring tmperror: device not found
done.
------------------------------------------------------------------------------------------
MX-Root
by AdamOutler
adapted from the Transformer Prime script by sparkym3
http://forum.xda-developers.com/showthread.php?t=1706588
and the root method by miloj
http://forum.xda-developers.com/showthread.php?t=1704209
------------------------------------------------------------------------------------------
--Copying files--
Copying su:
------------------------------------------------------------------------------------------
MX-Root
by AdamOutler
adapted from the Transformer Prime script by sparkym3
http://forum.xda-developers.com/showthread.php?t=1706588
and the root method by miloj
http://forum.xda-developers.com/showthread.php?t=1704209
------------------------------------------------------------------------------------------
--Copying files--
Copying su:error: protocol fault (no status)protocol failure
Copying debugfs:
Copying debugfs:error: device not founderror: device not found
Copying debugfsinput:
Copying debugfsinput:error: device not founderror: device not found
...done copying files.
Backing up tmp and Linking /system to tmp...
...done copying files.
Backing up tmp and Linking /system to tmp...error: device not founderror: device not founderror: device not founderror: device not found
...done linking /system
...done linking /system
Rebooting...
Rebooting...error: device not founderror: device not found
Step 2 - Rooting...
Step 2 - Rooting...debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 921
debugfs: debugfs: debugfs: debugfs: debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs:
debugfs: Allocated inode: 921
Cleaning up...
Cleaning up...
Restoring tmp...
Restoring tmp...error: device not founderror: device not founderror: device not founderror: device not found
...done restoring tmp
...done restoring tmperror: device not founderror: device not found
done.
done.
Needless to say, i hasn't worked. (I would replied in the thread I linked to, but for some reason I wasn't able to...)
casual 1 click
i tried casual 1 click for my at&t s3,received the following error:
too many devices detected.
any help would be appreciated
Please do not thank me, this is not my work. This is pruly FYI[
Hey all, here's a great How to, on rooting w/ a Mac
http://www.youtube.com/watch?v=2xykRe9IcOE&feature=em-uploademail-new
Will this work on Ubuntu linux as well?
Great job, thanks man! Cant make it much easier than that!
quiiiick problem
So i just used this method for root, everything went...ok?
now that my phone is rebooted, i've got no cellular connection. No data, no calls. Wifi works fine. nothing but a slashed circle in place of signal.
What have i managed to do with something this simple?
Seaborn111 said:
So i just used this method for root, everything went...ok?
now that my phone is rebooted, i've got no cellular connection. No data, no calls. Wifi works fine. nothing but a slashed circle in place of signal.
What have i managed to do with something this simple?
Click to expand...
Click to collapse
reboot your phone
done that
Restarted multiple times, same result.
results of terminal root:
waiting... If you get stuck here, try another USB port.
Start Rooting...
3174 KB/s (1862336 bytes in 0.572s)
2975 KB/s (91980 bytes in 0.030s)
42 KB/s (142 bytes in 0.003s)
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 2098
debugfs: debugfs: debugfs: debugfs: reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
RootMac.sh: line 40: unexpected EOF while looking for matching `"'
RootMac.sh: line 42: syntax error: unexpected end of file
Seaborn111 said:
Restarted multiple times, same result.
results of terminal root:
waiting... If you get stuck here, try another USB port.
Start Rooting...
3174 KB/s (1862336 bytes in 0.572s)
2975 KB/s (91980 bytes in 0.030s)
42 KB/s (142 bytes in 0.003s)
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 2098
debugfs: debugfs: debugfs: debugfs: reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
RootMac.sh: line 40: unexpected EOF while looking for matching `"'
RootMac.sh: line 42: syntax error: unexpected end of file
Click to expand...
Click to collapse
As stated in the OP this is an FYI. I would suggest either commenting on the YTube vid or asking this question in Q&A.
This works great. Simplest root ever!
Y dis not in ur index so I cn unstk?
Hi evreyone !
I spent hours trying and reading posts everywhere I could without any success.
I'm trying to follow this rooting guide: http://forum.xda-developers.com/showthread.php?t=2634196 (Root and Dual Recovery for Locked Bootloader) and I'm stuck in a bootloop at step 10.
I'm using the last Z1C-lockeddualrecovery2.7.117-BETA.installer.zip and I noticed an error during recovery installation (after DEVICE WILL NOW REBOOT!):
Code:
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
(Note that I'm using Linux... I tried to run the bash script both as a user or as root)
If I continue the rooting process by flashing D5503_14.2.A.1.114_Generic UK.ftf (step 9), I'm stuck at step 10 as I can't boot any recovery. The phone is stuck in a bootloop, and after the green light pressing vol up (ou down) won't do anything...
I tried the whole process (from the begining: docomo) several time and end up everytime with the same result: an error at the end of the recovery installation and a bootloop at step 10 that prevent me from entering any recovery...
I'm out of ideas ! What can I do to manage the installation of the recovery ?
OldBeurt said:
What can I do to manage the installation of the recovery ?
Click to expand...
Click to collapse
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Thanks for your answer !
XperienceD said:
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Click to expand...
Click to collapse
Since I don't have access to any recovery, I don't understand how I can follow this guide (step 5: Go to recovery menu[...]).
What did you meant ?
OldBeurt said:
I don't understand how I can follow this guide (step 5: Go to recovery menu[...])
Click to expand...
Click to collapse
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
XperienceD said:
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
Click to expand...
Click to collapse
Of course I red the requirements. The root method described is the same (http://forum.xda-developers.com/showthread.php?t=2642081) than the one I followed (http://forum.xda-developers.com/showthread.php?t=2634196). And so the result is going to be the same: being stuck in a bootloop after flashing the recovery form the computer (flashing witch returns an error that I quoted above).
I need help to "recover" the recovery, I mean to be able to properly flash the dual recovery on my phone (whether I wish to unlock the bootloader or not is not the point for now, since I need to root with the locked bootloader in the first place).
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Thanks for your input !
zxz0O0 said:
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Click to expand...
Click to collapse
I don't know where the error came from, but I tried several times (about 10) and it end up the same way ! I will try on another machine (Linux too).
zxz0O0 said:
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Click to expand...
Click to collapse
Yes I'm using install.sh, I just pasted the relevat part of the output, but here I paste all of it:
Code:
Will attempt to get root to install!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 0.056s)
362 KB/s (17768 bytes in 0.047s)
325 KB/s (15578 bytes in 0.046s)
11 KB/s (501 bytes in 0.043s)
272 KB/s (11791 bytes in 0.042s)
3186 KB/s (44383 bytes in 0.013s)
70 KB/s (3082 bytes in 0.042s)
9 KB/s (385 bytes in 0.041s)
3645 KB/s (657704 bytes in 0.176s)
3521 KB/s (2597754 bytes in 0.720s)
3936 KB/s (1842873 bytes in 0.457s)
5217 KB/s (2447499 bytes in 0.458s)
193 KB/s (8124 bytes in 0.041s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread on XDA for more details.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================