I put Ubuntu on my 7 using the Ubuntu desktop installer (had to do it manually, but yea...) that came out semi-recently and I want to go back to good ol' Andy so I can try out some cool USB OTG stuff I saw recently. I'm having a bit of trouble finding out how to flash Android back to it. Clockwork is gone and I tried an unbrick method and it didn't work. Anyone have any ideas?
Thanks!!
rmp5s said:
I put Ubuntu on my 7 using the Ubuntu desktop installer (had to do it manually, but yea...) that came out semi-recently and I want to go back to good ol' Andy so I can try out some cool USB OTG stuff I saw recently. I'm having a bit of trouble finding out how to flash Android back to it. Clockwork is gone and I tried an unbrick method and it didn't work. Anyone have any ideas?
Thanks!!
Click to expand...
Click to collapse
There might be a better way of doing this but I always use wug fresh's toolkit and use the flash stock button. All it requires is bootloader with required drivers. That will flash the stock android and stock recovery!
Sent from my Nexus 7 using xda app-developers app
I shall give it a shot right meow. Thanks!
Edit: HA!! That's how I rooted my N4! I already have it and everything! Didn't recognize the name. I'll let everyone know how it goes.
After getting every damn error in the world and having to do it manually-ish, I got it. Thanks! Forgot about that program!
Related
Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.
Are you plugged in to your PC using the USB cable?
Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app
AndroidNinjaReview said:
Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
AndroidNinjaReview said:
Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.
Click to expand...
Click to collapse
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.
CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
The message I get is error: device not found when I use the adb reboot recovery. And I'm not familiar with it at all. I was trying to get that TV off animation and I was following a guide. This is my first root. So far....not a good experience.
Sent from my SCH-I510 using xda app-developers app
simms22 said:
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.
Click to expand...
Click to collapse
Can you tell me how to do this without the toolkit? I'm lost....
Sent from my SCH-I510 using xda app-developers app
help!
CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:
AndroidNinjaReview said:
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:
Click to expand...
Click to collapse
So i think all i need to do is flash the factory image. how would i go about doing this?
I flashed a patch for the tablet UI, but after it installed, it is stuck in CM10 animation. Tried to manually boot into recovery and its stuck on Google with the unlock sign. Imma nubee sorry... Please i really need some help.
Have you tried to hook up to a computer and try command adb reboot recovery?
akamachine45 said:
I flashed a patch for the tablet UI, but after it installed, it is stuck in CM10 animation. Tried to manually boot into recovery and its stuck on Google with the unlock sign. Imma nubee sorry... Please i really need some help.
Click to expand...
Click to collapse
Travisdroidx2 is right. You simply need to connect your N7 to a computer's USB port and then you can access recovery mode via the steps you mentioned or via adb. It's a bug that Google is going to fix eventually (I hope).
Sent from my Paranoid Nexus 7
Hi,
If you wish to use Tablet UI, I would recommend you to flash my rom It is called 'SmoothROM'
Thanks
Sent from my Nexus 7 using Tapatalk 2
How?
how do i do the ADB recovery??
Def, i will check out your ROM. post me the thread.
I GOT IT!!
Thank you so much!!
i check the tool box for nexus 7 and did like you said adb recovery and got it to restore.
THANK YOU!! seriously!!
LOVE XDA!!
LOVE ANDROID!!
jamesst20 said:
Hi,
If you wish to use Tablet UI, I would recommend you to flash my rom It is called 'SmoothROM'
Thanks
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I Don't think this is a good time to advertise your ROM.
Hello!
First post here and let me start off by saying i have no experience what so ever with rooting or custom roms . Purchased a N7 today that the seller said is running a custom rom. The wallpaper says clean rom so maybe that means something. It is running 4.1.2 and is prompting me to update....i assume to 4.2. My question is can i update? If so where does that put me? Will the update put me back to stock or is the device still rooted or running a custom rom?
Hey...i warned you...i know nothing about this but this appears to be the place to figure it out.
I have been reading for quite some time and could not find a clear answer.
Thanks in advance!!
You probably wont be able to update, you would have to flash back to stock 4.1.2. first .It does a check of certain stock files and system apk's before it will update,you would be better off going to https://developers.google.com/android/nexus/images and getting the full stock 4.2 and doing a flash using wugs,there are alot of tutorials on here for directions.
Flashing the stock image over the device is fairly simple. I'm not adv savvy at all, but the wugs toolkit works SO LONG AS YOU GET YOUR DRIVERS SET UP RIGHT. Wigs also requires you to be running Windows. But wugs toolkit will allow you to flash the factory OK mage and then root it so you can use stickmount and ad away and such.-Ara
Sent from my Nexus 7 using xda app-developers app
AraDreamer said:
Flashing the stock image over the device is fairly simple. I'm not adv savvy at all, but the wugs toolkit works SO LONG AS YOU GET YOUR DRIVERS SET UP RIGHT. Wigs also requires you to be running Windows. But wugs toolkit will allow you to flash the factory OK mage and then root it so you can use stickmount and ad away and such.-Ara
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you both....I will continue reading and see if I get enough confidence to mess with it.
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
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!