Related
EDIT: Problem solved using zergRush with DooMLoRD's tools, using the community provided Mac script. Thanks a bunch for all your help~
I'm having a problem finding a suitable rooting method for my Verizon Xperia play R800x.
Android version is 2.3.3, and the kernel version is 2.6.32.9
First off, on Sony's bootloader unlock page, it says that CDMA phones cannot have their bootloaders unlocked. Additionally, putting the code *#*#7378423#*#* doesn't do anything on my phone. No service menu, nothing. On that note, Clockworkmod Recovery shouldn't be able to work either, since that requires an unlocked bootloader (right?), thus I can't flash RootXperia.
Gingerbreak no longer works, tried it personally, in addition to reading that an update broke it.
zergRush looks like my last option, but I use a Mac, and the only tutorials I can find are for Windows. I suppose if the Mac terminal isn't TOO different it'd work, but I really don't know.
Is there something I'm missing?
SuperOneClick will root it, but you may have to use Windows
You'll be able to install cwm after you've rooted. Search the Market for Xperia cwm installer
Honestly, on the r800x. PM Alejandrissimo, There is a charge for services. However getting the bootloader unlocked and where you can flash and do things. Is quite worth it. Sadly the r800x.. isnt as easy as the GSM models, so dont try to think that it is. CDMA sucks heh.. Least I got mine done tho. =D
Michealtbh said:
SuperOneClick will root it, but you may have to use Windows
You'll be able to install cwm after you've rooted. Search the Market for Xperia cwm installer
Click to expand...
Click to collapse
That sounds like an idea. I'll have to find a Windows computer though, but shouldn't be too hard. Unless it requires the Android SDK installed separately too.
Mysticales said:
Honestly, on the r800x. PM Alejandrissimo, There is a charge for services. However getting the bootloader unlocked and where you can flash and do things. Is quite worth it. Sadly the r800x.. isnt as easy as the GSM models, so dont try to think that it is. CDMA sucks heh.. Least I got mine done tho. =D
Click to expand...
Click to collapse
I just care if it's rooted. I don't really want to flash ROMs or kernels, I just wanted root access, and from most of what I read, unlocking the bootloader first was the way to do it.
AvataroftheSun said:
That sounds like an idea. I'll have to find a Windows computer though, but shouldn't be too hard. Unless it requires the Android SDK installed separately too.
I just care if it's rooted. I don't really want to flash ROMs or kernels, I just wanted root access, and from most of what I read, unlocking the bootloader first was the way to do it.
Click to expand...
Click to collapse
It is possible to use zergRush on a Mac.
Go to this thread
[HOW-TO] Root Phones w/ Android v2.2.x-2.3.x (zergRush Method)
Scroll down to where it says "[ Scripts posted by others ]", and youll find "Rooting script for MAC OSX"
Enjoy
AvataroftheSun said:
That sounds like an idea. I'll have to find a Windows computer though, but shouldn't be too hard. Unless it requires the Android SDK installed separately too.
Click to expand...
Click to collapse
If you look at the Linux script in the zergRush thread (how to root 2.2.x thru 2.3.x, or something like that) in the Android development subsection, that'll be closest to a Mac script...
Sent from my R800x using Tapatalk
Leraeniesh said:
It is possible to use zergRush on a Mac.
Go to this thread
[HOW-TO] Root Phones w/ Android v2.2.x-2.3.x (zergRush Method)
Scroll down to where it says "[ Scripts posted by others ]", and youll find "Rooting script for MAC OSX"
Enjoy
Click to expand...
Click to collapse
Oh wow, I never saw that when I skimmed that post. I'll try it this way then.
I just received my GSM Nexus that came with 4.0.4 and hopped on to root. Half the methods warn against using the method with 4.0.4 or have replies reporting 4.0.4 problems. The other half require 3-4 downloads, running command windows, and 30-40 minutes of time and a factory reset. What gives? Every other android phone I've had in the last 3 years have all had ultra simple one-click programs. Plug it in. Click. Done.
What's so different about this nexus that requires this complicated stuff?
BobbyDash said:
I just received my GSM Nexus that came with 4.0.4 and hopped on to root. Half the methods warn against using the method with 4.0.4 or have replies reporting 4.0.4 problems. The other half require 3-4 downloads, running command windows, and 30-40 minutes of time. What gives? Every other android phone I've had in the last 3 years have all had ultra simple one-click programs. Plug it in. Click. Done.
What's so different about this nexus that requires this complicated stuff?
Click to expand...
Click to collapse
There's nothing complicated about it. You only think it's complicated because you are used to one-click programs -- which is the very reason I don't recommend using them: it prevents the user from learning anything, much like using a calculator before learning how to add and subtract.
Obtaining root access on a GNex is extremely simple. It consists of booting or flashing a custom recovery and using it to flash one zip file. That's it.
And the reason that a lot of one-click exploits don't work on the GNex is that it is running the latest version of Android, which has patched the security holes the the older exploits were using.
Sent from my Galaxy Nexus using Tapatalk 2
Already tried the Gnex Toolkit 6.1?
This is supposed to work with 4.04. I didn´t try it yet, i rooted mine GN with 4.02.
But it wasn´t much more than 1 click with the toolkit.
My guide will work.
Ignore all toolkits, and do it the right way.
You'll thank yourself later if you ever need to go back to stock...
Or have a bricked device.
Srsly.
What is OP talking abouit? the GN is one of the EASIEST phones to root.
Its very easy, here:
https://www.youtube.com/watch?v=FK-AyIJm_6s&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
Troll?
Sent from my Galaxy Nexus using Tapatalk 2
zephiK said:
What is OP talking abouit? the GN is one of the EASIEST phones to root.
Click to expand...
Click to collapse
Not if all your used to is installing an app with one big button saying "click here to root". So many people don't realize that you don't need a one-click app or a toolkit to make rooting easy -- all it takes is a little bit of reading.
efrant said:
Not if all your used to is installing an app with one big button saying "click here to root". So many people don't realize that you don't need a one-click app or a toolkit to make rooting easy -- all it takes is a little bit of reading.
Click to expand...
Click to collapse
Toolkit is available. Doing the manual method is not the only way of doing it.
Not that I'm endorsing using a one click root because it is relatively easy,
get drivers.
fastboot oem unlock
fastboot flash recovery
This phone is hard to root ?
Nono...the Droid Incredible was hard to root way back. We had to rely on a race condition and precise timing to get the exploit to work. THAT was hard.
I'm very confused. Every nexus phone always had one command:
Fastboot OEM unlock
Gnex is the same as all previous nexus. What am I missing here? Just fastboot one command and you're done.
RogerPodacter said:
I'm very confused. Every nexus phone always had one command:
Fastboot OEM unlock
Gnex is the same as all previous nexus. What am I missing here? Just fastboot one command and you're done.
Click to expand...
Click to collapse
The problem here is that the OP has not done much (if any) reading on this.
Yes, I agree with you, being able to unlock your bootloader makes gaining root access easy. But what you posted: "Just fastboot one command and you're done." is not a procedure to gain root (its information like this that makes a lot of n00bs think unlocking their bootloader is the same as getting root access), and it is certainly not a way to explain it. I could be mistaken though...
I think your just use to other phones that either u Odin it or use app that would flash the phone with root on it. I remember first Android I did it was a pain took time to get timing right for first few times I thought I was missing something
Sent from my Galaxy Nexus using Tapatalk 2
Jubakuba said:
My guide will work.
Ignore all toolkits, and do it the right way.
You'll thank yourself later if you ever need to go back to stock...
Or have a bricked device.
Srsly.
Click to expand...
Click to collapse
I used Jubakuba's guide; very straight forward, no surprises. Highly recommended!
If all you are used to is one click methods, then yes, it SEEMS hard. It is actually very simple.
Fastboot OEM unlock
Fastboot reboot bootloader
Fastboot flash recovery recovery.img
Fastboot reboot recovery
Flash the su.zip from recovery
Reboot to a newly rooted phone
Done. And I even added at least one step that you don't HAVE to do.
Sent from my Galaxy Nexus using XDA
thos25 said:
If all you are used to is one click methods, then yes, it SEEMS hard. It is actually very simple.
Fastboot OEM unlock
Fastboot reboot bootloader
Fastboot flash recovery recovery.img
Fastboot reboot recovery
Flash the su.zip from recovery
Reboot to a newly rooted phone
Done. And I even added at least one step that you don't HAVE to do.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is on the right track.
But how about:
1) Where do I enter those commands?
2) Where do I get all the required files? Is recovery.img the same as cwm.img the same as recovery-clockwork-5.5.0.2-maguro.img?
3) How come my PC doesn't recognize my device?
efrant said:
This is on the right track.
But how about:
1) Where do I enter those commands?
2) Where do I get all the required files? Is recovery.img the same as cwm.img the same as recovery-clockwork-5.5.0.2-maguro.img?
3) How come my PC doesn't recognize my device?
Click to expand...
Click to collapse
1.) A command prompt
2.) Download the SDK - it has everything you need (drivers, fastboot, adb). The image is any image you download, put whatever it is named there.
3.) Because you don't have the drivers set up properly. Download the SDK. If it doesn't auto-detect select it manually from the usb drivers folder in the SDK. If it doesn't detect select manually from a list and pick android bootloader interface.
This has to be one of the easiest devices to root, took less then 5 minutes.
using fastboot it is also the easiest one to return to stock. I had to return mine to google due to a defect and it took less then ten minutes to do.
The OP just needs to read rather than looking to be spoon fed.
In each development section there are instructions in a sticky post.
Because everyone who wrote a procedure assumes people are not noobs so they skip steps.
I am a noob with my phone and it took me hours of reading various procedures and piecing them together to get my phone rooted
Not tell if this is trolling or real
Sent from my Galaxy Nexus using Tapatalk 2
So I'm new to the HTC One, (Literally, just got it 25 minutes ago) and coming from the Note 2 about 6 months ago, was the last time I rooted and Rom'ed a phone. Since then, I have had a completely stock Galaxy S4, and since I was unable to ROM it up, I stopped caring. Now that I just got the HTC One, I searched up the forums and see things from Bootloader isnt unlocked, to S off, etc. I am so lost, and I'm unsure where to begin. I just honestly want to find out the steps in which I need to install a ROM, since its been so long. I read the stickies, and I don't understand what is the difference between S Off, Bootloader etc. I dont even know what S Off is! lol
Thank you for helping me out, and just point me to the right direction of what to do first. Please don't be snobby, I have searched, I just dont see what you have to do first, and so on.
Also, is there a way to do any of this on a Mac? If not, I can use my laptop, but just prefer on my mac.
Thank you again!
ONLY FLASH ROMS YOU FIND IN THE VERIZON HTC ONE SECTION - roms you get from the general htc one section or ANY OTHER section will not work and will cause you major headaches. Read through this Q&A section and you will see what happens when you try and flash things you shouldnt.
Before the first thing you do you need to get the adb/fastboot stuff download the sdk from here - Android SDK - the main things you will need from the zip file you download is the "platform - tools" folder. This will give you adb and fastboot. I would suggest renaming the folder to something simple and moving it to the root of the C: drive. Any file you send to your phone via adb or fastboot needs to be in this folder.
Well the first thing you will need to do is figure out what software version you are running. To do this you need to boot your phone into the bootloader. The bootloader is a special part of the phone where you get access to fastboot, you use fastboot to flash things like recoveries, boot/system and such images as well, you also can get to the RUU tool from fastboot. To boot into the bootloader I find it easiest to power down the phone completely, once completely powered off press and hold the volume down button and power button until you get to the boot loader
Here is an image of the bootloader screen - http://www.blogcdn.com/www.engadget.com/media/2013/04/att-one-bootloader-unlocked.jpg
In the bootloader you use the volume buttons to move up and down and the power button to select.
The software version of your phone is the number next to the "OS-" in the bootloader screen it will be "OS-1.10.605.x". Once you know what software version you have, download the rumrunner tool - [s-off] rumrunner s-off for Verizon HTC One - READ the post more then once and make sure you follow the instructions exactly, with any luck you should get s-off without much trouble.
S-Off means you can change any aspect of your phone, this is a double sided sword because once s-off have more ways to turn your awesome phone into a fancy desk paperweight
Unlocked Bootloader - this is for people who unlocked there phones via htcdev, the phone is not s-off so you can not do things like install custom kernels but you do get the ability to install custom recoveries.
Custom Recovery - The tool you use to flash roms, backup your current rom, wipe your phone and restore nandroids. With the Verizon HTC One you get Clockwork or TWRP, personally I like TWRP.
Post back here when you get Rumrunner to work and I will post more instructions.
http://forum.xda-developers.com/showthread.php?t=2473644
very meticulously follow these directions. you should try to understand what s-off, unlocking the bootloader, root etc. all specifically. that said, this exploit does it all for you.
you're going to need the htc one windows drivers (if you're on windows), minus the actual htc manager software (google/search these forums for them) and you're going to need adb/fastboot, which you can find in the android sdk (google it), or in a smaller download somewhere on this forum.
Thank you. Once I finally finish movie night with the wife I want to read this all and follow through. Thank you
Sent from my HTC6500LVW using Tapatalk
No, you can't use your mac, unfortunately. Ya gotta use your pc.
So I cant download RUU for my phone, the webpage is down? Im trying to download it for 1.10.506.8 (whatever the last digit is for 8)
justinisloco said:
So I cant download RUU for my phone, the webpage is down? Im trying to download it for 1.10.506.8 (whatever the last digit is for 8)
Click to expand...
Click to collapse
RUU or Rumrunner? At this point, unless there has been a step you did not tell us, you should just need to run Rumrunner. RUU would be used to flash back to stock at some future point.
The links to Rumrunner seems to be having issues. I have been having problems with most of the links coming from goo.im. Here is a mirror you can use:
http://rumrunner.us/downloads-2/
There is a lot on this page, but assuming you are running the .8 firmware on your phone right now use this link:
http://rumrunner.us/rumrunner_downloads/rumrunner_m7wlv_1.10.605.8.zip
calash said:
RUU or Rumrunner? At this point, unless there has been a step you did not tell us, you should just need to run Rumrunner. RUU would be used to flash back to stock at some future point.
The links to Rumrunner seems to be having issues. I have been having problems with most of the links coming from goo.im. Here is a mirror you can use:
http://rumrunner.us/downloads-2/
There is a lot on this page, but assuming you are running the .8 firmware on your phone right now use this link:
http://rumrunner.us/rumrunner_downloads/rumrunner_m7wlv_1.10.605.8.zip
Click to expand...
Click to collapse
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
justinisloco said:
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I too had a few issues getting it to work at first. Make sure you read the prerequisites very well and everything is perfect. Also make sure any anti-virus and firewall programs are disabled or completely uninstalled even. My firewall was causing it to hang up. Then even after that it took a few trys to get it to take. And make sure you have the correct version of rumrunner for the version of firmware your phone is using.
I also had issues getting the recover to flash, and I ended up having to update my SDK Tools and run the CMD from inside that folder where I also put the recovery. This may be common knowledge but at the time I didn't know that.
justinisloco said:
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Few things to make sure you have done for Rumrunner to work
- YOU HAVE TO USE USB2.0 if you use USB 3.0 the program will not work
- Uninstall HTC Sync and any other programs on your computer that are used with your phone
- Enable USB Debugging
- Disable Fastboot
- Enable "Unknown Sources"
- Disable "Verify Apps"
- Make sure there is no security on your phone, no passcodes, faceclock or anything else
- Disable Lock Screen Security
- Make sure you run the soju,exe with admin privileges
If that doesnt work, copy the text from the program so I can see where it went wrong.
Wozzie said:
Few things to make sure you have done for Rumrunner to work
- YOU HAVE TO USE USB2.0 if you use USB 3.0 the program will not work
- Uninstall HTC Sync and any other programs on your computer that are used with your phone
- Enable USB Debugging
- Disable Fastboot
- Enable "Unknown Sources"
- Disable "Verify Apps"
- Make sure there is no security on your phone, no passcodes, faceclock or anything else
- Disable Lock Screen Security
- Make sure you run the soju,exe with admin privileges
If that doesnt work, copy the text from the program so I can see where it went wrong.
Click to expand...
Click to collapse
I have all of that. I updated to 1.10.605.10 so maybe that may work, and rebooted my pc. I'm just getting home now so I'll see if anything changes
Sent from my HTC6500LVW using Tapatalk
OK Here is my Log-
==================== rumrunner S-OFF 0.0.3 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ
Press ENTER to exit
Click to expand...
Click to collapse
justinisloco said:
OK Here is my Log-
Click to expand...
Click to collapse
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Wozzie said:
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
Click to expand...
Click to collapse
Use this to download Ubuntu - Ubuntu Desktop Download - make sure you download the 32-bit version.
When loading Ubuntu, you do not have to install it, you can click "Try Ubuntu" when prompted and not have to worry about having things setup on your computer to have two os's.
Wozzie said:
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
Click to expand...
Click to collapse
May have to be my first time. Finally an excuse to try it out. just curious, can I run this OS on a Mac? From a flash drive? I can use my windows but it's mainly for work and now that I think of it they may have put some internet blocking thing on there (not antivirus) because of sensitive information
Sent from my HTC6500LVW using Tapatalk
as a complete noob myself, this thread was very helpful. Thanks guys
justinisloco said:
OK Here is my Log-
Click to expand...
Click to collapse
That looks like a Driver issue. Verify you can connect with ADB, if not you need to double check you have the HTC drivers installed correctly. Sometimes you have to let the phone site for a bit for all the drivers to connect correctly the first time.
calash said:
That looks like a Driver issue. Verify you can connect with ADB, if not you need to double check you have the HTC drivers installed correctly. Sometimes you have to let the phone site for a bit for all the drivers to connect correctly the first time.
Click to expand...
Click to collapse
Can you point me in the correct direction for the Drivers?
Usually, if I'm not mistaken, they usually automatically download on Windows when I plug the phone in. When I used to root the Nexus 7 for example, it wouldnt connect. The HTC I am able to connect to my PC and trade out storage, and I do not have HTC Sync installed on the Windows becauase I have nothing but work stuff on there anyway.
Im at work right now, maybe I'll use this computer and see if this helps rather than my laptop at home.
justinisloco said:
Can you point me in the correct direction for the Drivers?
Usually, if I'm not mistaken, they usually automatically download on Windows when I plug the phone in. When I used to root the Nexus 7 for example, it wouldnt connect. The HTC I am able to connect to my PC and trade out storage, and I do not have HTC Sync installed on the Windows becauase I have nothing but work stuff on there anyway.
Im at work right now, maybe I'll use this computer and see if this helps rather than my laptop at home.
Click to expand...
Click to collapse
It is listed as a requirement in the rumrunner thread: http://forum.xda-developers.com/showthread.php?t=2473644 If you dig in the thread a bit there are some good links. I think this may be the one you will end up needing:
http://forum.xda-developers.com/showthread.php?t=2376761
calash said:
It is listed as a requirement in the rumrunner thread: http://forum.xda-developers.com/showthread.php?t=2473644 If you dig in the thread a bit there are some good links. I think this may be the one you will end up needing:
http://forum.xda-developers.com/showthread.php?t=2376761
Click to expand...
Click to collapse
Alright, Work computer is a no go. When I get home, I will download those drivers and try this again. Im getting so used to keeping my phone stock at this point that I dont even know if its worth it! LOL.
Thanks again for your (and everyone so fars) help. It is appreciated!
FINALLY GOT PAST THE SCREEN!
Call me an idiot, but I didnt have USB Debugging enabled! I Couldve sworn it was already enabled! I feel like a total noob!
Now I will just follow the directions in that first thread and I should be good to go?
Is there a working root method for 10.5.0?
Is the Bin4ry's Root not working anymore?
KF2 10.5.0
No, Bin4ry's Root dont work. it realy messes up the sytem. looking for new method.
xromz24 said:
No, Bin4ry's Root dont work. it realy messes up the sytem. looking for new method.
Click to expand...
Click to collapse
I rooted mine on 10.5.0 a couple weeks ago using Bin4ry's root. It seemed to work fine after that, but I didn't run it too long before attempting to put custom android on it. Ended up flashing the wrong boot loader and then replaced the motherboard. The New one was 10.5.0 as well and rooted using bin4ry then flashed correct boot loader. It's running android like a champ now. No more limited o.s. and haven't run into any issues as of yet.
Can you put up instructions please
Steve1698 said:
I rooted mine on 10.5.0 a couple weeks ago using Bin4ry's root. It seemed to work fine after that, but I didn't run it too long before attempting to put custom android on it. Ended up flashing the wrong boot loader and then replaced the motherboard. The New one was 10.5.0 as well and rooted using bin4ry then flashed correct boot loader. It's running android like a champ now. No more limited o.s. and haven't run into any issues as of yet.
Click to expand...
Click to collapse
I've been trying to figure out how to root my Kindle Fire 2 Gen for a few weeks now....can there be anyway you could like put a video how to do it so people don't get bricked devices and for beginners it would save a lot of people's time and money don't you think i think it would be fair to everyone if they were able to have this info on what software to use and what boot loader who else agrees because rooting devices is a open source process which should be shared with all like i said it would be great to know how to do this process if you can do thank you
Trainboy001 said:
I've been trying to figure out how to root my Kindle Fire 2 Gen for a few weeks now....can there be anyway you could like put a video how to do it so people don't get bricked devices and for beginners it would save a lot of people's time and money don't you think i think it would be fair to everyone if they were able to have this info on what software to use and what boot loader who else agrees because rooting devices is a open source process which should be shared with all like i said it would be great to know how to do this process if you can do thank you
Click to expand...
Click to collapse
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
question
Steve1698 said:
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
Click to expand...
Click to collapse
but what version of bin4ary did you use
Trainboy001 said:
but what version of bin4ary did you use
Click to expand...
Click to collapse
Root_with_Restore_by_Bin4ry_v30
Steve1698 said:
Root_with_Restore_by_Bin4ry_v30
Click to expand...
Click to collapse
i tried it and not when im on my kindle my screen is flashing the logo screen and it's really slow what do i do??
Trainboy001 said:
i tried it and not when im on my kindle my screen is flashing the logo screen and it's really slow what do i do??
Click to expand...
Click to collapse
I'm not sure. Mine didn't do that. It seems like the thing ran like **** after rooting, but after rooting I just went on with flashing 2nd bootloader and twrp then installing a custom Rom. So honestly I couldn't tell you much more about it... I just got it to work somehow. Sorry, good luck.
flopower1996 said:
Is the Bin4ry's Root not working anymore?
Click to expand...
Click to collapse
I delved into the guts of Bin4ry's Root a little bit. It uses 3 (IIRC) binaries, "getroot", "su" and "busybox" and plays games with remounting blocks as RW and using getroot to put things where you wouldn't normally be able to. It utterly failed for me on the first go because of the new tightened file permissions everywhere in 10.5.0.
Doing
Code:
C:\adb> adb root
before running Bin4ry's script helped out a lot, and everything seemed to go correctly until the busybox install phase when it ran into a permission error once again.
I may look into this some more tonight; and I may try running both Bin4ry and Qemu root sequentially as per
http://forum.xda-developers.com/showthread.php?t=2075959
That's how I rooted my KF2 once before.
Steve1698 said:
I just went by the following guide...
http://forum.xda-developers.com/showthread.php?t=2100963
Followed it exactly as its posted and it worked. The first time I tried I used a different guide and ended up hard bricking to a state that it wouldn't even turn on. Replaced the motherboard with a used one and then followed the guide in the above link and it worked for me. I rooted first using bin4ry then just followed that guide. Then installed a custom android Rom. Make certain of which kindle you have before flashing anything to it.. it's a crappy feeling sitting there looking at a dead kindle. I'm not saying that method will work for everyone on 10.5.0, but I was able to get it to work for mine. First time I've hard bricked a device and it was because I downloaded and flashed a file which was meant for a different model kindle.
Good luck! If it doesn't work then hopefully someone can come up with a more modern method.
Click to expand...
Click to collapse
I followed it too, and now have custom bootloader & TWRP. I would like to stress a few points:
1) Most of the adb commands didn't work on the first go. What worked for me was typing
Code:
C:\adb> adb root
C:\adb> adb shell
adb# <command>
adb# exit
C:\adb>
in place of
Code:
C:\adb> adb shell su -c "<command>"
2) DO NOT skip the backup instructions. They saved my butt; they may save yours. A fastboot cable is highly recommended.
These directions for grabbing the backups as files worked better for me:
http://forum.xda-developers.com/showpost.php?p=41956668&postcount=3
3) Before I found "adb root" I skipped Step 3 since I couldn't make it work and figured it might not be essential. Ended up with a bootloop. That was when I needed the fastboot cable and my backup files from when I rooted before the "upgrade" to 10.5.0.
4) I was never able to get to fastboot without a fastboot cable before I discovered "adb root". I suspect
Code:
C:\adb> adb root
C:\adb> adb reboot bootloader
will work, but I haven't tried it.
Stupid question...
Hi folks,
Can I ask a really stupid, noob question? I've not had any experience with rooting android devices in the past, but my son has a KF2, v10.5, and he'd like me to root it so he can access the play store. I've read a lot of posts on here about the signed roms and so forth, and because I'm new to the topic a lot of it is going over my head. So some questions:
1) I think, from reading here, that these warnings only apply to replacing the default rom on the KF2, to get a more android like shell. Rooting in itself is a prerequisite for doing this, and doesn't have the associated risk - is that right?
2) I should be able to root the device using the steps in this thread http://forum.xda-developers.com/showthread.php?t=1886460 ? That would then allow me to install the play store? The fact I'm using 10.5 doesn't impact on this?
2b) How much risk is there in this? I think most of the risk is in applying custom roms, and the advice to get a fastboot cable applies to that rather than simply rooting the device?
3) The latest version is v36, but v30 was mentioned below. Am I better going for the latest version or going with v30
Again, sorry for the dumb questions!!
Kev
---------- Post added at 06:14 PM ---------- Previous post was at 05:38 PM ----------
Also, if the bin4ry stuff is okay to use on 10.5, which option should I use when I run it? Been looking through the batch file, and I'm suspecting NEWSTANDARD?
kev1609 said:
Hi folks,
Can I ask a really stupid, noob question? I've not had any experience with rooting android devices in the past, but my son has a KF2, v10.5, and he'd like me to root it so he can access the play store. I've read a lot of posts on here about the signed roms and so forth, and because I'm new to the topic a lot of it is going over my head. So some questions:
1) I think, from reading here, that these warnings only apply to replacing the default rom on the KF2, to get a more android like shell. Rooting in itself is a prerequisite for doing this, and doesn't have the associated risk - is that right?
2) I should be able to root the device using the steps in this thread http://forum.xda-developers.com/showthread.php?t=1886460 ? That would then allow me to install the play store? The fact I'm using 10.5 doesn't impact on this?
2b) How much risk is there in this? I think most of the risk is in applying custom roms, and the advice to get a fastboot cable applies to that rather than simply rooting the device?
3) The latest version is v36, but v30 was mentioned below. Am I better going for the latest version or going with v30
Again, sorry for the dumb questions!!
Kev
---------- Post added at 06:14 PM ---------- Previous post was at 05:38 PM ----------
Also, if the bin4ry stuff is okay to use on 10.5, which option should I use when I run it? Been looking through the batch file, and I'm suspecting NEWSTANDARD?
Click to expand...
Click to collapse
Okay, in case anyone else is interested, it worked fine. I used the new standard method in bin4ry. Worth noting that I was able to run adb commands before starting. If you can't then you need to sort that out first
I've installed the google play stuff now, just trying to log into a google account...
I rooted mime with kingo root with a pc.
Im looking to put gapps on it while leaving it stock. The method I used before was moving google framework and a couple of other things yo /system/app. This no longer works.
I dont have secon bootloder or anything on it anymore. Is there a way anyone knows to just put google play no it, nust being rooted stock?
Wow, 2014!! lol
My stupid Kindle updated before I rooted it and now it keeps failing to root. I've tried binary root and king root with the pc and the app. I'm really irritated about it and even more irritating is how old this device is and the chances of someone fixing the issue being minimal at best. I was gonna use it as a car radio with CM.
Hello all. I am new to the N7. I look forward to trying out some of the awesome development in this forum. Before I begin I need to ask some things. I have spent ALL DAY today reading forums and researching this device b4 I begin. But to be honest, I can not spend days reading every post out there and still be a dad here. So I am trying to stream line this some. I am not a newbie in rooting / roming. Sorry if I have not seen a topic like this b4 posting. There are just so many in this forum now to go through. I will delete this one once helped if nessary. Also THANK YOU VERY MUCH in advance for any help I get here.
1. I have a Verizon note 2, Verizon PERMANENTLY locked the bootloaders on their phones so development has stoped/ slowed drastically. I know the N7 has a locked bootloader that can be unlocked. Is this still true on a stock 5.1.1 lollipop version? or Is there a step to reflash to an older rom I should do first?
2. I see the wugs toolkit out there and a nexus toolkit. Is there any reason to use one over the other? Are either of these working on my STOCK 5.1.1 rom still?
3. Can someone please run down the steps to achieve UNLOCK, ROOT, AND CUSTOM RECOVERY? I seen how wugs does all that in it's program. So if that is the way than a good link to use Please.
Once again. Thanks in advance for your help here. Please also feel free to add in here anything I need to be aware of b4 I begin making my N7 a beast of a tablet. I can not wait to try out some of the awesome roms and mods I have seen so far.
:thumbup::beer::thumbup::beer::thumbup::beer::thumbup::beer:
To root or not to root? That is the question.
1. It's unlockable
2. No need for a toolkit just use fastboot, unless you don't want to know what you're doing. It's in the platform-tools folder of the android sdk. There are many guides on xda about how to use it. Don't forget to install googles usb driver.
3. Very easy. Boot the tablet to the bootloader by holding volume down and power while turned off.
Plug into the computer and open a command prompt in whatever folder you have fastboot and type fastboot oem unlock and hit enter. Follow the steps on the tablet.
For recovery download the recovery .img you want and put it in the fastboot folder. Type fastboot flash recovery whatevername.img
To root just download the su zip from here and flash it through recovery.
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Batfink33 said:
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
:thumbup::thumbup::thumbup::thumbup:
To root or not to root? That is the question.
robrooter said:
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
[emoji106][emoji106][emoji106][emoji106]
To root or not to root? That is the question.
Click to expand...
Click to collapse
Here's the thread on the issue. I bought my N7 yesterday and I'm affected by this. I can't resolve it and am stuck on stock at the moment which is annoying as I bought it to mess about with Roms and kernels. I'm not sure how you identify which tablets are affected but it seems the later manufactured ones are.
http://forum.xda-developers.com/showthread.php?t=3064562