Related
No matter what I do or use, (Aptana or Eclipse) errors always show in the XML files and I can never get anything to run.
I've done google searches and I can't find answers...I also can't seem to force ignore the errors in the IDE.
The other day I almost broke my keyboard, it's driving me crazy because it's such a stupid issues I can't seem to fix.
PLEASE, I just want it to work...xda is my last resort, I don't want to bug you guys about this, but I just want answers.
*** BUMP ***
without the files and errors no one here can help you.
http://pastebin.com
nenn said:
without the files and errors no one here can help you.
http://pastebin.com
Click to expand...
Click to collapse
You want me to upload the entire eclipse/aptana setup I have?
This is not unique to the sources, this happens with any code...this has something to do with my IDE setup.
Same thing happens on my workstation and my desktop at home.
in the spirit of understanding the problem, how far along developing are you? have you tried compiling the sample code thats out there already?
without information on what you know how can anyone help you solve your problem?
nenn said:
in the spirit of understanding the problem, how far along developing are you? have you tried compiling the sample code thats out there already?
without information on what you know how can anyone help you solve your problem?
Click to expand...
Click to collapse
Yes, can't compile anything...it always tells me an XML error.
I'm not at a point where I can give you the exact error, but I probably can tomorrow.
Start Eclipse and delete all Errors in the Problems View.
Then try to recompile.
Sometimes it solve the problems
Post the xml manifest and errors.
It is a pain to get started. Take a break and try again.
I would recommend un-installing Eclipse and any Android SDK stuff and start from scratch re-installing everything. If you haven't already, use the Android developer section walkthrough to set Eclipse up properly. They indicate which versions of Eclipse and the JDK to download. Maybe you installed the wrong versions of Eclipse or JDK?
Just something to try.
PM Kingklick he's the best at compiling Android.
Hello, I've downloaded the ZSKG1 from samfirmware and used MultiLoader v5.65 to upgrade my Wave, but unfortunately the following error occurs:
Platform 'so' checking is failed...
Platform 'so' modification is detected !!!
Same error occurs after replaced the battery and restart the phone. I can only make my phone work by reload the XXJL2...
Was there any problem with the firmware? Please kindly help!
Thanks!
Hi NitramNach
to flash S8500ZSKG1 you need to have FIRST S8500ZSKA2
Were you flashing from that FW???
I tested that FW (Don't ask me why)and Didn't have this issue
Please try again and let's see what will happen
Best Regards
Thanks! Forgot it had been mentioned in the download page, I'll try that.
Btw, there is a FactoryFs_S8500_Open_HkTw_XXKG1.pfs file, I load it as Factory FS instead of PFS, am I correct?
Also, is that the ZSKG1 does not include the swype like input method?
Btw, there is a FactoryFs_S8500_Open_HkTw_XXKG1.pfs file, I load it as Factory FS instead of PFS, am I correct?
Click to expand...
Click to collapse
No you are wrong
it is a *.pfs file so it should put in the pfs box
Also, is that the ZSKG1 does not include the swype like input method?
Click to expand...
Click to collapse
yes it doesn't include swype
i don't really know why is it removed
Best Regards
Tried to load ZSKA2, boot up, and then load ZSKG1, but still got the same error message...
I had removed the sim and sd card before loading firmware, will this be the root cause?
Can you post your multiloader Screen shot so i can see how you put the files in it please???
Its solved. i've loaded the .pfs file as PFS (the last check box) instead of the Factory FS which we usually used for .ffs file.
Thanks a lot for your advice!
Guys,
I'm so angry , I just rooted the nook glowlight and am unable to install any apk files.
I'm always getting "there is a problem parsing the package", whatever I found on the internet :crying:
Is there no file explorer by default on it ? And why this parse error ?
And most websites just crash, grrr
Anyone, anyone please anyone : HELP MEEEE
Do you have ADB working? Can you see a logcat?
Do you know that these APKs are actually good and designed for API level 7?
Also, is installation of apps from unknown sources enabled in nook color tools? Most (all?) of the NST rooting packages include it, but you do have to set the flag to get packages found via the internet (rather than the google store) and copied to the device to install.
I get that error sometimes when downloading .apk files from some sites. Your browser might not be downloading the file with the correct filetype suffix. Can you see if it has the .apk suffix on it? I've found that some browsers do better than others with handling this file-type. If you can get xScope browser or Opera Mobile I think those were better. It's also possible that a retry of the download will work, or that the file itself is just bad.
I get the same error on my nook simple touch.
the same apk's work on my galaxy nexus.
Anyone knows what might be the problem and how to solve it?
A logcat will tell you exactly what the problem is.
Use ADB and get a logcat.
xd4d3v said:
I get the same error on my nook simple touch.
the same apk's work on my galaxy nexus.
Anyone knows what might be the problem and how to solve it?
Click to expand...
Click to collapse
Are you sure these apks are compatible with Android 2.1 Eclair? Not everything will work. Which programs are you trying to install specifically?
bobstro said:
Are you sure these apks are compatible with Android 2.1 Eclair? Not everything will work. Which programs are you trying to install specifically?
Click to expand...
Click to collapse
I haven't thought of that. but you're probably right.
I'm surprised the error message is not more obvious though.
xd4d3v said:
I haven't thought of that. but you're probably right.
I'm surprised the error message is not more obvious though.
Click to expand...
Click to collapse
guys
I've got motorola xt800 (milestone/ glam)
I am getting the same error " parsing error "
There is a problem parsing the package
its on Android 2.1 eclair
and its not rooted
what should i do ?
pls reply
I cant even access market ... cant download any apk files
jaybhatia999 said:
guys
I've got motorola xt800 (milestone/ glam)
I am getting the same error " parsing error "
There is a problem parsing the package
its on Android 2.1 eclair
and its not rooted
what should i do ?
pls reply
I cant even access market ... cant download any apk files
Click to expand...
Click to collapse
Wrong forum.
Try installing any other package with requirements : 2.1+
In Settings check "Allow Installation of Non-Market Apps" .
Install apk from SDCARD.
I'm 90% sure you are just trying to install a package not compatible with A 2.1.
osowiecki said:
Wrong forum.
Try installing any other package with requirements : 2.1+
In Settings check "Allow Installation of Non-Market Apps" .
Install apk from SDCARD.
I'm 90% sure you are just trying to install a package not compatible with A 2.1.
Click to expand...
Click to collapse
Renate NST said:
A logcat will tell you exactly what the problem is.
Use ADB and get a logcat.
Click to expand...
Click to collapse
I have a similar problem...
new to rooting and romming, finaly!!!! got my ms770 lg motion back to stock and I too am getting the error " there is a problem parsing the package".
I noticed that if I download an app, it installs fine, no problem...but when I transfer from my pc, it shows up with that error message when I try to install.
I have read a LOT of these forums , trying to determine how to solve this riddle...they all say try THIS file manager, or, make sure installation of non-market apps is checked, or some such thing...
Well, the "allow installation of non-market apps" thing IS checked...still no dice...
What do I do with the log once I get it?
Basically....can someone please point me in the right direction? Please?
sebastienbo said:
Guys,
I'm so angry , I just rooted the nook glowlight and am unable to install any apk files.
I'm always getting "there is a problem parsing the package", whatever I found on the internet :crying:
Is there no file explorer by default on it ? And why this parse error ?
And most websites just crash, grrr
Anyone, anyone please anyone : HELP MEEEE
Click to expand...
Click to collapse
hey juz check if ur sd is protected with password or something. and its the reason y its showing... if sd is protected under developer options & phone is rooted it occurs. check that out n try and tht prob will be solved..it worked for me. check that out n reply.
anish.2010 said:
hey juz check if ur sd is protected with password or something. and its the reason y its showing... if sd is protected under developer options & phone is rooted it occurs. check that out n try and tht prob will be solved..it worked for me. check that out n reply.
Click to expand...
Click to collapse
This thread is almost a year old, therefore it is considered "dormant" or even "dead". Please refrain from posting in old threads.
Thanks.
I solved it.
In my phone These Error was occur twice a week. I found Best solution of "There is a problem parsing the package". For you I share this Link you can solve it by this link: youtu.be/njwRDPtfe_k :good:
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
ggiiaann91 said:
decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
Click to expand...
Click to collapse
Could be many reasons, you don't have enough information yet to know. Crucially, you failed to paste the verbatim error and the context surrounding it here. Or even link to the theme you refer to. So we don't have much to go on.
As it is labeled as an OTA theme, it will be specifically formatted for that custom ROM. So wouldn't it make more sense to seek help in the custom ROM support thread?
The actual error could be anything from a corrupt download (did you verify the md5 checksum or try downloading the theme again?) to a marginal USB cable (did you try a different USB cable and port?). Or many other things. Did you search the support thread to see if anyone else was troubleshooting similar issues?
.
Sorry, I'm completely new to the forum so don't know my way about.
How would I go about obtaining/providing the verbatim error?
ggiiaann91 said:
How would I go about obtaining/providing the verbatim error?
Click to expand...
Click to collapse
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
fffft said:
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
Click to expand...
Click to collapse
I appreciate that, I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
I also searched for the errors I am experiencing and whilst I found several other threads, none are a similar scenario to mine.
I am not using Odin or Kies, I was able to root my phone successfully, and installed the Alliance Rom with no issues.
My issue occurs after downloading an the OTA update/theme and then going into recovery mode > Install Zip > Choose zip from /sdcard > OtaDownloads/ > Install Black_Glass_S5
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
ggiiaann91 said:
I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
Click to expand...
Click to collapse
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
ggiiaann91 said:
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
Click to expand...
Click to collapse
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
It's not my intention to be vague, I simply do not know what information is relevant/beneficial to you.
I deleted the file and then re-downloaded a new copy but it still won't unzip the file, the issue also occurs for another OTA file.
If there's specific info I can provide then by all means let me know and I'll provide it.
Appreciate the help and patience - evidently I'm still a noob when it comes to all the features/tools.
ggiiaann91 said:
If there's specific info I can provide then by all means let me know and I'll provide it.
Click to expand...
Click to collapse
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
fffft said:
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
Click to expand...
Click to collapse
I wasn't disagreeing - I've not got any other information to provide currently.
Will try searching the forum more to see if I can find anything else in the meantime.
g935f stuck on logo
hi i tried to remove pattern lock of my s7 edge with z3x but phone just stuck on logo now im trying to take it to download mode but can not boot , just i can go to recovery mode , can anyone help me , is this possible i can flash by sd card.
fffft said:
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
Click to expand...
Click to collapse
You should be nicer. That was just plain rude.
guau pues buscais el update.img lo meteis y listo
"read only"?
ggiiaann91 said:
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
Click to expand...
Click to collapse
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
thanks this helped me a lot
Greggofaster said:
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
Click to expand...
Click to collapse
I realised I couldn't boot from sd card because I was creating the boot card through a card reader from this post so that really helped me thanks
"Hey i'd rather you do the work for me" kinda thang is a bit annoying. People are so silly sometimes.
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/att-s7-edge/development/howto-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
NoogleGexus said:
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/att-s7-edge/development/howto-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
I had the exact same problem as you, which is strange because I've used ADB on the same setup (same cable, port, phone, OS, drivers, etc.) to sideload packages with no issue. It's such a hard issue to solve, as even RAM/space requirements could cause it.
Long story short, nothing fixed the problem for me either. I'd trust that your file is fine - I don't think you need to re-download it.
Sadly, I think your best option is just buying a cheap SD card. It sucks, but sideloading the package from the SD card via recovery worked perfectly for me.
As was said previously, use an SD card.
NoogleGexus said:
Hi,
I am currently following this 'How-to' guide here: https://forum.xda-developers.com/at...to-update-galaxy-s7-edge-firmware-to-t3541329
However, when I get to trying to Sideload 'v8 (G935AUCS4APJ4) to unreleased (G935AUCU4BQA4) update file' - it says it 'cannot read *filename*'. I've visited the troubleshooting link in the OP's post, but to no avail. Tried everything, new USB Cable, different port, different ADB drivers etc.
I'd like to say that the problem lies with the file itself, but having seen other people have success with it, means it must be a problem on my end.
Do any of you have any suggestions on how to fix this? If possible, can anyone link a new upload of it?
For reference: I own the US model, G935AUCS4APJ4 is what I am on now. I am using the Sideload method as I don't have an SD Card. Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
You need to place in *filemane* file you download and rename to .zip. In example if you name downloaded file update.zip you should wrote " adb sideload update.zip" w/o qotes.
Good luck.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app