yashsingh1/xdaforums huggingface dataset:
[JAM, MDA Compact, S100 General] vijay555:
Re VNC

I've used this one quite well:

http://www.parystec.demon.co.uk/pt_vnc2.htm

But there are other free versions I imagine.

V
[JAM, MDA Compact, S100 General] Contactor-E:
@JuNiOr_Gr

Which Port did you open for Terminal Services?

Did you then connect to you Internet IP from your PPC or to your local IP?

If you use VNC you have to open the VNC Port (default 5900).

Ist there a software firewall (e.g. XP Firewall) installed on your PC?
[JAM, MDA Compact, S100 General] jwhitham:
For terminal services to work you must have a password set on your XP account. Otherwise it should work with port 3389 forwarded. I use it fine from my Magician over GPRS.

Only thing is that it's a shame you don't seem to be able to turn off desktop background, themes etc that you can from the Desktop version of Terminal Services Client as this would improve speed.
[General Questions and Answers] stubey:
Running CM10.1.3 stable on Samsung Galaxy S3 I747 and when I woke up this morning my google now widget was gone, just the widget. not on my home screen anymore, nor is it in my widget drawer. Google Now works perfectly, there is just no widget anymore. I've tried clearing data for google search app, using titanium backup i've uninstalled it and reinstalled google search from play store. Nothing else on the phone seems to have disappeared or stopped functioning.

Anybody else had this issue or have any advice?

Thanks,

Stu
[General Questions and Answers] Gringster:
I do not own an S3, but many people seem to have encountered this issue on different phones. Some searching on Google showed that the best solution is to... reboot your phone :). You may also try to clear your cache and Dalvik cache, even fix the permissions. The widget should come back.
[General Questions and Answers] stubey:
yea I google searched before I posted. Rebooted, cleared system and dalvik cache, rolled the app back to "factory version" and cleared app data and cache. Still nothing.
[General Questions and Answers] Metalcore18:
How do you think, what is better Nexus 4 or Lg Optimus G?:o
[General Questions and Answers] Gringster:
I must admit to not have trying either of them, but I generally feel that Google phones are much more reliable and appear to work better for longer periods of time. They are also more fit for tweaking and more popular with devs.

In contrast, LG's are working hard to build up a reputation, yet their phones are often slower then similar models. Their design is also a point to consider in making your choice, personal taste matters a lot ;)
[General Questions and Answers] amit6351:
which one is better canvas 4 vs canvas doodle 2 :good:
[General Questions and Answers] Sanjay:
Canvas 4

Sent by 桑傑庫馬爾 :stirthepot:

---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------

Optimus g

Sent by 桑傑庫馬爾 :stirthepot:
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Hey there.

I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:

The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.

I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).

I guess that's it for my Nexus 7 :confused: or does anyone have an idea what I can try to do. I'd be really thankful.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Jagutherrschaften...

Try pressing VOLUME DOWN + THE POWER ON KEY and HOLD BOTH for 30 seconds (or as long as it takes to break out of the 'bootloop').

