Related
Since we are not able to boot into recovery mode and run update.zip is there a way to manually apply themes to the Desire builds we are using?
Such as [MOD] Smooth Sense Icons v.1.0 (now with screenshots)
Thanks in advance.
+1
i have been asking this question since day 1..and no honest reply
I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode
well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!
[★] said:
I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode
Click to expand...
Click to collapse
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.
jjones1983 said:
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.
Click to expand...
Click to collapse
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one
yes..
i have even tried with droid exployer and it bricks the rom..it boots the at the android screen it just flashes black..dont understand..im using darkstone sense rom..he has the espresso bar..and i cant add anything too it
[★] said:
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one
Click to expand...
Click to collapse
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.
11calcal said:
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.
Click to expand...
Click to collapse
ahh thanks and how do I put it into debug?
edangel said:
well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!
Click to expand...
Click to collapse
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.
gardndj said:
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.
Click to expand...
Click to collapse
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much
all those guides
[★] said:
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much
Click to expand...
Click to collapse
are for phones that can be rooted and flashed with recovery..for us on the hd2 we HAVE to adb every file 1 by 1...sucks..and even the terminal method..you will see errors on your phone..i wish darkstone would just say how he put the espresso on his rom.
Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot
themes are ROM/framework specific which is why certain themes are only available for certain ROMs. shu8i builds are based off of cyanogen and are therefore the easiest to theme IMO. I have done a theme thread for that particular set of builds and have had great feedback from users.
So FWIW, a theme cannot be applied to just any ROM. If you want to get into it, you will need to find and extract the .PNG files from the framework-res.apk , pull the framework-res.apk from the build you are currently running, replace the images, and replace the framework-res.apk in your build with the patched one with the new .PNG's
there are plenty of TUTs on XDA explaining how to theme, only difference is us HD2 users have to manually push the files instead of using the convenience of an update.zip that is flashable in recovery.
Moved you guys over to general.. Best of luck!
makomek said:
Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot
Click to expand...
Click to collapse
I understand that this thread is old, but I just found it. Trying to install a new framework-res.apk to my device using this method. I have it in a zip file (which is the format that would be used on a normal device to flash it from recovery mode).
Well I tried this; it lets me choose the theme (zip file) that I want, and it then prompts me to choose OK to reboot in recovery mode and continue the installation. Nothing happens when I choose OK.
Any further info on how to do this? What am I doing wrong?
Hello, I have scoured the internet looking for ways to improve the speed and performance of my samsung fascinate and have only found instructions on how to do this with a pc. Are there any methods out there for a mac? My phone has been rooted and works fine, but I notice lag from time to time. Any help would be much appreciated. Thank you.
The only thing that is really PC only is flashing via Odin, and most of the stuff you do in Odin can be done on a Mac anyway. Most upgrades (kernels, roms, and other mods) come in flashable zip files for Clockwork recovery. If you can transfer the file to your SD card, you can update the rom or kernel fairly easily.
Yeah I'm a Mac user. Everything you need can really be found in the rom manager app these days. As stated above you can also just move the zip files from Mac to phone. But if you are uncomfortable inside recovery, rom manager pretty much does everything for you. Good luck.
Sent from my SCH-I500 using XDA App
Ayracon89 said:
Hello, I have scoured the internet looking for ways to improve the speed and performance of my samsung fascinate and have only found instructions on how to do this with a pc. Are there any methods out there for a mac? My phone has been rooted and works fine, but I notice lag from time to time. Any help would be much appreciated. Thank you.
Click to expand...
Click to collapse
If you're rooted, you can find a flashable zip of a kernel that you want, but if you don't want to use cwm to flash it (i don't see why you wouldn't, it's the absolute easiest way) you can use redbend_ua. It will most likely be included with the kernel you chose.
so what you need to do is push redbend_ua and the kernel (zImage) to /tmp
Code:
adb push /path/to/redbend_ua /tmp/redbend_ua
Code:
adb push /path/to/zImage /tmp/zImage
Once done with that you're going to adb shell and set permissions and flash the kernel you want.
Code:
adb shell
# cd /tmp
# chmod 755 redbend_ua
# ./redbend_ua restore zImage /dev/block/bml7
# ./redbend_ua restore zImage /dev/block/bml8
All in that order if you wanna take that route to installing a kernel
That bit of code actually saved me when i was experimenting with flashing a custom recovery that i dumped through odin. Hope this helps you.
I have problem runing script from init.d folder. Script maked by link2sd work, but every script i add wont run on boot.
I set same permision liki in link2sd script... any idea?
when try to open script from init.d folder with root explorer there is no txt. :/
Have you tried script manager?
sent from my gt540 mur4ik RC0 806mhz
yes, it`s work when run script manueli... but not working when set run on boot.
goto data/local and edit the userinit and put this code in it
sh /system/etc/init.d/scriptname
that should force the script to run.
i dont have userinit in data/local
just to create it, or...?
yes just create a userinit.sh file then put the command in it
not working, strange...
can you upload the script you are trying to run so i can do some tests for you?
yes, it`s simple script to enable swap on swap partition. work fine when run it with gscript, script manager... but i want to run it auto on boot.
edit the script to look like this
Code:
#!/system/bin/sh
#
# enable swap on ext partition
#
echo 30 > /proc/sys/vm/swappiness
swapon /dev/block/mmcblk0p3
noup, mmcblk0p3: no such file or directory.
have you partitioned your sdcard properly and what way did you do it?
yes, i partitioned it with recovery. swap work fine when i run script manuele, or run comand with terminal. problem is than script wont run on boot, not only this one, v6 super charger wont run eather.
--------
i forgot, i use greendroid 2.0 and 666 infernal kernel
god thats odd what rom are you using mur4iks,joes or one of the softmod GB
greendroid 2.0 and 666 infernal kernel
this kernel hava init.d suport... i think.
it should support swap ok because init.d folder belongs to busybox which the ROM has i would say for you to get the best from your phone is to upgrade to a gingerbread rom preferably CM7 as it supports swap straight fro boot and it also allow V6 SuperCharger to run properly i can help with a 2.1 rom because i only had 2.1 on my phone for 30seconds before flashing a 2.2 CM6 rom.
i use CM7 before (mur4iks M6 was last i try), but every day there was some little bug, and i have big problem with battery, gps... so i went back to 2.1.
tnx for try helping me.
no problem sorry i couldn't help more.
I open this thread to motivate to carry ice cream sandwich to our Motorola Defy Mini, and now we need to update root our devices and enjoy the latest versions of android.
Let's see if we can all get something.
I searched the internet and found yesterday that the Motorola Defy mini and htc xplorer have the same hardware, and the latter has adapted cyanogenmod 9.1, we can start there.
Let's try in this thread and with the help of all get a fully functional ics rom.
Please someone can move thist post to defy development
davis15 said:
Please someone can move thist post to defy development
Click to expand...
Click to collapse
Have you found new informations about the CM for defy mini? I am really impatient !!
You can find some kind of hw comparison on wikipedia's Snapdragon chipset:
http://en.wikipedia.org/wiki/Snapdragon_%28system_on_chip%29
and look at similar models what for support they got
.
CM10 HTC Explorer (Pico) port
First thing: What SystemROM size showing in Titanium Backup?
Model name will show as A310 (Explorer). Try that because I don't have Defy Mini. Build contains stock defy mini kernel. Defy Mini recovery: http://forum.xda-developers.com/showthread.php?t=2187074. Make nandroid of stock rom. Tell if you can boot to it. If yes i will try made custom kernel (kexec or 2ndboot) & simpler cwm usage (2ndinit or 2ndboot) ,Model name will show as A310 aka Pico. If not, when restore nandroid or reflash stock rom via RSD Lite.
LINK: http://www.gigasize.com/get/g3kc53g7o7d
Also: if it boots make screenshot (better photo cause i will know if you didn't faked) of About Phone.
new stock roms
I just got a new Motorola Defy Plus phone with gingerbread 2.3.x stock rom.
Where can I find a Motorola Defy Plus ICS or Jellybean stock rom?
Not Cyanogenmod or AOKP/AOSP.
Is there any such thing as a stock ICS or Jellybean for Motorola Defy Plus rom?
So far all I see is cyanogen/aokp/aosp ics and jellybean roms.
Does this means that most likely there are no stock ics/jellybean roms for the phone?
Thanks
Misterjunky said:
I just got a new Motorola Defy Plus phone with gingerbread 2.3.x stock rom.
Where can I find a Motorola Defy Plus ICS or Jellybean stock rom?
Not Cyanogenmod or AOKP/AOSP.
Is there any such thing as a stock ICS or Jellybean for Motorola Defy Plus rom?
So far all I see is cyanogen/aokp/aosp ics and jellybean roms.
Does this means that most likely there are no stock ics/jellybean roms for the phone?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1795647
created kernel for defy mini
For who is interested:
I created an ICS kernel based upon the motorola sources merged with some stuff from a 3.4 kernel from code aurora.
You can find it on https://github.com/de-wolff/android_kernel_motorola_xt320.git
I think it is capable of everything you need, but I am still working on the CM stuff for it.
(At this moment my phone can start using fastboot, into a CM9 version.I have a working touch screen, a working volume button, audio, when I touch the screen, and a working shutdown. I will commit this also soon, so anyone who is interested, can create his own CM9 version)
If someone can point me to how 2nd boot is supposed to work, I would be very thankful.
de-wolff said:
For who is interested:
I created an ICS kernel based upon the motorola sources merged with some stuff from a 3.4 kernel from code aurora.
You can find it on https://github.com/de-wolff/android_kernel_motorola_xt320.git
I think it is capable of everything you need, but I am still working on the CM stuff for it.
(At this moment my phone can start using fastboot, into a CM9 version.I have a working touch screen, a working volume button, audio, when I touch the screen, and a working shutdown. I will commit this also soon, so anyone who is interested, can create his own CM9 version)
If someone can point me to how 2nd boot is supposed to work, I would be very thankful.
Click to expand...
Click to collapse
2nd-boot is similar to how 2nd-init works where it uses a hijack to and it boots the custom kernel on top of the Motorola Stock kernel. It basically consists of a miniature bootloader to execute 2nd-boot. Can please upload what you have so far? I can help you to debug it. Thanks.
more progress
I am able to make a booting system, using code at:
https://github.com/de-wolff/android_device_motorola_xt320
I produced images and kernel:
http://dewolff.home.xs4all.nl/system.tar.gz
http://dewolff.home.xs4all.nl/kernel
http://dewolff.home.xs4all.nl/recovery.img
http://dewolff.home.xs4all.nl/boot.img
It boots (using fastboot), display working, touchscreen working, onscreen keyboard working.
I am convinced the kernel is complete, but I have still to create a correct camera.lib, and correct audio libs.
Also the gpu is not used (yet), but that is a matter of finding the right egl adreno libraries, and creating the correct libgsl.
If anyone wants to explore it: In system/lib/egl is egl.cfg.
This is a text file. When you remove the # on the second line, after reboot the system will try to use the adreno gpu.
The way to put system on the phone is extract on your system (eg using) remove all files in the existing system, create all directories on the system, and then transfer all files using adb push.
de-wolff said:
I am able to make a booting system, using code at:
https://github.com/de-wolff/android_device_motorola_xt320
I produced images and kernel:
http://dewolff.home.xs4all.nl/system.tar.gz
http://dewolff.home.xs4all.nl/kernel
http://dewolff.home.xs4all.nl/recovery.img
http://dewolff.home.xs4all.nl/boot.img
It boots (using fastboot), display working, touchscreen working, onscreen keyboard working.
I am convinced the kernel is complete, but I have still to create a correct camera.lib, and correct audio libs.
Also the gpu is not used (yet), but that is a matter of finding the right egl adreno libraries, and creating the correct libgsl.
If anyone wants to explore it: In system/lib/egl is egl.cfg.
This is a text file. When you remove the # on the second line, after reboot the system will try to use the adreno gpu.
The way to put system on the phone is extract on your system (eg using) remove all files in the existing system, create all directories on the system, and then transfer all files using adb push.
Click to expand...
Click to collapse
Use the Adreno Libs from the Qualcomm website. Is Hardware Acceleration working? How come it's saying its CM7 in the Github
@MauroSZ This is the instructions on how to install the custom ROM.
Use these commands in cmd
Code:
fastboot erase system
Code:
fastboot -w
Code:
fastboot boot recovery.img
Now mount /system
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
Code:
exit
Code:
adb push system.tar.gz /sdcard
Code:
adb shell
Code:
cd /system
Code:
busybox tar xvzpf /sdcard/system.tar.gz
Code:
exit
Code:
adb reboot-bootloader
Code:
fastboot boot boot.img
And you will boot into the custom ROM.
EDIT: Custom ROM is not BOOTING
@Guitwo2 @Bernd.Defy @wilberfish and @junk031 There is a custom ROM for Defy Mini by @de-wolff
Read the previous post for installation instructions.
@de-wolff, I'm getting a blue screen, is that how it boots up?
Going to try this later. Sounds great!
Sent from my HTC Desire C using xda app-developers app
rootdefyxt320 said:
I'm getting a blue screen, is that how it boots up?
Click to expand...
Click to collapse
No, this is when you use a normal boot (with old kernel)
At this moment you have to boot using fastboot:
$fastboot boot boot.img
When I have everything more working, and the rom is smaller (at this moment it is 136M and the gapps are not even installed on it.) I will try to implement 2ndboot in the rom,
And I will also create a more user friendly way to install it.
de-wolff said:
No, this is when you use a normal boot (with old kernel)
At this moment you have to boot using fastboot:
$fastboot boot boot.img
When I have everything more working, and the rom is smaller (at this moment it is 136M and the gapps are not even installed on it.) I will try to implement 2ndboot in the rom,
And I will also create a more user friendly way to install it.
Click to expand...
Click to collapse
Contact @Hashcode to port 2nd-boot to our device. Upload our stock init.rc and he will find a 2nd-init hijack. Once, we have the hijack, we can boot into 2nd-boot. So I extracted system.tar.gz and adb pushed all the files to it and already did a fastboot boot boot.img to the phone and it gives me a blue screen. I already formatted /system how come I keep getting running out of space. Please give us a tutorial on how to install CyanogenMod to our phone. Just adjust the updater-scripts for gapps so that it flashes it to /flex and symlink it to /flex/app and /flex/lib.
rootdefyxt320 said:
Contact @Hashcode to port 2nd-boot to our device. Upload our stock init.rc and he will find a 2nd-init hijack. Once, we have the hijack, we can boot into 2nd-boot. So I extracted system.tar.gz and adb pushed all the files to it and already did a fastboot boot boot.img to the phone and it gives me a blue screen. I already formatted /system how come I keep getting running out of space. Please give us a tutorial on how to install CyanogenMod to our phone. Just adjust the updater-scripts for gapps so that it flashes it to /flex and symlink it to /flex/app and /flex/lib.
Click to expand...
Click to collapse
Thanks for your suggestions.
There is a lot to do, and it is a hobby project, so I will do those things one at a time. But when there is progress, I will keep you informed.
Maybe your problem is you are using windows?
(In that case symlinks will be expanded to the whole file)
But there is an alternative way:
Boot into fastboot and do:
Code:
fastboot boot recovery.img
adb shell 'mount -a'
adb shell 'rm -rf /system'
adb push system.tar.gz /sdcard/
adb shell 'tar -xzvf /sdcard/system.tar.gz'
adb reboot-bootloader
fastboot boot boot.img
de-wolff said:
Thanks for your suggestions.
There is a lot to do, and it is a hobby project, so I will do those things one at a time. But when there is progress, I will keep you informed.
Maybe your problem is you are using windows?
(In that case symlinks will be expanded to the whole file)
But there is an alternative way:
Boot into fastboot and do:
Code:
fastboot boot recovery.img
adb shell 'mount -a'
adb shell 'rm -rf /system'
adb push system.tar.gz /sdcard/
adb shell 'tar -xzvf /sdcard/system.tar.gz'
adb reboot-bootloader
fastboot boot boot.img
Click to expand...
Click to collapse
Bugs are Hardware Acceleration but I'm going to try the Qualcomm ICS ARMv7 Libs, wrong DPI, no settings. I will send my logcat and dmesg later.
EDIT: When I try to run a OpenGLES2.0 benchmarks, it crashes. Basically for now it's only a bootup. I suggest you to contact @cute_prince to help you to port CyanogenMod as he has ported it to HTC Pico (Explorer). Also another suggestion is that you use the codename of the Defy Mini which is Tinboost to compile CyanogenMod.
You guys are really amazing!, it won't surprise me that all the information, tutorials and videos all around the web came from all the experiments you made here. Thanks for all the time you spend, and go on guys!
Waiting for the ICS upgrade.
@cute_prince. Would you please help us to port CyanogenMod 9 to our device? As the Defy Mini has the same chipset as the HTC Explorer. I will provide whatever you need to port CM9. Thanks.
So is there a possibility of CyanogenMod on our device?
Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone
According to some people, this bug should be fixed now.
Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!
Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?
Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.