Problems with rooting - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I followed dr ketan's guide to root my Note. When I ran the BAT file, it went until the following place and stopped:
--- STARTING ---
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *
Waited for about 15 minutes, but nothing happened. So I removed the cable, connected back and tried again. The bat file will now stop at the line:
--- STARTING ---
--- WAITING FOR DEVICE
Tried disconnecting and connecting again with the same result. What could have gone wrong?
I've installed Samsung Keys on PC and the kernel version is 2.6.35.7-N7000DDLA5-CL919506 [email protected] #2, if that makes any sense.

Did you enable allow unknown sources and also under development enable USB debugging? I am running ICS, so can't look it up exactly. Check that once if not then you may want to temporarily disable firewall etc to allow the script to finish.
Hope this helps.

krishsastry said:
Did you enable allow unknown sources and also under development enable USB debugging? I am running ICS, so can't look it up exactly. Check that once if not then you may want to temporarily disable firewall etc to allow the script to finish.
Click to expand...
Click to collapse
Yes, I've enabled both. You think it may be a firewall settings problem? I don't have admin rights to change them in this computer.

thameera said:
I followed dr ketan's guide to root my Note. When I ran the BAT file, it went until the following place and stopped:
--- STARTING ---
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *
Waited for about 15 minutes, but nothing happened. So I removed the cable, connected back and tried again. The bat file will now stop at the line:
--- STARTING ---
--- WAITING FOR DEVICE
Tried disconnecting and connecting again with the same result. What could have gone wrong?
I've installed Samsung Keys on PC and the kernel version is 2.6.35.7-N7000DDLA5-CL919506 [email protected] #2, if that makes any sense.
Click to expand...
Click to collapse
You have used my guide, but have you read it properly?
My guide starts from page Rootable n Non rootable ROM.
Your ROM is LA5 which is nonrootable
If you have not downloaded my recent guide, just download it from last link on my signature, follow it. it will answer all your questions.

dr.ketan said:
You have used my guide, but have you read it properly?
My guide starts from page Rootable n Non rootable ROM.
Your ROM is LA5 which is nonrootable
If you have not downloaded my recent guide, just download it from last link on my signature, follow it. it will answer all your questions.
Click to expand...
Click to collapse
Sigh. I've always been bad at following guidelines.
It seems the only option is to downgrade first. Anyway having to stop the firewall and antivirus is also a problem coz I don't have access to a Windows machine with admin rights. Will see.
Thanks a lot!

does anyone know how to remove a preinstalled app, my tablet is rooted i just dont know how to remove a preinstalled app? any ideas?

use titanium backup. with great care on which app you uninstall.

praetorius said:
use titanium backup. with great care on which app you uninstall.
Click to expand...
Click to collapse
back it up first. Then freeze it. Reboot. If all is well for a few days, you may then uninstall, I reckon, but you don't really need to as freezing is enough.

Related

[HELP]cmd adb error msg...

I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum
Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!
SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
This IS in the wrong forum.
Moved.
Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...
And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )
the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb
The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.
virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that
Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,
I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis

Require some guidence Samsung Captivate