(or BOTH VOL KEYS + POWER ON if the above doesn't work... although it should).

Keep them pressed until you boot you into the bootloader....

You should now be free to run fastboot commands, to either fastboot flash back to factory stock... or you could attempt to just boot into recovery, and maybe do a Nandroid Backup restore from your previous setup (assuming of course, you created one).

Anyway... as long as you can still access the bootloader... all is not lost.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Sorry, I forgot to mention that I can't boot into bootloader. I tried every single combination of keys. The bootloop goes on and is completely unimpressed by my keypresses. Bad bad thing.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
How fast is the bootloop? and how long are you pressing the buttons for?

Lean on them, as it where, for a good minute or so... the device has to pick up the 'interrupts' sooner or later.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Thank you for your answers. I tried every combination and kept the keys pressed for 2 mins. Nothing. The only thing I can actually do is shut the device down by pressing POWER + VOL UP for a long while.
[Nexus 7 Q&A, Help & Troubleshooting] neo45215:
If bootloop doesnt stop and you cant get into bootloader....then just long press power button..that should stop the cycle...and then volm down plus power button....should get u into bootloader..atleast worked for me..
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Now here is what it looks like (doesn't matter if I press keys or not): https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv

The normal method you described neo45215 doesn't work for me as well.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Mmm... this is a strange one...

Just had a look a your video... and I've seen a few bootoops, but never one involving a Custom Recovery and ONLY the Bootloader Unlock screen (yes, that is the Bootloader - it's just not normally recognized as such, because it's not in FASTBOOT mode).

If you've shutdown the tablet by pressing VOL UP + POWER ON, you've effectively booted the device into APX mode (it looks like it's shutdown, but it isn't) - if it is in APX mode, the device is now awaiting for you to run some nvFlash commands, which currently can't be done (though there is now, a very specific exception, which is not applicable here).

I agree with the previous poster, [MENTION=5110171]neo45215[/MENTION], VOLUME DOWN (hold), then POWER BUTTON, (whilst still holding VOLUME DOWN), should boot you into the bootloader... but I think precise timing is required. Please read the following, carefully, several times.

----------------------------------------

QUOTE from

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

"Starting from booted or boot-looping OS:

Power (10-15 seconds) -> Normal OS Boot**

** Bootloader Interrupt: In any of the cases where you hold the power button down to try to break out of the current operating mode, if you press the Vol-Down button right after you first see the black and white screen with the Google logo, the tablet will proceed immediately to bootloader/fastboot mode, rather than booting the normal OS. You need to be ready though - you only get about 1 or 2 seconds to do this! (Thanks to RMXO for pointing this out) Note that this means you can get to the bootloader directly from any other mode!

This also explains why, when attempting a cold start using Vol-Down + Power, if you accidentally let go of the vol-down button when the screen first lights up, the Nexus 7 will boot to the normal OS. In this case, pressing Vol-Down initially is actually superfluous - what makes the device go into bootloader/fastboot mode is the Vol-Down press

immediately following the google splash screen

- there actually is no unique "Go to fastboot from a cold start" method."

----------------------------------------

I'm at loss to suggest anything more helpful... this looks like the bootloop from hell!:( But I'm convinced, that with the correct timing and persistence, some key-combo interrupt could break the Nexus 7 out of it.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Thanks a lot for your help, I have tried everything, I can't get anywhere... neither bootloader nor recovery.

Additionally I can't make the device do anything I want by adb.

And as a "bonus" I can't send my Nexus7 to repair because this stupid bootloop shows "ClockworkMod Recovery v6.0.3.8" :silly:
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Really sorry to hear this... it is baffling::(.

I've been hanging around on XDA since January, and I've come across a lot of weird behaviour, reported by other posters. But this is something that is outside my experience.

A few questions... (no guarantees, but I'll try to see if I can come up with something)...

Can you post download links for EVERYTHING you've flashed...

The ROM, the Gapps, the CWM recovery.

Also, what order did you flash them in?

Did you use fastboot? or a Toolkit at any time?

Where you rooted BEFORE you embarked on this endeavour?

How did you acquire root?

How long have you had the Nexus 7?

Is it a WiFi only model or a WiFi and 3G model?

Have you flashed any other Custom ROMs prior to this one?

If, so, any problems?

Do you know your current bootloader version number?

What was the battery status (percentage) prior to you flashing this ROM?

Sorry for all the questions... but something, some tiny litlle detail, might set a 'eureka!' light bulb off in my head.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
OK, I'll try to answer as detailed as possible:

ROM KaosDroid7.0.0

FittingGApps

CWM Recovery (Touch) was installed through ROM Manager Premium

The order of what I did was: I made a backup in Titanium Backup Pro, then I made a nandroid backup by ROM Manager Premium. I went to recovery, wiped /cache and /data, then flashed KaosDroid7.0.0, flashed GApps and rebooted. After my Nexus7 had fully booted I restored some user apps and settings via Titanium Backup Pro. I had to reboot. After that I explored that clock was force closed whenever I tried to access the alarm clock. I wondered if I could possibly have overseen a checkmark when restoring with Titanium Backup Pro (maybe forgotten to untick a system app or setting) which could lead to the force close. So I decided to start over again.

This time I thought about using ROM Manager Premium for wiping and flashing. I started the app and it told me there was an update for CWM Recovery. So I installed this update through ROM Manager Premium - CWM Recovery Touch 6.0.3.8. I rebooted and went to recovery to flash ROM and GApps again the normal way. Before flashing I wiped /cache and /data again. Everything went fine until I rebooted the tablet and found myself in this "bootloop of hell" as you called it... After having tried a lot to break it, I opened the Nexus7 to remove battery for the first time.

OK, now the other questions:

I bought my Nexus7 about 11 months ago, it's the 16 GB WiFi only version. I aquired root by using this Toolkit and everything went really smooth. I tried several ROMs yes, after some time I came across KaosDroid (don't exactly know which version I started with, maybe v5.0.0) and really liked it. I flashed a new version whenever there was one and never had any problems before.

I am not sure about my current bootloader version, I have some not too long ago nandroid backups on my PC, can I find out anywhere in there? About battery, it was 55 % or so before I started flashing, maybe even more.

The way I see this is: It looks like ROM Manager has messed something up. I have never seen a screen like the ROM Manager screen that occurs in the bootloop right after the Google screen before. Unless maybe when making a nandroid backup through ROM Manager, not sure about this. But it shouldn't be there in a normal boot sequence as far as I understand it.

The only way I can access my Nexus7 is via USB on my PC. And I have like 5 seconds to act while this ROM Manager screen is on, that's the time frame when my PC says "Nexus7 connected" and even the Toolkit finds the device and says it's in "ADB mode", then prints the serial number, but sadly after that it waits for the device to enter adb mode forever.

EDIT: And of course I can get access in APX mode, but from what I have read there is no way to do anything because commands etc. to install a new bootloader are not known (yet?).

Thanks a lot for your help and patience, it actually helps to know there is someone who reads this :good:.

It's not the end of the world if I can't reanimate my Nexus7 but it served me so well for almost a year and I really like it :).
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Hey again GedBlake.

The last thing you have to do is apologize for helping me a lot, reading through all my text and making things clear for me. And even more you flashed stuff to your device to test if my situation can be reproduced - good that it's not ;). You've spent a lot of free time just to help, that's really great :good:.

With my bootloader still being intact and the device being recognized by my PC I wonder if maybe I can manage to fastboot flash a different bootloader and/or a new recovery which might maybe break the silly loop when booting. That's my only idea left but if the bootloader isn't in fastboot mode at some time during the loop this won't work too. But I'll give it a try, it's better than cutting tomatoes on my Nexus7 :laugh:.

Thank you very much for your help. If there is anything worth reporting I will of course.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Thanks for your kind words... they're appreciated.

Unfortunately, before you can fastboot flash anything, the Nexus 7 needs to be properly booted into the bootloader (the screen with the green Android lying on its back, and the word START adjacent to the POWER BUTTON)... and that requires breaking out of the bootloop first.

Indeed, if the VOL DOWN+POWER ON button combo was working as it should... breaking out of the bootloop would AUTOMATICALLY boot your Nexus 7 into the bootloader.

Finally, your bootloader doesn't need to re-flashed. One you have a stable bootloader boot, normally, (and the easiest way), would just be to flash back to factory stock.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Hey again.

Thanks for your explanation, I am not really a newbie with PCs and Tablets etc. but some things are not very interesting until you really need to know them. Like bootloader and fastboot in Android.

So the conclusion in my case is that maybe some day someone will find out how to get access to the N7 via APX - or to be precise, someone finds out or gets to know the necessary commands to flash something to the N7 over the APX-interface. Right?

Because from what I've read it doesn't really make sense to send my N7 in for repair right? Although it hasn't even had its 1st birthday yet I have no chance to get a warranty repair or exchange as it's very obvious I rooted the device and flashed stuff (the damned ROM Manager-screen clearly shows this). And ASUS charges 90 $ (or €, don't know) just for diagnosis, that's a bit much for a device that cost 199 €.

Any further advise? Could I buy a broken N7 from eBay for example and repair mine this way? I would have to change the mainboard right?

Have a nice sunday everyone :o.
[Nexus 7 Q&A, Help & Troubleshooting] neo45215:
U said you opened the battery...so wen u plugged it back in again,u shouldn't be in bootloop technically... Just a boot!...wat happens if u press the volm down and power button combo just as u insert the battery?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Jagutherrschaften...

Really sorry it had to end like this:(:(... but... perhaps it doesn't...

Nothing about your situation makes logical sense... but reading through your posts again, I find this- On the 3rd October, you posted...

QUOTE FOR EMPHASIS:-

"...by pressing POWER + VOL UP for a long while..."

This key press combo doesn't actually shut down the device... it just pushes it into APX mode. It just looks like it's shutdown.

But that's not my point... my point is your Nexus 7 detected that key press interrupt... and acted accordingly.

It did what it was supposed to do.

Maybe you hit the buttons at JUST THE RIGHT INSTANT during the bootloop... and if it can do it for one key press combo... it can do it for another:). Namely, POWER+VOL DOWN.

And for this reason... I think you need to try and try and try and try and try again... until you hit the same PRECISE TIMING SWEET SPOT... such that POWER+VOL DOWN takes you into the bootloader.

Vary the timings a bit here and there... alternate pressing the buttons, both before AND after when the Google logo appears.

By your own account... you've already done it once (you just got into the wrong mode... APX mode instead of bootloader mode).

But here's the danger... if after your Herculean efforts, you do manage, finally, to access the bootloader... you absolutely cannot afford to reboot the device normally until after you've fastboot flashed back to factory stock... otherwise the whole cycle will begin again.

So... you need, in preparation...

* A fully charged Nexus 7.

* All the drivers needed (if you don't already have them) installed on your PC.

* The Jellybean 4.3 Factory Stock image downloaded (see my Sig, second link) and unzipped and ready to go.

* A working knowledge of how to use Fastboot.

* And finally... an indomitable spirit!:) of perseverance... and, of course, a fair amount of free time.

------------------------------------------

I am convinced that your tablet is recoverable.

It's gotta be worth a shot... "once more unto the breach, dear friends", as old Bill Shakespeare would have it.

Anyway... the very best of luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
[MENTION=5110171]neo45215[/MENTION]:

Technically yes, but my N7 doesn't seem to know this ;). Of course I've tried to get into fastboot mode right after putting back the battery as well. No chance, same bootloop.

[MENTION=5049483]GedBlake[/MENTION]:

Thanks for the encouragement, I will for sure give this a try (or several long trys to be precise). Hopefully tonight I'll have a lot of time to press keys ;).

And my answer to what Bill says would be: "To infinity... and beyond!"
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
No success so far, I tried pressing buttons for at least 1 h, nothing...

Just wanted to update the status :).

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
Facing same problem

Hello guys. I've done pretty much the same thing and my tab is in the same boot loop that this thread is all about.

The interesting thing is that the ROM I flashed is also KaosDroid7.0.0. I'm unable to prevent any further insight. Sorry for bumping. My clockwork mod version is btw, 6.0.4.1 which proves that the problem might not be clockworkmods or even ROM manager's problem. Since I hadn't used ROM manager.

Also, Is there any way whatsoever to use this APX mode? To fix my nexus.

---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------

Well, I followed OP's steps almost exactly. First I'd restored the Kitkat factory image, and then I'd proceeded to install the KD 7.0.0. And after that, I realised I'd forgotten to flash Gapps. So I rebooted and then went into CWM to reflash and after that is when my Nexus 7 became useless :crying:

---------- Post added at 02:14 PM ---------- Previous post was at 02:05 PM ----------

Jagutherrschaften, did you send in your Nexus 7 for repair?
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
Bro, did you by any chance, after Aroma installer from KaosDroid closed. Did you uncheck the Reboot option? Because I think that this is what happened to my device. I'd rebooted manually.
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
Sorry if this is a bump. But I need to know what happened to your Nexus 7 after.
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Thanks for asking :o. Sadly I don't have something better to answer, still the same thing. After having spent literally hours of pressing buttons I finally gave up. No idea if I should try to get it repaired somewhere or sell it on eBay (my data is still on it, so rather not) or if I just search my biggest hammer and... ;)
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
Thanks for the reply. Because, I am facing the same problem, and I'm wondering whether it's worth trying for an RMA
[Nexus 7 Q&A, Help & Troubleshooting] Jagutherrschaften:
Nexus 7 works again

After almost giving up hope I took my Nexus 7 out some days ago and tried to get into fastboot mode again.

Same thing as before, bootloop and no reaction to my keypresses.

So I decided to check for a replacement motherboard on ebay and finally bough this.

With the help of this Guide it took me 30 - 45 min to replace the whole motherboard of my Nexus 7.

The only thing you have to be careful with are the cables held in position by retaining flaps. Just from looking at them it isn't always clear which part/side is the retaining flap and which isn't.

But the pictures help a lot here - they show exactly on which side you have to push carefully to open the flap.

Even with the costs of shipping that almost doubled the price for the replacement motherboard I don't regret having done this. Now my Nexus 7 runs like a charm again. I felt really sorry because I had bricked such a nice device and now it makes me really happy that I was able to fix it :o.

So if you still have the same unsolvable problem, maybe you want to think about a replacement too :fingers-crossed:.
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
[MENTION=379945]Jagutherrschaften[/MENTION]

Sadly, I'm not able to find any replacement motherboards for my 32GB Nexus 7. All of the ones I can find are 16GB ones.

It'll still work, I suppose, but I don't want to downgrade my nexus.

But otherwise it's just a brick
[Nexus 7 Q&A, Help & Troubleshooting] jeswinjv:
Do startup manager and disable sum unwanted apps.....

via XDA Premium developer's-app
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
Bro. My Nexus 7 is bricked. All you can see is a blank screen. I can't even press any buttons. Please don't reply unless you have actually understand the problem.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
Do you mean you can't even get it to turn on? I would try for RMA then as Asus are unlikely to look too hard at it . I had a look for a motherboard and the only 32gb one I could find was £130 whereas I found a 16gb one at £30
[Nexus 7 Q&A, Help & Troubleshooting] daspalme:
Hey guys.

I have the same weird recoveryloop-problem since yesterday.

I flashed ParanoidAndroid 3.99 via Rom Manager. It booted till the PIN enter screen and rebooted into this loop.

I also had no luck getting into the bootloader by pressing VOL-, so I think Ihave to say goodbye my old friend.

But what this VOL+ mode? what can theoretically be done with this?
[Nexus 7 Q&A, Help & Troubleshooting] nobody_nowhere:
APX mode is useless, right now. As we cannot access the API yet. I doubt you have generated the 'Blobs' necessary for this.

As a person facing the same problem, I can honestly tell you that, you have only one choice. Google is unlikely to help you. Even the dumbest technician can make out that the tablet is rooted.
[Nexus 7 Q&A, Help & Troubleshooting] KnowledgeBroker:
Well, I made a boo boo.. first bricked device. After reading all of this, and scrolling back in my command prompt - I clearly see I typed fastboot flash boot then the recovery - but now I can't access the bootloader and the recovery doesn't fully start, just like the original user here. No combination of buttons do anything besides that mode people talked about with vol+

Just want to give people the conclusion - if you accidently types fastboot flash boot "name of the recovery" - you can be in our boat.. sigh.

Anyone want to buy a tablet for a good screen? LOL.
[Nexus 7 Q&A, Help & Troubleshooting] knljndl:
Same issue with me...

I flashed xenon hd the the gapps

Then the same thing happened with me too...

Another one bricked....