Related
Why oh why can I not get anything to boot on my gosh darn incredible? I've tried everything except making it all work.
I want so badly to get something to boot, but alas it never happens. Stuck at the white screen is as far as I ever get. I don't even get the satisfaction of seeing a bootloop, at least then I'd be seeing some sort of progress. Its disheartening. I've tried all kinds of roms and system dumps to no avail.
There must be something I'm doing wrong, what?
Sent from my ADR6300 using XDA Premium App
Do wipe data and cache before flashing?
Yeah. I did manage to get a boot loop with the huashan gingersense leak. So some progress.
Sent from my ADR6300 using XDA Premium App
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
gnarlyc said:
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
Click to expand...
Click to collapse
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Mr. Rager said:
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Personally, I wouldn't copy entire folders over. I also wouldn't copy the boot.img over. I'm not saying that it won't work in some cases. It might. I've always swapped the kernels inside the boot.img, and renamed the device specific init file. Then, I would compare the init files from an existing ROM for my device with the init files from the ROM that I'm trying to port and see if there are any lines that are device-specific. If the init file is trying to start up something that doesn't exist on my device, then it doesn't make sense to keep that line. On the other hand, there might be a line that changes something for that ROM that IS needed.
This same thing kind of goes with the libs and other files too. You might have one lib that relies on another lib being there. And it might need a particular build of that lib. And other files might call certain libs. This is one reason that building from source generally works better over the long run than trying to get one device's ROM to work on another.
You have device specific and ROM specific things going on at the same time, so wholesale copies tend to miss one or the other. Plus it's nice to dig in and get an idea about what's going on.
Also, if you can get adb access while it's booting, grab a logcat. It might give you an idea about what is failing.
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Mr. Rager said:
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Click to expand...
Click to collapse
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
dsixda said:
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
Click to expand...
Click to collapse
I've had a busy past couple of days, but I'll check into the recovery dump and see what's up. I did change the ro.board.
I was trying to abstain from your porting tools, no offense, only so I could do it manually. Just trying to gain more experience, I guess, and learn. Your kitchen is excellent. I use to set up my environment and deodex among other things. The porting tool, though greatly eases the pain and shorten the manual labor ( yes lazy America) , take the learning curve out, a bit. But I guess I could take a look at the script to see what's going on too. Lol.
EDIT#1 - So I just tried to flash my rom. However, it wouldn't, because for some reason my phone is very particular about how one copies files over to the sd card. For one, you have to have the phone booted up, MIUI GB latest in my case, and mount usb storage. If I mount it through recovery, it corrupts my sd card, too bad I wish I knew that earlier. It's a PITA really...Ubuntu...
But, as phone WAS:
Hboot - 0.92
Radio - 11.19
Ship S - OFF
I tried copying and flashing through recovery. Fail as usual. So, I was gonna boot up into MIUI and try to copy from there, and got the infamous 5-vibe and twinkle.
I tried several times to boot into MIUI, but after many battery pulls, I figured out something ODD. In the bootloader the first couple of times it skipped the scanning process, then it started scanning again. Upon further inspection:
Hboot - still 0.92
Radio - still 11.19
Ship S - ON <---NOT A TYPO
Why? I haven't a clue. I tether my phone, so I got it booted, yay, but to do it, my sd card has to be removed and my usb plugged in, then turn on. So, my next edit will be a progress update. AFTER I s-off again ( that sounds kinda dirty, lol ), and re-format my sd. Also, my phone thinks it's charging...ITS UNPLUGGED. Lol, infinite-charging batteries, it's the future...
Sent from my ADR6300 using XDA Premium App
So...Good news is I got another incredible with amoled screen
Bad news I got another incredible with nothing on it, or rooted :-( But I rooted it before I even activated it with *228
But, alas, I still have all of my work on my computer. I managed to back it up before my phone crapped out. Plus I kinda get to start from the beginning so I can be more observant, and particular.
So, back to work...will update tonight.
Edit 1 - So after some more tinkering I've managed to fix some issues, but others have popped up namely the HTC Sim card authentication, which I have no idea about, yet, bouncycastle.jar is being stubborn by not fiding its classes, and libaudioflinger.so is failing to link to libsystem_server.so which in turn fails the link to libandroid_servers.so. Same three problems as before it seems.
Here's a pastebin of the logcat.
http://pastebin.com/QYde7fuQ
I'll keep tinkering about and see what I can come up with. Hopefully I'm closer to getting this thing booted up than I think.
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
SummonerOfDeath said:
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
Click to expand...
Click to collapse
Pull me a recovery.log when you try installing the zip, and I'll have a look for you.
Sent from my HTC Hero using XDA Premium App
S.O.D. proudly presents.... recovery.log!
Here it is, i attached my own update.zip (rosie-signed.apk), maybe you could have a look at it as i don't know where the fault may be.
greets SOD
I would already be happy if you managed to solve the update.zip issue (would help me with other updates) but the main prob is adb noch really working, seems like some system part is blocking this?
my hero was originally a t-mobile google g2, created goldcard, rooted, custom recovery, new radio and custom rom.
a few details:
device HTC Hero (T-Mobile Google G2, the black one )
rom Salsasense RC2 (at the moment...)
recovery CWM 2.0.5.7 (think so, but im sure i got the latest)
sd 2gb
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
SummonerOfDeath said:
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
Click to expand...
Click to collapse
Fixed your update-script, new line for each command is needed
/facepalm
JieeHD said:
Fixed your update-script, new line for each command is needed
/facepalm
Click to expand...
Click to collapse
not serious no? /facepalm -.-" thanks will try that right now xD will give feedback if my device is still alive afterwards xDD
greets, S.O.D.
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
stroobach said:
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
brick after flashing modified rom.
push to /system/app didnt work.
flashing restarts recovery.
jieehd's tip of single lines for every command doesnt work, same as above.
error 0 = apk is not made for your device/rom, wont install.
error 7.. dunno, think its not matching binary or parsing error.
files from my thread? as post above says one is a log and the other is defect^^
i doubt weather will work as its eating HUGE amount of resources. if u want this lockscreen, maybe try salsasense, has got a 3.0 alike lock...
holidays now, wish good luck in coding would be happy if u found a solution
greets, SOD
were can i find HTCG2/hboot/PC10IMG.zip been looking all over for it and its no were to be find
Got some questions.
1. You want WHAT? And what is the purpose?
2. In how far is this related to this topic?
3. If u give us a path to this file, why do u ask where it is? Maybe try dowloAding some random rom (probably some ruu) and do extract & search..
4. Are you really willing to contribute to this topic? I dont see the point of posting this.
5. Obey forum rules. If u have got a question, post it directly in q&a section, not in some random topic or directly explain the connection to the actual topic.
Greets, s.o.d.
agnostic900rr said:
I dunno, no idea
Click to expand...
Click to collapse
what don't you know? may we help you? whats the purpose of all these posts?
i think i'll give it a last try next time wenn i got salsa sense installed and either find a solution instantly or give it up, as noone is willing to support me and i can't do much more with my poor coding skills.
seems like we have to admit that hero's dying and i have to wait for my contract to end so i get a new phone.
greets, s.o.d.
Ok I am trying to build a Torch APK from git sources from Wayland_Ace. I went to repository and downloaded them as a zip. I've set up ADT and have Eclipse running. I chose to create a project with existing sources and chose the folder I extracted from the zip.
Now, I want to make some edits to this and I already know how and what I am going to, but I figured I would make sure the app would build before I made any changes and it won't. I get four "TORCH_STATE cannot be resolved or is not a field" errors and few warnings about some imports never being used.
I have a feeling this is because it's importing the settings from stock Android and not CM10.1. Can anyone help me fix this so I can build a Torch APK. I've Googled and fooled around with this for hours and have not had any success and am getting a bit frustrated.
admiralspeedy said:
Ok I am trying to build a Torch APK from git sources from Wayland_Ace. I went to repository and downloaded them as a zip. I've set up ADT and have Eclipse running. I chose to create a project with existing sources and chose the folder I extracted from the zip.
Now, I want to make some edits to this and I already know how and what I am going to, but I figured I would make sure the app would build before I made any changes and it won't. I get four "TORCH_STATE cannot be resolved or is not a field" errors and few warnings about some imports never being used.
I have a feeling this is because it's importing the settings from stock Android and not CM10.1. Can anyone help me fix this so I can build a Torch APK. I've Googled and fooled around with this for hours and have not had any success and am getting a bit frustrated.
Click to expand...
Click to collapse
How are you trying to build the apk? Through eclipse or through the android sdk?
fairct said:
How are you trying to build the apk? Through eclipse or through the android sdk?
Click to expand...
Click to collapse
Eclipse.
admiralspeedy said:
Eclipse.
Click to expand...
Click to collapse
I took a look at the source (CMs, not the one you pulled), and it is indeed because you don't have the CM SettingsProvider. It may sound foolish, and I'm not sure what will happen, but you could try commenting it out. I think that's just updating a system var so that things like the power widget can update appropriately. Worst case scenario you get a force-quit, or your LED won't turn off, forcing a battery pull
fairct said:
I took a look at the source (CMs, not the one you pulled), and it is indeed because you don't have the CM SettingsProvider. It may sound foolish, and I'm not sure what will happen, but you could try commenting it out. I think that's just updating a system var so that things like the power widget can update appropriately. Worst case scenario you get a force-quit, or your LED won't turn off, forcing a battery pull
Click to expand...
Click to collapse
I'm not going to do that, however your answer is extremely helpful now that I know it's caused by settings provider. Do you know how I could use a different settings provider in Eclipse? I could take the CM10.1 from the git of the ROM I'm using and somehow use it in Eclipse.
I really find it strange that I can only find a couple other people asking the same question as I. Do people not edit a single app from Cyanogenmod or some other ROM like AOKP without rebuilding the entire source? Upon doing some more Googling, it seems I need an Android.jar from Cyanogenmod.
Hoew I get this, I'm not sure.
admiralspeedy said:
I really find it strange that I can only find a couple other people asking the same question as I. Do people not edit a single app from Cyanogenmod or some other ROM like AOKP without rebuilding the entire source? Upon doing some more Googling, it seems I need an Android.jar from Cyanogenmod.
Hoew I get this, I'm not sure.
Click to expand...
Click to collapse
Well, I think they generally pull whatever APK they want, and then modify it to make it work. In some instances, that means changing other apks due to interdependency. Maybe someone who's familiar with building in eclipse could point you in a better direction...
I did it. I followed a guide to build a custom Android.jar from my phones framework.jar and Eclipse wouldn't build after because of it, so instead I only replaced the class files for settingprovider and my app had no errors after. I then saved the class files I edited, decompiled the classes.dex from the existing Torch APK and replaced the classes in it with my edited ones, recompiled that into a new classes.dex and put that in the Torch APK and it worked!
Hello,
I was wondering if there is anyone that might be able to give me a little advice.
I am decompiling the dialer app and trying to convert it to being a black dialer like the international version.
I am running into a problem after I recompile it to test it causes it not to work at all.
I am not sure if it needs to be signed or maybe there is a problem with the way the compile is working even though I am not getting any errors.
I have recompiled framework a few times and that has worked okay.
I am just trying to change the colors xml and have not changed any of the images, I am not sure if that might be an issue or not.
Or if I might even need to switch out the image files as well.
Any help on this would be greatly appreciated.
TheArtiszan said:
I am not sure if it needs to be signed or maybe there is a problem with the way the compile is working even though I am not getting any errors.
Click to expand...
Click to collapse
It's great that you want to learn how to invert or theme apps. But without meaning to discourage you, you need to do some reading. Quite a bit of reading by the sounds of it. There are a lot of threads on this subject, complete with tips, examples and introductory guides.
I can't shake the impression that you haven't read many threads about theming. And you seem to want the answer handed to you, rather than put a little work into learning this. You aren't asking a simple, straight forward question. You are asking for someone to teach you all of the ins and outs when you could easily find a tutorial yourself. Put a little initiative and work into this and then you will have something to be legitimately proud of when you finish inverting an app.
Unless you have an unusually easy app, you are probably missing multiple steps. You normally need multiple frameworks, emsure that your decompiler is up to date and yes there will be signing too. .9 pngs need special tools, you may need to edit dozens of image files and xml code too.
I'd encourage you to stick with it. But don't expect to succeed before you make an effort to read at least a handful of threads and guides and figure some of it out yourself.
.
Maybe start here:
http://forum.xda-developers.com/showthread.php?t=2524248
http://forum.xda-developers.com/showthread.php?t=2203166
http://forum.xda-developers.com/showthread.php?t=916814
http://forum.xda-developers.com/showpost.php?p=46723334&postcount=27
http://www.elementalxdesigns.com/ec...OOL-APK-Multi-Tool-Decompile-and-Compile-apks
.
You are having a signature missmatch error. You can try the xposed module to force matching of signatures. If that works, then i'll tell you what to do next.
fffft said:
Maybe start here:
http://forum.xda-developers.com/showthread.php?t=2524248
http://forum.xda-developers.com/showthread.php?t=2203166
http://forum.xda-developers.com/showthread.php?t=916814
http://forum.xda-developers.com/showpost.php?p=46723334&postcount=27
http://www.elementalxdesigns.com/ec...OOL-APK-Multi-Tool-Decompile-and-Compile-apks
.
Click to expand...
Click to collapse
Oh I totally understand what you are saying.
Sorry, I wrote that on very little sleep and rereading it, it is not very clear.
I have moded things like the play store and dialer and other things before.
I have used the apktool.jar that is up to date, installed the framework-res twframework and systemui apks as dependencies like what are needed.
It is just that if all I do is decompile it and recompile it with no changes it does not work.
This has always at least worked in the past if I have not made any changes before recompiling to insure that the process is working okay.
And it seems not to in this case.
I get no errors from the recompile or any warnings even.
This was not covered in any of the tutorials I had read before or found on a google search.
You didn't get a popup message with an explicit error message. But the information about the errors is still there in the system logs, event viewer, logcat, etc. Without those key details we can't really troubleshoot in a methodical fashion, but it is still possible to guess at the cause.
And a bad signature is a plausible guess. So start by checking that. A good way to approach it next time would be to try decompiling and putting a package back together again (before trying any serious edits) to see if your configuration is working or not.
.
.
TheArtiszan said:
Oh I totally understand what you are saying.
Sorry, I wrote that on very little sleep and rereading it, it is not very clear.
I have moded things like the play store and dialer and other things before.
I have used the apktool.jar that is up to date, installed the framework-res twframework and systemui apks as dependencies like what are needed.
It is just that if all I do is decompile it and recompile it with no changes it does not work.
This has always at least worked in the past if I have not made any changes before recompiling to insure that the process is working okay.
And it seems not to in this case.
I get no errors from the recompile or any warnings even.
This was not covered in any of the tutorials I had read before or found on a google search.
Click to expand...
Click to collapse
fffft said:
Clear like mud. I understand that you didn't get a popup message with an explicit error message. But that information would still be in your system logs, event viewer, logcat, etc. And we could have looked at the signatures if you had linked the files too. Since we don't have any of that though, we can't really troubleshoot in a methodical fashion - we have nothing to go on. It would have helped if you posted your system error logs, event log, logcat, the app signatures, etc.
Without any details, the guess above is as good as any for a place to start. A bad signature is a plausible cause to your problems. The very first thing you should have done is decompile and recompile without any changes. Then the same with a single, simple edit to confirm that your configuration is valid.
So to start.. confirm that your signature is valid.
.
Click to expand...
Click to collapse
It is a signature mismatch. The dialer has a shared user ID with the system. If the signature that the system uses does not match to that of the dialer, then it denies all permissions and denies installation of the package. Trying the xposed module first will be the easiest option (plus i wanna see if it works ) then i'll help you figure out how to get it working without the xposed module.
elesbb said:
It is a signature mismatch. The dialer has a shared user ID with the system. If the signature that the system uses does not match to that of the dialer, then it denies all permissions and denies installation of the package. Trying the xposed module first will be the easiest option (plus i wanna see if it works ) then i'll help you figure out how to get it working without the xposed module.
Click to expand...
Click to collapse
Ahh Okay thank you.
That was what I was thinking the problem was but wasn't sure.
Especially more so that I am on a all stock odexed rom.
I will give that a try later when I have a little time and let you know what happens.
Hey guys, i figure this might be a longshot but if anyone has or know someone who has an android rearview mirror ie: http://www.ebay.ca/itm/201130187577?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
If you could take 5 minutes and copy some of your files using adb, you might save me from having turned my android mirror into a paperweight.
adb pull system/framework d:\files\framework
I ran some scripts and i accidentally nuked some files without having made a backup (smart i know..) i'm pretty sure the culprit is framework-res.apk but just in case the command pulls the whole framework folder.
Thanks!
---
It has a weird launcher forced into it, that cannot be replaced as far as i can tell and has an app fireeye.apk that also boots and is forced into memory. I tried to get a different launcher to work, but their interface is modified and the home button is not really a homebutton, but is hardlinked to their launcher. Trying to bypass that i managed to screw it up, also no fastboot, it uses livesuit for restore and as far as i can tell no chance of flashing the cm for allwinner as it has a really weird partition set. I'm kinda stuck.
I have one
I have 2 of these and I am interested in helping you. what do I need to do to get you a copy of the files on it?
Recovery???
How did you get it into recovery mode??? i messed something up and it wont go pass the Android logo!
Sorry to dig up an old thread.
I have one of these dashcams and the fireeye app keeps freezing on me. its really annoying. Until yesterday i have put up with it by resetting the device. Yesterday i was invloved in a minor car accident only to realise that the fireeye app had frozen again and did not get a recording of the accident. would have come in usefull.
Has anyone had problems with the fire eye app freezing and have you figured out a a way around this?
Hoping someone can help
OlvrCA said:
How did you get it into recovery mode??? i messed something up and it wont go pass the Android logo!
Click to expand...
Click to collapse
There is another thread about this
http://forum.xda-developers.com/general/connected-car/android-reversing-mirror-model-rt01-t3097492
This is the download link, and there are instruction which will tell you how to upgrade it.
http://yunpan.cn/cKzgb95TaCEJk
Password: 8880
These were the instructions I got from a seller on aliexpress.
It's a little different but maybe someone could extract from here and make yours work