I got the OTA update today and it failed (phone was rooted). CheckedOnce it rebooted I tried the 3 button combo to get into recovery and it worked. As well as going into DL mode using USB. Hopefully this will fix others who could only get into recovery and dl mode using ADB. Also, even though it "failed" it did update to JH7. haven't checked GPS....
Same for me.
Sent from my SAMSUNG-SGH-I897 using XDA App
I got the same results as you but my GPS is still terrible.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rooted and Lag fix installed. Update "failed" but seems to have installed JH7 (no new apps though). I get a GPS lock indoors now, something that has never happened before but a 40 minute drive in the car today yielded no locks ever, even after two reboots. It seems like it may have helped in one regard but dang, driving around in a convertible for 40 minutes should have gotten a GPS lock.
The three button recover mode worked the first time I tried it after the JH7 install. Before today I spent easily an hour+ trying every key combination documented and I never once saw recover. After the update I hit recovery on the first attempt, cool fix that wasn't even documented officially.
I'm getting the same results. I've spent countless hours googling and trying every key com possible trying to get into recover mode prior to the OTA update and nothing worked. Last night i checked to see if the update is available for my phone and it was. The phone downloaded everything without a problem, it rebooted and pooped out at 50%. After reading this post I tried the 3 finger salute and like you guys i got it to work.
When you guys check the baseband version did it change? There were reports of failed updates but baseband version changed. (mine didn't)
I did the root when I got the phone. I cancelled the original OTA update for reasons I don't know.
then I tried 3 button combo and IT DIDN'T WORK!
I tried to do the update again and kept getting communications error .
I tried to flash the JH7 ROM, that still didn't fix it.
Used Odin3 to go back to stock and try to update, this time it downloaded the update but crashed at 50%, JH7 never installed (said JM6 in about). But low an behold, that 50% somehow fixed the 3 buttom combo!
went back and flashed Cog 2.1 and 3 button still works!!!
Another 3 button combo fixed by OTA JH7.
Fixed for me. Further updates will be less nerve racking for sure now.
Mine worked in the past. I did not try it after I put cognition on the first time and then last night had a horrible brick moment cause I did a stupid restore.
I work like a champ now thanks to the good folks at this message board. The only thing is I cannot get into download or recovery mode which is concerning to me. I need the ability to do this from cold start, the only way in for me right now is once booted to go in terminal emulator and issue the command.
Does anyone have any suggestions for me? I am running cognition 2.1.1 right now, I have done 1 restore with Odin as well.
Mine worked in the past. I did not try it after I put cognition on the first time and then last night had a horrible brick moment cause I did a stupid restore.
I work like a champ now thanks to the good folks at this message board. The only thing is I cannot get into download or recovery mode which is concerning to me. I need the ability to do this from cold start, the only way in for me right now is once booted to go in terminal emulator and issue the command.
Does anyone have any suggestions for me? I am running cognition 2.1.1 right now, I have done 1 restore with Odin as well.
Related
I used designgears' jh7_ota.zip to update my phone to JH7. It worked fine. The one reason why I used it was because the OTA update had gone through to 100% and then crashed. In the "About phone" menu it had the right kernel version and the right baseband version, but the Build number was stuck on ECLAIR and not showing ECLAIR.UCJH7 like it should. So after using the JH7_OTA.zip it showed the right build number and the PC Internet option was gone from USB options like it should have been. Also, the GPS started working pretty well.
The one thing that sucked was it completely wiped my phone. So after reloading all my apps and redoing all the customizations I finally got it back to how I like it. Then I happened to notice that the "Build number" had somehow reverted back to just "ECLAIR". I also noticed that "PC Internet" was back as an option when USB was plugged in. I have no idea how it reverted back after I had successfully installed JH7. I never used ROM Manager or Titanium Backup to restore anything, I just went and redownloaded everything and reinstalled everything.
Has anyone else seen or had this happen to them? I had to reinstall JH7_OTA.zip again. And again it wiped my phone out completely. Having to go back through and reinstall everything all over again. How annoying.
You could always master clear, flash stock JF6 and then use Mini Kies to get the update. That way you know you have a fresh install.
I just did that coming of Cognition, loved it but didn't use any of the useful features (mobile AP, tethering) to make it worthwhile. I still bought DG a beer, dude works hard.
That was what I did to get the JH7 update. Although, I did use designgears' zip file rather than mini kies. Mini Kies wasnt out at that time. I used odin one click to revert to stock JF6, then the first thing I did was install clockwork recovery, then I installed designgears' zip file. Everything worked great for weeks. Cant see how or why it reverted back to build number "ECLAIR" from "ECLAIR.UCJH7".
I reinstalled JH7 with DG's zip file again since I still had it on my sdcard. Its back to the right version, build number says the right thing and pc internet is not an option and gps seems to work good and battery life seems to be better again. If it monks up again I will flash back to JF6, then use mini kies to get the JH7 update and try that.
I dont know whether its android or its just this galaxy S, but I've never had such a glitchy phone before. Random software crashes, random shutdowns, half-baked gps, updates that dont work and even brick phones. Just seems like I cant go more than a day or two without something on this phone F'ing up. Is this how it is with android all the time? This feels like the microsoft windows world a la 1995-2000. I thought we moved past all these crashes and glitches with plug and play and with Windows XP.
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
jahfry said:
May or may not be the same thing ... but ... my wife updated to the current release OTA and said it worked. However I noticed the other day that she still has the PC Internet option that shouldn't be there.
Click to expand...
Click to collapse
Go to About Phone and look at the build number on her phone. If it really took the full update it will say "ECLAIR.UCJH7". If it didnt it will still say "ECLAIR".
The very first time I tried to get the update OTA, it downloaded, then installed and it went to 100% on the install screen, but once it reached 100%, it then said "Update is failed". And when I rebooted it, the build number was still at "ECLAIR". and I still had PC Internet option and Quick Office wasnt installed and it acted kind of "glitchy".
When I downloaded and installed the zip file from Designgears, I could tell right away the the update was truly installed. Build number was "ECLAIR.UCJH7". PC Internet option was removed from usb options. Quick Office was installed. It ran a little smoother. GPS performance was somewhat better, and I did notice improved battery life.
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
If you can get to the factory reset in the settings menu that would the first thing to do. And then check for an update. Make sure you set the wifi to not turn off and I would keep the screen from shutting off while downloading the update. Check in settings "about Device". If your not 3389 or higher then you need to update
I had this problem back in November when I first got my tab. Even though nothing seemed to work right, I was able to connect it to my desktop and push across clockworkmod v .08 and a custom rom. So, I never used the original rom more than 10 minutes.
If you can't get it connected while booted in original rom, then Bekit's NVFLash full restore procedure works really well. Just follow the steps carefully and it's a quick and painless factory reset to a known working rom.
These things are virtually unbrickable (is that a word?).
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
badfrog is correct. If you factory reset the device it should be fine from there - then you set up your wifi and get the update.
Go into your app drawer and choose Settings. I don't remember if you can do it from the menu button as I'm on a different launcher.
Inside Settings go to Security and select Factory Data Reset. Do this, the unit will reboot and come back up at which point you'll be asked to set it up. It may take some time. Set your Date and Time correctly and set up your Wifi and such.
Once that's done you'll likely get a prompt to update very soon after Wifi connects. DO NOT DO IT, yet.
Within Settings, go into Display and set the Display Timeout to Never.
This ensures that the tablet doesn't sleep or turn off your wifi while it's downloading the update. It's not likely to happen but if your connection is on the slow side and the timeout is set too low, it can mess things up.
Once you've done that, proceed to let the tablet update itself. Again, it may take a bit of time.
Once it's done, make sure you take not of what you have. You'll find this information under Settings in the About section. The last version I got was 3389 - but something newer MAY be there for you. If you get anything less than 3389 then you will have to wait until you get another notification for an update. I don't remember how they work - but I THINK you should get the newest one there.
Once you've confirmed you're on the most current build, It may not be absolutely necessary to do it, but I would factory reset again just to clear the 'gunk' of the older TnT out in case there is actually any.
When I got mine and powered it on the 1st time, I got a bunch of FCs. I powered off and then on, and no more FCs, and it was fine after that. I think I posted asking about that, and someone (roebeet, I think) said it was a known problem. I don't remember the TNT version, but it was the one before 3389, or one before the one before 3389.
Jim
It is a known problem, especially with the older firmware. Sometimes the FC's are so bad that you can't even get into the settings to do a data wipe.
I've actually called CS about this, as an example of why they need an offline updater of some kind to get around issues like these. Suggestion: if you don't want to install clockworkmod, at least try to update the firmware to the latest and greatest, via one of the newer stock ROMs we're retrieved:
http://forum.xda-developers.com/showthread.php?t=842000
That might get you enough access to get into the Settings menu and do the factory restore.
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
try putting it back in download mode and see if odin recognizes it if it does do the return to stock agian
fawn87 said:
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
Click to expand...
Click to collapse
Check out my thread on the HOW TO. The link is on the signature line. Read it a few times.
re: the first paragraph with the colors -rainbow - it's due to lack of GB bootloaders.
The part where the phone is not responsive:
http://forum.xda-developers.com/showthread.php?p=19445643.
This link give you various method of getting into DL mode.
If it doesn't work,
try a different usb port on the pc, diff usb DATA cable, try a diff computer.
IF the phone is still not responsive, you a need a usb jig to put the phone back in DL mode.
search youtube for "usb jig". There's a vid that shows you how to make one.
gl
First, Lonnnng time reader/modder/hacker/technut, first time poster.
Secondly, my questions are: 1) Anyone else had such a positive experience as I did? And 2) Anyone else reproduce or trigger this ‘update’ in ICS?
Story below:
So I just purchased TF101 used, brought it home, and found out the long and hard way about the SOD/RR/DOCK/BATTERY/KERNEL issues that are plaguing a lot of users. So I researched for the past week (I'm a new owner), tried JB, ICS, etc, rom after rom. Still had same issues, and new ones (no wifi, sound, docking support gone, etc).
So, I went BACK to honeycomb 3.01 by flashing official update (WW version as I am in Canada) zip via CWM. I wiped cache, dalvik, data via CWM. Installed the zip. Tablet booted up perfectly. I did not sign into the google store. Turned tablet off completely WITHOUT being docked. Cold booted. Shut down. Used it for about 1.5 hrs, no reboots and could not repeat SOD/RR. However, HC is very slow compared to ICS. I then looked for the 3.2.1 update as it apparently makes the dock work correctly, and could never find it ANYWHERE (one rapidshare link and it was dead), all links were dead as the JP vers is the only one on Asus official site. 'check for updates' within the tablet did not work.
Next, I downloaded official xx.27 ICS off Asus website (around 253mB). Same procedure. wiped all cache/data/etc, flashed in CWM still (never put stock recovery as many recommended, didn't see the point). Booted tablet. Signed onto wifi, skipped signing in google account. Once in, turned off and cold booted back on. Used it for maybe 10 secs, and Asus updater pops up in task bar. The update had the same file-name of the update I just flashed however it had a July 27 date on it, and it was 302 mB (noticably larger than the 250~mB) update. NEVER saw this dialog before, even with my many attempts previously and all the different flashes/roms. Updater rebooted, installed itself (maybe 2 mins). I shut down completely once back in. Also, I still have not signed into my google account.
Following ICS update and shutdown, I then plugged my dock into wall outlet. I then finally docked (while off and for first time during entire process) the tablet, which then booted up. It immediately recognized the tablet, and made that ping sound confirming it was connected. Tablet booted up. I shut down, cold booted one last time. I then put it away on my shelf, lid closed. I opened this morning and 0 SOD or battery drain, which happened with EVERY SINGLE kernel/rom I tried for the past week. It would either SOD or RR. I left it open on 'about tablet' with uptime counter. It is still going. I checked various emails this morning, and ran some videos, etc, etc. Trying to reproduce RR/SOD. Usually it would occur within 10-15 mins of actually using it unit/being on wifi/etc/sleeping and waking.
I have a feeling that somehow Google is sending code (since you authorize OTA updates when you sign in) via being signed in that is somehow RR/SOD'ing (my theory), or there is some mysterious update I somehow triggered through this process. If anyone has reproduced this please let me know. But for now, this seems to fix battery drain at the very least, however I am running stock CPU clocks.
As i and many other are familiar with the RR/SOD troubles i have to say since i've updated with stock rooted .27 i haven't got the trouble anymore
Just checked and my transformer is still 86 % of battery capacity with an standby time of 1 day 18 hours
Before this update it almost always RR after using it when it was in standby mode again !
Ever since this update procedure my RR/SOD problems went down to near 0. I had one reboot in 3 long days of using my device, and that was from the stock browser. Which crashed before as well, anyways. I think this is a definite fix, which DOES NOT rely on external apps.
Not sure exactley how I triggered the update process. Please someone reproduce this 300~mB update that I triggered using CWM the entire update process!
Also, I have since extesively installed Google Play apps, and non-market sources. Not one crash, SOD, or RR. Dock work, charges excellent. Been using the unit for 2-3 days off and on with cbr viewer, movies n music playing, tonsof web browsing, etc. NO RR! NO SOD!
Hey Guys -
I hope this is the correct forum to post this in - its the closest I could find...
After owning an Nvidia Shield (now "Portable") and loving it, I went ahead and purchased an Nvidia Tablet which came in 3-4 days ago. It's great except for that without the Controller (which is on Backorder ), you really can't do anything a standard tablet doesn't do.
Once updated, I rooted it and proceeded to install all the tools and apps I use. One thing I had always wanted to try out was the Modded Google Play. I saw that it had an installer so installed it and applied the modded version. Once back up, I had some difficulty with stability so went back to the original version installed (4.8.20.)
Since then, sometimes when I boot up, WiFi doesn't work and is disabled. I'm not saying I can't connect, but that it's in the "Off" position and greyed out to where I cannot turn it on! After a 2nd reboot, it would work again.
Yesterday, I rebooted and it was disabled again. This time, though, no matter how many times I restarted, it was still disabled!! I tried uninstalling / reinstalling Google Play a few more times as well as a few other reboots with no luck.
I will also say that I tried one more thing which may be the cause. I tried out Freedom to check it out, but it crashed when opening plus I found out it takes away functionality so uninstalled it. After uninstall, I found out the hard way that I had to rename my hosts file to get online working. At that point, though, WiFi would at least be enabled.
Any suggestions for what I can do? If I need to restore to OEM, I will - I just need to know the correct process as I am rooted. I'm on build KOT49H.20258_426.6902.
Thanks!
I had this happen when I first booted mine up. Then again when I unlocked the bootloader. I didn't do anything other then keep trying and it came on. It hasn't done it since.
Sent from my XT1060 using Tapatalk
Thanks for the reply. I ended up just performing a full reset and starting from scratch. At least I know what I want installed on it, now. That resolved the issue and it retained the root.
Thanks Guys
I was really worried about it, I chatted with nvidia support and they said to return it to the store. For whatever reason it started working, and hasn't done it since. I've seen a couple posts on it, so it might be a software bug.
Sent from my SHIELD Tablet using Tapatalk