Related
I got a nexus7 a week ago but decided to root the device today just to try apps which require root, i rooted it fine but i decided to unroot and thats where the problem started i cant boot pass the google image, i can get into where you hold down volume and power for so many seconds and team win recovery which says i have no OS in the reboot section, i've tryed nexus 7 toolkit v3.2.0 and nexus root toolkit to restore back to factory system but no luck, so is it me doing something wrong or is my nexus 7 just a paper weight now.
Doubt it,
Being you still have a custom recovery you didn't follow the right steps to unroot, might need to unlock the bootloader again, but follow one of the many guides, and try to stay away from a tool kit
Sent from my HTC Vision using xda premium
Unlock bootloader
Flash boot, recovery, system, userdata.
Files are zipped in the factory images directly from google.
Wipe cache.
Relock bootloader.
Reboot into recovery.
Factory reset. (Nexus 7 will only see 8GB if you don't do this step)
That is the gist of how it's done.
I followed a step by step guide on laptop man website but when i come to flash the android image it says file too large, i used 4.2.1 from googles site, if i'm correct when you type fastboot -w update image-nakasi-jro03d.zip (in the walkthrough) i can replace it with a later newer android in this case 4.2.1 jop40d
You could do it that way. Some people have. Although I received an error every time I did.
I didn't receive an error when I flashed the files in the zip.
First make sure you have the correct factory image for your device downloaded.
Then make sure you extract the boot.img, recovery.img, system.img, and userdata.img files to your fastboot folder and perform the following actions...
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
Lastly, boot your system up into recovery and perform a factory reset from there. If you don't do the last step they you will be stuck with ouly 8GB, vice 16 or 32.
It's that easy.
When i try to boot into recovery mode i get the android mascot with a red triangle, does that mean i have no recovery file.
OOOPS the system booted up into android as the recovery mode didnt work (as above) is there anyway i can reset to factory settings to get the 32GB back as it shows 6GB.
Update: I think i sorted it out now somehow as it shows up as 27.oddGB now (about same as i got it) instead of 6GB, anyway thanks for your help, it seemed complex well it is but once you know whats what it's not so, the hardest part is getting the files and putting them in the right places
When I try to reboot to recovery via the bootloader it just hangs... Can boot to recovery inside android (usually using Rom Manager or another reboot application)... any idea why?
I have read reports that it will hang when booting into recovery if not connected to a PC.
And as for that triangle you see.... That's normal.
That means that your in recovery mode. Your menu is just hidden.
Press power and volume up to view it.
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
marcfeld said:
Good morning,
I followed the tutorial here on XDA on how to basically factory reset my Nexus 7. Unfortunately, while going through all the steps I also deleted my recovery. Now I am unable to flash any recovery back on my device. I have tried flashing Clockwork, TWRP and even Google Stock recovery, but it won't work. Neither flashing via Nexus 7 toolkit nor by hand was successful, instead it always returns the following error message:
Booting into Android using an Insecure Boot Image..
cannot load "root\boot-insecure-.img' : No error
Now my Nexus 7 is in some random state, since Android 4.2.2 is installed, but rooting via the Toolkit returns the same message when it comes to the point of flashing a recovery. Then it simply skips the remaining steps and does not install the superuser app. I also downloaded and tried using the ROM Manager, but since root-access is missing, it can't do anything either.
Do you guys have any solution to this?
Help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Though toolkits save a lot of time, I always prefer to do stuff the manual way and I suggest you do the same. To flash the recovery do the following steps
1) a) if you are running Windows open cmd as administrator and CD into a folder containing adb and fastboot .exes
b) copy paste a downloaded recovery image in the same folder and rename it to recovery.img for simplicity.
2) boot into boot loader by pressing power volume down and volume up all together after the device is turned off
3) in bootloader enter the fastboot mode and in cmd on PC type
Code:
fastboot devices
At this moment your device should turn up in the command prompt.if it doesn't then try installing the Asus drivers and repeat the steps above carefully.
4) once all that is over type
Code:
fastboot flash recovery recovery.img
And then the recovery must be flashed . you will get an output on cmd with the time taken to flash it too .
Then reboot into recovery and enjoy.
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Thanks a million guys!
I will try this as soon as I get home tonight and let you know.
nourtsW escape
This did the trick!
Thanks again guys!
marcfeld said:
This did the trick!
Thanks again guys!
Click to expand...
Click to collapse
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
GedBlake said:
Glad you got it sorted.
With Android, there's always 'more than one way to skin a cat!'.
Rgrds,
Ged.
Click to expand...
Click to collapse
I am so relieved, because I thought I had bricked it...
GedBlake said:
A succinct summary, Red Devil.
I always maintain, on a my Windows laptop, a folder called FastBootAdb, that contains the following files...
fastboot.exe
adb.exe
AdbWinApi.dll (needed by Windows)
AdbWinUsbApi.dll (needed by Windows)
If I wish to flash a new recovery.img (or a new boot.img - useful for certain kernels, that consists of nothing but a boot.img, like franco for example. Most custom kernels though, consist of more than just a boot.img, and need to flashed via TWRP or CWM, and can't just be fastboot flashed).
Anyway... I just copy the new recovery into this folder, rename it to recovery.img and run the fastboot command accordingly...
Code:
fastboot flash recovery recovery.img
...similarly with the boot partition...
Code:
fastboot flash boot boot.img
To be honest, I'm puzzled why people feel the need to overcomplicate this very simple procedure with toolkits.
Rgrds,
Ged.
Click to expand...
Click to collapse
ive done this exactly step by step and i getthe system cannot find the specified path i made a folder inside the windows folder i named it recovery in the command prompt i did cd windows then cd recovery then i typed fastboot devicesthen it said that
Help! Nexus 7 won't accept recovery flash image
I've tried all the above. I can get to the command prompt, and fastboot devices sees my device. I input the above commands to reflash, it starts with message "sending 'recovery' <xxx.xkb>' then nothing. It just sits there until I reset or reboot my nexus 7. Can anyone help?
My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks
If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.
I now have android sdk set up.
What are the commands I should issue to root?
Thanks
now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway
Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it
When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'
You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.
hello everyone
im pretty new to the forums but have always seeked help from here so i know this is probably the best place to get more help.
so my nexus four is a little messed up. i had an error regarding "com.android.systemui" so i tried to factory reset but it still popped up over and over. i then accidently wiped everythin off my phone including the OS.
so i used skipsoft toolkit do work on my phone so i tried to use it to help me but everytime i try to load google stock image from the options but i get an extraction error and keeps getting errors when extracting the .tar file.
and i cant seem to push files to my phone so i can install via recovery. so im all confused and i downloaded the stock firmware from google.
any advice would be great.
and im stuck on the google logo and i can get into recovery and fastboot mode and the lock state is unlocked.
thanks
You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
The factory image comes a compressed tar, I've noticed when you download it the extension is wrong sometimes, make sure you have a .tgz file (rename if necessary) and winrar/7zip will extract it fine.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app
DrFredPhD said:
You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
hey thanks..so yes i can get into fast boot but im not too good cmd or anythin like that. so koush universal driver is that easy to use?
jd1639 said:
Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha
wink4lif said:
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
perfect thanks, once i manage to download it ill give it a shot. thanks
i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus