Related
As topic states Im having trouble with a program called Navizon. I have tried uninstalling and reinstalling numerous times, including removing all registry entried for navizon. each time it installs fine, however when I go to start the program I get this:
Navizon.exe - Native Exception
A Native Exception Occurred.
ExceptionCode: 0x80000002
ExceptionAddress: 0x00e28328
OK to terminate
CANCEL to debug
hitting cancel and ok both boot me back to programs list
I have a post on navizons tech support forum, and there have been two people with advantages who have successfully installed and ran the program...as far as I can tell the only difference is our roms. Of course im running the greatest ever, AP Dual Black 3.0 rom. Do you guys have any advice as to what could be causing my error? If you want to check out my post on their tech support forum, heres the link.
http://www.navizon.com/phpbb2/viewtopic.php?t=1658
just an update, did a hard reset, and installed Navizon works great, had to be a scummy program conflicting
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
bariz143 said:
Hi guys.
Just started to build my own AOSP build from source. Im using Ubuntu 12.04 LTS and everything works great with repo sync and building the rom.
I flash the build and everything works great to. Time and date is correct. Google sync works. Google now works.
But when i reboot my phone the time resets to 1970 for about 15 seconds till it goes to current date and time. But i get like 10 notifications from all of my apps saying google sync error, Time error and WhatsApp says time error to. Goggle sync is stuck on sync. google now dont work and so on.
I have tried to build it over and over again without luck. I wiped everything before flashing the zip. I even did a fresh clean install of ubuntu and did everything from the begining but it still resets to 1970.
I tried to build CM11 rom also and everything works great. No time issues. So why is pure AOSP doing this?
Someone said something about qualcomm time daemon not storing time in data/system/time directory .
I have been trying to fix this for days without any luck.
Click to expand...
Click to collapse
I'm not a dev (though I know how to compile, just not any coding) so don't have a fix for you, but found this as a potential work around until someone can help you sort the rest: http://software.techassistbox.com/datetime-1970-bug-aosp-workaround_136694.html
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
bariz143 said:
The time issue is solved thank you
Time to include Superuser to the build but i have no idea how to do that.
Someone want to help?
Click to expand...
Click to collapse
Out of curiosity, how did you resolve?
I was under the impression that you just have to add the SuperSU apk to /system/app and the SU binary to /system/bin, but not entirely sure on that part. If you are trying to bake it into the actual Settings app, not sure on that.
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
es0tericcha0s said:
Found some guides on how to add stuff AFTER it's been built, but not during the build itself.
I know a lot of the devs get bombarded with inane questions from random people so often ignore PMs. Not saying your question is, but most of them don't like to answer questions there that should be in the thread for their stuff so often just overlook the inbox.
Come to think of it, you aren't really adding SuperSU TO Settings, just enabling a shortcut in the Settings app that leads to the app.
http://developer.android.com/reference/android/provider/Settings.html
I'm wondering if this:
public static final String ACTION_APPLICATION_SETTINGS
Activity Action: Show settings to allow configuration of application-related settings.
In some cases, a matching Activity may not exist, so ensure you safeguard against this.
Input: Nothing.
Output: Nothing.
Constant Value: "android.settings.APPLICATION_SETTINGS"
Part isn't something to do with creating that link...? Just making an educated guess.
Info on adding stuff after it's built - might be helpful to see where things are at?
http://forum.xda-developers.com/showthread.php?t=2184207
http://forum.xda-developers.com/showthread.php?t=2341389
Also, check out this dev/thread: http://forum.xda-developers.com/nexus-4/themes-apps/mod-custom-options-settings-app-ops-t2593536 Maybe you can ask him or decompile his Settings.apk and see where he added the necessary coding in.
Click to expand...
Click to collapse
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
bariz143 said:
Holy sh!"¤%t. Thats alot to do. I have to study this for a month to maybe succed
Compiling the rom feels alot easier when reading this haha
Click to expand...
Click to collapse
The more you learn, the more you realize you dunno.
es0tericcha0s said:
The more you learn, the more you realize you dunno.
Click to expand...
Click to collapse
Haha good answer. Man I don't know where to start. I will look in to it but not today.
deleted
Just noticed that my aosp build cant locate my location. And thats a huge setback. Really need help with this. Without gps there is no way i can use this this rom as a DD.
Downloaded gps status app and started it and it doesnt find even 1 satelite so something is wrong there.
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
es0tericcha0s said:
See if you can grab the gps.conf file from a working rom for your phone. Or try this - which might be able to make the right one for you: https://play.google.com/store/apps/details?id=org.fastergps
Click to expand...
Click to collapse
Tried that app. Nothing happend. Going to grab a gps.conf file from some rom.
EDIT: Just tried that without sucess. No gps lock at all. Think it has something to do with my binaries. Cant figur it out
EDIT2: FIXED:but GPS connection is very bad. Have to go outside to get a lock. Could get connection inside before
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
es0tericcha0s said:
At least you are making progress. So the gps.confg file helped a bit? Now that it is working somewhat, maybe one of the GPS status apps can help make it stronger?
Click to expand...
Click to collapse
Okey its not the gps.conf file. Just flashed a custom rom (No names) and it locates my location in a heartbeat inside my apartment. My build is much slower and don''t work inside.
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
bariz143 said:
Dropped development ATM. Need to fix gps. Dont know where to start. I tried with the binaries again without luck
Click to expand...
Click to collapse
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
kidkoala_uk said:
Bariz I have the same time issues which bin files did you replace/add was time_daemon one of them?
Click to expand...
Click to collapse
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
bariz143 said:
I just extracted all the binaries from stock rom and put them in my vendor if I remember it right. It was a long time ago since I developed. To much for me man
Click to expand...
Click to collapse
Cheers bro.
Edit: Issue now resolved the Google proprietary blobs are missing a number of files. Got the necessary files and added to my build.
AOSP build resetting time to 1971 after reboot in Airplane Mode
bariz143 said:
The Google binaries had some missing files so I pulled the binaries from stock factory image and it worked
I want the superuser baked in as the other roms out there
Still haven't found a guide or help from someone.
What happens to XDA soul where everyone helped each other back in the days. I have pm a lot of developers and no one answered back
Click to expand...
Click to collapse
We are having the same issue with a Nexus 5 (Hammerhead) where the date/time are not sticking after reboot when in Airplane Mode (no data connection, wifi off). Can you provide some more detail about how solved the problem? Which binaries and how did you pull them over? Thanks.
So... I have an Archos 55 and well, root is dangerous, particularly when you're being annoyed with pop up adverts and want to get them gone.
TL;DR:
So basically this all started when I found that web pages and adverts were just opening. Whether I was using the device or not, they'd just magically appear, sometimes ten at a time, accessing the internet at will. I was not best pleased as I have not long purchased the phone, but true to form, Archos have no idea what customer service means, so I was left to attempt to remedy the situation myself. Ordinarily, I would have just formatted and reinstalled the O.S, I do that with linux all the time alas I knew that was difficult.
Instead I sought to find out what exactly was causing the adverts. I deleted all the apps I had installed, but still the adverts kept coming. I did a factory wipe. Still with the adverts. At this point I was a bit stuck, so I grabbed an anti-virus app. It showed a few things that were causing problems including one trojan, under com.android.settings (or something to that name). I made a few enquiries and needless to say, this wasn't a false positive, but it had meant that I had a trojan...and I really don't like trojans. Cue the rage and the not thinking properly as I deleted com.android.settings without making a backup thinking... "shouldn't be too hard to put back"...oh how wrong I was...
I of course tried to make amends by grabbing a "copy" of settings from another site (and possibly a different phone) but I was told that it was ROM and no amount of permission changing was going to change that (I tried and I apparently failed, I may have possibly been doing something wrong, but I don't think my chown/chmod skills are `that` shabby).
The problem:
- No access to settings. Settings doesn't exist. (No access to USB Debugging either because that requires tapping the about phone bit and guess what...)
- Can't install apps as something has "Stopped".
- No access to WiFi
- Using Linux (Ubuntu something or other...15 I think).
- Mobile Tinkering Newb (But I'm not totally tech illiterate).
I do have access to fastboot mode apparently.
So what I think I need is a way to reinstall lollipop 5.1 so I can get back to square one, without (at least initially) using ADB (because I've tried and my device just refuses to show). I've also tried a few "needrom" things but, of course, they don't work because linux.
If anyone could possibly help me, I would be greatly appreciative in any way. I just want wifi back really. (I can see that wifi works and a network is available I just can't edit the settings to access it). If I can provide more information, please ask and I shall provide.
[SOLUTION]
Back up your device <- Essential
Grab a rom from NeedRom
Enable Fastboot.
Enable USB Debugging etcetera.
Use custom software (provided by NeedRom) (I know this seems dodgy but you try anything when you're desperate enough and this works so...if you're worried then take precautions and make a backup of your own phone first.) to open up the .pac file. Check where the files have been opened up to.
Copy the files to a more stable area (i.e from Temp to your Data drive), they should be in .img format as .pac basically appears to be some kind of archive that groups them all into one.
Use Fastboot (you might need to enable this so make sure you do it) and flash the .img files to the phone and sparse them to about 250MB.
Restart the phone.
Check phone works properly.
If works properly, consider donating to NeedRom.
Anyone?
Trojan
I have the same problem, but I didn't uninstall the setting, did your Trojan installed random apps too? Like MyApps or something like that?
Seeing the same problem I think the problem is that the device comes with it, but I haven't found anything else to do apart from installing avast to tell me when unknown sources get on to install a random app.
Talasa said:
Anyone?
Click to expand...
Click to collapse
Hey I fixed it, I have Uninstalled settings and successfully installed them again, no pop ups since.
Message me so I can tell you how to do it.
Fantasma198 said:
Hey I fixed it, I have Uninstalled settings and successfully installed them again, no pop ups since.
Message me so I can tell you how to do it.
Click to expand...
Click to collapse
Hi! How did you solve the problem? Please let me know
It appears to involve installing an apk installer from the Google Play stores (any will do it seems). Then by installing a copy of the Settings.apk.
Neither of which I am able to do as, due to getting rid of settings Google Play won't work. So....
Edit. I managed to get Google Play installed and then installed an APK installer. However installing settings is restricted as security won't let me install unofficial apps. >.>
How do u get rid of pop ups
Fantasma198 said:
Hey I fixed it, I have Uninstalled settings and successfully installed them again, no pop ups since.
Message me so I can tell you how to do it.
Click to expand...
Click to collapse
How do u get rid of them my phone is plaqued with them they are so annoying I didn't even root my phone just done a simple software update thanx
R3b3l3k8 said:
How do u get rid of them my phone is plaqued with them they are so annoying I didn't even root my phone just done a simple software update thanx
Click to expand...
Click to collapse
Hi,
What you have here is a virus.... and like me, it's probably embedded in settings. I.e It comes with the device.
There is no way to get rid of those adverts....except...by voiding your warranty. You will need to wipe your device and reinstall a rom, preferably not your original. (That or send it back to Archos). Taking your phone back to the store and demanding a refund is an option before I proceed further and this is the solution I recommend.
Take this moment to back up all your data.
What I did however and what seems to have gotten rid of them is firstly head over to NeedRom (search) and acquire a freely provided Rom of someone else's phone. There are two versions for the Archos Platinum 55 and it will depend on your specific phone.
Now you will need to flash (this will destroy all data on your phone so make sure you get it backed up) your rom. You can use the ADB solution but that couldn't work for me. So I used Fastboot instead, however to use this the rom provided by needrom is in a .pac file format, you need to get the .img file from it. You can do this by loading up the software provided by NeedRom (named FactoryUpload or something like that) load the .pac file and look at the file path locations. The one I checked was for System. I then went to where it said it was, in my case a Temp folder, copied and pasted all the data to somewhere not temp (all the .img files I needed were there).
Then I used Fastboot to flash the rom entirely there are much better Fastboot tutorials out there than I can explain myself. This flash included System, Recovery, Cache and basically everything, however it wouldn't let me do it all at once. I had to use a particular "flag" or "switch" so that it would `sparse` all the files over 250MB (that was the number I chose) and it worked after that.
This is the only way without returning the phone to get rid of the adverts *if* the virus is indeed in Settings. There's no way to remove Settings safely. I tried.
I'm trying to upgrade my Samsung p7510 10.1 tablet from Ice Cream Sandwich 4.0.4 to either Marshmallow or Nougat, or better. I've installed TWRP 3.1.1 and rooted with SuperSu. I've had to assume root has worked as can't download root checker onto my tablet.
So, far I've managed to find a version of Marshmallow "ROM-STOCK_MMB29K-seed.zip" on androidfilehost.com. But when I try installing I keep getting error message "Updater process ended with signal: 4". I've wiped the Data, cleared the Cache and Dalvik Cache. Also searched the internet for info on the signal 4 problem but not found much other than to remove the "assert" line from the updater-script file in the OS zip.; that did nothing.
So, a few questions:
- Anyone know where I can get OS zips from for a Samsung P7510?
- And any ideas on resolving the signal 4 issue?
- Any other ideas?
P.S. The only reason I'm updating is I want to use it for Kindle but can only reach HTTP sites, not HTTPS. Assumed that is because it's so old that everything is out of date. And that stops me from downloading anything from just about anywhere, including Google Play.
P.P.S I have searched the forums but couldn't find anything helpful or with links that worked.
Thanks in anticipation
Might I suggest the stabelest ROM I've ever run on my P7510. I've had this installed on mine for over a year now. There are of course some minor bugs.
The signal 4 issue is most likely a Binary issue and should no longer be relevant since you should reset the device to factory and start over. Another thing is once you Root it you can't download from Google play because you now have an unverified device, it has something to do with Google Pay. You'll want to look for APKs. Although SuperSu is usable, you're going to want Majisk insted. I hear of some problems using SuperSu.
I have these files here in my PC if any of the links no longer work but you'll want to know how to flash it so you'll need the video. I'll check back soon and drop a link to my files. if you need them. I'd need to upload them to my Google Drive first.
If you have any other difficulties I'm usually here about once every week.
P.S. Your tab is better than a Kindle and I would not suggest using it as such, it runs pretty crappy that way . Amazon does have an app you can use. And I see that you have been having difficulties finding Operating Systems for your tab and yes it's because the P7510 first hit the market in March of 2011 there aren't many people doing much with it anymore. There's about 3 or 4 of us left.
Firstly, thanks for your help @Casper Young .
In particular the video was brilliant. I did have a few runs at the update, however, the process was very straightforward. The key issue was the TWRP version I was using. It was supposed to be for the P7510, but realised it was actually for the P7500, consequently the aosp files weren't loading. I think that was also the cause of the errors I was getting. And although none of the links were working I managed to get the file names from the video and sourced them from androidfilehost.com:
twrp2870-20150814-p4wifi.tar.md5
aosp-7.1-p4wifi-20170506.zip
Once I had those it was simple and the update worked smoothly.
I've also added the app from apkpure.com as Google play was a complete pain trying to get the tablet recognised. Now very pleased with the build and apps, all running very smooth.
thanks again
Glad you had no problems. There are some minor bugs. Flash doesn't work for the camera. And check your memory capacity. I use Apex Launcher for my home screen which organizes better for me.