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.
Greets All,
I need some help. I just installed VirtualBox on my system and then installed Ubuntu, the reason is I am trying to uncompress a kernel, fairly old one. Now before anyone asks, I am trying to look for the bluetooth mac address problem, as we all know its still generic. But I found a kernel that its either real or unique, either way it works, but the kernel is incompatable with Nand/zip roms. I tried to go to the dev that made the kernel, and got no response for a month now, so I am trying to see if I can find it and fix it with my limited understanding.
I have done searches for how to do it, and even found commands on google, but for some reason its not spitting out the results as the sites say it should, so I am hoping someone can tell me, or give me step by step instructions on how to decompress this kernel.
All the commands are from terminal mode, and I even had found a script on here that suppose to do it, but I cant get it to run right. So if anyone can help me, I would greatly appreciate it.
Thanks.
Really? No one can help with this? Does everyone like the generic Bluetooth Mac Address?
I'd really like to know this too
Well if someone would help me with the commands, myabe I can find how to impliment it into a zip/nand kernel and be done with this dumb generic.
Would anyone be willing and able to create a dump of a clean Windows 10 for Phones system image and share it with me? I searched around in the installation for non-supported devices threads, but did not see a reference to anything.
An FFU image extracted from the updater would also work, thanks in advance!
Why is that?
I see.
But at least it's possible, even if not very probable.
Although, we should check if we can use WinRAR, since it's possible to edit the images without breaking the signiture.
Assuming we have a signed image.
Not possible. There are many threads trying to achieve what you're hoping to do with cabs and such, and it's not possible when the bootloaders are signed and damn near everything in the system requires a signed cert.
But how does that prevent us from opening and modifying them with WinRAR?
Even if we can't boot the new files, it's still a step.
So open it with WinRAR, if possible.
At least to get an idea of the structure of the OTA, that peice of information may help us form an idea as to at least part of the structure of the system.
It's better to have (theoretical) partial read access, than no access at all.
feherneoh said:
FFU is not OTA
Click to expand...
Click to collapse
Alright, but can you open it inside WinRAR?
Now we're talking, what we need now is someone to examine the partitions and their layouts.
Unfortunately , I'm not at that level but at least I can understand these things, so I would like to hear the results.
Is anyone exporting the partitions yet?
Unfortunately, I don't know the partition layout in Windows 10 Mobile, but perhaps they should all be exported and examined?
Not for myself, however I had thought that it may help others attempting to port Windows 10 Mobile in the future.
you can try to download MI4 rom
http://en.miui.com/thread-189556-1-1.html
It's a Nexus 7 2013, the Wi-Fi model.
I am pretty sure this file is just irreversibly damaged now. I did adb push meaning to push a file to /sbin while following a tutorial online, and for some reason I put sbin/sh, probably because I had been seeing errors with /sbin/sh earlier, and I have been up all night trying to get Ubuntu Touch on this thing, frustrated and tired and not really paying close attention to what I was doing. I'm also not particularly qualified to be messing around with a device at this level, if you couldn't have guessed. I never used adb tools until tonight.
Anyway, I found absolutely nothing out there on how to fix this by searching the internet, so perhaps I've broken new ground with my stupidity. However, I am assuming that if I had a copy of this sh file from a Nexus 7 that wasn't handled by someone as careless as me, then I could simply replace the broken file with the untouched copy, by deleting the current one in TWRP and then using adb push to replace it with the new one.
So I guess I'm asking two questions:
1. Would this work?
2. If so, would someone with the same device please make a copy of this file and upload it here so I can try that?
I suppose I could also buy another Nexus 7 and get the file off that one, but if it isn't too much trouble for someone to copy the file from theirs and give it to me, that would make my life a little easier. And, on the very off chance that someone else makes the same dumb mistake later on, here it will be for them.
Of course, this is assuming that would work and that it's the only way to fix it. Regardless, any help would be appreciated.
EDIT: Ok, so maybe it wasn't damaged. I just rebooted and it works now. I was going to delete the thread but it appears that is not an option.
Hello everyone, I need help. As English is not my native language, please forgive me for grammar and spelling errors if there is any. I am a Chinese student and our school uses a modded version of the Lenovo TB-X605M for teaching, which has restricted recovery (unable to mount any storage device) , no recovery mode (you have to scan a QR code provided by the service provider to enter) and no developer options (which means I cannot use ADB).
Now I’d like to use it for more purposes, so I decided to flash it through EDL mode (9008).
I read from online that this tablet uses the programmer file “prog_emmc_firehose_8953_ddr.mbn”, but I can’t find this file, and I also can’t find ROM for fastboot flashing (where I can extract the file).
Does anybody have the programmer file or the ROM for fastboot flashing? In addition, will it be OK to use programmer files for the same SoC but designed for other OEMs? I need your help. Please comment below. Thank you very much.
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Renate said:
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Click to expand...
Click to collapse
Thank you for replying.
No. I'd like to try it later as I don't want to risk too much.
For EDL Clients , will "QPST Tool" be OK? And does HWID and Hash do? I never read about them on Chinese Android forums. Anyway, I am going to check out if I can connect to it and try to find them in QPST Tool and write them down.
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Renate said:
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Click to expand...
Click to collapse
Thank you for your advice.
As I have said before, I have never heard of what is HWID and Hash and I don't know what they do. What I am going to do is to wipe userdata , and I have no idea whether I need to know about HWID and Hash to do this. I am going to try some loaders I found on a Chinese forum. I will start trying from some other Firehose files for the same SoC.
Moreover, I viewed the link in your first reply and found all these files are with the extension name .bin , instead of .mbn . Are they loaders? If they are , how should I use them?
I am just an ordinary student and I am not familiar with command lines. I seldom use it unless I can't do it with GUI.
The HWID tells your processor, the Hash tells you who signed it.
To get a loader to work the two must be compatible.
I am not responsible for the content on Chinese forums.