Im experienced rooting phones and i already read the faqs, but this seems to be the hardest phone ive ever come across with rooting. superoneclick freezes before i get a chance to use it,i tried using odin which gets stuck halfway through, ive closed all kies process also, ive tried using "DooMLoRD's Easy Rooting Toolkit" and it gives me this error "rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!""
i feel like i exhausted every idea to root it, i feel like i either brought a broken phone or im just dumb lol,but can anybody please help me.
Last I tried I did with SuperOneClick and ZergRush exploit.
Make sure you have dev mode enabled on phone, and I had to run the app in compatibility mode (running Win7 x64) AND as admin (right-click).
The SuperOneClick tool, DooMLoRD's Easy Rooting Toolkit and the zergrush exploit do not work on UCKK6 (2.3.6) Gingerbread, only on UCKH7 (2.3.4).
You can follow the guide which is the first link in my signature. You will need to flash the stock plus root package using Odin, paragraph 2C. You said you had trouble with Odin before, but you didn't say with what firmware package. This is your best path to root, and the only one that does not increment the flash counter.
With odin ive tried both packages in [Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root), ive also tried the "odin3 one-click" from that thread, it wouldn't recognize my phone all the odins ive tried would recognize it. i will try the stock root package from that thread.
Could be user error. Have you ever used Odin successfully before?
Or it could be a driver problem.
I would suggest that you make sure it's not user error first. Use the following guide. Follow it step by step in order
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
i can't even use odin now my phone is labeled as unknown device, its a shame i don't know what else to do. ill either just keep using it on 2.3.6 or sell it since i don't think its possible to root it now. Before it was being recognized by both computers now its not.
is there anyway to root it from the phone?
Sounds like a driver problem. I had the same issues. Google this it helped me. Samsung USB Driver for Mobile Phones v 1.4.8.0 and Delete Kies. After I deleted Kies everything worked. So maybe this will help you. Then you can start over using Creepys post.
im uninstalling kies right now and downloading the usb drivers, my phone was already recognized by windows i don't understand why that changed
chillywillyhoe said:
im uninstalling kies right now and downloading the usb drivers, my phone was already recognized by windows i don't understand why that changed
Click to expand...
Click to collapse
Just to be sure, uninstall kies and if you have Samsung USB Drivers for Mobile Phones listed under program manager also uninstall that, then reboot, download the USB drivers, install, reboot again. Usually driver problems happen because people are too lazy to reboot their computers between uninstalls and reinstalls, and again afterwards.
i uninstalled kies and the usb drivers, rebooted, installed the usb drivers, rebooted, and my device still shows up under "unknown device", i have no idea what to do now
Basically it says its not installed, but it says its installed.
I'm not sure this is related, but perhaps you can try toggling usb debugging mode (settings->developer options) or enable usb mass storage mode before connecting your phone?
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Yeah I'm hoping he knows he has to have usb debugging disabled at least one time when plugging in so it detects it properly.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
seanpr123 said:
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Click to expand...
Click to collapse
i extracted it but there's a bunch of folders, what folder is the right one to choose? how do i enable usb mass storage?
seanpr123 said:
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Click to expand...
Click to collapse
Phalanx7621 said:
Yeah I'm hoping he knows he has to have usb debugging disabled at least one time when plugging in so it detects it properly.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
usb debugging is off, its still not seeing it
chillywillyhoe said:
i extracted it but there's a bunch of folders, what folder is the right one to choose? how do i enable usb mass storage?
Click to expand...
Click to collapse
I believe last I tried I was able to point to the general directory and tell it to traverse through sub-directories and it worked after that.
Also, does your dir look like this:
Or this:
seanpr123 said:
I believe last I tried I was able to point to the general directory and tell it to traverse through sub-directories and it worked after that.
Also, does your dir look like this:
Or this:
Click to expand...
Click to collapse
I'm using XP by the way if that helps and mine looks like the second one, which folder do I choose because its not letting me choose the whole USB drivers folder just one folder.
FINALLY!, thank you all for your help, i serious have no idea what happened, as soon as i seen it recognized it i just went for it, i assume im rooted now, so i got to figure out a way to put cwr on it.
chillywillyhoe said:
FINALLY!, thank you all for your help, i serious have no idea what happened, as soon as i seen it recognized it i just went for it, i assume im rooted now, so i got to figure out a way to put cwr on it.
Click to expand...
Click to collapse
Before you go off, a couple friendly warnings: CWM is built into the custom kernels for our phone, it is not separate, so DO NOT attempt to install it/update it separately from the kernel you choose. Also, NEVER, EVER use ROM Manager.
As for how to install a custom kernel which will include CWM, just follow creepy's guide from 3a.
Related
I have downloaded the app from eclips3 and have tried rooting my phone..when i go to reboot my phone and holding down vol down plus pwer key my phone does not read the PB00IMG.zip file, eclips3 has been a lot of help but we have ran out of ideas. Does anyone else have any ideas of how to root my phone or put a ROM on it?
1. try a new sd card
2. make sure you have at least 50 % battery life...
3. Re download the image..
if not...go to verizon n tell them you cant root your phone.. LOL! jk...
hope someone else knows what to do...
lol thanks..do you think verizon will help me root it?? lol jk;-)
do you have the PB00IMG.zip in the root of your sd card (not in any other folders?)
The Beginning
You are going to need the Android SDK installed and working as we all the latest version of Java.
Extract and run ‘SDK setup.exe’ . You can find a quick setup on the download page for Android SDK.
Make sure you install the SDK for 1.5, 2.1 and USB Driver package (to make it easy just click to install all).
Put your phone into USB debugging mode: Settings > Applications > Development > check USB Debugging
Connect your phone to your PC
Open device manager on your PC, the device with the yellow exclamation mark next to it is your phone.
Right click on the device and click ‘Update Device’. Find and locate your Android SDK directory and find the ‘USB Driver’ Folder. If you can’t find the USB Driver folder then you didn’t install the USB Driver Package.
Once your Device driver is updated you can continue on to the next step: Rooting your phone.
Rooting Your Phone
Download PB00IMG.zip
Place PB00IMG.zip into the root directory of your SD Card. (Thats right inside your SD Card, not inside any other folders.)
Power down your phone.
Turn your phone back up by holding down the ‘down volume’ and the power on keys at the same time. It should bring you to the HBOOT screen. When it says Push Activate you have to push down on your trackball. The process will take about 10 minutes, and when your phone starts back up it will take quite a bit longer than usual.
Your Phone is now rooted!! (That was the easy part)
Install Recovery Image
Be sure your phones SD card is not mounted to your computer before you start anything.
Download Recovery.zip
Extract file contents to your \tools\ directory of your Android SDK.
Open up a command prompt and go to your tools directory (‘cd …./android-sdk-windows/tools’ or where ever your directory is but cd is the change directory command) , and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
You now have a recovery partition on your phone, you can access it by going into recovery mode on your phone (volume up + power on).
Install new rooted ROM
Download eris21official-root.zip
Copy eris21official-root.zip into the root directory of your SD Card.
Reboot your phone into Recovery Mode. (power down your phone and turn it back on with volume up and power button)
Go to Wipe, and do a wipe of data/factory reset, as well as dalvik-cache wipe.
Go back to the main menu and select “Flash Zip from SDcard”. You should see your eris21official-root.zip, select it and press the track ball to flash it.
You are now done and are running the latest version of the root rom. Remember these last step because they are the steps you will be using to use other ROMS or to update.
Click to expand...
Click to collapse
if you follow those steps step by step then it should work... its exactly what i did and what a lot of other people have done
for custom roms just find the rom you would like to try and follow the 'install new rooted rom' steps
i have downloaded and set up the sdk but i dont have a yellow triangle with an explanation point on my device manager..my phone is in debugging mode. I have just tried over and over copying the PB00IMG.zip file to my sd card and it still doesnt read it. It just says trying to read image PB00DIAG.img and a few others and says no image then goes straight to the hboot screen.
naenaek22 said:
i have downloaded and set up the sdk but i dont have a yellow triangle with an explanation point on my device manager..my phone is in debugging mode. I have just tried over and over copying the PB00IMG.zip file to my sd card and it still doesnt read it. It just says trying to read image PB00DIAG.img and a few others and says no image then goes straight to the hboot screen.
Click to expand...
Click to collapse
I'm rooting right now (my third Eris, actually) and it does that. You need to agree to updating by pressing volume up or down (don't recall which one, the screen will tell you, though..). It looks like it wants you to run through the first step all over again but it's not, the second time is the actual installation of the .zip on your sdcard.
-mak
it says my drivers are up to date when i click update drivers...so now i am stuck trying to root my phone..the problem i am having there is i cant get my phone to read the PB00IMG.zip file from the hboot screen.
lg optimus s
can this phone be rooted
tlove008 said:
can this phone be rooted
Click to expand...
Click to collapse
First, this post doesn't belong here as this is the HTC Droid Eris forum. Your phone isn't even an HTC brand. I looked and saw that XDA doesn't have a section for an LG Optimus S so I would guess not, personally. Perhaps you should try Google?
Good luck.
I have an S-OFF HTC Incredible S 4G running 2.3.3 trying to get it rooted, I am trying to keep up but so use to stupid iPhone modding/themeing so just lost on how to send or use my SD card for ROMS? Can I just use the old word (shsh) files over to my phone while its plugged in its the Fdisk and do I put the files into 'root', I have installed Superuser app/ROM Manager app onto my phone also have Gingerbreak.v.120apk on my desktop plus Superuser.apk am I lost or what and anyone willing to help but go easy on me?
Thanks, TheCrow
Do you have ClockworkMod Recovery installed?
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
I am all about trying to get things done in the easiest way possible to help the people that are new to Android.
This method has worked for me but there is no guarentee that it will work for you and I am no way responsible for anything that happens to your device.
DO THE ROOTING PROCESS AT YOUR OWN RISK
Procedure to Root HTC Incredible S
1. Install the ADB on your computer, but before that you will have to turn on the USB debugging in your incredible S which can be turned ON by pressing the “Menu” key first then “Settings” > “Applications” > “Development”. Now here you will find an option of “USB debugging”, select the option and just accept the warning which it will pop up. It’s very important to put the device in the USB debugging and also important to go through the ADB setup process without which it’s not advised to proceed.
2. Now you will have to download the Rooting package which you will have to unzip the same and need to place in the location path c:\adb after which you will have to connect the phone to the computer.
3. Now, open the command prompt and key in the “cmd” and then you will have to make use of the change directory command so that the directory in which you have placed the rooting file can be accessed.
4. Next type in the “pushroot” and enter the same, basically this will push in the pushroot.bat file.
After this type in adb shell /data/local/tmp/getroot and after that type in adb shell and press enter.
After typing in the above commands, you will now be prompted as # after which you will have to type in /data/local/tmp/pushroot.
That’s it you have now successfully rooted the HTC Incredible S
TheCrow1372 said:
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
Click to expand...
Click to collapse
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Theonew said:
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Click to expand...
Click to collapse
I appreciate the one above yours and kinda understand it but waaay too indepth maybe, I also tried yours but when I go to HBoot menu and Recovery to look for the .zip file it is no where and I plugged my device into computer and 'debugging Enabled' also set my connection as 'disk drive' to load the file to my SD card but still can't find it?? I can't believe it is this hard cuz I see many others rooted and flying away on their Incredible S 4G, I was able to get the Gingerbreak.v.1.20apk on my device but it just keeps loading and saying that it will reboot once successful but after 20-30mins I figured it was not going to work also I have ROM Manager installed already but as you know no Superuser previlliages yet so can't load CWM
TheCrow1372 said:
but as you know no Superuser previlliages yet so can't load CWM
Click to expand...
Click to collapse
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Theonew said:
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Click to expand...
Click to collapse
I'll try finding it without being plugged in to pc, I put Gingerbreak.v.1.20apk on my SD card no issues so I shouldn't have an issue putting the CWM on but do you have a newer version (sorry) also do you think one of my issues is that I have a CWM on my 'Astro' file finder but the files say they don't exist so should I delete it and start over with a newer one that you may have and should I take of ROM Manager until I finish putting these files in cuz it should not be this hard others are rooted on their Incredible S 4G 2.3.3.
TheCrow1372 said:
so I shouldn't have an issue putting the CWM on
Click to expand...
Click to collapse
Please explain this. Here's the image: http://downloads.unrevoked.com/recoveries/cwm-4.0.1.4-vivo.img .
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Also when I go to my 'Programs' on my computer 'Uninstall' it shows the SDK Tools with an 'X' beside it like it did not fully install, I don't know if I really need the ADB & SDK tools but I'll keep trying that later but I want to try your methods as well cuz as I mentioned it should not be this hard to root my phone right but I have to go to Doctors so I will check in later and keep trying
TheCrow1372 said:
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Click to expand...
Click to collapse
You are not supposed to open the image. Download Android Flasher, connect your device to your pc, run Android Flasher, select recovery (at the side), find the image file you downloaded, select it, click ok (and again if necessary), and it'll do the rest.
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
TheCrow1372 said:
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
Click to expand...
Click to collapse
Did you read/understand my previous post?
Kinda but how does that have anything to do with rooting my Incredible S (sorry) its just that I'm new to HTC devices and I've been told that I have to be rooted to put ROM themes on my device and I have S-OFF, thats not enough is it? I tried the guy above yous method of ADB but my computer does not 'recognize that path', I did exactly what his video says but again is either of these methods going to get me 'rooted cuz all I want to do is start enjoying my phone plus your saying I don't have to have 'Superuser Permissions' to use CWM?? Sorry bro if I'm being difficult but I just want to be rooted already and have you heard of this angermod or what ever its called, like Gingerbreak or something?
HELP PLEASE lol, thanks
Forget about Gingerbreak. The tool (and instructions) is to flash the custom recovery (ClockworkMod) to your device. I said this before, and I'll say it again, using ClockworkMod recovery DOES NOT require root. You are going to root your device by using Clockwork to flash the file attached in post #5. After flashing that file, your device will be rooted.
When I go to extract it they ask for a gehroot password, I copied what looks like a password under my Incredible S/Vivo but that one did not work for the CWM download
I will try this tomorrow 4 sure and thanks for your patients, fill you in when I'm rooted (hopefully) Also is there a special password to download the CWM for my Incredible S/Vivo, sorry again?
One more question (sorry) the one I did download the other day was supposed to be CWM but it has all kinds of other files with it like 13 files including 'SuperOneClick' also suv1/v2/v3 plus 'busybox' but don't see cwm anywhere so anyway do I use the 'Android Flasher' and flash all of them like the whole folder or each one individually?
In the CWM image file, there are like 13 files that came with it like suv1/v2/v3 plus busybox and SuperOneClick so which or all of these files do I flash with Android Flasher?
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
There are a few posts regarding rooting Canadian ICS Note. It seems there is a script in the OTA ICS upgrade that re-installs stock recovery (3e) after flashing CWM using ODIN.
Note: The offending script only exists in the OTA ICS upgrade, and not in update from Kies or samfirmware ROM.
If you don't have the offending script, then after Step 7, just reboot into recovery, install superuser ZIP from CWM, reboot, and you're done.
I'm summarizing the steps needed to flash CWM and root Canadian ICS Note:
1) Download Odin, CWM tar, and superuser zip (http://forum.xda-developers.com/showthread.php?t=1763896 Post # 3)
2) Install Odin
3) Copy superuser zip file to Phone
4) Start Odin and browse for the CWM tar file in the PDA section
5) Put the phone into download mode (VOLUME DOWN + POWER, then VOLUME UP)
6) Connect Phone to PC
7) Flash CWM with Odin
8) As the phone is rebooting, take out the battery. This is done to avoid the script install-recovery.sh from reinstalling stock recovery
9) Put battery back and boot into recovery (VOLUME UP + VOLUME DOWN + POWER, Release POWER after first vibration)
10) Install superuser ZIP from CWM, you are now rooted
11) Reboot phone
12) Install root explorer or ES File explorer and enable root operations and /system mount on them.
13) Find /etc/install-recovery.sh and rename it to install-recovery.sh.bkp
14) Repeat steps 4 to 7
15) Reboot. You should now have CWM and Root.
Thanks to SKyRocKeting727 and aleks07.
This could not have come at a better time...I was just sitting down at my computer to try this...Wish me luck
Success won't come from luck but it will from reading every step twice at least before any clicks or taps.
Thanks so much! Worked like a charm! Just finished nandroid backup of stock Bell rom with SU.
Getting ready to Try Flapjaxx UCLF6 rom.:good:
This thread should be stickied...
worked! thanks a lot
With ES File Explorer, I get "Sorry, operation failed" attempting to rename install-recovery.sh. I installed Terminal Emulator, and tried a simple
Code:
su
mv /etc/install-recovery.sh /etc/install-recovery.sh.bkp
to which I get "Read only file system"
I checked back in SuperUser, and ES Explorer (and Terminal) have root allowed; es file explorer has Root Explorer enabled in settings.
Ideas?
Edit: I realise the OP lists "install_recovery.sh", but I have no such file, just "install-recovery.sh". The contents are exactly what you'd think, though, conditional test to restore the recovery image.
Second Edit: I am an idiot. I missed "Mount /, /system as writable". Carry on, nothing to see here
THANKS MAN!!!!! it worked!
I've been trying for days to figure this out.
It appears I didn't have to do steps 12 - 15? My phone appears to be rooted and CWM is installed.:good:
Wintersdark said:
With ES File Explorer, I get "Sorry, operation failed" attempting to rename install-recovery.sh. I installed Terminal Emulator, and tried a simple
Code:
su
mv /etc/install-recovery.sh /etc/install-recovery.sh.bkp
to which I get "Read only file system"
I checked back in SuperUser, and ES Explorer (and Terminal) have root allowed; es file explorer has Root Explorer enabled in settings.
Ideas?
Edit: I realise the OP lists "install_recovery.sh", but I have no such file, just "install-recovery.sh". The contents are exactly what you'd think, though, conditional test to restore the recovery image.
Second Edit: I am an idiot. I missed "Mount /, /system as writable". Carry on, nothing to see here
Click to expand...
Click to collapse
Lol I was just gonna tell you to mount the system as writable.
Good luck, I just had to rename the file since I was already rooted.
I wonder if we rename back to the original than well get stock recovery again?
Easy way of doing it I guess.
hmm...
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
ygong said:
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
Click to expand...
Click to collapse
You'll find, though, that after you reboot into Android, CWM will be gone. You'll still have root though. To find the file in ES File Explorer, you'll need to go into ES's settings and enable:
Up to root
Root Explorer
/, /system write able
Then you just click up until you get to /, then click Etc, and install-recovery.sh will be in there.
ygong said:
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
Click to expand...
Click to collapse
Yup exact same here!
Wintersdark said:
You'll find, though, that after you reboot into Android, CWM will be gone. You'll still have root though. To find the file in ES File Explorer, you'll need to go into ES's settings and enable:
Up to root
Root Explorer
/, /system write able
Then you just click up until you get to /, then click Etc, and install-recovery.sh will be in there.
Click to expand...
Click to collapse
yeah CWM is still installed...
even though i rebooted my phone
Yup mine is still installed after reboot too!
Sent from my SGH-I717R using Tapatalk 2
kwhit said:
Yup mine is still installed after reboot too!
Sent from my SGH-I717R using Tapatalk 2
Click to expand...
Click to collapse
I think it might be helpful in this thread to list which Canadian Carrier you are with to determine which ones have to take the additional steps...
I am with Bell Mobility and can confirm that, for me, it was necessary,,,,,,
I am greatful to the OP and encourage and any of you that were helped to hit the Thank You button from his post..
crutzulee said:
I think it might be helpful in this thread to list which Canadian Carrier you are with to determine which ones have to take the additional steps...
I am with Bell Mobility and can confirm that, for me, it was necessary,,,,,,
I am greatful to the OP and encourage and any of you that were helped to hit the Thank You button from his post..
Click to expand...
Click to collapse
You are with Bell, I am with Rogers, and my friend is with Telus, and we all had to do the renaming of the script. I'm not really sure why some have to do it and some don't. Also, not sure why AT&T Notes don't have to do it.
zaptor99 said:
You are with Bell, I am with Rogers, and my friend is with Telus, and we all had to do the renaming of the script. I'm not really sure why some have to do it and some don't. Also, not sure why AT&T Notes don't have to do it.
Click to expand...
Click to collapse
Were you rooted on GB before?
Just looking for common denominators....
crutzulee said:
Were you rooted on GB before?
Just looking for common denominators....
Click to expand...
Click to collapse
Myself and my friend with Telus were not rooted before on GB.
I'm on Bell did root my phone when I was on GB
Rogers, and I was rooted, but had reflashed to pure stock before upgrading to ics.
-------THIS GUIDE IS NO LONGER NEEDED------
If your on a rootable version follow the guide and instructions to install a pre rooted Firmware, with Rbox's custom recovery.
This I supposed was good to use to have SuperSU before we had any type of recovery.
-----UPDATED V3-----NEW DOWNLOAD LINKS-----
*PLEASE READ THROUGH THE FULL GUIDE BEFORE STARTING.*
FIRE STICK Replace King/o Root with SuperSU v3.
Thanks @joojoobee666 for his suggestions on layout of the guide to try make it more understandable to folk and also to incorporate a step into the script to make it a little easier still.
First off i am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
REMEMBER GUYS, the process for this to work is root with KINGOROOT - reboot-root with KINGROOT - reboot - run the commands - uninstall KINGOROOT. Failing to follow the order of the steps could soft brick you.
Prerequisites
Fire Stick
Fire OS 5.0.5 (if your on anything other than 5.0.5 use my other guide to downgrade to 5.0.5 here:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298 ) dont forget to block updates again.
An understanding that 2 separate root programs are used in this guide KINGO ROOT and KING ROOT.
Installation Procedure :
You must follow these steps exactly as they are here, any deviation from this could cause you to brick (which is undo able so dont worry too much)
If you are not already rooted you need to root with KINGO ROOT. Once rooted reboot your Fire Stick. download it from here :
https://root-apk.kingoapp.com/kingoroot-download.htm
Your now able to follow the guide after you Root with KINGO ROOT.
Procedure
1.) Download the rar file containing the scripts and APKS:
http://www.filedropper.com/firestickroot_2
http://s000.tinyupload.com/?file_id=73723140467469181970
http://www.megafileupload.com/7nfv/firestickroot.rar
2.) Extract the file pack in the rar to /sdcard on your Fire Stick, PLEASE DOUBLE CHECK THIS. YOU NEED TO HAVE THE FOLDER STRUCTURE CORRECT OR IT COULD CAUSE PROBLEMS. YOU SHOULD HAVE /SDCARD/FIRESTICKROOT/CONTENTS . Inside the firestickroot folder you will see KING ROOT, install this and open it. Grant any permissions to it and let it take over root. When its finished, reboot your Fire Stick.
3.) Open an ADB Shell connection to the device. You should now see a prompt like this:
[email protected]:/ $
4.) Run the "su" command and choose "Allow" when prompted by KINGROOT on the screen. If successful, you should now see the following in the terminal:
[email protected]:/ $ su
[email protected]:/ #
5.) Run the following command:
sh /sdcard/firestickroot/root.sh
if successful you should see something similar to this
[email protected]:/ # sh /sdcard/firestickroot/root.sh
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
rm: /system/app/Kinguser.apk: No such file or directory
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
cp: /system/xbin/su: Text file busy
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Success
-----------Your Welcome--------------
6.) Run the SuperSU application, go to settings and un-check Enable Superuser then re-check it.
7.) Reboot the device (either hold play and select or run "reboot" from the ADB Shell prompt)
8.) Open ADB Shell once again and run "su". This time you should see the SuperSU prompt asking to allow the ADB Shell process to run as root.
9.) Uninstall KINGOROOT
10.) If you have any reminents of KING ROOT installed uninstall them, if it wont let you uninstall, re-install KING ROOT but DONT OPEN IT! then you can uninstall it.
IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again.
Thumbs up if ive helped
If anyone can make use of another app from chainfire, Flashfire, as it now will work with chainfires Su binaries installed. The app allows for backup/flash all partitions/install zips etc. Im not sure if its fully working or maybe an older version might?
Anyway ill leave that for anyone who might want to test that app out.
*IMPORTANT*
If you still cant seem to manage this, delete he associated KINGOROOTS SUPERUSER manually, then right after you have installed KINGROOT and rebooted navigate to /system/xbin and delete the file daemonsu. When the script finishes run it a second time, if you dont get chainfires SuperSU installed manually install it. This is included in the script to carry out this task but seems it wont work for everyone.
sconnyuk said:
be back soon with re-written guide v2 that is much simpler.
Click to expand...
Click to collapse
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
asafegous said:
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
Click to expand...
Click to collapse
Ive re done the guide made it much simpler, spent 2 days on it trying all ways to brick my device in the process and could not brick it no matter how hard i screwed up.
This newer guide should work 1st time if followed correctly, and you will be shot of Kingo/o Root.
Im real sorry but to make a custom recovery is a little beyond me.
sconnyuk said:
*Update*
I am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
The guide has been re done again by myself as it was far too long and although there was zero chance of bricking (with the use of Kingo Roots windows tool) ive put v2 together which is much simpler and all in a single script you will have no chance of any brick, with success the first attempt
This guide is for Fire Stick 5.0.5, you need root access with KingRoot, so if your rooted with Kingo Root please update your root app with the KingRoot apk in this pack, it will take over your Kingo Root and use King User.
Please note, you must root originally with Kingo Root, restart then Re-root with KingRoot then restart again, if not you will find that after a restart you will get unrooted.
Also be aware, if you have followed this through and still after a restart you are unrooted navigate to /root/system/xbin and delete the file daemonsu, then try again.
Download the pack here : http://s000.tinyupload.com/?file_id=02940258229221060594
Extract it in your Fire Sticks /sdcard directory.
You should have a folder in your Fire Sticks /sdcard directory called firestickroot.
Ive noticed myself that if im at the standard fire tv stick launcher sometimes king/o root fails to grant permissions so for the next step be aware and maybe have firestarter/app starter launcher loaded up.
Connect your Pc/Laptop/terminal to your fire stick and type the following commands. (grant permissions to all)
su
sh /sdcard/firestickroot/root.sh
Thats it, the script will remove KING ROOT and all associated files and install su binary and SuperSU apk.
Once you restart make sure you are using ChainFires SuperSu and uninstall Kingo Roots stuff.
Thumbs up if ive helped
Click to expand...
Click to collapse
II
@sconnyuk, could you pls add another d/l mirror? Thx
dave157 said:
@sconnyuk, could you pls add another d/l mirror? Thx
Click to expand...
Click to collapse
I certainly will when I get home later.
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
joojoobee666 said:
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
Click to expand...
Click to collapse
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
sconnyuk said:
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
Click to expand...
Click to collapse
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
joojoobee666 said:
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
Click to expand...
Click to collapse
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Nowhere in the guide says you must install SuperSU apk, the script does this for you. All you should be left with when it completes is KingoRoot and a newly installed SuperSU apk v2.01
sconnyuk said:
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Click to expand...
Click to collapse
Thanks. Will give all that a go here and let you know.:good:
joojoobee666 said:
Thanks. Will give all that a go here and let you know.:good:
Click to expand...
Click to collapse
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
sconnyuk said:
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
Click to expand...
Click to collapse
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
joojoobee666 said:
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
Click to expand...
Click to collapse
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
If not, run kingroot windows tool if that works then ok, if not dont close it open kingoroot up and then try, you will get it detected it happened to me a few times when i did v1 guide
sconnyuk said:
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
Click to expand...
Click to collapse
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
joojoobee666 said:
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
Click to expand...
Click to collapse
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
sconnyuk said:
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
Click to expand...
Click to collapse
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now? (side note, there is not daemonsu in /system/bin currently)
joojoobee666 said:
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now?
Click to expand...
Click to collapse
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
sconnyuk said:
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
Click to expand...
Click to collapse
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
joojoobee666 said:
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
Click to expand...
Click to collapse
Let it sit there a while, will probably go to optimising screen.
If it wont re root it with Kingo/king on pc and dont restart after, just let it sit and it should go to optimising screen.