yashsingh1/xdaforums huggingface dataset:
[HTC One X] ToneyEricsson:
Hi thanks but I logged into my Google maps from the same account from a desktop and none of the places in my Google maps search history were showing. All the same I deleted my history from Google maps from my desktop and synchronized but the history is still showing on my HTC One X.

I now have disabled Google search from my desktop and synchronized again and still the same history is showing on my HTC One X.

Its as if the search history is permanent on my HTC One X.

Would there be any specific file on my HTC One X that I could possibly delete with say root explorer where it could be remembering maps search history from???
[HTC One X] ghori1989:
It worked for me. I dont use google desktop.

The only other thing i can suggest is that you download history eraser and try to clear it that way.

https://play.google.com/store/apps/details?id=mobi.infolife.eraser&hl=en
[HTC One X] ToneyEricsson:
I just tried with history eraser even that didn't work hmmm.

Something I notice is when logged into Google maps on a desktop in the search bar I can see these searches when clicking on the grey arrow on the right but going into delete history and clearing all doesn't get rid of them maybe this is a Google bug? I have also cleaned my desktop browser's with Ccleaner but these searches are still there in Google maps.

Edit: Just further to say I have tried Chrome in Incognito mode and the searches still appear so this can't be a browser cache or cookies issue. Really not sure how to resolve this....
[HTC One X] ghori1989:
Sorry im out of ideas. Maybe contact google if they can help.
[HTC One X] ToneyEricsson:
It was Google - after clearing history from desktop it appears to take time before everything is erased even after syncing from phone.

Now those pesky searches that I couldn't get rid of have magically disappeared :)
[HTC One X] ghori1989:
Nice one
[Motorola Droid RAZR] Tennisboy2:
Is there any way to overclock the razor?
[Motorola Droid RAZR] shobon:
http://xdaforums.com/showthread.php?t=1754888
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
Ok. So here's the deal. I'm trying to update to 4.2.2 from 4.1.2, but in recovery I get assert failed, emmc this that and the other.

I'm currently on JZ054K trying to update to JOP40C. I am also fully stock. It's hurting my head using everything I learned from other devices.

*I don't want to do anything with the Nexus into the rooting process. I want to stay fully stock for once.

Please and thank you. :)
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
The "this that and the other" is the only thing which is relevant.

Post the exact error message. If you don't remember what it was, re-attempt the OTA and post a screen shot.
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
I'll take a photo today. I've been slacking. Away from the forums a bit.
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
Re: 4.1.2 &gt; 4.2.x

That's the assert failed error. Fully stock neXus.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
OK, thanks for that.

Time to come clean though - when you say "fully stock", do you mean

(a) The device has never been rooted ever, or

(b) The device was rooted at one time and then (believed to be) returned to stock.

The assert error that is occurring is a complaint that the boot partition ("LNX") fails a checksum.

This would really only happen under two or three circumstances:

(1) Somehow the boot partition got modded by a root user - eg replacement of the entire boot image such as a "new kernel" or even something tiny like a change to /default.prop, OR

(2) You developed a media (eMMC flash chip) error in your boot partition after the device left the factory, OR

(3) Google/Asus somehow screwed up either the checksum calculation or your N7 slipped out of Asus's factory with a non-standard flash of the boot partition.

Now (3) seems a little bit unlikely. There was a previous user in these forums that reported exactly this same thing happening with a stock (never rooted) device; iirc though, he had a different factory ROM than what you are reporting. So, both his case and yours could be condition (2).

The things which is strange about this possibility (2) is that if a media error occurred randomly in the boot partition, it would be in most cases be fatal to the booting of the device, and neither you nor that other user reported booting troubles. The media error would have to be in a non-critical location such as in the slack space after the end of the boot image but before the end of the partition.

The reason I mention this is because of the way that apply_patch_check() assert seems to work: note that there are 5 parameters total:

filename,length1,sha1val1,length2,sha1val2

This suggests that a successful apply_patch_check() checks the SHA1 signature of the starting file - over an exact byte count, and if that succeeds it actually performs a trial patching operation so that it can compute the SHA1 signature of the output (patched) file and verify that the patch-trial-file has the correct length. This means that partition slack space is probably not included in the first checksum.

This is an extremely conservative and excellent approach to patching things in the field. Note also that the OTA does not touch/modify a single file on your tablet unless everyone of these checks goes to completion.

Also, the stock recovery performs a signature check on the entire zip file that is downloaded by the OTA before any of these other checks begin - which means, that when a stock recovery is used it is impossible to have a bad download being responsible for the errors that you observe.

