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
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.
Hi everybody and happy 2014 from Italy!
For this Christmas i decide to get a tablet and i choose the nexus 7, i bought it from a guy coming from ipad
he bought the table on 24th Dec and i get i 3th Jan for a cheap price. I started to configure the tablet and everything
worked fine till i ota updated it. The update fails and after the reboot the device begin to freeze while running angry birds.
This is very strange, so i started to check around on how to update it and after many searches i always fall down in the update
fail error. I tried first to flash android kitkat through adb sideload and i got the message :
assert_failed: apply_patch_check("/system/lib/libchormeview.so"...
E:Error in /tmp/update.zip
(Status 7)
Installation Aborted
the i tried to fastboot a previous firmware update from google development site (JSS15R) and i got the same message.
My tablet runs the JWR66N firmware, i wouldn't root, unlock the bootloader or even flash a custom rom for the
moment i would like first keep it as it is for a couple of weeks and than start to search a good custom rom.
I tried to search this forum but i didn't find a solution that fits my needs, anybody has may help me?
Pleaze HELP!!! THANKS in ADVANCE! CIAO!
PS.: The OTG doesn't work with current firmware do i have to flash a custom rom to use it or it is supported in next update?
It sounds like he's tweaked at least one core file, such that you can't get the OTA update. Since you don't know what he's done, I would recommend that you root and flash the stock 4.4.2 ROM (which is unrooted). You will need to unlock first and also install the generic Nexus 7 drivers.
You can get the full 4.4.2 from here. There's a file "flash-all.bat" within that will flash the stock recovery and 4.4.2: https://developers.google.com/android/nexus/images#razor
Drivers are here: http://developer.android.com/sdk/win-usb.html
You can use WugFresh's Nexus 7 toolkit to unroot and flash custom ROMs. It also has a copy of fastboot, I believe, which you'll need to unlock. Or you can get fastboot and ADB from here.
USB OTG doesn't work unless you're rooted, or unless you use an app like Nexus Media Importer (costs a few dollars).
Guybrush.d said:
Hi everybody and happy 2014 from Italy!
For this Christmas i decide to get a tablet and i choose the nexus 7, i bought it from a guy coming from ipad
he bought the table on 24th Dec and i get i 3th Jan for a cheap price. I started to configure the tablet and everything
worked fine till i ota updated it. The update fails and after the reboot the device begin to freeze while running angry birds.
This is very strange, so i started to check around on how to update it and after many searches i always fall down in the update
fail error. I tried first to flash android kitkat through adb sideload and i got the message :
assert_failed: apply_patch_check("/system/lib/libchormeview.so"...
E:Error in /tmp/update.zip
(Status 7)
Installation Aborted
the i tried to fastboot a previous firmware update from google development site (JSS15R) and i got the same message.
My tablet runs the JWR66N firmware, i wouldn't root, unlock the bootloader or even flash a custom rom for the
moment i would like first keep it as it is for a couple of weeks and than start to search a good custom rom.
I tried to search this forum but i didn't find a solution that fits my needs, anybody has may help me?
Pleaze HELP!!! THANKS in ADVANCE! CIAO!
PS.: The OTG doesn't work with current firmware do i have to flash a custom rom to use it or it is supported in next update?
Click to expand...
Click to collapse
These are just wild suggestions on my part. Uninstall all of the Chrome browser updates. If you're using Chrome Beta uninstall that, like I said these are just guesses on my part but the libchromeview makes me suspect the Chrome browser and uninstalling the updates won't hurt anything. Reboot then try the update again. If it fails do a factory reset then try again. If it still doesn't work you will need to flash the system image or the stock rom and of course to do either you will at the very least need an unlocked bootloader. OTG needs root and to use the app Stickmount.
This behavior started within the last month or so.
My Nexus 7 randomly reboots 2 or 3 times per day most days, but not every day. It's running the factory ROM and it's not rooted. It rarely reboots when it's actually being used. Usually the reboots happen when it's sitting idle. Googling around led to suggestions to take a bug report immediately after it reboots. I have a couple, but I don't know what I'm looking for in them. The files are over 111k lines long so it's not like I can just skim through the file. How can I go about finding out what's causing the tablet to reboot?
Lines beginning with F are describing fatal errors, E are for errors, W for warnings. Which stock image is installed?
tetakpatalked from Nexus 7
Are you using the latest update 4.4.2?
I think what i would recommend that if you are really concerned about this problem you have two options. One you could take it in and if you have a warranty you could possibly return it as a faulty device and get another tablet.
Second what i would recommend that you do is try erasing everything on the device and re-flash a clean stock factory ROM back on to the tablet and see if that helps.
One last option is that you could do a logcat or catlog and see if that helps you any...
You could do a log session and upload the text file here on xda (if its not too big) or maybe put the output on something like pastebin and maybe someone here on xda could help you. Most likely if i had to guess is that I think it might be a program that is causing your tablet to reboot.
So if you don't want to do do a reset and flash a stock factory ROM to your device try thinking back when your tablet was working correctly. Did you happen to install any extra apps? Maybe a big game? You could try deleting apps one by one to see if any of these newly added apps may be the culprit.
Here is a link on how to do a logcat or catlog session -> http://forum.xda-developers.com/showthread.php?t=1726238
Here is a link on how to hard reset your tablet -> http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
the above tutorial is for the 2012 nexus 7 the commands are the same just replace the stock image with the correct nexus 7 2013 one.
i hope this has been helpful...
-droidshadow
IDK
having this issue too. even if I flash a custom ROM and even if i hard reset/restore! I think it will be fixed in the next android update. Its annoying because im like in school using photoshop on my tablet to do a alternate book cover for a book report, then all of a sudden it shuts off and I loose my work!...
Android 4.4.3, will be released in the next week or so. Google has said it will fix the random reboot, most of us have been dealing with.... No need to flash anything... Just need to be patient with it for seven more days
--=={BSnapp} ==--
I didn't have any unwished reboots on Carbon ROM 4.4.2. Not a single one.
tetakpatalked from P5110
OK, all guys with fastboot conectivity problems, it really makes me sad to read about your issues and I hate to hear about bootloops and desperate forum mates!
Therefore, I think this will be solution for most of you: I will post here a new guide within less than 24 hours how to install ADB and fastboot in Ubuntu/Linux OS!
When you install Ubuntu OS, it takes only another 2 min to install ADB and fastboot.... and IT WORKS THERE!
Linux is in general much better than Windows for flashing Android devices. And it needs no stupid, nasty drivers so the things can't go so easyly wrong.
Use this time and already install Ubuntu aside your Windows. In most of cases it works flawlessly. You will have dual boot possibility. Please check WWW how to do it, it costs bit of time but it is really easy afterwards.
tetakpatalked from Nexus 7
Here it is:
http://forum.xda-developers.com/showthread.php?t=2726287
Good luck guys!
Don't forget feedbacks please!
tetakpatalked from Nexus 7
This is my first post, so please forgive any mistakes I make with a post.
My wife's Galaxy Note 8.0 tablet was being stupid, it would refuse to properly use the internet from our Asus router, would connect but apps would insist there was no connection. Was getting tired of that crap so I decided to install a custom ROM, since samsung can be kind of jackasses abandoning most their devices after one major update, was only running Kitkat for crying out loud. I had done so before, but issues arouse. For one, I had great difficulty finding a proper TWRP for some stupid reason, NO ONE seamed to know where to get a well working version. I found one, but it messed everything up, it seems to work just fine but any ROM I install has massive issues with the Google apps, they crash eternally and continuously so I can do literally nothing, can't even get past first setup. I came across talk that it was old TWRP to blame, that it has issues with newer OS's like the lollipop I was trying to install, and FINALLY managed to find a newer version of TWRP, but freaking Odin keeps hanging on it's install, gets to "Nand write start" then stops doing anything. I have tried different cables as well as different computers, does jack crap so far to help. My backup I made in TWRP doesn't even work, when I restore the result is nothing but a boot loop. I am trying to find a stock os to restore it to (mostly) original condition, but it is absurdly difficult for some stupid reason to find, found one all in one exe that didn't work for a damn. I was hoping there might even be a way to install the newer TWRP from with TWRP itself. Can anyone help me with any part of this?
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
kge420 said:
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
Click to expand...
Click to collapse
Sorry, but you are going to have to be a little more specific. I installed Switch, but connecting an off device obviously does nothing, should I install and let it boot into a broken ROM again, where gapps crashes, and connect it then?
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Thanks, pretty much.
kge420 said:
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Click to expand...
Click to collapse
None of what you said really made sense, I could not get to ANYTHING AT ALL that was not Odin or TWRP. But that link you had gave me the name for the stock os, I searched that and flashed it and now everything is great. So thanks, sort of. You even mentioned that method not working for you I think in that thread, but it did for me, so yeah.
All good then.