Hello all.
I am having no luck rooting my N7 with Linux (Newest version of Ubuntu). I was able to unlock the device, but I cant seem to root. I have read an red and read and searched for weeks on end to no avail. One problem I find frustrating is the tutorials which assume I know exactly what Im doing.
- Debugged, plugged into the PC, the N7 is instantly recognized and I can access its folders from the PC. But once I bootload I lose that connection.
- I really am not too familiar with Linux and the Terminal, but I am slowly learning. Some tutorials expect me to know what all the code means and I have no clue sometimes.
- I really want to learn this process, but the countless different tutorials are confusing. Ive tried a NRT for Linux but once the instructions include terminal code screens, i get lost.
Any help is appreciated.
Thanks
Related
hi all thought i would share my experience with SGS semi brick in the hope that some of you would find it usefull.
firstly i would like to thank everyone in the dev community for all the information and hardwork going on out there.
secondly thanks ryanaz for the great software Z4Root and oclf they worked great (once i used them properly my own fault)
thirdly if im repeating information thats already been covered elsewhere then i apologise in advance but i couldnt find it
back to topic: stock SGS with 2.1 on tmobile uk connected to windows 7 pc
last night i managed to semi brick my phone in the following way:
1. updated to froyo using official method via kies
2. ran z4root and executed temporary root
3. ran oclf seemed to work ok but following oclf reboot i ended up with black screen and occasional vibrate with glowing softkeys if touched and nearly crapped myself as i broke my phone
from research it seems that this problem indicates a fooked partition screwing up the internal sd and logically it is probably because i used temporary root as the root is removed following a reboot so during oclf reboot memory may have been corrupted.
i have since used permananent root and oclf and it worked really well no problems
my phone does not have the 3 button recovery mode and i was gettin a bit concerned after hours trawling the net it seemed i was going to have to go for the 301k resistor jig which i didnt really fancy.
fear not i figured out a method of getting into download mode without 3 button method or 301k jig using odin and adb commands.
its a combination of different methods for different things and it may not work for everyone but it worked for me. maybe some of the more experienced dev's can shed some light on it or refine the process.
required:
odin
pit file
rom files
adb
slight dos command knowledge (easy to find on net if you dont have it)
its important to say at this point that the phone wasnt fully bricked as the fault indicated the bootloader was intact and if the following works for you then the procedure should work.
quick check to see if it may work connect phone via usb with battery out, boot up odin, put battery into phone and switch on. if its recoverable then it will show a connection in odin in yellow with a com# (# will be a number indicating a com port. the number isnt important so long as theres one there)
if you try and flash the phone it will fail no matter what pit or rom you use as you cannot get into recovery or dowload mode.
to get into download i had a play with adb (search adb for how to use it. i hadnt heard of it before yesterday it requires knowledge of command line use in dos mainly just to navagate to the adb folder and execute adb. search dos commands if you cant figure it out and look for CD for change directory and dir for dir list)
important bit:
follow the procedure earlier to get phone communicating with odin then start adb. once in adb i used the command:
adb reboot recovery
and hey presto my phone went into download mode i was then able to reflash the phone using the normal Odin methods.
now i have my lovely phone with a faster operating system, streamlined rom and root access happy days.
just as footnote i had never messed with android before yesterday as i had always been on windows mobile so with a bit of research its amazing what you can learn. and i know this guide isnt very n00b freindly but its how i best remember it from last night after searching various things for 5 hours(ive slept since then) if any of it is incorrect then i apologise in advance but ive left it intentionally vague as the experienced dev's will know what im talking about and the n00bs(like me yesterday) it wont hurt you to go and research the topic and you might learn something instead of just posting questions all the time
peace out
p.s. forgot to mention ensure that you kill any kies processes running on your pc before attempting this and ensure you have internet connection so windows 7 can obtain drivers if required. xp or vista may require drivers to be manually installed though not sure
thank you so much!!! you just saved my phone. I was going to send it to a service, but now I can flash it with odin
Or, the morale of the story, always make sure you have 3BR
I want to root my nexus 7. I don't know how to all the tutorials are for windows or useing the tool kit I want to do it manually I don't have my boot loader unlocked
Whaleshark345 said:
I want to root my nexus 7. I don't know how to all the tutorials are for windows or useing the tool kit I want to do it manually I don't have my boot loader unlocked
Click to expand...
Click to collapse
All the tutorials presume unlocking of the bootloader. afaik, nobody has bothered to find a separate privilege escalation method of rooting for the N7.
fastboot is available from Google (SDK) for Linux. That means that fastboot methods are identical, irrespective of platform.
There is nothing that prevents you from re-locking the bootloader after you have rooted - with the penalty that unlocking it later will cause a full wipe of /data.
Technically though, it is the *act* of unlocking the bootloader that causes a voiding of the warranty. If they really wanted to do it, I have no doubt Asus could detect a re-locked bootloader (by examining low-level flash write counters).
cheers
Thanks but i was wondering if someone could explain it to me a little more clearly and pro give a link to a tutorial
Unlock the bootloader. There is zero reason not to, except for the factory reset it does.
Whaleshark345 said:
Thanks but i was wondering if someone could explain it to me a little more clearly and pro give a link to a tutorial
Click to expand...
Click to collapse
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
bftb0 said:
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
3 seconds
bftb0 said:
How long exactly did you look around? Two seconds?
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
I can understand where the guy's coming from. I've now Googled about six different 'tutorials' on how to root the Nexus 7.
They are all total ****. Horribly written with unclear, incomplete, and contradictory instructions.
Seriously--that one you linked is only good if you already know how to do it. For someone that doesn't...it's useless.
I rooted my 7 months ago (unlocked bootloader, etc.), but lost root with the 4.2.2 update. I can't find the instruction set I used last time, and the tutorials I've found so far actually have me wishing whoever wrote them was here now so that I could beat the **** out of them.
Seriously, whoever wrote them--especially the one you linked--sucks. Bad. A lot. Terrible writing.
A shortcut is to install Windows in Virtualbox and use Wug's utility to get the job done, an extra step but this will surely save you a lot of time to do it manually.
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I dont understand what is so complicated about rooting a nexus device. it is literally the EASIEST device to root and flash. Not sure why people need walkthroughs or tutorials.
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
reboot into recovery
install supersu.zip
what part of that is complicated that requires someone to hold your hand and help you type out the commands??
@fre1102
Well, I suppose that poorly written tutorials and a flood of newbs looking to be spoon fed is good for generating ad revenue for XDA. Not really great for what made it a compelling site in it's early history, though.
On the other hand, the OP asked a help question - and failed to do so in the help and questions forum. That certainly appears like a lack of paying attention, does it not?
I suppose you might have a complaint if you had actually been paying someone to give you advice, but to complain about the quality of something that costs you nothing seems a bit like an entitlement problem - whether you are correct in your appraisal or not.
It's an internet bulletin board - there is no barrier to entry and the quality is going to vary widely. That makes it YOUR RESPONSIBILITY to decide what to believe. It's not as if people are coming in to your home and forcing you to do any of this stuff.
Nobody here owes you anything; this site has always encouraged folks to take responsibility for their own actions. If you have a rooted device that is borked - simply put, that is YOUR FAULT. Period.
Pirateghost said:
http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html
I dont understand what is so complicated about rooting a nexus device. it is literally the EASIEST device to root and flash. Not sure why people need walkthroughs or tutorials.
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
reboot into recovery
install supersu.zip
what part of that is complicated that requires someone to hold your hand and help you type out the commands??
Click to expand...
Click to collapse
You can even cut that down by a step by installing the latest version of TWRP 2.4 which will autmatically detect an unrooted rom and root it for you.
I gotta admit though that getting some custom roms was a little confusing to me in the beginning after rooting and flashing a samsung phone using heimdall in Linux. It's the lack of a good guide that really didn't help. I was hoping that there would be a sticky in the Q&A or a wiki topic about it but those sections for the nexus 7 aren't that organized.
Maybe we should start using the wiki... It would be easier to keep up to date even if someone decides to abandon a thread since anyone else can go in and edit it, and if we get repeated questions we can just copy and paste a link for those who want to be spoon fed since they will always be a constant presence on this forum.
EDIT:
I had to use the cyanogenmod rom building wiki to get a good, well-written guide on unlocking the n7 and flashing a custom recovery. Good thing I had started building the rom before I got the device shipped to me since it helped to have a "good" version of cwm6 laying around.
thanks guys I rooted it was easy just needed to adjust the commands for Ubuntu witch is just adding a "sudo ./" to the beginning of every command
Whaleshark345 said:
thanks guys I rooted it was easy just needed to adjust the commands for Ubuntu witch is just adding a "sudo ./" to the beginning of every command
Click to expand...
Click to collapse
Good deal. Some folks go to the trouble of customizing some udev configuration files (I think it's udev, but can't remember right now) so that unprivileged Linux users have permissions on individual USB devices.
To me that seems like quite a bit of trouble for stuff that I do infrequently (using fastboot); I just drop to a root shell
$ sudo /bin/bash
#
and save a couple keystrokes with the fastboot commands.
BTW, when using adb from Linux, it is only necessary to start up the adb server with root privileges - the server process is the only thing needing privileges on the USB bus, so
Code:
$ sudo `which adb` devices
gets the party started but
$ adb pull /sdcard/myzipfile.zip
won't result in files owned by root.
Not surprisingly, all this stuff is less cumbersome using a Mac OS/X flavor of Unix - by default the USB devices are reachable by unprivileged users without any udev/hotplug diddling or sudo invocations.
cheers
I'm insanely frustrated. My N7 was rooted. Suddenly now it's not.
Absolutely nothing is working properly. I tried installing the adt-bundle for Windows. It doesn't install. All I get is a quick DOS prompt flash, and nothing actually installs.
I tried installing the Sixaxis pair tool. That won't work, because I get this message: http://i.imgur.com/VU9Ou14.png
I tried running CF Root, it doesn't detect my N7.
I'm using Windows 8. I don't know if it's my PC, my N7, or me. Maybe all of the above? But for some reason nothing seems to want to work. The sheer volume of information on rooting my device is overwhelming. If anyone can give me a hand, it would be greatly appreciated.
End result for me, is I just want to use my PS3 controller with my N7. It's not even working with a hard wired connection for some reason.
Do you still have a custom recovery installed?
I don't see anything in your post that says which rom you're using, also if you double clicked on something like adb or fastboot.exe you're doing it wrong, course it'll just immediately close, you have to run it from cmd.
Please go read some of the stickied posts because it seems like you haven't grasped the concept of using adb/fastboot and the problem is likely easily fixed if you just read the instructions instead of relying solely on tool kits.
I'm not using a rom, nor did I ever install a recovery. All I needed to do in order to use my PS3 controller wirelessly, was to root the device. That's all I need to do.
Is it not completely ****ed up that I get these two messages? My PC clearly shows that the ADB drivers are properly installed. However any kind of rooting tool I use does not detect my N7. USB debugging is selected on my tablet. I just don't get it.
http://i.imgur.com/xwTb1vS.png
wrong forum
Q&a
Sent from my Nexus 7 using Tapatalk 4
I use wugfresh's tool kit and it's very simple! Try it
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Wish39 said:
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Click to expand...
Click to collapse
Oopsie daisy.
Thanks, I will repost in the proper forum!
drjboulder said:
Oopsie daisy.
Thanks, I will repost in the proper forum!
Click to expand...
Click to collapse
It's fine. People make mistakes sometimes.
Also it looks like something majorly screwed up your Nexus 7. Hope you find a solution to fix it up sooner or later.
drjboulder said:
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Click to expand...
Click to collapse
can you connect through fastboot?
Hello,
I'm new here and I registered because now after searching, reading and trying different things I'm a bit confused
And: Most information is quite old...
I was donated a LG device that gives me these informations about itself:
Modellnummer: LG-K350n
Android-Version: 6.0
Android Sicherheitspatch-Level: 2018-04-01
Kernel-Version: 3.18.19
Build-Nummer: MRA58K
Software-Version: V10k-EUR-XX
My initial idea was to have postmarketOS on it and use it as kind of a small tablet - e.g. to read/write eMails, take pictures, have video-conversations via tox, use it as a music-player and maybe use it as a GPS-device (offline, just via GPS). Connections should only be made via WiFi. No SIM should be required - to make calls and SMS I have a separate feature phone, so I don't need the telephony-module.
After a while I befriended myself with lineageOS or even replicant. In such a case maybe I would even use it as cellphone and keep my feature-phone just as a back-up.
My main aspect is to have a device I control - not someone else (e.g. google).
I know that it would be easier just to use stock android and maybe fiddle a bit around, but I don't trust android/google/...
I don't need google-applications, facebook/What's-App, some cloud-based-stuff... - never did and never will. (I prefer to stay away from things that require these - if something has it mandatory then I will not use it.)
What I did until today: Following gottlasz' guide Friendly root method for lg k8 and k10 but got stuck without a version of TWRP that fits on my firmware. I found one that clamied to be OK for my firmware (https://www.cyanogenmods.org/downloads/twrp-recovery-for-lg-k8/). Booted into it, then I installed rce_univ.zip, supersu and rce_univ.zip again. But then the phone was in a bootloop saying that it was corrupted before it tried to boot itself again. With the help of a friend I restored the stock-ROM with LG Bridge (he has Windows10 on his laptop) - that took about 10 hours because here we don't have fast internet-connections...
I'm willing to put effort in this project and try to build/compile all kinds of things myself. But I need help in the way someone could guide me with what are the steps to be taken next. My PC (amd64) is running linux (gentoo to be precisely) and in a VirtualBox I have a copy of Window$ XP SP3 (32-bit).
After this toying around I found it hard to get up-to-date informations on what is possible today. And I don't want get stuck again like I was (and of course I don't want to brick it completely ).
So, please help me on my way to free my phone, I'd be glad to offer further information if needed.
Thanks a lot!
Quick answer, forget about it not going to happen.
I have k350nds with same hardware but it's dual sim and long time ago I was trying to build rom from lineage sources since there is mt6735 device tree for ex cyanogenOS and I didn't succeed because lack of knowledge and computing power, however even if I did succeeded I won't be able to flash it because nothing can be flashed, not even twrp it can be only booted from fastboot, because of some 'security' measures, it may be reverse engineered and some with knowledge can make a rom but it won't happen since device isn't so populated etc. And therefore you can only use this phone as is, I think at this point it cannot even be rooted. I received update of 11mb which didn't update patch level or anything else that I notice.
Professor Woland said:
Quick answer, forget about it not going to happen.
(...)
Click to expand...
Click to collapse
Hello Professor Woland,
thats' a pity! But thanks for your answer anyway!