I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize
groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
After u root:
1. Go to market and search for busybox and install it.
2. Open busy box, and follow the steps in it install the required commands.
You should be good now.
mcord11758 said:
Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize
Click to expand...
Click to collapse
@mcord11758: * one more collision *
diablo009 said:
@mcord11758: * one more collision *
Click to expand...
Click to collapse
We are in sync
mcord11758 said:
We are in sync
Click to expand...
Click to collapse
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?
diablo009 said:
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?
Click to expand...
Click to collapse
I am in sales, but my educational background Is business
groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
Wow, I had my phone rooted and flashed within an hour of even learning what it all was.
Video tutorials are the best way to learn the basics, and once you have a grasp of what youre doing written instructions become easier to understand.
I recommend watching as many ROM review and install videos as possible, make sure to watch them more than once and while youre actually doing the steps.
thanks for the quick responce
I did download busybox from the market, but it tells me that everything is unavailable, and that my phone is rooted but my nand protection is still on. Plus busybox tells me that it can't find itself, whatever that means. lol
Pls let me know how to correct this.
By the way I used super 1 click 1.6.3 to root my device.
Thanks ppl your all awsome.
I also watched lots of videos, but could not find anything specific to my device. What other device videos are compatible in content with my samsung captivate?
thanks again.
Did you click install in busy box?
I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install
groovydude1981 said:
I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install
Click to expand...
Click to collapse
I would not use one click lash fix, but that is just me. If you want a lag fix consider a custom rom. One click lag fix is obsolete
thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.
some help
groovydude1981 said:
thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.
Click to expand...
Click to collapse
This is probably a great place for you to start.
http://forum.xda-developers.com/showthread.php?t=887525
there is a one click out there with root, unroot, and non market apps. i'm looking for it for you
EDIT
Here it is
http://forum.xda-developers.com/showthread.php?t=803682
Also before doing too much i'd familiarize yourself with the ODIN one click and learn about it as well as download mode so you know how to fix a bricked phone, well a soft bricked one.
I used super 1 click to root my phone, but anything you can send me is most appreciated. I will not be able to thank you enough.
Try rooting again with Galaxy one click root.
What will galaxy one click do for me that super one click wont?
They both essentially do the same thing. After your phone has been rooted you need to see if you can find the Super User app. It should be installed on your phone.
I've meant to update the Q&A sticky with what versions are easy to root.. so I apologize for not having it there.
When you install anything that requires root access (hence why your phone is rooted to begin with ) you would get a pop up requesting to have that application gain root access.
But.. there are only a few 3rd party apps that require root access if your not going to flash a custom ROM.
Titanium Backup btw will install the latest version of BusyBox for you - it is a highly used application to backup your system and applications for your phone.
Another highly used application is ROM Manager (used for flashing ROMs)
I would highly suggest you get familiar with how you restore your phone back to stock - then check out teh sticky under the dev forum on how to flash a custom ROM.
Then your on your way to becoming a fellow flash junky
I'm in the same boat as groovydude.
I have a 2 month old Samsung Captivate (first smart phone). I'm trying to root it. I have run SuperOneClick at least 6 times trying everything that I can find in the forums. I have drivers installed. Does anyone know if this tool will work on this phone, or if there is a tool that does. The output from SuperOneClick-ShortFuse is below. Every time it runs it tells me it is rooted, and every app that I open requiring root tells me it is not.
I have tried instructions to root via Update.zip. The instructions were to drop the file on the internal sd. When I plug the phone into the usb port, two drives show up. Nothing can be dropped on either. They both say to insert a disk. I have no external sd card. Does anyone know what might be the holdback?
Also, SuperOneClick said that BusyBox was installed, but I could not find it, so I downloaded Stericson's BusyBox installer. It failed to install with a message that the phone was now rooted but BusyBox was not found. It said the application failed because the phone is not "nand unlocked." What is nand unlocked? The only unlocking procedures that I can find instructions for are to unlock a phone from a carrier. Is this what "nand means"?
I tried Titanium Backup to install BusyBox, and it complains that the rom is not rooted after both other processes said it was. TI offered to download and install BusyBox and it failed too.
Does anyone know why all these procedures say that they have rooted the phone but nothing still works? Or what is nand unlock? and how is it done?
SUPERONECLICK OUTPUT:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
558 KB/s (585731 bytes in 1.024s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
974 KB/s (1062992 bytes in 1.065s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 1.5
OK
Remounting system with read-write access...
OK
Pushing su-v1...
640 KB/s (26256 bytes in 0.040s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1626 KB/s (196521 bytes in 0.118s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi-v7a
ro.product.model=SAMSUNG-SGH-I897
ro.build.tags=test-keys
ro.build.version.release=2.1-update1
ro.build.description=SGH-I897-user 2.1-update1 ECLAIR UCJH7 release-keys
ro.product.brand=Samsung
ro.product.device=SGH-I897
ro.build.version.incremental=UCJH7
ro.build.type=user
ro.build.date.utc=1282903617
ro.board.platform=s5pc110
ro.product.name=SGH-I897
ro.product.board=SGH-I897
ro.build.user=jetaek.lee
ro.build.display.id=ECLAIR
ro.build.version.codename=REL
ro.build.product=SGH-I897
ro.build.id=ECLAIR
ro.build.version.sdk=7
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.region=GB
ro.build.date=2010. 08. 27. (???) 19:06:57 KST
ro.product.locale.language=en
ro.build.host=sep-11
ro.build.fingerprint=Samsung/

[SCRIPT] GladRoot v4.3 (Bell 0.37.4, AT&T 1.26/1.52/1.57/1.83 Supported)

Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.​Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!​GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.​
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
​Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**​Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
​DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)​Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.​Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
​
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?

[Q] Having trouble routing. Help appreciated!

Ok, I have a N7000 with stock gb and KK2 kernel and I want to load the Paranoid Android ICS rom. First I see that I must route my phone, so I tried following the instructions at:
http://www.android.gs/how-to-root-samsung-galaxy-note-n7000/
These instructions make it sound darn simple, but perhaps I am really dumb? Ok, so first I downloaded the latest kies as well as "CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.rar"
After installing kies, I got it to connect to my note although not without heart ache. Eventually I found that it would only work if I first disabled USB debugging. But that wasn't enough. Then I had to reboot the phone. (Without that step it wouldn't work). It wasn't clear to me if I even needed to make it connect to kies. The instructions didn't say I needed to. Ok, so then I start "not-rooted-yet.bat" which displays this:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
(3) enable "UNKNOWN SOURCES"
(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 !!!
I can only easily do items 2-5. It's hard for me to imagine that I should just ignore the other 3 items.
Instruction #1 confused me. How do I accomplish that? It seems that the adb drivers come with the android sdk but the instructions don't say anything about installing that. That seems like a big deal and if it was required it seems that it would surely be mentioned?
Plus I found this post which also indicates that the sdk is not required.
> victorlht88:
> no u don't need the android sdk to root.
> just install kies, plug your phone with usb debugging enabled
> and let it install the drivers.
> restart your comp and plug your phone in (download mode),
> downgrade the firmware (if need be) with odin and simply
> root using cf root.
> its not that tough.
However those instructions seem about as clear as mud, since if I plug in my phone with usb debugging enabled, kies just hung forever saying "connecting".
Do the adb drivers get installed just by installing kies or do you somehow have to coerce kies to do this?
And then there is step 6. But I don't get any prompt of any kind when I plug in the phone to the pc.
And then there is step 7. I don't know what this means, but my guess is that I have to copy the zimage\zimage file to somewhere on the phone. However where exactly? There is no zImage folder on my phone! Plus even if there was, I couldn't copy anything to it after checking "USB debugging" (mass storage mode) I can no longer see my phone in explorer. What happens when I plug the phone in is that the phone says "USB connected" and then two new drives appear on my PC. However if I try to click on either of those I see "No disk drive. Insert a disk and try again". I even tried rebooting my pc, but then I get even more than two new drives showing up briefly, but they always give the same error message as before.
... yet I know that thousands of people have routed their phones ... so I am left pretty mystified. If anyone can clarify these instructions it would help me greatly, and maybe others as well.
Thanks
~Paul
Follow dr. Ketans thread in the development section.
And once on download mode with usb connected, CLOSE KIES. Otherwise odin will not work.
Sent from my GT-N7000 using xda app-developers app
Hi, your guide is taken from here. I think there is a missing step, which is to download the InitialCFRootFlasher.zip from the end of post #2, and you need to follow the instruction step "1.2. If you are not rooted yet: Using the zergRush exploit".
Btw, adb drivers are included when you install Kies in your PC. Once Kies is installed, you have to close it. Make sure your phone is in USB debugging mode before starting the procedure.
praetorius said:
Follow dr. Ketans thread in the development section.
Click to expand...
Click to collapse
Ok, those instructions seemed more clear. Different script as well although perhaps not significantly so? In any case it worked. I'm not rooted! Thanks all
~Paul
you said your kernel is kk2, then why did you use CF Root KK1?
Cf root kernel for KK1 and KK2 is same.

I Can't root my se xperia x8

I m not pro or something and i know that it this thread may be a thrash but please guys help me root my phone i have tried to root it with the superoneclick but it does fail at rageagainstthecage and i mean it stucks there i have done the usb debbuging and also i havent mounted the memory card / sd card.
I have also tried one other program DooMLoRD v4 and it also fails because all the time it tries something and it says failed failed failed ....
Could anyone help me im a newbie so i need as much help as it would be possible.
Thanks for reading.
its firmware is 2.1-update1
model number e15i
TraCegr said:
I m not pro or something and i know that it this thread may be a thrash but please guys help me root my phone i have tried to root it with the superoneclick but it does fail at rageagainstthecage and i mean it stucks there i have done the usb debbuging and also i havent mounted the memory card / sd card.
I have also tried one other program DooMLoRD v4 and it also fails because all the time it tries something and it says failed failed failed ....
Could anyone help me im a newbie so i need as much help as it would be possible.
Thanks for reading.
its firmware is 2.1-update1
model number e15i
Click to expand...
Click to collapse
install all drivers that need for x8 here and here
1. use flash tool - click PADLOCK icon
or
2. use x8toolbox
i have pc company i believe that covers it as i have read
use superoneclick
the problem is that i used superoneclick and it stucks at a point where it says rageagainstthecage
BlackRabbit1703
how do i install
X8_drivers??
turn on usb debugging then use superoneclick, try newer version...if u'r using newer then use 2.1.1..it worked for me.....have u installed gordon't gate drivers?
if superoneclick 2.1.1 not working then install gordon gate drivers then use flashtool for root
bandarigoda123 said:
turn on usb debugging then use superoneclick, try newer version...if u'r using newer then use 2.1.1..it worked for me.....have u installed gordon't gate drivers?
if superoneclick 2.1.1 not working then install gordon gate drivers then use flashtool for root
Click to expand...
Click to collapse
yes and also i have 2.3 superoneclick i just stuck rageagainstthecage for some reason
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
i have installed the drivers but i dont know why
try with x8toolbox
stamatis16 said:
try with x8toolbox
Click to expand...
Click to collapse
i dont know how to use it correctly i select e10 then close my phone press back button then connect it to pc again
just use superoneclick 2.1.1
try it now
TraCegr said:
i dont know how to use it correctly i select e10 then close my phone press back button then connect it to pc again
Click to expand...
Click to collapse
no need for flash mode with x8toolbox, you just connect it without doing anything, with usb debuging on
stamatis16 said:
no need for flash mode with x8toolbox, you just connect it without doing anything, with usb debuging on
Click to expand...
Click to collapse
i did it with usb debugging and it shows me an error i chose 1 and then 1 and after this
processing command...
waiting for device...
running psneuter exploit on device...
unable to chmod /data/local/tmp/psneuter: no such file or directory
device not exploited!!!
this error comes.
and about superoneclick2.1 i cant use that i get an error
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,05s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,05s
Waiting for device...
OK 0,03s
2.1.1
Getting manufacturer...
Sony Ericsson
OK 0,02s
Getting model...
E15i
OK 0,02s
Getting version...
-X_d
OK 0,02s
Checking if rooted...
False
OK 0,03s
Installing BusyBox (temporary)... - Step #1
2015 KB/s (1062992 bytes in 0.515s)
OK 0,55s
Installing BusyBox (temporary)... - Step #2
OK 0,16s
Rooting device... - Step #1
cannot stat 'C:\Users\TRACE\Downloads\Compressed\SuperOneClickv2.1.1-ShortFuse\Exploits\psneuter': No such file or directory
OK 0,04s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0,02s
Rooting device... - Step #3
OK 0,00s
Rooting device... - Step #4
./psneuter: not found
FAILED
somehow i managed to install a program superuser
TraCegr said:
somehow i managed to install a program superuser
Click to expand...
Click to collapse
OK you should be rooted now..
To test quickly, open terminal and type:
su
followed by ENTER
If you are rooted then you'll get a prompt askinmg you to allow root access..
Good luck..
i saw that when it was rooted ehm how can i install the app 2 sd i need it

Categories

Resources