Nexus 7 Help Thread
- Thread starter KidCarter93
- Start date
So I have very stupidly wiped my OS on my Nexus 7. Currently, I can get into bootloader, and I can get into TWRP recovery. Device is seen in my Laptop as Android ADB Recovery Device. But when I run ODIN (Its an old one - Odin3 v1.85) the device doesn't show up.
Where am I going wrong!! Used to flash stuff all the time before Android got good enough not to need it!! Now I feel like a total newb!! Hoping someone can help me revive my Nexus 7 so my daughter can have it for reading books
Where am I going wrong!! Used to flash stuff all the time before Android got good enough not to need it!! Now I feel like a total newb!! Hoping someone can help me revive my Nexus 7 so my daughter can have it for reading books
Hi, Dayzee...
You're going wrong by using ODIN, which I'm reasonably certain is propriety Samsung software, and definitely won't work on a Google Nexus device.
To reflash the Nexus 7, you need to do so via fastboot, with Google's factory stock images available here...
https://developers.google.com/android/images#nakasi
--------------------------
A few general points...
Do not reflash the bootloader if it's already on v4.23 ~ this is the latest version of the bootloader, and reflashing it again is pointless, and needlessly risky. If it can be avoided, I strongly suggest you do so.
-----------------------------
To confirm you have a valid fastboot connection prior to reflash (when the device is in fastboot mode), you should use...
Code:
fastboot devices...because this...
Code:
adb devices...only works when Android is fully booted.
-----------------------------
Good luck, and I hope this helps.
Rgrds,
Ged.
So, I am not new to android flashing, but, I have not seen this before (apart from the Nexus 5, but it never took this long).
I am trying to wipe and flash an android 5.1.1 build to my Nexus 7 as I intend on using it for a security system app. I followed the guide here: (apparentyly I can't post links but the title is: "[GUIDE] Flashing a Factory Image with fastboot / return to stock") and after completing the device auto-reboots, and then sits at the boot screen for ~30 minutes. I am going to go to sleep soon, and see if it ever finally boots but... is this normal? I know the Nexus 5 had an insanely long boot time after a factory restore (same for the Pixel), but, how long is the Nexus 7's?
I am trying to wipe and flash an android 5.1.1 build to my Nexus 7 as I intend on using it for a security system app. I followed the guide here: (apparentyly I can't post links but the title is: "[GUIDE] Flashing a Factory Image with fastboot / return to stock") and after completing the device auto-reboots, and then sits at the boot screen for ~30 minutes. I am going to go to sleep soon, and see if it ever finally boots but... is this normal? I know the Nexus 5 had an insanely long boot time after a factory restore (same for the Pixel), but, how long is the Nexus 7's?
So I picked up a refurbed nexus 7 wifi that had android 6.0.1 and flashed Lineage 14.1 via TWRP and everything worked fine for a few days. A few times the tablet was unresponsive and I had to shut it down via holding the power button. The last time I did this it got stuck on the boot with the Google image staying on the screen. I can get into TWRP but the screen is not responsive to my touch.
Any ideas ? I know that I could drop a new Los image onto the device and control TWRP via a mouse attached to the usb but I think that the bootloader might be the problem and dont want to make a bad situation worse.
Any ideas ? I know that I could drop a new Los image onto the device and control TWRP via a mouse attached to the usb but I think that the bootloader might be the problem and dont want to make a bad situation worse.
The booting time depends on the number of apps you have but I have never seen anything beyond 4 minutes on any of my devices. Ofcourse, my apps are less in number. If any of my devices went beyond 4 minutes, I assumed something was wrong and went about reflashing/rectifying it.
Custom ROM
I have 2 Nexus 7 2013 mobile (4G LTE) tablets running Lineage OS 14.1, which is not going to be updated. What should I do? Just go back to stock and live with it?
Thanks for your advice.
I have 2 Nexus 7 2013 mobile (4G LTE) tablets running Lineage OS 14.1, which is not going to be updated. What should I do? Just go back to stock and live with it?
Thanks for your advice.
Last edited:
If you have the Nexus 7 from 2012 try this one: https://xdaforums.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514/
Please be attentive when suggesting ROMS. I don't think that the AOSP ROM suggested by you is compatible to the LTE version of the 2013 tab. The thread title refers to the 2012 version and the OP refers to Grouper/Tilapia. As far as I know, the 2013 model has a different name, Razor/Deb. So I don't think the ROM suggested by you is compatible.
As a side note, I am running the AOSP ROM suggested by you in my 2012 wifi tab and it is the best I have come across so far.
@jhford
Hi everyone, I have a problem that I did not encounter until now with Nexus devices.
I have a Nexus 7 2013 Wifi and tried installing TeamWin recovery and somehow it did not work and the device would not boot up normally, so I decided to use Google's factory images to reset everything. But after successfully running the script Google provided, the device keeps rebooting and constantly shows the Google logo and then reboots again.
Can you help me please? I'm confused that even Google's tools do not work
I have a Nexus 7 2013 Wifi and tried installing TeamWin recovery and somehow it did not work and the device would not boot up normally, so I decided to use Google's factory images to reset everything. But after successfully running the script Google provided, the device keeps rebooting and constantly shows the Google logo and then reboots again.
Can you help me please? I'm confused that even Google's tools do not work
Last edited:
Hi, VollNoob...
You're posting on the wrong forum!
This forum is for the Nexus 7 2012, the model from the year previous to yours. You might have better luck, with a more useful response, by posting your question somewhere here...
https://xdaforums.com/nexus-7-2013
Having said that though, you should ensure you've flashed the correct Google factory image for your device, which is...
razorg for Nexus 7 (2013) & the latest version being Marshmallow 6.0.1 (MOB30X)
...and which can be found here...
https://developers.google.com/android/images#razorg
From your description, it sounds like an old fashioned bootloop problem, which can sometimes be resolved by booting into recovery and clearing cache/dalvik cache. If not, a reflash usually sorts things out.
I have the Nexus 7 2012 and haven't reflashed it for years, nor have I bothered much with the root/reflashing scene on my more recent devices, so I'm a little bit rusty on the specifics.
Good luck, and hope this helps
Rgrds, Ged.
Last edited:
Hi, VollNoob...
You're posting on the wrong forum!
This forum is for the Nexus 7 2012, the model from the year previous to yours. You might have better luck, with a more useful response, by posting your question somewhere here...
https://xdaforums.com/nexus-7-2013
Having said that though, you should ensure you've flashed the correct Google factory image for your device, which is...
razorg for Nexus 7 (2013) & the latest version being Marshmallow 6.0.1 (MOB30X)
...and which can be found here...
https://developers.google.com/android/images#razorg
From your description, it sounds like an old fashioned bootloop problem, which can sometimes be resolved by booting into recovery and clearing cache/dalvik cache. If not, a reflash usually sorts things out.
I have the Nexus 7 2012 and haven't reflashed it for years, nor have I bothered much with the root/reflashing scene on my more recent devices, so I'm a little bit rusty on the specifics.
Good luck, and hope this helps
Rgrds, Ged.
Thanks a lot! I will have a look there and will double-check if I downloaded the correct version of the Google tools.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]ASUS GOOGLE NEXUS 7 – GROUPER & TILAPIA (WiFi & 3G)[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: Do I need a toolkit to root this bad boy?....?[/SIZE]
Its a Nexus, imo if you need a toolkit you're either not experienced enough for rooting or too lazy Toolkits are out there and they are really straight forward, but you should get to know how to use fastboot/adb in case you need it. If you don't know what you're doing, you shouldn't be mucking around with your $200+ toy in case you screw something up and don't know how to use ADB or fastboot to restore it
[SIZE=+1]Q2: I'm thinking of getting this device/I'm new to this device. What are the main problems i should look out for? [/SIZE]
Look through the following threads - Nexus 7 defects? - List of known faults.
[SIZE=+1]Q3: Which ROM/kernel/recovery etc. would be the best choice for me? [/SIZE]
No-one can answer this for you. We all have our favorites, so just test different ones out and see which you prefer.
[SIZE=+1]Q4: When I flash my first custom ROM, how come I get stuck in a bootloop? [/SIZE]
While it's recommended that you always do a full wipe before installing, you HAVE to do a full wipe before installing your first ROM. If you don't, you N7 will not boot up.
[SIZE=+1]Q5: I flashed a new kernel and when I change frequencies, it reverts to stock settings 1.3GHz after a while. WHY??? [/SIZE]
You need a patched PowerHAL. On a very basic level, after a while the stock google PowerHAL likes to revert a lot of settings to stock. This includes the CPU clock speeds, etc. I got my PowerHAL from here
http://imoseyon.host4droid.com/grouper/beta/
And I flashed the nofreq one. It will NOT change your frequency, ever. After you flash the PowerHAL, use your favourite app (I like tricksterMOD, but support your devs by buying their apps) to set your kernel settings, and set them on boot. This is the easiest way to get settings to stick.
OR
You could use an init.d script to set a maximum clock speed. This way, you will need a kernel/ROM that supports boot.img.
http://xdaforums.com/showpost.php?p=35493253&postcount=1366
This is a lot more difficult but it works
[SIZE=+1]Q6: How much overclocking is too much? Am I damaging my device? [/SIZE]
No chips are created equally. Some can take more OC than others. It is fact that too much OC can shorten the life of your CPU. A general rule I have seen used a lot is to not go around 20-30% over the stock speed. That is around 1.5GHz which most kernels get up to. However, a lot of devices can take more and will go higher. See for yourself, just don't be stupid
[SIZE=+1]Q7: What is the difference between x and y kernel governors/schedulers? [/SIZE]
See here: [GUIDE]Kernel Governors and I/O SCHEDULERS
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
[SIZE=+1]Q8: I tried to boot my device into recovery from the bootloader and now it is stuck on the google screen. Is it bricked? [/SIZE]
No. Probably not. Chances are you're on an old bootloader, which has a bug that doesn't allow you to get into recovery from the BL without being connected to a computer. So, connect it to your computer, hold vol down/power for 10 secs to go back to the bootloader. You can go to the recovery from there.
[SIZE=+1]Q9: On my HTC (whatever) I could transfer files onto my sdcard while in recovery. How do I do it on the N7? [/SIZE]
You can't drag/drop in recovery between your N7 and a PC. Either boot into android and transfer your files, or use ADB while in recovery.
"adb push nameoffile /data/media" or wherever your things are (beware of how many 0's there are on your sdcard).
[SIZE=+1]Q10: My files on my "sdcard" appear under /data/media/0/0/0/0/0/0/0/0/0/0/0/0/0. WHY so many 0's?? [/SIZE]
Ask Google. It’s got to do with the multiuser feature brought to android in 4.2. Ever user has their own folder, so you might have /0 and /1. If you're having troubles with it in recovery, I would update to the latest TWRP.
[SIZE=+1]Q11: I’m trying to update my stock rooted modded N7 to 4.2 from 4.1.2 but it won't work. Help? [/SIZE]
You need to be running completely stock to update. So, you need to either flash a stock ROM or the stock image.
[SIZE=+1]Q12: When I finish watching a video the screen goes weird. Its like, washed out or something. Is my device bricked? Is my screen bricked? [/SIZE]
No. Its the tegra smartdimmer. When your device is playing a video, the Tegra 3 automatically bumps up the contrast and dims the backlight, to save battery. This is a feature. To turn it off, either use a script or tricksterMOD (which is much easier).
[SIZE=+1]Q13: Battery life on this kernel/ROM sux. I've been using it for half an hour and its dropped 30% already. Why? Restoring to my old kernel..[/SIZE]
When you flash a new ROM/kernel, you need to give it a few battery cycles before battery is reported accurately. So, flash the new kernel, drain it (not necessarily to 0%), charge it fully, drain it again, charge, then play around. Do not complain about battery or anything without doing a few cycles first.
[SIZE=+1]Q14: I am about to flash another ROM. Do I have to full wipe or can I flash it on top? (Dirty flash).[/SIZE]
Usually you can probably dirty flash. But if it causes problems, don't report them. Best thing to do is to reflash the ROM with a full wipe and see if bugs persist. I always wipe when changing to a different ROM, but when updating a ROM i don't wipe usually.
[SIZE=+1]Q15: Should I unlock the bootloader when I get the tablet if I am going to root it anyway?.[/SIZE]
I would say no. Because, if there is a problem you have sort of voided your warranty. I like to keep my devices for a month without rooting/unlocking them in case there is a fault or something. You should do the same, I’d hate to have a brand new device, root it and then find a fault and have voided your warranty. Companies can be sneaky and can probably try to avoid fixing your device under warranty if you tamper with it. However you could always relock and revert to stock, but it is much easier to be patient and make sure there are no problems
[SIZE=+1]Q16: Will rooting my tablet make it faster/awesomer and have improve battery life?[/SIZE]
Short answer: no.
Long answer: nope.
Rooting alone will not change anything relateds to battery or performance. However custom ROMs, kernels and other mods will change things. For example flashing a more optimised kernel might improve performance, especially if you overclock it. Similarly, underclocking generally improves battery life. Of course it depends on what crap you have on your device too, but that's the general idea. Usually in the OP of a ROM/kernel thread, and in the comments you can get a good idea on whether it is optimized for battery, performance or a combination.
[SIZE=+1]Q17: What’s difference between N7 “Grouper – Nakasi” and N7 3G “Tilapia – Nakasig”?.[/SIZE]
Wi-Fi (all models) = Nakasi - Grouper
3G/Wi-Fi = Nakasig - Tilapia
The Nakasi/Nakasig is the image (operating system)
and
the Grouper/Tilapia is the hardware build.
Because one of the files for the phone call apk is named "tilapia"
assert(getprop("ro.product.device") == "tilapia"
getprop("ro.build.product") == "tilapia".
[SIZE=+1]Q18: Can I use same recovery for N7 “Grouper” and N7 3G “Tilapia”? [/SIZE]
Yes, but it is preferable to use a special recovery for the tilapia. You will find 3 special recoveries for Tilapia.
[SIZE=+1]Q19: What's the difference between "Development" and "Original Development"?[/SIZE]
Here are the rough guidelines as to what should be placed in "Original Development":
*Official release of highly original and upstream custom ROMs (built from the ground up with significant original development within them).
*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
*A significant "first" in development for a device. This is something which took considerable time/effort and is generally accepted by developers to be non-trivial.
*Kernels which are built with beneficial changes that are not simply pulled from other kernels already available.
*Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
*Significant port of a ROM from one device to another, giving enhanced features or functionality to the users of the target device.
All other development work goes into "Android Development".
*
[INDEX]All In One Nexus 7 Index Thread (WiFi)
[Index]All for NEXUS 7 - "Nakasig/Tilapia" - (3G/GSM/HSPA+)
[GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions (FOR 3G VERSION)
*Use the thanks button if someone helps you or answers your question*
*Read the sticked threads*
*Google probably knows the answer to your question*
<> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to those who contributed to the production of this FAQ, especially kinfauns, kidcarter93, philos64, ronnie498, fellow RC's, me20Welcome to the Nexus 7 Help Thread
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd it 3rd post, be sure to come back here and read some more. It will help you to learn even more.
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most.
1.markj338
2.
3.
4.
5.
Nexus 7 Moderators
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - Shreyas Jani, chrisd1a1, GODZSON, Divine_Madcat, babijoee and Moscow Desire. If you have any questions about this forum in particular then feel free to drop them a PM.
In post 2 there will be some really useful links so be sure to check them out.
In post 3 there'll be an FAQ which will help you out aswell8Useful Information & Links To Help You
XDA In General
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Nexus 7 links further down this post.
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
Nexus 7 Helpful Links
I'll have these threads numbered so if you ask a question and it can be answered by looking at the first thread here, I'll say "Go to post 2 > nexus 7 > thread 1"
1. READ THIS FIRST - Nexus 7 General Section
2. [GUIDE] Flashing a factory image with fastboot/ returning to stock
3. N7 kernel test results (Performance & Battery tests)
4. Nexus 7 All-In-One Development Index
5. [Index]- 28 Jan 2013 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
6. NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
More will be added at a later date3Thread cleaned...
Just a friendly reminder .. if you can start a post by saying :
"I have posted this already in its own separate thread..."
You do not need to be finishing said post..2
There is a difference in being new and being spoon fed. You will find your answer in the Franco kernel thread.
Cheers Danny
