yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] Speed_Br:
I just bought my xperia s yesterday and facing similar problem. But after update to JB the camera is perfect now.
[Sony Xperia S, Acro S, Ion] Maxamb:
Thank you :) Then I'll upgrade to JB.
[Sony Xperia S, Acro S, Ion] luptatorul:
Problem Solve

Hey! This problem is probably because of the firmware... upgrading to jellybean will solve your camera for sure, specially that the camera lag is fixed in .96 and works flawlessly. You could try this! http://xdaforums.com/showthread.php?t=2425192 Come back with feedback!
[LG Optimus 2x] saler9:
Hello guys,

I'm hoping to get some help here, since I've lost 2 days trying to flash my phone with a custom ROM.

The phone was running Official Android 4.0.4 Ice Cream Sandwich V30A, and I did the following in order to flash it:

After unsuccessful rooting attempts with SuperOneClick (stuck at step 7) I found another way, using nvflash, following these instructions. Somehow I thought I need to unlock the bootloader first, in order to root the phone, so I did that first. After that, I rooted my phone with SuperSU Root as described in this tutorial, and also installed CWM.

I thought that I was ready for the flashing part, and downloaded a custom ROM along with the right GAPPS, and followed the instructions carefully.

First few attempts I got stuck at the beginning of rom flashing process, than I found a solution, where I needed to delete the first line in the META-INF\com\google\updater-script file, then the flashing came trough, but somehow to quick I thought.

After everything was wiped/cleaned/flashed I click on “reboot system now” after which the phone should reboot into the new rom, but nothing happens, the phone acts "dead", it won't turn on, or boot into recovery mod. I was sure that I've bricked my phone, but luckily I was able to get it back on using the APX method with nvflash and boot flash.

But then the phone starts with the official ICS 4.0.4, as if nothing was flashed.

After another day of searching for a solution, I've found out that there are different partitions for different rom's, than I realized that I was trying to flash

Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM

LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly

Jelly Bean on a ICS device wich logicaly should run on a different partition, so I downloaded a ICS based ROM EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1 and got the same issue when flashing, where I had to delete the first line in META-INF\com\google\updater-script, but than the flashing process went trough and seemed more genuine than before as it took longer to finish, so I was happy for a moment, and rebooted the device, and voila nothing...he's deaaaad again.

Can someone please help me to find out where the problem lies.

Thanks for any help, I hope someone takes the time to read this.
[LG Optimus 2x] saler9:
No one here to help...:(

Finally I've managed to install TWRP over CWM with AIO Tollkit, to see if the problem was with CWM.

The flashing process/time seemed similar, but the phone actually booted this time, but not into the new "flashed" custom ROM, but into the old stock one which should be wiped/deleted...:confused:
[LG Optimus 2x] SREEPRAJAY:
Dont worry too much....

Just use the All In One Tool Kit by spyrosk.....just wipe everything....as I suspect that all your partitions have been disturbed.....for the link for this tool, check my signature

Flash the one from JellyCream.... (it is new bootloader ROM on the dev section) or if you want the 4.3 based CM ROM, then find the one from tonyp....

You will loose the data on the Internal SD card....if you have a backup on the external, then restore form it....

Edit: Eaglesblood ROM is not supported by the developers as far as I know....
[LG Optimus 2x] saler9:
Finally

Thank you for replying/helping :good:

As it seems, it was a bootloader issue (ord/new). My phone has the new one, and I thought that the ROMs I've downloaded

Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM

LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly

EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1

would run with the newBL, since they ware recently updated or made, and there was no clear info about the boot loader version.

Now after 3-4 Days of struggling, I've tried a ROM which is made and clearly stated for the newBL,ParanoidAndroid v2.6 "p990-2.6-14-newbl-tonyp.zip" and flashed it without any problems. I didn't have to wipe the whole internal storage with AIO Toolkit, I've followed the usual flashing procedure.:victory::laugh::good: the new rom looks awesome. I hope that I won't have any lock screen or random reboot issues, like before.

Now I'm gonna help a guy, who has the same problem.
[LG Optimus G (International)] dsb_spain:
Hello

I've installed a oficial ROM of LG Optimus G (10g) with kdz file. When it put iParam= 1 i close the program and then disconnect usb cable but LG's logo is stopped and don't do anything

I see in post that enter in recovery and do wipe with a cmd file, but when reboot after this is stopped again with LG's logo

Can anyone help me ? i can't use mobile

Thanks
[LG Optimus G (International)] phamluong92:
Charge battery to about 75%. Disconnect cable from anything. Make sure the phone is turned off and full computer installed drivers for your devices. Press both volume keys at the same time (Press Volume - and Volume +). Connect cable with Computer. On screen of phone will be display logo: DOWNLOAD MODE. done.

Run Flash Tool or KDZ Tool, then flash file ROM do you want. Good luck!
[LG Optimus G (International)] LNJ:
Power + volume down will get you the LG factory reset.
[LG Optimus G (International)] dsb_spain:
Thanks for your help !

the problem has been solved

bye and thanks
[Nexus 7 (2013) General] MasterJam882:
Hey guys.

I just wanted to inform you that new update for Nexus 7 is out.

Unfortunately I was not able to catch the ota link.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) General] kendong2:
i uploaded it here
[Nexus 7 (2013) General] chickenmon:
be careful

