Recommended Posts

Rooting a Nexus device should be the simplest thing to root. I know you've looked at a few guides, have you tried this one? Using Toolkits can actually make things more complicated so this one is a bit more manual.

Essentially you need to unlock your bootloader (assuming you haven't already) and then you can flash a custom recovery and root.

Hope that helps

did you read the link??

the second paragraph says

You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.

All the android devices are pretty easy to root (just rooted a nexus 10 minutes ago - mannually)... if you dont want to do it like i did, use the toolkits :)

Nexus 4: http://forum.xda-developers.com/showthread.php?t=1995688

Nexus 7: http://forum.xda-developers.com/showthread.php?t=1809195

Nexus 10: http://forum.xda-developers.com/showthread.php?t=2001868

All the android devices are pretty easy to root (just rooted a nexus 10 minutes ago - mannually)... if you dont want to do it like i did, use the toolkits :)

Tried the Nexus 4 Toolkit, sat there in the fast boot screen, hit yes to unlock it and it sat there forever saying "waiting for device"

Hello I am the maker of the universal naked drivers so if you need to connect get that first here:

http://forum.xda-dev...08#post28610908

If any users is having issues with the Nexus 7 rooting ti may be cause you hit JB already which has all exploits closed. What you need to do is unlock the boot loader and push root to your system, here's how.

1) Unlock bootloader

2) Boot not flash custom recovery from fastboot

3) mount /System

4) /System is NOW accessible through ADB

5) use ADB to push the SU through command

6) reboot done

If you download my Transformer Prime "Urkels Fresh Start" covers this and if you replace the files and use same commands you will be good to go.

Urkels Fresh Start:

http://forum.xda-dev...d.php?t=1929189

Hello I am the maker of the universal naked drivers so if you need to connect get that first here:

http://forum.xda-dev...08#post28610908

If any users is having issues with the Nexus 7 rooting ti may be cause you hit JB already which has all exploits closed. What you need to do is unlock the boot loader and push root to your system, here's how.

1) Unlock bootloader

2) Boot not flash custom recovery from fastboot

3) mount /System

4) /System is NOW accessible through

5) use ADB to push the SU through command

6) reboot done

If you download my Transformer Prime "Urkels Fresh Start" covers this and if you replace the files and use same commands you will be good to go.

Urkels Fresh Start:

http://forum.xda-dev...d.php?t=1929189

Is this just for Nexus 7? Any guides for Nexus 4?

Is this just for Nexus 7? Any guides for Nexus 4?

Same process on Nexus 4

Unlock

Boot custom recovery

mount /System

and push files to Nexus 4, the nexus 4 does not work with the normal superuser (ChainsDD) and the variant of Chainsfire is used for now. SuperSU

mskip from XDA makes a toolkit which uses my naked drivers, this tookit will automate the process I just mentioned.

http://forum.xda-developers.com/showthread.php?t=1995688

Same process on Nexus 4

Unlock

Boot custom recovery

mount /System

and push files to Nexus 4, the nexus 4 does not work with the normal superuser (ChainsDD) and the variant of Chainsfire is used for now. SuperSU

I tried that, it just hands indefinately on "waiting for device" when I tell the program to unlock it.

the process is the same for all google devices... waiting for device is usually related to missing drivers or lack of privileges on windows... on linux it works as it should btw (just run sudo fastboot for the operations)

I tried that, it just hands indefinately on "waiting for device" when I tell the program to unlock it.

I think I know the issue, first you must uninstall any previous drivers and use mine (which is also the default for the toolkit).

Before you run the toolkit you need to install the driver multiple times, once per fastboot and once per ADB. each mode shows differently in devices manager so you must install it for each mode.

You are 100000% having a driver issue ;)

Please read the red below form my drivers thread:

Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

I think I know the issue, first you must uninstall any previous drivers and use mine (which is also the default for the toolkit).

Before you run the toolkit you need to install the driver multiple times, once per fastboot and once per ADB. each mode shows differently in devices manager so you must install it for each mode.

You are 100000% having a driver issue ;)

Please read the red below form my drivers thread:

Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers

Ok deleted all the drivers, I try to install them from the program but I get this

VIA5x.png

Ok deleted all the drivers, I try to install them from the program but I get this VIA5x.png

The problem is you are using Windows 8 and need to go to my thread to disable driver enforcement, you are installing drivers through the tool kit which will not give you the error plus needs to run as Admin

If you install them normally through device manager it would have shown this to you. Disable the enforcement and then reinstall the drivers. I would do this manually with my package until you can confirm you got around Windows 8 driver enforcement.


Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ?More PC Settings?.
Click ?General?.
Scroll down, and click ?Restart now? under ?Advanced startup?.
Wait a bit.
Click ?Troubleshoot?.
Click ?Advanced Options?
Click ?Windows Startup Settings?
Click Restart.
[/CODE]

Another question is can updating to jellybean un-root cause superuser seems to have stopped working?

if you're on the stock rom and you updated OTA then yes it will remove the root if you don't have one of the root keeper apps installed on your android

Here's a dumb question. Hwo do I fully back up my Nexis 7? Plug it in and just drag everything to a folder on my PC?

are you already rooted? if so just boot into CWM and make a backup from there

Do is rooting even worth it? I'm not even sure I understand the concept. Is it like Jailbreaking on iOS? I'm only even looking into it because I wanted to try the Saxaxxis app and apparently it needs the device to be rooted.

Does rooting void your warranty?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!