Hello everyone! I really need some help here I just got my brand new nexus 7, and I am trying to update from 4.3 to 4.4. I have a problem though, because it keeps getting stuck at about where the letter "A" is on the screen. The bar will sit there for hours and not go any further. I have tried restarting, two factory resets, and I have no idea what else to do. Please someone help? Thanks so much!
Since it's new, I highly recommend downloading the full stock 4.2.2, rather than spending time trying to update. The "flash-all.bat" file will do a full wipe and install 4.2.2 completely, with no need to get updates.
https://developers.google.com/android/nexus/images#razor
You will need to "unlock" first, which can be done easily through the Nexus Root Toolkit. After that, the same Toolkit can root your new N7, if you so desire.
http://www.wugfresh.com/nrt/
JakeReis said:
Hello everyone! I really need some help here I just got my brand new nexus 7, and I am trying to update from 4.3 to 4.4. I have a problem though, because it keeps getting stuck at about where the letter "A" is on the screen. The bar will sit there for hours and not go any further. I have tried restarting, two factory resets, and I have no idea what else to do. Please someone help? Thanks so much!
Click to expand...
Click to collapse
Don't rely on tools. Do it manually, it's easy. Watch the tutorials.
Unlock bootloader and install custom recovery http://www.youtube.com/watch?v=6k4rCaMPSQ8
Root http://www.youtube.com/watch?v=yTdUd-jlbP0&feature=youtu.be
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
I also do everything manually, but for the sake of newer owners getting used to the device, I'll refer them to the kit.
Related
Okay, this might not be the place to get some divine intervention to start (or stop) happening, but I'm really starting to get a nervous breakdown and I desperately need some help. I'm going to tell you my story, because it's my last resort before throwing this phone in a fire and never buy anything Samsung related ever.
So the phone came out of the box and for some magic reason I got the bootloader unlocked and phone rooted. It all started with installing CWM I think. This stopped my phone from taking OTA updates. Of course I could have known, but for some reason I installed CWM. I don't know why! I regret it, I don't even want a different ROM installed, I thought it was necessary to root the phone. So when I got the OTA, at first I was like YEAH YEAH, but then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. It was 2 in the morning and I had to get up early to go to Dublin for two weeks. This was really not the time...
So after trying a few times of getting the OTA update message again and failing every time I got it, I started searching. Yes, CWM is installed so you can't OTA they all said. Nice, now I hate on the back laying androids AND CWM. Of course the one to hate is me, but I already hate myself so that's no use. Anyway I used the Galaxy Nexus Toolkit 5.6 to put back stock recovery. Now I had to wait a few weeks again before the update turned up again... By this time the phone started to be REALLY slow when scrolling through the home screen(s). It also is empty before the day is done, but I don't know if that's because of the phone being f'ed up or because I'm too demanding.
Anyway, back to the story. Finally the update came about a week ago, and again I was like YEAH YEAH! But then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. To make things more fun it did a reset of my Go Launcher, 7 screens of widgets and autistic arranged shortcuts gone... Of course I wanted to try again, so this morning the OTA came again and had the same result. By now I killed quite a few, so this has to end, but don't worry there is more torment ahead.
I can't figure out what is wrong now, so I thought, f~ this s~, this phone deserves a full undress and back to the womb operation. So installing all Galaxy Nexus Toolkit v6.0 stuff and drivers. Connect phone, start toolkit, choose 3 (GSM 4.0.2. build ICL53F), phone turns up in main menu, try to put back recovery, -waiting for device-...
It stopped... Or it didn't really stop, it just stood there saying, -waiting for device-... So again a few innocent people died. Tried a different choice, (relock bootloader, just to give the phone a good beating) -waiting for device-...
I raged, pulled my hair, again killed a few, silently cried in a corner and finally started typing this eulogy...
Please kind sirs and madams, help me get this phone back to stock 4.0.4, accepting OTA, bootloader unlocked and rooted, I'm really desperate...
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
How do you proceed?
First you need the SDK for you system
http://developer.android.com/sdk/index.html
After this you have to start the SDK manager and install "Android SDK Tools" and "Android SDK Plattform-tools" if you are using Windows you have to install USB drivers too. You could find this under the point "Extras".
After that you have to download the factory image to clean your device, once.
(Notice your SD-Card gets wiped)
https://developers.google.com/android/nexus/images
Look for right version, which fits to your device.
Now you have to bring your telefon into the bootloader by pressing all 3 buttons at the same time Volume+/Volume-/Power. After this you have to unlock your bootloader if you don't already done this.
Now plug in your phone into your computer an go into the unpacked folder from your factory image. There would be an file called flash-all. You have to run this file. Now your phone is flashed with stock rom, stock kernel newest baseband and stock recovery. Now you get ota updates from google. After this you should look for an howto root your phone in the developer section. You don't have to install clockworkmod recovery for rooting. But clockworkmod isn't change the ota. You get OTA with cwm.
Hope i understand your problem an you could understand my bad english. But i want to help. If some questions ask here into the thread.
regards
theSlack said:
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm out of the house a lot, leaving for Brussels in a couple of hours. I don't want the hassle anymore. I just want to be able to leave the house to go to another hotel and update OTA. I don't have time for all this flashing stuff.
Sent from my Galaxy Nexus using XDA
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
If you want to head back to stock ROM, then one of the ways to do it would be to install Android SDK & then follow the instructions from Google developers site.
Else you can try using the Galaxy Nexus Toolkit to do this for you. I think the latest version is 5.7.
Android SDK - http://developer.android.com/sdk/installing.html
Android Images - https://developers.google.com/android/nexus/images#yakju
Galaxy Nexus Toolkit - http://windows.podnova.com/software/5996358.htm
smsmad said:
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
Click to expand...
Click to collapse
Ah yes, I now see where I went wrong with the toolkit, I didn't put the phone in fastboot. Stupid...
How is the stock recovery supposed to look like? After putting back stock recovery with the GN Toolkit, I press 'vol+/vol-/power' and choose recovery. It then displays the belly up android with exclamation mark. Is that the way it should be? Am I doin' it wrong?
yes it is the stock recovery. But you dont need it. Flashing everything into fastboot mode(bootloader)
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
If you flashed the latest Factory-Image there is no OTA out there. It is the newest version of ICS for your Device.
Maybe i don't understand what you mean with failing OTA. Could you explain it a little bit more?
As I said in the long story, I'm currently 4.0.2. and every time when my phone says, "You have update 4.0.4. standing by, please reboot" it fails.
i would prefer to flash the factory image and root your phone again
then you have a cleaned phone and OTA should work but you don't need them because you are at latest version.
https://developers.google.com/android/nexus/images
i wrote how you could flash it page before, remeber you wipe your data from sdcard
Lex_Michdeandroid said:
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
Click to expand...
Click to collapse
I don't know if I can answer why the OTA isn't working (I'll leave that to smarter men than I), but having an unlocked bootloader and root access won't stop the OTA. I had my phone in that state when the 4.0.4 update came out and all was fine, just had to run the command to get root of my phone again as OTA removes root.
Ah great! S~ has just hit the fan, it's bootlooping after trying option 8 (flash stock rom from google). Oh I really am going to kill myself sooner or later...
Edit: not killing myself yet, just had to pull the battery... Let's see what I f~ up next...
Very strange you problems i don't know the Toolkit and don't know how it flash the stock rom. But i could imagin that it only flash rom and not the other things like recovery and so on.
Try out the hard way without toolkit and use sdk and included batch file into the factory image. it is the clean way and you see whats done.
Ok, I now rebooted the phone after option 8 in the toolkit and it seems I'm running 4.0.4. I have to go to Brussels now for two weeks, but I'll try to post some screenshots later. I'll also be back to thank all of you for holding my hand, I just don't have the time right now. Of course this won't be my last problem (I still have a TF101 that needs some RMA action), but I hope I won't be needing too much time consuming support anymore.
Just got in the hotel, and unable to use my phone in Belgium. No available network... Wifi works, 2G/3G works in The Netherlands, 2G/3G unavailable in Belgium...
Screenshot of my device: http://oi46.tinypic.com/34xp89y.jpg
Sent from my Galaxy Nexus using XDA
Just tried my SIM in a different phone, problems are with my network. Phone works with different SIM, so false alarm.
Sent from my Galaxy Nexus using XDA
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
msedek said:
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I rather eat my own shhhhh... shorts than buy something with an apple on it. With the help of you guys it always works out fine, it just takes a life or two.
Sent from my Transformer TF101 using XDA
Hi guys
I have a rooted GSM Gnex cunning running JB 4.1.1. I have used Toolkit v7.6.0 to root which was the easiest way for me, all went well and is rooted.
However on the Fastboot screen (blue bar at the bottom) reads "Fastboot Status- FAIL Invalid Command"
If I attempted to install any ROM via CWM TRWP ROM Manager etc, have tried 3/4 today, I get the error below
E: Error in /sdcard/(which ever ROM I'm installing)
(Status 7)
Installation aborted.
Along with the wee Android and red triangle
And suggestions where I have gone wrong?
My Gnex rooted and installed ROMs without an issue prior to a repair with o2 where they apparently installed 'new o2 software'.
Thanks folks
wworx said:
Hi guys
I have a rooted GSM Gnex cunning running JB 4.1.1. I have used Toolkit v7.6.0 to root which was the easiest way for me, all went well and is rooted.
However on the Fastboot screen (blue bar at the bottom) reads "Fastboot Status- FAIL Invalid Command"
If I attempted to install any ROM via CWM TRWP ROM Manager etc, have tried 3/4 today, I get the error below
E: Error in /sdcard/(which ever ROM I'm installing)
(Status 7)
Installation aborted.
Along with the wee Android and red triangle
And suggestions where I have gone wrong?
My Gnex rooted and installed ROMs without an issue prior to a repair with o2 where they apparently installed 'new o2 software'.
Thanks folks
Click to expand...
Click to collapse
Flash cwm again, sometimes it doesn't stick, and without it it's really hard to flash roms
Tried that a couple of times with no success, still the same error
what command are you typing in?
Now your asking me to open a command window
I have been trying to install ROM through CWM GOO manager and ROM Manager most of the day with the same error
I'm a complete newbie when it comes to command prompts etc
I hate using 'I told you so' like comments, but you really shouldn't be rooting, especially via tool kits, if you are a noob. I really suggest reading/learning what tool kits are doing so you can troubleshoot.
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
I hate using 'I told you so' like comments, but you really shouldn't be rooting, especially via tool kits, if you are a noob. I really suggest reading/learning what tool kits are doing so you can troubleshoot.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Agreed. If you can't use fastboot/command prompts, you have no business rooting. Tool kits shouldn't even exist because they allow this. For first time rooters, always learn fastboot/adb, it isn't very hard
Sent from my Galaxy Nexus
Thanks for the replies guys.
The 'I told you so' comments not a problem, we all learn by our mistakes, and hopefully better ourselves.
The phone has been successfully rooted and a few ROM tested until I found one I like, it was unrooted to see what the OTA JB update was like.
Now any pointers on where I will learn the required fastboot/command prompts?
Give me gas boilers and turbines anyday
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
should tell you how to flash ROMs as well without using ROM manager so you have a less chance of it not working.
Agreed, that's a great option. I personally used this guide to get moving, http://www.droid-life.com/2011/12/1...extended-batteries-day-one-thoughts-and-more/ , but this forum will answer pretty much any question you might have at this point in the process.
Sent from my Galaxy Nexus using xda app-developers app
And by this forum I mean xda.
Sent from my Galaxy Nexus using xda app-developers app
Hi there,
I have a slight issue with my nexus 7, I would say I am a novice with technology - so hopefully someone can help me out! I have a rooted nexus 7 and I recently tried to install 4.3 jelly bean (without looking at instructions on here) which has left my Nexus 7 stuck on the coloured X screen that usually appears when you boot the device. I have tried to cLear the data cache and restart a fair few times but it just can't get past that screen! Asus have told me it would cost a minimum of $220 to have the device repaired so before I even consider that option I wanted to see if someone could help me out?
Thank you in advance!
Download Wug's Nexus Root Toolkit. Once it is open, click "Soft-Bricked/Bootloop" under the "Restore Stock + Unroot" button. After your selected soft bricked, click that button. Press ok on the popup window, and let it download the software. You will be given further instructions to repair your device from the program after you've completed these steps.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Thanks
supitsronnie said:
Download Wug's Nexus Root Toolkit. Once it is open, click "Soft-Bricked/Bootloop" under the "Restore Stock + Unroot" button. After your selected soft bricked, click that button. Press ok on the popup window, and let it download the software. You will be given further instructions to repair your device from the program after you've completed these steps.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thank you, the wug website has been down for a few days so hopefully it will work soon! I'm missing my nexus!!
Br1t7s said:
Thank you, the wug website has been down for a few days so hopefully it will work soon! I'm missing my nexus!!
Click to expand...
Click to collapse
The first time I bought my N72013, I was really eager to root it and ended up with what you have. Wug is a real nice toolkit for Nexus users. Just to add to what the other guy said, make sure you get the correct factory image for your device (JSSR1Q or something like that).
There are 3 ways to go about flashing that and you need drivers if ever you're missing some. Just a few cents of mine.
I don't root it. What s the point?
And it works fine since August 2012....
Just enjoy your tablet... And if anything happen, it's to Asus to repair.
Don't even open it...
Cant root on a mac?
MartCLEANRFr said:
The first time I bought my N72013, I was really eager to root it and ended up with what you have. Wug is a real nice toolkit for Nexus users. Just to add to what the other guy said, make sure you get the correct factory image for your device (JSSR1Q or something like that).
There are 3 ways to go about flashing that and you need drivers if ever you're missing some. Just a few cents of mine.
Click to expand...
Click to collapse
Hi there,
I am overseas at the moment and only have access to a Mac - is there a program you (or anyone else) can recommend to try this process to restore my nexus?
Cheers!
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
doublewhamy said:
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
Click to expand...
Click to collapse
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Aerowinder said:
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Click to expand...
Click to collapse
I appreciate the assistance!