Hello there,
I recently rooted my android mobile 2.3.6 version. I installed HiUninstaller and removed various system embedded applications like Facebook, some games, as well as the default GUI, since I already had installed a third-party one, named as Holo Launcher from Play Store.
I happened last day that my phone turned off due to low battery and then I turned it on and now it is stuck at the logo. I think that this is because that it is not able to find the default GUI whereas I have installed a third-part one.
I also tried connection my phone to my PC via USB cable and launched a command "adb devices" and my device is also not listed there, maybe because it has not loaded completely yet.
I hope that you guys shall help me out on your earliest.
Thank you for your time.
Related
I recently purchased an Optimus T and rooted it with z4root and then installed Titanium Backup to delete some of the preinstalled apps, like the Pacman Demo.
As I was removing each app, (~5 at this point) the Home button suddenly stopped working, followed by total phone death. Even after factory reset, when I was trying to access the phone, eventually I was shown a "... setup.exe stopped responding..." (or something like that) message and my phone just stayed stuck on the booting screen (android) every time I restart (w/o entering factory reset).
Does anyone have any ideas, or know which apps can prevent the phone from booting properly? A list of safe apps to delete would be helpful too. I thought I was pretty cautious with removing only non essential apps, but it seem bricked. Thanks again!
daramji said:
I recently purchased an Optimus T and rooted it with z4root and then installed Titanium Backup to delete some of the preinstalled apps, like the Pacman Demo.
As I was removing each app, (~5 at this point) the Home button suddenly stopped working, followed by total phone death. Even after factory reset, when I was trying to access the phone, eventually I was shown a "... setup.exe stopped responding..." (or something like that) message and my phone just stayed stuck on the booting screen (android) every time I restart (w/o entering factory reset).
Does anyone have any ideas, or know which apps can prevent the phone from booting properly? A list of safe apps to delete would be helpful too. I thought I was pretty cautious with removing only non essential apps, but it seem bricked. Thanks again!
Click to expand...
Click to collapse
About list off apps, I have to agree. Even it there is litle problem with dependencies, some minimum describe of these issue will be great!!
So, about your problem - I think, that you will have to download original ROM and do flashing with KDZ_FW_UPdater. (search on xda for more information).
But definitely, if it's possible I would try to install custom recovery throw adb shell (android SDK tools) and do backup of system for possibility to recovery or saving at least few data, and after try wipe and install one of custom ROM.
This happened to me after I tried deleting preinstalled apps on my Optimus One... Sent it in for repairs since it just stopped working. The tech guy said he did a "software update" and everything is good as new (except for the LGMITS error once in a while)
They didn't even bother trying to fix mine. They just told me to send it in and gave me a replacement.
So I finally figured out what I did wrong - basically when I was doing the deleting, I accidentally deleted the LG Home app, which effectively deactivated my (duh) home button and effectively stopped everything from functioning properly. For some reason I thought it was just a simple link from my phone directly to the LG website, as would happen with new PCs very often. Well... won't be doing THAT again.
However, my web2go button isn't working. I have to force quit every time I try to click on it. Can I just get rid of it or will it just give me more trouble later on?
At least you knew what went wrong with yours... I was just erasing CarHome and Layar and the LG App Adviser among other things i wont be using like Twitter and Latitude.
And they even gave you a new one x__x I had to wait 5 days before everything was good as new. After the first fix, USB debugging and mass storage stopped working so I sent it in for another "software update"...
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
Hi!
I'm new on XDA, so I'm sorry if the thread is placed in wrong subforum - if it is, I'm asking mod to move it in more proper place.
I bought Lenovo Lemon 3 - it was advertised as Vibe K5 Plus, but apparently the seller wasn't that reliable as I thought. As far as I know, the differences beetwen these models are little or none, but I have pretty big problems with the phone.
First of all it has some preinstalled software, which isn't in Play Store and some of them I can't even find in the net. The apps I would like to get rid off are KingRoot, MaxxAudio and SecurityIT. I successfully managed to disable MiBrowser - with help of KingRoot tool Purify actually. I tried to disable SecurityIT also, but if I do that I can't enter Settings->Apps. When I try the com.android.settings is stopped and it's not working till i enable SecurityIT again.
Second of all is that process com.android.phone is stopping randomly. Sometimes I click "ok" and I it starts working again. But sometimes it keeps crashing until I restart the phone. Since it's a dual sim phone and I'm using only one sim I thought that maybe this is causing a problem, but inserting second card wouldn't work, so currently I have no idea what is causing the problem. I tried cleaning cache and appdata with no effect. If the process is crashing and somebody will call - the phone restarts itself when I try to answer.
Thirdly it's hot. Even if I'm not doing anything and all apps are off and Im charging the phone it sometimes says that it can't be charged because of too high temperature on battery. Sometimes it works fine, but sometimes it's too hot too touch and I don't know why.
Oh, and one more thing. Something is installing random software. It looks like every time I open Chrome something is opening new tab and redirecting to PlayStore. I am trying to close these tabs while they're loading, but sometimes it loads too fast. Every morning I uninstall some new app, which is apparently installed by night. And those apps aren't added to my Play Store Account. I have disabled unknown sources, but I can see that phone is checking for updates around 2 a.m - so maybe those apps are from there - but I can't see any possibility to disable auto-updates. I have disabled auto updates in Play Store and I have "Lenovo Enhanced Experience" unchecked. Most of apps I installed from Play Store are games I had on the previous phone so I am sure they're not dangerous. Any ideas to prevent the installation of this unwanted software will be appreciated.
Since I used KingRoot to disable MiBrowser I apparently rooted it, but I was reading that this works only with KingRoot installed and with internet connection. And it's sending some data to China, which is not nice. RootChecker says it's rooted.
Lenovo Launcher it's not great either, I downloaded Lollipop Launcher from store and it works fine, but I had to block Lenovo Launcher from autostart, because it was very irritating and was enabling few times.
I am living in Europe so I was thinking is it possible to put on this phone Lenovo Vibe K5 Plus Stock ROM? Or is it this "trashy" like the one I have? I really like specs of the phone and I don't wanna return it, but I don't like the software behavior. Can you tell me what I can do to improve this? I don't care about warranty and I would like to have pure, non trashy Lollipop, so if it is possible somehow I would be glad for any help.
Thank you in advance for any help!
Lenovo Lemon 3 K32C36 > Cyanogenmod 14 - 7.1.1: SUCCESS
Hi
Did not know where to post this, I was not allowed to post in developer forums:
For those unlucky enough to have bought a Lenovo Lemon 3, I offer hope. My daugther's 'Lemon' now runs cyanogenmod 14 near flawlessly.
Here's what finally did it.
1st you have to unlock the bootloader. I found this page, google translated it,
http://4pda.ru/forum/lofiversion/index.php?t717648-420.html
and near the bottom is this link to a 'one-click bootloader unlocker'
http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=56376
[All this is similar to the Lenovo unbricking described here:
https://forum.xda-developers.com/k5-plus/how-to/unbrick-vibe-k5-plus-qfil-qpst-method-t3467830
but a lot of that is not what you need now.]
You have to install and run QPST from this on a Windows machine, and the Lenovo and Qualcomm USB drivers and the Visual C thing too to set it up.
I fiddled for a while but eventually got QFIL to recognize the Lemon. Keep in mind Win is pickier about USB cables than Linux.
Following instructions carefully, that one click then worked!
I moved back to Linux and adb and did the second part (pasting instructions from the Win .bat file into a root terminal). Sure enough, when I booted into recovery I had TWRP! But it showed no files on the Lemon and said there was no OS there! Nevertheless I was able to boot back into the awful K32C36 system with no problem.
So I went back to adb and did it again, but this time from the info and links on this page - but I did not at that time see the need to root.
https://forum.xda-developers.com/k5-plus/development/recovery-twrp-3-0-2-0-lenovo-vibe-k5-t3391100
Beyond all expectation TWRP then booted and all was visible.
I then picked this ROM page because someone had wrote that they had it working on K32C36
https://forum.xda-developers.com/k5-plus/development/unofficial-cm14-lenovo-k5-k5-plus-t3478288
to get this
http://moto.shreps.fr/Lenovo Vibe K...cm-14.x/cm-14.1-20161213-UNOFFICIAL-A6020.zip
Then onto SD card with it and pico 7.1.1 gapps
Install with TWRP (after backing up lame old ROM and wiping system, data, cache, as advised).
Long wait during 1st new system boot (I thought it was defeat) -- but comes the little blue man bringing very good Nougat.
Hope someone gets helped here .
Hei Guys, Good Evening,
Just had a quick question. I recently got a brand new fake "Samsung S8+", it runs on an Mt6580 processor, and android 6.0.1, kernel vs. 3.10.0. I rooted it as soon as it came, with King root no problem. However, once I had root access I went ahead, and deleted the stock browser which I assumed would just trace all my logins and stuff online. This created a myriad of problems: I now get the "Unfortunately X has stopped working" notification for every single app I try to open that needs Internet access. Rendering the Phone close to useless. If anyone has the same phone, could you please upload the apk of the stock browser for me, so I can get my Phone back? Or supply an alternate solution.
Things I've Tried:
1. Turning it on and Off (didn't work)
2. System Restore/Wiping Cash (didn't work)
3. Putting in custom boot loader and installing custom rom (No custom boot loaders work, and 'easy magic twrp' does not recognize my phone as mediatek device)
4. Installing Custom rom using ADB (doesn't work, cant pinpoint the reason)
I have searched the entire Internet, and also tried to make other browsers my stock browsers, nothing works.
Really appreciate your Help,
Jan
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.