If your device was never rooted then it seems to me that the odds point towards a hardware error that occurs during the patching-test operation.

If your device is still in Warranty and truly was never rooted, I would encourage you to try and get a new replacement or RMA repair (not a refurb). You are going to have to haggle with Google and show them that assert failure image.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] najaboy:
Re: 4.1.2 &gt; 4.2.x

It bears mentioning that, since the OTA is a patch, it's going to error out if the system is as the OP describes it. I'm unaware of any update zip that patches 4.1.2 to 4.2.2 directly. Since he's skipped a couple updates, he's going to have to do some sideloading to catch up and get to an upgradable state.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Good catch najaboy

I didn't catch that (JZO54K -> JOP40C) reference, but oldblue910's OTA thread does list such an OTA as having been available in the past.

Plus, iirc the boot image check occurs late in the OTA installer script, possibly even the very last assert() before patching actually starts - so it is hard to imagine that all other checks would have succeeded had a mis-matched OTA been applied.

However, it is indeed odd for "back dated" OTAs to get downloaded automatically esp when more recent upgrades are available, i.e. JZO54K->JDQ39. And nowhere did the OP mention side-loading.

Looks like the OP's got some 'splainin to do...
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
Ok. So yes.

A. The Device is FULLY STOCK. Never touched anything on it. Brand new on Christmas day.

I've been watching QBking's videos about upgrading it, and yes. I thought the same thing. Going from 4.1.2 to 4.2.2 directly, I noticed that seemed a bit off. I've seen more than just me with this issue. A few on XDA, and few on other websites.

I have tried downloading the 4.2.1 update. I tried sideloading it once. It failed. Atleast I believe it did. I don't know if I had the right download though.

All help is appreciated. I thank you guys as well. This 4.2.2 update is just what the OTA checker keeps throwing at me. I've tried clearing the data/cache of Google Services Framework(I believe this made me redownload the update).
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Curiousn00b,

I'm 99.99% positive that you were applying a valid OTA file.

For instance if you have JZO54K on your tablet, and you were going to apply a sideloaded OTA you could choose any of 3 OTAs

JDQ39 (4.2.2) from JZO54K

JOP40D (4.2.1) from JZO54K

JOP40C (4.2) from JZO54K

My comment in the prior post was only that the automatic download always seem to download the OTA update to the most recent (in this case JDQ39) release, so your mention of JOP40C ota seemed slightly off; but if there was some reason to pick an older update, sideloading should still allow that to work correctly.

Bottom line is that a fully stock, never unlocked, never rooted tablet should be capable of accepting a factory OTA, and I would thus consider your tablet to have some unknown defect.

Just to be clear (I recall that the previous person reporting your symptoms was on JRO03S), you are currently on JZO54K, correct?
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
I found multiple people with it via Google. Couldn't really find a fix for it.

And yes. I'm on JZ054K.

Tomorrow I'll try going to 4.2 from 4.1.2. I'm pretty sure I've tried it already. I remember seeing the C/D parts at the end of these 2 files.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
If the problem occurs during the initial checksum of the (currently installed) boot image, then none of the three OTAs (starting from the same JZO54K base) will succeed. If there is something very strange - say a read/write error during the trial patching operation, I suppose it is feasible that one could succeed and another not. But they all should start out looking for the identical bootloader SHA1 checksum as they should be expecting the same (jzo54k) starting condition.

Anyway, post your results.
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
Re: 4.1.2 &gt; 4.2.x

This is after trying 2 of the updates.

One to 4.2 and other to 4.2.2.

The first on is 4.2.2
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
As I said, I didn't really expect any of them to succeed.

Where to proceed from here? You really only have 3 choices:

- Use your tablet on 4.1.2 and never upgrade

- RMA for repair/refurb replacement

- Root it, fix the problem, and relock it (so that it is 100% stock again). No guarantess that some trouble won't develop down the road.

As I said before, neither you nor I have any explantion for why a never-rooted tablet would not be able to accept a valid factory OTA. Your tablet either:

(a) slipped out of the factory with an unknown bootloader variant, OR

(b) the boot partition managed to develop bit-rot that does not affect the tablet's ability to boot, OR

(c) there is some other unidentified hardware fault that occurs during the apply_patch_check() process

