I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.
Related
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
dskyers said:
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There's no one click method I know of for the Nexus S.
What do you mean you can't root & it won't budge? This phone is about as easy they come (without some one click app): http://forum.xda-developers.com/showthread.php?t=931865
Install the android sdk on your computer.
Put the su.zip file on your sdcard partition of the phone.
Put the phone in fastboot mode.
Fastboot flash the recovery.
Select recovery.
Select install zip from sdcard.
Flash it.
Reboot.
You're done.
If your computer doesn't recognize the phone while it's in the bootloader, you gotta install the google Nexus S drivers or the one from PDAnet. That was where I got stuck at 1st when I tried rooting. Fastboot couldn't find my phone because I had the generic windows drivers.
Also if you have PDANet on, turn it off before putting your phone in fastboot mode.
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
vapor311 said:
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Interesting. So the steps on the referenced one-click method you posted are:
1) put your phone in fastboot
2) do the fastboot oem unlock command manually.
3) run a batch file that contains two lines (fastboot-windows.exe flash boot boot.superboot.img & fastboot-windows.exe reboot).
I guess that's easier than putting your phone in fastboot directly and typing in a command to flash clockwork, then selecting a zip file to install from clockwork, but not much.
The drawbacks here are of course that it's superboot, and that it requires you to unlock the bootloader. I guess it's useful if you're really noob, but it only saves you typing one command.
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
vapor311 said:
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Why do you prefer it unlocked?
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
main reason i think there is no one click root is because its so simple to do on this phone
vapor311 said:
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You do not need an unlocked bootloader (currently) to use custom roms, or to root, or to flash clockwork recovery, etc...
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
vapor311 said:
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Of course, but since you contradicted my statement earlier that one disadvantage to the posted method here was that it had you unlock the bootloader by replying that you like having yours unlocked, I was trying to pin down if there was an advantage to unlocking the bootloader that had been discovered that I hadn't heard yet.
There's indication on git for our phone that the next update includes a change to the bootloader being able to use the fastboot boot command while locked. Unknown what that will actually do in terms of just fastboot flashing clockwork to apply root and custom roms.
I c wut u did there. I'm not sure how the update is going to affect things ATM. I keep it unlocked for "in case sh*t" happens. Never know what an update will bring in changes to rom management.
Sent from my Nexus S using XDA App
OK so I'm commingle from the epic and I want to root for titanium but I've seen there is different varrent and different ways to root what meatod will work and I have looked and searched before I get the plaza use search I just don't want to brick using wrong root meathod thank you in advance for who ever is willing to help
Sent from my Nexus S 4G using XDA App
+1
Sent from my Nexus S 4G using XDA App
Do you have SDK and working fastboot? That is step one.
Yep
Sent from my Nexus S 4G using XDA App
*note* i did not develop this method entirely i scrapped it together from multiple posts found here on xda. I give credit to those who did the work first. it worked fine for me hopefully it works for you too.
download sdk tools and install
download fastboot drivers and install
both found here
after that, download clockwork recovery
also download superuser files you want eclair/froyo su it works for gingerbread too.
open command prompt and enter the following
Code:
fastboot devices
if it doesn't return your phone in the following line double check that your fastboot drivers are properly installed.
if it does enter the following
Code:
fastboot oem unlock
follow the onscreen prompt on your phone. volume up to "yes" and hit power to confirm
Your phone is now unlocked. next step installing a recovery.
navigate to the folder where the clockwork recovery image is located.
Code:
cd C:\users\#username#\downloads
or wherever the file is on your pc.
then enter the following
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
you now have a proper recovery installed on your phone you may now vol dn to recovery and hit power to confirm
VERY IMPORTANT
in recovery vol dn to "backup and restore" power to confirm
select Backup and hit power again.
you just created a nandroid backup of your phone if you ever mess it up you can restore it back to when it was stock and problem free
In recovery vol dn to "mounts and storage" power to confirm
then choose "Mount USB storage"
copy the SU zip to the root of your phone's storage
then "Unmount"
then "+++++Go Back+++++"
then "install zip from sdcard"
then "choose zip from sdcard"
Choose su-2.3.6.1-ef-signed.zip
then select "Yes - Install su-2.3.6.1-ef-signed.zip"
Reboot your phone and you should now have a stock rooted phone.
Ty Joe I will do this as soon as I get home
Sent from my Nexus S 4G using XDA App
tildog said:
No I have not but did not want to start on anything till I confirmed that the method will not brick I will dl. Sdk. And drivers tonight at work ATM
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D
netarchy said:
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D
Click to expand...
Click to collapse
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Just remember to make a nandroid backup in clockwork after you're done rooting, so you always have a working setup to fall back on if something should go wrong in the future
tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
i just came from the evo and rooted that phone way before any one click roots where out. Trust me the nexus s is 100 times easier to root than any other phone it's actually pretty quick and easy, i just went into great detail so anyone could be able to follow it hopefully. I think i have seen some 1 click roots for the ns but i never looked into them once i saw how relatively pain free it is to do this way.
i remember having to copy and paste adb commands and spamming them while my phone rebooted. and hopefully... hopefully it would unlock the evo.
just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..
shabbypenguin said:
just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..
Click to expand...
Click to collapse
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.
Thanks all. I'll try this later tonight and report back. I've seen a few root methods around here but wanted to make sure it was no different for the ns4g before I actually got into it.
So to confirm one more time Joe's method he posted here should work for the ns4g as well, right?
Sent from my Nexus S 4G using XDA App
matt2053 said:
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.
Click to expand...
Click to collapse
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Yeah for sure, I'm not saying its good or bad. Just pointing out the difference in that method. Some people prefer to keep the bootloader locked anyway. Unlocking it is always one command line away.
Sent from my Nexus S using XDA App
shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)
netarchy said:
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)
Click to expand...
Click to collapse
cool thanks for the support man
Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?
oubravs2b said:
Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?
Click to expand...
Click to collapse
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.
netarchy said:
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.
Click to expand...
Click to collapse
Good to go I think - thanks netarchy!
So for you all that are trying to follow joe's steps, they are correct except the download linked in his post will give you the 3.0.0.4 version of Clockwork and you need the one referenced by netarchy (3.0.2.4). All worked as planned after that.
Rooted and ready to flash netarchy's kernel on ns4g!
I've always rooted and flashed roms on my phones. Everything from the sweaty palmed s-offing of my Desire to the simple fastboot commands on my Galaxy Nexus. I've then always gone on to flash roms at least weekly.
I'm about to buy a Nexus 10 and feel like leaving it stock but rooting it to be able to use stuff like Ti backup etc. Is this as straightforward as the GNex - fastboot unlock and fastboot flash su.zip?
I want to still have OTA updates though, does this mean I need to keep the stock recovery and is there a 'root keeper' app?
xda premium app on AOKP'd GNex
GrenW said:
I've always rooted and flashed roms on my phones. Everything from the sweaty palmed s-offing of my Desire to the simple fastboot commands on my Galaxy Nexus. I've then always gone on to flash roms at least weekly.
I'm about to buy a Nexus 10 and feel like leaving it stock but rooting it to be able to use stuff like Ti backup etc. Is this as straightforward as the GNex - fastboot unlock and fastboot flash su.zip?
I want to still have OTA updates though, does this mean I need to keep the stock recovery and is there a 'root keeper' app?
xda premium app on AOKP'd GNex
Click to expand...
Click to collapse
There are different methods, but if you want to stay on stock, use superboot method. You just need to install a drivers on your pc, and double click a file. You don't need to be unlocked or anything. Search for Nexus 10 superboot on the search button.
Btw I recommend you, if you still don't have the nexus 10 and plan to flash roms, you should use wugs toolkit. Root, unlock, install twrp (custom touch recovery) and in case any day you want to flash a rom, you won't need to unlock and lose your data. Just make a backup and you're ready to go.
Superboot: http://forum.xda-developers.com/showthread.php?t=2003938
Wug Toolkit: http://forum.xda-developers.com/showthread.php?t=2015467
If you want to still have otas, then just use superboot, you don't need to keep the stock recovery but to avoid problems keep it. Just make sure before use ota, you haven't changed any file in the folder /system. For example if you place the aosp browser in /system/apps, put the original files on there, flash the ota, and then put the aosp browser files again. And yes, on the google play there's root keeper and it can be used on nexus 10.
Thanks. I should have the drivers set up on my pc unless I need Nexus 10 specific ones. This was the biggest pita lat time.
Doesn't installing a custom recovery stop OTAs working?
Things is, you're right. I know I'll probably end up flashing a custom rom in the end.
xda premium app on AOKP'd GNex
GrenW said:
Thanks. I should have the drivers set up on my pc unless I need Nexus 10 specific ones. This was the biggest pita lat time.
Doesn't installing a custom recovery stop OTAs working?
Things is, you're right. I know I'll probably end up flashing a custom rom in the end.
xda premium app on AOKP'd GNex
Click to expand...
Click to collapse
Nope it doesn't. Once the ota shows up, and reboots to recovery, if you have a custom one, it asks if you wanna keep it.
Thanks. All I know is on the Galaxy Nexus the OTA can fail if it detects a non-standard recovery.
Maybe its a CWM thing?
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
stator said:
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
Click to expand...
Click to collapse
Hi, stator...
Your post isn't quite clear... does the device boot normally? If so, you should have no problems booting into the bootloader.
But first download the latest UPDATE-SuperSU-v1.51.zip to your Nexus 7.
Shutdown the Nexus as normal. Then press and hold the VOL down button... whilst continuing to hold, press the POWER ON button.
This should boot you into the bootloader (in fastboot mode).
From there, and from your PC, Fastboot flash a custom recovery... (Chainfire recommends TWRP)... with the line...
Code:
fastboot flash recovery recovery.img
Where recovery.img is the name of your custom recovery. I usually just rename it to 'recovery.img' (without quotes) anyway - makes for less typing at the command prompt.
Ensure you get the correct recovery for your device....
TWRP for Nexus 7 Wi-Fi ('Grouper') or TWRP for Nexus 7 3G ('Tilapia')
Although a new version of TWRP is now available (2.6), I had some weird issues with this... particularly when copying Nandroid backups off of my Nexus 7 to my PC. Random 'permission denied' messages would crop up running an ADB PULL command... copying via MTP didn't fair much better either. TWRP 2.5 works without problems though, and it's the version I would recommend.
Anyway... back on topic...
Upon completion of flashing TWRP, boot into that recovery (whilst still in the bootloader)... and select INSTALL... navigate to the folder where you downloaded Chainfires SU root updater (usually, the 'download' folder)... and SWIPE to confirm.
Reboot as normal... you should now be rooted. This can be confirmed by any one of the numerous Root Checker apps available in Playstore.
I haven't experimented with busybox... if you mean this version, I haven't installed it, and nor am I going to... at least not for a while.
My Nexus 7 is still in the process of being rebuilt from the ground up, after having fastboot flashed the factory image, necessitating a full wipe (I was running a custom ROM/Kernel combo before)... so I'm taking this slowly, re-installing apps carefully.
It seems that some apps that worked fine under 4.2.2 are broken under 4.3. MX Player and Adobe Flash Player to name a couple.... but QuickPic and Titanium have now been fixed and work fine under 4.3. I'm under no illusions that Adobe Flash Player will be fixed anytime soon... it's been technically deprecated by Adobe for a while anyway.
Anyway... good luck... and hope you get root sorted.
Rgrds,
Ged.
I am having problems with Busybox as well even though i did not take the OTA. I flashed CleanRom, and Faux kernel.
Just fyi
Sent from my Nexus 7 using xda premium
First and foremost I would like to apologize for taking so long to reply. Real life had me out of town and I didn't have my tablet with me. I tried the advice given but it didn't work at first. It took multiple attempts but I finally got my tablet back to stock. I guess my Nexus 7 didn't agree with the 4.3
OTA while rooted. I can now unlock, root, and even change roms once again. I don't know for sure what was causing the problem but it's all good now. Also, I was always able to use my tablet during my little crisis. I was just unable to unroot or even flash a new rom. Thanks again for all the help.
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
shevich said:
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I sincerely hope this is a joke. I most definitely said thanks. I even apologized for taking so long to reply. Please try to be constructive or don't bother to post. I've been frequenting this site for quite sometime although I've never posted or even joined until recently. This community has been extremely helpful. The last thing that is needed is another troll. Thank you.
He was talking about using the thanks button.
Sent from my Galaxy Nexus
Heya...
On my 16GB Grouper I had installed the stock rooted 4.3 rom. Yesterday a system OTA update message appeared on my screen - 1.7 MB. I let it download and install over night and just went to bed. Came back in the morning to a boot loop where the device got stuck with the four colorful thingies animation. I can access the bootloader, but the recovery seems to be broken. Can't remember if I had anything other than the stock one... Anyways, now I'm strugling to get this thing going again. I am a zero at ADB but willing to learn whatever is necessary to get me started with a working recovery at least. No tool root box will do anything really for me...
Thanks for your help in advance
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
hettige677 said:
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah. It would be dumb to actually learn what you are doing to your device. You should totally use a toolkit.
/s
Sent from my Galaxy Nexus
Honestly, I'm just showing the user one way, I anticipated him of being a newbie. For the record, it shows you all the process's happening.
Sent from my Nexus 7 using xda app-developers app
Thank you guys. You might not believe it, but I'm not a newb to Android or flashing. It's just that I've always been playing around with Samsung devices and there you'd normaly turn to Odin in case something went wrong. Here it's different.
Anyways, with this comprehensive guide I've been able to reflash a recovery image and my old rom. Unfortunately losing all of my data in the process, but there was no way to save it.
http://www.androidupdate.us/recover-bricked-device-fastboot/
In case this happens to anybody else.
Cheers