Related
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Heres the latest update so far...
Installed Lenovo K3_Note_MTK6752_Android_5.0_20150513 ROM from http://www.teamandroiders.com/lenovo-k3-note-stock-rom-firmware/
Its Android version 5.0, and still the same problem, almost every app still gives me the same error.
Going to try a rom built for Lenovo K3 Note T3s and reply afterwards.
quetiano said:
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Click to expand...
Click to collapse
Ok when you flash it the flash tools, you use the preloader.bin and lk.bin frome the original rom?
When you instal the new rom make recovery reboots betwen wipes? This last is for you make a clean instal and avoid problems like that you have it now, or meaby you can lost the imei number, or the keyboard miss it, i dont know many problem came if you dont make reboots betwen wipes
I hope be helpfull to you.
Enviado desde mi Lenovo K50-t5 mediante Tapatalk
Thank you for your reply.
I came across a website that had a guide to try, two options were available, the first option I have tried and it worked, havent tried the second option though. The first option was the Android System Webview app, where, by opening it under apps in settings, and choosing to uninstall the update, it should help fix my error, and it did. There were one or two apps that still gave me the same error but most of the apps began to work after doing this.
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...
I installed one ui on unlocked note 9 exynos variant with 6gb ram and 128gb rom. It had a bug which didn't allow the incoming and outgoing call in LTE/3G/2G(Auto Mode). So, i thought of rolling back to oreo. I deregistered myself from beta participation through members app, then i downloaded smart switch application on pc. Upon clicking downgrade, it analyses and downloaded all required files. When installation was initializing it gave a error "failed to recognize software update mode". I tried it around 5 times, everytime same error comes. I tried reinstalling driver, switching usb port, reinstalling app on pc and even deleting temporary files but problems remains same on every attempt, pls help me!
Gokul krishna said:
I installed one ui on unlocked note 9 exynos variant with 6gb ram and 128gb rom. It had a bug which didn't allow the incoming and outgoing call in LTE/3G/2G(Auto Mode). So, i thought of rolling back to oreo. I deregistered myself from beta participation through members app, then i downloaded smart switch application on pc. Upon clicking downgrade, it analyses and downloaded all required files. When installation was initializing it gave a error "failed to recognize software update mode". I tried it around 5 times, everytime same error comes. I tried reinstalling driver, switching usb port, reinstalling app on pc and even deleting temporary files but problems remains same on every attempt, pls help me!
Click to expand...
Click to collapse
**
**
Hey I did it yesterday and it gone fine. Note 9 128GB, exynos.
Guiry said:
**
**
Hey I did it yesterday and it gone fine. Note 9 128GB, exynos.
Click to expand...
Click to collapse
But mine is always showing "Unable to recognize the update mode"
Gokul krishna said:
But mine is always showing "Unable to recognize the update mode"
Click to expand...
Click to collapse
Are you successful downgrading back?
delusion8399 said:
Are you successful downgrading back?
Click to expand...
Click to collapse
Yeah. Actually i tried without deregister. Then Samsung switch rolled me back to 8.1. Thanks to all.
I am in the same situation
Gokul krishna said:
Yeah. Actually i tried without deregister. Then Samsung switch rolled me back to 8.1. Thanks to all.
Click to expand...
Click to collapse
You just re-registered for the beta and then went through smart switch again?
Interesting sounds like you have to be registered to the Beta before you can downgrade back to Oreo.
bro, the "in-depth test" apk doesn't work for me. I tried installing the apk but the phone kept prompting "App not installed"
....???
any solutions for this? thanks man
Edi
Tried it without the "in-depth test" APK, phone showed me:
The serial is not match
fastboot_unlock_verify fail
So bad for me
not much progress here. APK still doesn't work
chickentikka007 said:
bro, the "in-depth test" apk doesn't work for me. I tried installing the apk but the phone kept prompting "App not installed"
....???
any solutions for this? thanks man
Edi
Tried it without the "in-depth test" APK, phone showed me:
The serial is not match
fastboot_unlock_verify fail
So bad for me
not much progress here. APK still doesn't work
Click to expand...
Click to collapse
Same here too!
have anyone go solution????????
Bump
ALELOCOOO said:
Bump
Click to expand...
Click to collapse
[GUIDE]Bootloader Unlock Realme C12
After 6 months from launch date, we finally got bootloader unlock permission on March 2nd 2020 for Realme C12 initially based on Realme UI 1.0. Later Realme gave permission for UI 2.0 too. Before doing anything to device, keep a copy of Stock...
forum.xda-developers.com
You can use this
Any ideas on how to get firebase notifications going ? i have set up GMS successfully with Googlifier but not notifications .
No at the moment you don't. I installed GMS via Googlefier and cannot receive push notifications from Gmail, Calendar (or any Apps that uses Google Play-Service Push notifications API). Microsoft Authenticator won't work also, as the above-mentioned is missing from the GMS installed by Googlefier.
Luckily, WhatsApp push works.
So i managed to get push notifications going again by redoing setup and then freezing GSF with Multi tool - YAY!
Last bit of the puzzle is that i seem to be stuck on the .121 software which i downgraded to so i could get Google going - now when i click check for update on the phone or in Hisuite, it doesnt show any new updates (i was on .184 before downgrading). any ideas why?
Progress though
mahdibassam said:
So i managed to get push notifications going again by redoing setup and then freezing GSF with Multi tool - YAY!
Last bit of the puzzle is that i seem to be stuck on the .121 software which i downgraded to so i could get Google going - now when i click check for update on the phone or in Hisuite, it doesnt show any new updates (i was on .184 before downgrading). any ideas why?
Progress though
Click to expand...
Click to collapse
Software updater doesn't work anymore once you reflash using hisuite proxy. Your only way to upgrade now is to rely on hisuite proxy
Riyal said:
Software updater doesn't work anymore once you reflash using hisuite proxy. Your only way to upgrade now is to rely on hisuite proxy
Click to expand...
Click to collapse
But if I flash another rom with hisuite proxy it's going to reset the phone again isn't it? How can I update to latest release without losing data?
Seems liked i have wrecked my device - i forced an update to .182 using hisuite proxy and hisuite. now the phone boots up is fine for 20-30 seconds and then just reboots. any ideas how to fix?
mahdibassam said:
Seems liked i have wrecked my device - i forced an update to .182 using hisuite proxy and hisuite. now the phone boots up is fine for 20-30 seconds and then just reboots. any ideas how to fix?
Click to expand...
Click to collapse
You used the wrong version for your device.
Go to settings about phone and see if you still have your IMEI. If it's empty then you corrupted your modem partition and you can't fix it.
If it's still there then boot yo eRecovery and do a reset and update.
Riyal said:
You used the wrong version for your device.
Go to settings about phone and see if you still have your IMEI. If it's empty then you corrupted your modem partition and you can't fix it.
If it's still there then boot yo eRecovery and do a reset and update.
Click to expand...
Click to collapse
Yup that's what I figured, imei was blanked. I I sent it for warranty repair last week, good thing my main device is a oneplus 8t
mahdibassam said:
So i managed to get push notifications going again by redoing setup and then freezing GSF with Multi tool - YAY!
Last bit of the puzzle is that i seem to be stuck on the .121 software which i downgraded to so i could get Google going - now when i click check for update on the phone or in Hisuite, it doesnt show any new updates (i was on .184 before downgrading). any ideas why?
Progress though
Click to expand...
Click to collapse
In my tries freezing GSF makes the gps location accuracy really awful in all app using gps and i don't know why. Really bad.
denzel09 said:
In my tries freezing GSF makes the gps location accuracy really awful in all app using gps and i don't know why. Really bad.
Click to expand...
Click to collapse
Not for me, everything worked perfectly fine. Until I F'd it up with the manual update I mentioned earlier haha.
mahdibassam said:
Not for me, everything worked perfectly fine. Until I F'd it up with the manual update I mentioned earlier haha.
Click to expand...
Click to collapse
Really weird, that problem is a common problem for many i have seen after freezed gfs.
Like this:
https://www.reddit.com/r/Huawei/comments/ha2sez