I would call Asus and see what they will do for you before you make a final decision. (Their warranty has a lot of weasel-words in it; they might tell you that it's not their problem.) If you want an RMA and they push back, I think you should keep repeating that the tablet is less than 3 months old.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] Curiousn00b:
I also noticed that I can't boot into recovery normally. I use ADB or the OTA way to reboot into recovery.

If I get into Bootloader and plug the USB in, the Nexus 7 will freeze at whatever selection I am currently on. Bootloader, Restart, Recovery, etc and nothing will happen.

When I click Recovery, I get a black screen with Google, nothing happens, plug the USB in, and still. Nothing happens. I don't know what's wrong with it.

Thanks for the help. :)
[Nexus 7 Q&A, Help & Troubleshooting] mvi57:
My N7 has the same error about the boot partition. It's rooted, unlocked, and has CWM installed. I'm running 4.1.2 (JZO54K). I downloaded the JZO54K to JDQ39 zip file, and got the failure

script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5062656:af83f09e77a64ed7ede2adad2a16bd0c12d5d7fd")

when I tried to install it via CWM.

How would I fix this - I assume I need to get a copy of the 4.1.2 boot.img and flash it, but I'm not sure how to flash it. I can do it in Windows if I have to, but I'd rather use Linux if I can. I have the adb tools installed on Linux.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Yes, that's right. It is easiest is to flash it with fastboot

fastboot flash boot boot.img

It can also be flashed to the block device

/dev/block/platform/sdhci-tegra.3/by-name/LNX

from a root shell (say in a terminal emulator) using the "dd" utility if you are familiar with that.

A custom kernel or even a trivial re-packing of the boot image (say for a small /default.prop file change) probably is what caused the boot image to be changed from stock.
[Nexus 7 Q&A, Help & Troubleshooting] mvi57:
I didn't install a custom kernel, and as far as I know I didn't change default.prop either.

I reflashed the boot image, it went ok, but I still get the error trying to do the update. I guess I'll have to wipe and flash the whole 4.2.2 image to get it installed. :(
[Nexus 7 Q&A, Help & Troubleshooting] mvi57:
Never mind, I flashed the bootloader-grouper-3.41.img instead of pulling boot.img from the .zip. It's working now. :o
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
That observation is extremely counter-intuitive.

While the bootloader is responsible for booting the recovery, it is certainly not "running" after the recovery starts booting, so it's hard to understand why or how it could have any effect at all on the OTA processing.

Is it possible that the error which occurred after you re-flashed the boot image (LNX) was something different than the original error concerning the checksum on the boot partition?

You might want to consider flashing the v4.18 bootloader to the tablet if you plan on using any dev kernels.
[Nexus 7 Q&A, Help & Troubleshooting] mvi57:
Poorly worded, sorry. After I flashed the boot.img I extracted from the zip file, the update ran fine. I looked at the error message again and noticed that one of the numbers matched the size of boot.img, and then realized I flashed the wrong file. I shouldn't do this stuff when I'm tired.

Thank you for all your help!
[Ouya General] mertzi:
Didn't see a post with this, this is the main reason I backed the ouya.

http://youtu.be/QB-H4j9hfLE
[Ouya General] eksasol:
Not a big deal, even my Galaxy Nexus with the XBMC hardware accelerated test build stream 720p over UPnP smoothly. I went ahead and bought an MK808 stick, but might get an Ouya when it's released for better hardware and quality control.

Sent from XDA app
[Ouya General] Conjukt:
Cool video. This is my main reason for buying the OUYA as XBMC is the only way I have found to stream movies to my kids PC while preserving the DVD menus and subtitles. I would rather my 6, 8 and 10 year old sons not handle my DVDs directly so I store all their movies on a 3TB hdd... can't wait for this to get in in June.
[Ouya General] josenightbreed:
Awesome to have xbmc, that will go great with an external HD for offline media. I wonder if a usb DVD or Blueray will work in the OUYA?
[Sprint Samsung Galaxy S III] kingable:
I would like to remove the long press menu "kill app" feature in the custom rom I'm running. It removes the search phone function that I prefer over the kill app feature. A lot of roms doing it now. Any help would b appreciated. Thanks in advanced.
[Sprint Samsung Galaxy S III] Speedin07si:
MOAR gives you the option to set double tap home to launch google now.