This update disabled TWRP and broke root on my tablet.
[Nexus 7 (2013) General] noonecanhide:
Does not update my deb....
[Nexus 7 (2013) General] scorpio16v:
I received the update OTA on my rooted (deb) N7/2, booted to TWRP and flashed the .zip, that is in /cache. Update runs fine. I didn't use the recovery option to fix SU permissions.

Just rebooted to OS, went to recovery and flashed the SU.zip afterwards.

Root and TWRP are working fine.
[Nexus 7 (2013) General] alpinux:
I received the update too and installed it via twrp.

All went fine exept for root. I just had to install chainfires root package (1.55) again.
[Nexus 7 (2013) General] heartbeat.rulez:
is it a sign to get a factory image in a short time?
[Nexus 7 (2013) General] kendong2:
might wanna install the deb version of twrp...
[Nexus 7 (2013) General] poisike:
OTA URL > http://android.clients.google.com/p...signed-razorg-JLS36C-from-JSS15J.7003a71d.zip

Thanks to kendong2 for the file name.
[Nexus 7 (2013) General] Elting:
Does the update solve the following touchscreen problem: the tablet lies on a table and the screen does not recognize your tabs...
[Nexus 7 (2013) General] poisike:
You have touchscreen problems on a LTE version? I don't have any problems on my LTE version with 08.2013 build date.

