Database Info

[Q] After disabling ATT, hell broke loose.

I have the shield tablet LTE version and after connecting to WIFI it immediately installed all OTAs upto the hotfix also. So here I am sitting with lollipop in my tablet and I decide to go for rooting and CWM installation.. After rooting using adb/fastboot and installing CWM image, I decide to disable ATTall access because I read that it stops the portable hotspot from working. So, did that and then process after process started crashing. First it started with background data not being enabled (playstore wouldn't open) , NVidia hub crashing, google text to speech crashing, etc.
So, I went to cwm and did factory reset. At the initial stages itself where it asks for language setup, the google text to speexh crashes and I cannot click next or proceed forward.
I flash the Lollipop OTA once again thinking it would overwrite the system but it didn't.. and the same issue keeps happening..
Now what do I do?
Regards
Alden

An update to the mess i was in...
I tried recovery mode at the fastloader boot menu and I got the robot lying down with a red exclamation mark sign. I pressed vol + key and it opened the original recovery I think. I wiped user data from this menu and rebooted. and now it has come to the original screen setup and so far no process crashes...
What could have caused this entire mess?

I am not sure what would cause your issues but i believe your best bet is to download the full rom image for your tablet and flash it via fastboot. That should get you back up and running. (Be warned doing this will erase everything on your tablet!! SD card will be untouched)

By fullmrom u mean the one from the nvidia developer website right?

Yes that is the one! I am currently at work so I cant post a link to it but if you need it ill try to post it once im off, in about 30-ish minutes. Good luck! (p.s. last resort is RMA)

Is your shield up and running once again? Just wanted to get an update. =]

Thanks javydawg, I didnt use the one on nvidias developer website as i simply did not have enough data left in my Internet plan .. its 2.3 gb in size... after recoVery i was left with lollipop so i flashed a 750 mb file tht i gt from these forums and updated it to the latest version.. i still haven't pinpointed the reason for my earlier trouble but will shout out if it happens again... have to be careful cos not sure if RMA is possible for me in India...

[Q] Bricked LS980. What Next?

Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out

ForceClosed said:
Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out
Click to expand...
Click to collapse
Here's a guide that can help you.
i am sure that there's guides here on xda too.

That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!

ForceClosed said:
That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!
Click to expand...
Click to collapse
Hahaha!! Happy that I helped someone!

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster

napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.

Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-

So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.

Troubleshooting Z5 Stuck in Limbo After Bad Flash TWRP

I've had a problem with my phone since flashing Lineage and Gapps in TWRP, something went wrong, it's acting like I have a corrupted version of Lineage with only the basic functions, Gapps is not installed and I've lost root.
The phone is an Xperia Z5, prior to flashing Lineage zip I had successfully rooted the phone, i flashed Lineage and then Gapps, an error appeared saying Gapps had not installed (possibly because it was the wrong version). After that the phone went into a bootloop (Sony logo, battery icon, then restart with red light in the corner). I was able to turn the phone on by holding down the power button for 5 seconds and lineage started up as normal with just the basic apps, I have been using the phone for the last month like this unable to find an answer on the forum. If I was able to connect the phone to PC i could use flashtool to flash the stock rom and start from scratch, but it only charges even though i have usb set to MTP in developer options, it's not detected by PC no matter how many cables I try. Also, it will not install apps from the Play website, it downloads and says app is installed but app isn't shown in list of apps. Can't get into TWRP because it says device is not rooted. When I switch phone off it restarts again and goes into bootloop, have to hold down power button to start it up. I wondered if anyone was familiar with these strange symptoms and knew if there was any way out? My phones stuck in limbo until I can find a way of doing a hard reset but without being able to get into TWRP or connect phone to PC I'm stuck.

{Solved}[HELP!!!][S8+HK] I messed UP, the system won't boot up because I've disabled all Google services by Package Disabled pro.

I've been using package disabled pro for a such long while but I made a terrible mistake in the last few days, I saw Google services are using too much ram, therefore I tried to disable all of them once for all and there were no any issue appeared at the moment, but a nightmare happened as when I was reboot the phone, the boot screen was stocked on "SAMSUNG" sign and I was waiting for a long time but the system won't boot up, so I realised I was screwed up that caused a lot of problems for me, for example I forgot my Google password when I tried to reset it shows that I need to receive the code of Google authenticator and I can't use my phone at the moment, so I tried also to use reserve number to receive the code, but the sim card just doesn't play nice with me because the sim card what I bought was from overseas, so I just stocked, ENVENTUALLY I decided to reset the phone from recovery, I tried but the system with same issue as when it booted up, so I decided to flash the firmware but I got only a raspberry pi 4 with me, it's running ArchLinux and I did some research on internet, eventually I found heimdall and then I tried to flash an official firmware I tried few times but it doesn't work and I realised that the FRP is locked I have no idea about how to unlock it, the point is I'm assuming if the App causes problem if I can turned it off, for example if I flash some specific *.bin or IMG it may works somehow? I'm not sure, please help me out!!~

The problem is solved by @hainguyenthao