Sent from a planet far far away.
[Sprint Samsung Galaxy S III] JoeFCaputo113:
Or you could just install Nova Launcher and swipe up, swipe down, etc to launch Google Now.
[Sprint Samsung Galaxy S III] kingable:
I just wanna remove it from the ROM. Thanks for the help and suggestions. :)
[Sprint Samsung Galaxy S III] Jimieo:
I'd love to get rid of it too.. Frequently part of my finger will press it unintentionally.. Quite irritating when I'm playing Modern Combat 4.
[Sprint Samsung Galaxy S III] kingable:
Guess its a no go :banghead:
[Sprint Samsung Galaxy S III] epic4GEE:
Hmm...When I'm on my home screen and hold the menu button it still launches google search/now, I'm using the stock launcher. Maybe I'm misunderstanding? Anyhow I don't know how to make it work normal, but maybe asking your rom dev very nicely will bring about a fix for you.:good: Honestly I love the kill app feature.

---------- Post added at 08:45 AM ---------- Previous post was at 08:41 AM ----------

Way off topic so please excuse me, just like to ask what's your player name? Curious if I've played against you on mc4, I got a bit crazy and ordered the new moga controller the other night, hope it's as good as I've heard.
[Sprint Samsung Galaxy S III] kingable:
I already tried asking the Dev but nothing. I'm getting used to it already so it's not bothering me as much
[Sprint Samsung Galaxy S III] LuigiBull23:
Change up the hardware key functions to your liking.
[Sprint Samsung Galaxy S III] Jimieo:
Same as my username here.
[Samsung Galaxy Nexus] electro`:
Don't question it.

I would just like to know how to do this.

Thanks in advance.
[Sprint HTC EVO 4G LTE] cjones46402:
Ok....My phone sucks when it comes to signal. Im in a 4g area but barely get 3g i.e. MAYBE 3 bars if Im lucky. Im going to give you all as much info as i can from my phone. Please help my out if you can. Call me whatever you want....but help me out! :D:D

About Phone:

CyanogenMod 10.0.0-jewel

Android 4.1.2

Baseband 1.02.12.0427

Kernel 3.0.51-geb1844c

pinky-ghost@cyanogenmod#1

Team Win Recovery Project v2.3.1.0

****TAMPERED****

****UNLOCKED****

JEWEL PVT SHIP S-ON RL

HBOOT-1.12.0000

RADIO-1.02.12.0427

OpenDSP-v25.1.0.32.0405

eMMC-boot

Apr 26 2012

I have read I need S-OFF to flash a new radio. All I have are Mac's in my house without bootcamp. Is there ANYWAY to flash a new radio with S-ON?

I have no idea how to put this thing back to stock. I think I used HTCDEV to root.

If anyone can point me in the right direction, I will greatly appreciate it!

Thanks in advance fourm.
[Sprint HTC EVO 4G LTE] Sloth:
The only way to update your radios while S-ON is to re-lock and take the OTA then unlock again and re-flash twrp

There is a new S-OFF method in Original Dev... not sure if it will work on Mac

Edit: if you update all the way to 3.16.651.3 you will no longer be able to use CM,AOSP,AOKP roms because they updated the touch panel driver in that OTA
[Sprint HTC EVO 4G LTE] cjones46402:
Looks like I'll never get this radio updated. Anyone in the Chicago area willing to use their windows/lnix system to do it for me for a small fee???:highfive:
[Sprint HTC EVO 4G LTE] Sloth:
FacePalm won't work? Or you can use a LiveCD to boot from your Mac
[Sprint HTC EVO 4G LTE] cjones46402:
Sorry for the delay in posting. Working 12 hours 6 days a week is wearing and tearing on the body. Found an old windows xp computer I had packed up for years. I hope this machine works....fingers crossed. Any help is appreciated.

Im going to look into this FacePalm thing. I really need a new radio. It takes me 15/20 mins to send a freaking pics if I don't have a WiFi signal.

As Im not familiar with windows I was wondering If anyone can point me in the right direction to get s-off on windows.

Im trying to understand adb shell.....fastboot with using terminal in Windows. Going from Mac to Windows just gave me a headache lol
[Sprint HTC EVO 4G LTE] trsix:
face

Use the facepalm. Very easy method. Download the files from their threadthen visit their chat channel.
[MDA, XDA, 1010 Software Upgrading] cerberos:
i have a recent boot loader so i need to use XDArit to write a card that will allow me to backup my rom right.

so i downloaded XDArit, the boot loader patch, ran XDArit, put in my MM card, pointed it to my usb SD reader, pointed it to the .nb2 file, and told it to write

it comes up with this error (even after rebooting into explorer):

failed to open device \\.\physicalDrive10

what am i to do? is it that you must use SD cards not MM cards?
[MDA, XDA, 1010 Software Upgrading] cerberos:
just trying to think of possible issues, could it be the SD card reader is plugged into my keyboard and not directly into a motherboard USB port?
[MDA, XDA, 1010 Software Upgrading] sheran_g:
Hey there cerberos,

Try the older version of XDArit.

It's also best to have the reader plugged directly into your mainboard.
[MDA, XDA, 1010 Software Upgrading] cerberos:
yes the older version of XDArit worked, thank you
[MDA, XDA, 1010 Software Upgrading] cerberos:
XDArit wont read the card though after i've backed the device to it
[MDA, XDA, 1010 Software Upgrading] AE:
Try following:

- write something to your SD with xdarit and leave xdarit working

- backup xda ROM to SD

- read it from SD with XDARit.

I experience the same problem: XDARit fails to read SD until it writes something to it first. Old and new versions are the same.
[MDA, XDA, 1010 Software Upgrading] Joe_PDA:
I tried this and received an error message that "the drive was not a removable drive and would probably overwrite a harddrive...okay?"

There are 5 choices in the drop down menu of drives. All give the same result.
[MDA, XDA, 1010 Software Upgrading] TandyJames:
http://xda-developers.com/forum/viewtopic.php?t=1451&highlight=xdarit
[MDA, XDA, 1010 Software Upgrading] cerberos:
well with the new one i get an error of failed to read device 4, which is strange as the reader appears to be device 14:)
[Galaxy Note II Accessories] boogief1:
I purchased a fosmon one on ebay and its horrible it doesnt cover whole sctren and also the finish on it its rough i want a privacy screen thats covers the screen of the phone fully and has a nice glossy finish
[Sony Xperia P, U, Sola, Go] darshanlama:
Hey All!!

Need immediate help here.. my younger brother's Xperia U keeps restarting on the boot - so it shows the Sony logo and then the Xperia logo for a long time and then restarts... I am not able to make it go further than that.. it was running stock GB and there was no tweaks or updates downloading before the issue.

I did all the basic troubleshooting, but no go.. I tried flashing but I get the below error - (Flashtool ver - 0.9.9.0)

13/020/2013 06:20:23 - INFO - Selected ST25i_6.1.1.B.1.10_Generic_World.ftf

13/020/2013 06:20:23 - INFO - Preparing files for flashing

13/020/2013 06:20:33 - INFO - Please connect your device into flashmode.

13/020/2013 06:20:34 - INFO - Opening device for R/W

13/020/2013 06:20:34 - INFO - Reading device information

13/020/2013 06:20:34 - INFO - Phone ready for flashmode operations.

13/020/2013 06:20:34 - INFO - Start Flashing

13/020/2013 06:20:34 - INFO - Processing loader

13/020/2013 06:20:34 - INFO - Checking header

13/020/2013 06:20:34 - INFO - Flashing data

13/020/2013 06:20:35 - INFO - Loader : S1_Root_3065 - Version : R5E006 / Bootloader status : ROOTABLE

13/020/2013 06:20:35 - INFO - Processing partition-image.sin

13/020/2013 06:20:35 - INFO - Ending flash session

13/020/2013 06:20:35 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0026";ERR_DYNAMIC="08 : TA flush failed";

13/020/2013 06:20:35 - ERROR - Error flashing. Aborted

13/020/2013 06:20:35 - INFO - Device connected in flash mode

13/020/2013 06:20:36 - INFO - Device disconnected

Please help!!!

Thanks,

Darshan

Xperia S - FXP kernel with NOVA ROM
[Sony Xperia P, U, Sola, Go] alwaysadeel:
use flashtool 0.9.10.1, i hope u have tried Software Update service by sony.
[Sony Xperia P, U, Sola, Go] Anthrax:
I guess the problem is the downloaded ftf is somewhat corrupted........
[Sony Xperia P, U, Sola, Go] alwaysadeel:
yes that can happen also, using SUS will cater for that.
[Sony Xperia P, U, Sola, Go] satya-1998:
Fastboot a custom kernel, boot into CWM and flash another ROM. oh wait, unlock bootloader first :D
[Sony Xperia P, U, Sola, Go] satan89:
Keep this as a last option, in case Sony decides to charge you for service.. Till then, your device is under warranty, so claim it if possible.

Sent from my ST27i
[Sony Xperia P, U, Sola, Go] Shatavarth:
-----------------------------------------------------------------------------------

Darshan, it`s completely okay. Need not worry. Chill. :laugh: First of all, Unlock the bootloader of the phone.

Then its all yours. :)

Reference of ROMS:

http://xdaforums.com/showthread.php?t=1936477

Good luck!