If the update is for fixing touchscreen problems, then I'm not sure if I should update...
[Nexus 7 (2013) General] Elting:
No, I have the FLO but I think, that FLO will get this update, too... sooner or later...
[Nexus 7 (2013) General] dasmanul:
Slightly OT here, but since it might still be useful for future OTA updates: How does one catch/find out the OTA URL of an update? I understand that the update itself gets downloaded to /cache and there you can find the filename, but what about the URL?
[Nexus 7 (2013) General] xdacinq:
simplest way is a proxy in your wifi network, which handles all http/https requests for the phone/tablet.
[Nexus 7 (2013) General] poisike:
If you know the update file name then it's easy. Address is android.clients.google.com/packages/ota/google_devicecodename/filename so in our case android.clients.google.com/packages/ota/google_razorg/filename
[Nexus 7 (2013) General] kendong2:
if i am not mistaken the url is also visible in logcat.
[Nexus 7 (2013) General] Jacktheskipper:
So just to make sure I`m getting this right, I have a rooted DEB with TWRP installed:

1. Flash the zip from recovery

2. Flash SuperSU.zip

3. Reboot

4. Done

Or is a reboot needed in between between steps 1. and 2.? Does anyone have a working link to the SuperSU files needed (thanks in advance!).
[Nexus 7 (2013) General] sfhub:
No need to reboot between 1&2, at least not on the wifi model.

http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
[Nexus 7 (2013) General] Jacktheskipper:
Thanks for the quick reply and the direct link!

Hope this goes down without trouble, will give it a try later! :good:
[Nexus 7 (2013) General] ptau:
Even more simple is:

1) just allow a USB developer mode in the settings (no root needed)

2) fire up your ubuntu linux :cool:

3) run adb lolcat | grep http in the terminal

and take a look for something like

I/SystemUpdateService( 3997): starting download of hxxp://android.clients.google.com/packages/ota/google_razorg/...
[Nexus 7 (2013) General] pizzone:
INDEED, but it takes 10 seconds to re-push TWRP/SU with the ToolKit :laugh:

In any case I never got Twrp broken before....NEW DEAL?

P.S.: This time I forgot to remove SuperSU (1.55) before allowing the OTA but I got the jobe done anyway. Please keep in mind that Voodoo OTArootkeeper doesn't wotk anymore with any 4.3 Android version. No way to recover the root without reflashing SU.
[Nexus 7 (2013) General] Jacktheskipper:
So just to make sure (cause I asked on the last page already): This will also break recovery when flashed from recovery?
[Nexus 7 (2013) General] pizzone:
I think so....because the OTA update also launchs the Custom recovery to run, but - as I said - it's not a major issue.
[Nexus 7 (2013) General] ptau:
JLS36C-from-JSS15J has a incremental recovery update inside, so I guess you may end up with a broken system ...
[Nexus 7 (2013) General] pizzone:
Now you're scaring me... :rolleyes:

Thanks God it did not happen to me. It looks like I have a working JLS36C Stock + SU1.55 + TWRP 2.6.0.0, but I'm not so smart with Android to say that it's going to last...

Once it works, is there any possibility to get the system broken in a future update???? :confused:

I think that the worst case scenario is to reinstall the stock firmware if anything happens? :crying:
[Nexus 7 (2013) General] ptau:
Honestly, I still don't know much about 4.3 and nexus7 either.

I'm really puzzled how many partitions there are ( 30! ):

ls -l /dev/block/platform/msm_sdcc.1/by-name

lrwxrwxrwx root root 2013-09-04 09:58 DDR -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 2013-09-04 09:58 aboot -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2013-09-04 09:58 abootb -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2013-09-04 09:58 boot -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2013-09-04 09:58 cache -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 2013-09-04 09:58 fsg -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2013-09-04 09:58 m9kefs1 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2013-09-04 09:58 m9kefs2 -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2013-09-04 09:58 m9kefs3 -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2013-09-04 09:58 m9kefsc -> /dev/block/mmcblk0p28

lrwxrwxrwx root root 2013-09-04 09:58 metadata -> /dev/block/mmcblk0p29

lrwxrwxrwx root root 2013-09-04 09:58 misc -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 2013-09-04 09:58 modemst1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2013-09-04 09:58 modemst2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2013-09-04 09:58 pad -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2013-09-04 09:58 persist -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2013-09-04 09:58 radio -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2013-09-04 09:58 recovery -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 2013-09-04 09:58 rpm -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2013-09-04 09:58 rpmb -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2013-09-04 09:58 sbl1 -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2013-09-04 09:58 sbl2 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2013-09-04 09:58 sbl2b -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2013-09-04 09:58 sbl3 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2013-09-04 09:58 sbl3b -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2013-09-04 09:58 ssd -> /dev/block/mmcblk0p27

lrwxrwxrwx root root 2013-09-04 09:58 system -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2013-09-04 09:58 tz -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2013-09-04 09:58 tzb -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2013-09-04 09:58 userdata -> /dev/block/mmcblk0p30

Personally, at least until I understand what needs a backup and what not, I'd rather

wait until google releases the factory images. Theoretically, I think, if you have a backup

from the original system and recovery, you'll be fine for a next ota.
[Nexus 7 (2013) General] sfhub:
lolcat->logcat

---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------

1.55 incorporated the OTA fix so it doesn't block OTAs.

---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------

In custom recovery, if you simply run UPDATE-SuperSU-v1.55.zip immediately after you run the OTA (ie before the reboot), you'll keep your recovery and have root back.
[Nexus 7 (2013) General] ptau:
An old secret, it works, try it ;)
[Nexus 7 (2013) General] sfhub:
Thanks, I will add that one to

adb hell

:)
[Nexus 7 (2013) General] Jacktheskipper:
Just some feedback fot those unsure, here`s how I did the update and it all went perfectly fine, didn´t lose root or recovery:

1. go to TWRP

2. flash update.zip from TWRP

3. flash SuperSU.zip

4. reboot

That`s it! Happy updating everyone!
[Nexus 7 (2013) General] zogger:
Failed

Tried it that way without success.

In TWRP:

Updating partition details...

Installing 'sdcard/update.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found.

Warning: No file_contexts

Verifying current system...

assert failed: apply_patch_check ("systen/app/CalendarGoogle.odex", "aab59978ce767b1a...

E: Error executing updater binary in zip '/sdcard/update.zip

Error flashing zip '/sdcard/update.zip'

tried the update file linked here and the one i got via ota.

I am on stock JSS15J (Rooted)

Any help for that?

TIA
[Nexus 7 (2013) General] lespaulman67:
I was wondering did this Nexus7 have any of the issue we are having with the WIFI version. I never seen any complaints.
[Nexus 7 (2013) General] ptau:
Yes, I had a similar issues (the touchscreen wasn't responsible in some cases, GPS sync sometimes took for ever 'tii reboot). The first ota a week ago wasn't helpful at all, but this one today morning AFAICS fixed everything :)
[Nexus 7 (2013) General] MasterJam882:
I still have some touchscreen hickups after the update. Not aas often as before but still sometimes ghost commands are present.
[Nexus 7 (2013) General] ptau:
Hmm, still no issues here. Did you flashed some recovery?

Just an idea: you could try a factory reset and see if that helps.
[Nexus 7 (2013) General] MasterJam882:
Yeah I flashed TWRP. But I doubt that this is the cause.

Factory reset would be my next step.
[Nexus 7 (2013) General] sfhub:
http://xdaforums.com/showthread.php?t=2428194

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] geckocavemen:
Just so I'm clear this is only for the LTE Nexus 7 correct?
[Nexus 7 (2013) General] MasterJam882:
I read the first thread few days ago.

For DEB there's only TWRP 2.6.0.0. A newer one is not available yet and I'm not sure if I can flash Flo 2.6.1.0 TRWP on DEB

To the second thread: I don't want to experiment with such files. I want to stay stock as possible. If you can guarantee that file x,y,z is the right for me ok but I don't want to try and mess around.

But thx mate

EDIT: Would flashing stock recovery fix the issues?
[Nexus 7 (2013) General] pgschk:
I have the same issue. I actually got it as OTA yesterday morning, and it failed with the same error.

I tried manually downloading and flashing via TWRP, but have the same issue.

Did you find a solution? I tried wiping, that didn't help. :confused:

EDIT: Okay, I actually found the solution. Maybe you have been as quick as me with installing a customer recovery and didn't wait for the deb version. I installed the flo version of TWRP, which worked fine. So far.

I flashed the deb version of TWRP (techerrata.com/browse/twrp2/deb) and flashed it (fastboot flash recovery name.img). That solved the issue for me and I have JLS36C now. Had to reflash SuperSU though.
[Nexus 7 (2013) General] pyler:
/data/data/com.google.android.gsf/shared_prefs/update.xml

Ota url is there under preference "url"
[Nexus 7 (2013) General] LennyXP:
could you explain more specific (with the links to the recovery) how you solved the problem of flashing the update?

I still always fail flashing with twrp 2.6.0.0
[Nexus 7 (2013) General] woldranger:
I thought all was done with my N7 till the OTA update yesterday. I was already on 4.3 but somehow it had downloaded an update so I just went along with it. Then I noticed Greenify wasn't working and today worked out what had happened. No recovery and no superuser rights.

I thought it was just going to be a case of flashing the Supersu zip, but now it seems I've got to install a different recovery set up. Is there one stand-out, simple option to go for? I've spent the last 2 hours looking all over online till I found a relevant, and current thread!

Does this mean I'm going to end up wiping my N7? I backed up with Titanium a week or so ago but have since added a load more apps.and dont really want to lose all my settings etc.

I'm not new to installing custom ROM's but not always had the best of luck - my tytung cm10 nativesd set up is running well but the recovery has vanished :confused:
[Nexus 7 (2013) General] ptau:
Unlikely. The fact is, I myself avoided to run the TWRP before the JLS36C ota and all issues are fixed. The kernel dmesg reveals that by the next reboot the kernel upgraded the touchscreen firmware flash:

http://xdaforums.com/showpost.php?p=45278441&postcount=21

My wildest theory is, that the TWRP kernel does the same upgrade but after a reboot to the old JSS15J this messed up something. So I think a factory reset could help here. But I may have just a better hw, who knows :confused:
[Nexus 7 (2013) General] sfhub:
You flashed TWRP and want to stay as stock as possible? :)

Anyway, those files won't change your existing setup. None of your files are touched or modified. They are isolated to only affect the touchscreen. The process is totally reversible. Installing is no more or less difficult than flashing TWRP.

Stock recovery won't do anything for your situation.

It is up to you. Perhaps it just depends on how frustrated you get with the touchscreen.
[Nexus 7 (2013) General] MasterJam882:
One question.

When you say that twrp is the reason for all that(makes sense as before everything was fine) stock recovery should do the trick no?

When twrp brings a new version with JLS36C drivers everything shoukd work aswell rigth? So it's just a matter of time.
[Nexus 7 (2013) General] sfhub:
To be clear, I'm not blaming TWRP. The issue is with the touchscreen firmware from Google/Asus which is upgraded underneath the hoods by the kernel.

Your old stock recovery cannot undo the change because it only loads firmware if it is newer than what exists (ie once you go forward it won't bring you back). You could however flash the JLS36C stock recovery and get the new firmware, with the caveat answered in your next question below.

When TWRP brings in a new version with JLS36C, all you are guaranteed is you'll have the new touchscreen software.

How it performs depends on which variance of touchscreen you have.

Some perform better with JLS36C/JSS15Q, some perform worse, and for some there is no difference. That's not just my personal opinion, it is backed up by a large thread of data from many users.
[Nexus 7 (2013) General] poisike:
Damn, this JLS36C update messed up my touchscreen, some touches get stuck after the update. I didn't have any issues with touchscreen before the update.
[Nexus 7 (2013) General] sfhub:
Same as JSS15Q for WiFi. For some people touchscreen improves, for others no difference, and for some it gets worse.

See this thread for solution:

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] poisike:
Thanks for the link, I have been following your touchscreen fix thread from the start.

The JSS15Q update actually fixed the touchscreen issues I had with my WiFi only Nexus 7 on JSS15J.

My LTE Nexus 7 just started rebooting when I put it to sleep. Very strange, I have not installed any apps or changed any settings (there was Google Chrome Beta update today morning). I'm going to try a factory reset.

Edit: it reboots every time I turn the screen off. I turn the screen off and about 10 seconds later the Google logo appears on screen.

Edit2: it seems it was Chrome Beta that was causing reboots. I killed Chrome Beta before turning off the screen and it does not reboot anymore.
[Nexus 7 (2013) General] pgschk:
I would like to, but since I just started posting am not allowed to include links :(

But I think it should be clear enough:

- Download TWRP for DEB: techerrata.com/browse/twrp2/deb (just add http :// to get the link)

- Connect your DEB to a computer with ADB installed on it

- Copy the downloaded recovery image to the same directory adb is in

- Open a shell, go to your adb directory and run

adb reboot-bootloader

fastboot flash recovery openrecovery-twrp-2.6.0.0-deb.img (check the filename, in case it's different)

fastboot reboot-bootloader

- Start recovery

- Flash the OTA Zip file

This worked for me at least :) Good luck! :victory:

Edit: Thanks jibril.r6
[Nexus 7 (2013) General] LennyXP:
for some reason when I flash the OTA file, I always get a "failed" message.
[Nexus 7 (2013) General] crazyg0od33:
Just got my N7 LTE tonight and it's running this build. Is there anything special I need to do to root it? I was going to use Wug's toolkit but this build number isnt on there as an option yet...

Thanks!
[Nexus 7 (2013) General] alpine101:
Wug's toolkit worked for me on this version, after I cleared out a load of older USB drivers from the system I use, using the procedures within his application. I used the 'Any Android' selection.
[Nexus 7 (2013) General] davenam:
is there any ROOT that will enable using nexus as a phone ? making phonecalls and SMS/MMS sending ?
[MDA III, XDA III, PDA2k, 9090 General] aslan:
I sometimes get the problem on my xda 2s where in a call nobody can hear me neither can I hear them.

To fix it I have to turn bluetooth on then off then re-establish the call (I saw another thread with this fix on it).

Is there not any permanent fix? Surely o2 would have to make a fix for it??????????????

Cheers in advance
[MDA III, XDA III, PDA2k, 9090 General] Triband81:
Does this problem occur only when you try to use BT to make/receive calls?
[MDA III, XDA III, PDA2k, 9090 General] goestoeleven:
Well-known bug (with a solution)

http://xdaforums.com/viewtopic.php?t=26304
[Asus  Eee Pad Transformer Prime] Passportpowell:
is there a multi window mod or app? not talking about a floating app although if there is a god one id like to know. I am talking about the multi window like on the galaxy s4
[Desire HD Q&A, Help & Troubleshooting] todorovke:
I recently had an issue regarding the proximity sensor on my DHD and I tried many different ROMs and calibration apps but none of them worked. Seems like the problem is the dirt that blocks the way of the sensor. I cleaned the grill from the dirt and everything is now OK. Hope I helped someone.;)
[Desire HD Q&A, Help & Troubleshooting] totalnoob34:
Dirt kills proximity sensors ;)
[Desire HD Q&A, Help & Troubleshooting] todorovke:
Absolutely

Took me a long time to discover it :(