Can you let us know the details:
1- Which android version you used
2- Which zImage version you used
3- What is you startup.txt like
4- Did you manage to solve it? and how?
This is a survey after finding out alot of people are having this problem and so far it is hard to pinpoint what the exact problem is.
If we can share our info together I am sure we can get to the bottom of it.
Thanks
1- I've tried Froyostone (sense and clean) latest builds from 7 Aug 2010
2- zImage from 14 Aug 2010
3- Startup as follows:
set mtype 2524
set ramaddr 0x18000000
set ramsize 0x0fc00000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
also tried
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1E400000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
also tried to replace cmdline by adding "rel_path=Android" and changing boot to bootlinux
Formatting SD always before re-trying
4- Still no solution, after Jumping to Kernel i get black screen or just freeze and nothing happens. Have to remove battery to reboot.
the details:
1- All latest built version with fullram zImage
2- kernel: darkstone 2.6.32.9 #35 (freeze)
Kernel: huanyu 2.6.32.9 #4 (sometime can work on first time after format SD)
Kernel: manusfreedom 2.6.32.9 #74 (shown rebooting in 5 second)
Kernel: ElBartoME 2.6.32.9#11 (freeze)
3- I am sure all version has correct startup.txt and add "rel_path=Android" in cmdline such as below:
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=Android"
boot
4- I have tried difference radio / rom but still no solution for me, but I only can use back old build version with Kernel: Cotulla 2.6.32.9 #103 (mattc Leo 1.4 / shubCRAFT 1.1)
I can only run these perfectly
PB81100 HX-BC
Radio 2.12.50.02
Laterest EnergyROM 23129
Hope someone can help me
Thanks
I only have this problem, when a .51 (European Radio) is installed (Non-TMO-US Version). With a .50 (U.S. Radio), booting the Kernel just works fine.
Solved
The rom update solved my issues too. Just used the latesd one and no more problems starting!
Thanx for your help!
Yep seems the ROM update to .50 solves this issue that most of the people are having!
Here you find all info on how to change your ROM version: http://forum.xda-developers.com/showthread.php?t=609477
i have .50 but i still get jumping to kernel. but just with the new coredroid build...
Jumping to Kernel
Dear All,
Still No Solution about this problem.
Trying all solution nothing success.
Any suggestion ?
Thanks.
Regards,
Arifin
what works for me
Always delete cache and data folder not the data file when switching Kernel, Rom or anything else. Android should run after this.
cw-data said:
I only have this problem, when a .51 (European Radio) is installed (Non-TMO-US Version). With a .50 (U.S. Radio), booting the Kernel just works fine.
Click to expand...
Click to collapse
this made the fix for me. updated radio to .50
Related
Hi, guys.
You can see that they are porting Android OS for others device using HaRET. I want that it will be for our devices too.
I read about HaRET and tried run HaRET with haretconsole on my device. But I found out that HaRET don't support our device yet. If you have HaRET source code, open file mach-types.h under folder include, you can see there many supported device but not Iolite or open the page
I sent an email to ask about support but nothing isn't now. If someone know how to do please tell me what i have to do?
Hope that Android OS will be ported for our device in the recent day.
Best regard!
woooow let's hope...
HaRET works on my Iolite. But I' a new user and not allowed to post links.
1u21 said:
HaRET works on my Iolite. But I' a new user and not allowed to post links.
Click to expand...
Click to collapse
How do it work?
Yeah, it run but we can't deploy device with it. For example when you run command watch GPIOS (through haretconsole), nothing will be appear
It works, but not really stable. Sometimes ist freezes and some functions don't work like bluetooth. You can send and receive SMS, make some phone calls and go online via WLAN. I don't know, if UMTS is running.
I'm still waiting for a Mod to unlock my account.
But it uses a huge amount of energy.
1u21 said:
It works, but not really stable. Sometimes ist freezes and some functions don't work like bluetooth. You can send and receive SMS, make some phone calls and go online via WLAN. I don't know, if UMTS is running.
I'm still waiting for a Mod to unlock my account.
But it uses a huge amount of energy.
Click to expand...
Click to collapse
Can you send me link via email [email protected], please?
Thanks in advance.
It could be this - kandroid dot org
No. I'm using not the korean version.
Android 2.0 is running on the Iolite, but too unstable. You can't use is it in anyway.
Did you have try it ?
Yes. It fills the whole 256 data.img with software. But the bigger problem is the necessary of a fast CPU. Everything runs slow and is more unstable. The Tattoo is not a similar phone to the Iolite.
I just found my problem. You should use HaRET version 0.5.1 (newest version is 0.5.2).
But I still can't make Android boot. Some changes in zImage are needed?
Android started with an unmodified zImage on my Iolite. But I have some new problems with Android and no time for solving.
Maybe the CPU is to slow for Android.
Can we have a link for the file?
dancer_69 said:
Can we have a link for the file?
Click to expand...
Click to collapse
Here is all versions of HaRET
http://www.handhelds.org/~koconnor/haret/
Click to expand...
Click to collapse
Sorry, I mean a link for android image, and the parameters of default.txt to be able to boot it with haret.
I already know where to find haret
I need it too, please, can you post the link?
Here is it:
http://www.androidonhtc.com/polaris/install
Well, we still need the contents of the "Default.txt" to boot the android image....
Use the normal default.txt and make some changes. Here is my default.txt
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1723
set KERNEL zImage3
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Hitachi 2=Topoly 3=Samsung
# mddi_client_vogue.vsync - Use hardware vsync, default is 1 but should be 0 if
# panel_type is 0
#
set cmdline "board-htckaiser.panel_type=2 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 lcd.density=120 no_console_suspend clock-7x00.mddi=0xa51 clock-7x00.ahb_div=2 clock-7x00.slow=1 clock-7x00.voltage=1 "
boot
Click to expand...
Click to collapse
I'm also using the new version of Android, which you can find on the same page. It works better, but you can feel the difference between 400Mhz and 528Mhz.
First this is a patch and not a fix for real mac address.
I have added new cmdline parameter 'wifi.mac_address' which enables you to set any mac address of the wifi interface. So to set a different mac address you need to add new parameter to your startup.txt:
Code:
[STRIKE]set cmdline "wifi.mac_address=00:11:22:33:44:55"[/STRIKE]
I have attached zip file with new zImage and wifi modules for testing purposes. Kernel is based on hastarin sources from Mon Oct 18 17:30:15 2010.
Backup your settings before you test the new zimage and modules.
To discover your mac address in windows look in the following thread:
h__p://forum.xda-developers.com/showthread.php?t=587705&highlight=mac+address
UPDATE: I have made a new patch for the same problem (new files attached). New kernel is based on hastarin sources from Tue Oct 26 22:18:43 2010.
Thanks to clio94 for showing me anther way to change mac address.
UPDATE2: Thanks to OSM for sharing his code for changing bluetooth mac address i have made new patch (and zImage for testing). I have added new parameter "bt.mac" for changing the bt mac address and renamed parameter for changing wifi mac address to "wif.mac" (because is simpler and parameter with the same name is used in michyprima r11 kernel). So for changing the mac address of wifi and bt cmdline looks like this:
Code:
set cmdline "bt.mac=00:11:22:33:44:55 wifi.mac=00:12:23:34:45:56"
If you are using desire HD builds and the patch it's not working you can try method described in:
http://forum.xda-developers.com/showpost.php?p=9806811&postcount=17
mdebeljuh said:
First this is a patch and not a fix for real mac address.
I have added new cmdline parameter 'wifi.mac_address' which enables you to set any mac address of the wifi interface. So to set a different mac address you need to add new parameter to your startup.txt:
Code:
set cmdline "wifi.mac_address=00:11:22:33:44:55"
I have attached zip file with new zImage and wifi modules for testing purposes. Kernel is based on hastarin sources from Mon Oct 18 17:30:15 2010.
Backup your settings before you test the new zimage and modules.
To discover your mac address in windows look in the following thread:
h__p://forum.xda-developers.com/showthread.php?t=587705&highlight=mac+address
Click to expand...
Click to collapse
Nice one, I hope they merge this into the master.
Thanks!
Until they get the NAND code working to read the real MAC address this will do nicely. I'll add it to my next kernel.
Virtual Dynamic MAC Address
this is awesome , i love it .
Virtual Dynamic MAC Address , this is exactly what i was looking for
greaaaaaaaaaaaaaaaaaat job
Long time waiting this feature.
Now hastarin r7.7 also add this feature.
Do you know michyprima R11 used "wifi.mac"
now hastarin r7.7 use "wifi.mac_address"
differenent property name.
Simply awsome !!!!! Been waiting for a fix for the mac issue
setting up
thanks very much. it solved a big problem.
Great job
Help
Ho do you patch the 'patch file' within the zip file?
Thank you in advance.
You need to have kernel sources.You copy the patch in to kernel folder and you give
patch -p1 < /path_to_patch/0001-Patch-for-wifi-mac-address-and-bt-mac-address.patch
Thanks. This is now included in my r8 kernel.
In desire hd build works only the first patch with "wifi.mac_address=00:11:22:33:44:55"
Τhe second version for some reason cannot change the wifi mac address.
Good tip
I have spend hours to understand why i could not connect anymore on my wifi supplier and the solution was just there I put my original winmo mac on the command line and it connects. Thanks a lot.
Thanks a lot for this patch, I have been using it in kernels that it is compiled with. I am going to learn to compile my own kernel soon and will be using it
Just a quick note that for some reason this isn't working in the build I'm now using.
I see that it gets executed but the driver doesn't use it:
Code:
<5>[ 0.000000] Kernel command line: rel_path=desire_hd2 nand_boot=0 wifi.mac=00:23:76:AF:B4:7F
<4>[ 0.000000] htcleo_macaddress_setup: cmdline mac config=00:23:76:AF:B4:7F | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 0.000000] htcleo_macaddress_setup parsed macaddr=macaddr=00:23:76:AF:B4:7F
<4>[ 0.000000] | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 0.000000] htcleo_macaddress_setup parsed mac_address= 0:23:76:af:b4:7f | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 130.232330] wlan: eth0: Broadcom Dongle Host Driver mac=00:11:22:33:44:55
I even changed the default in the code (board-htcleo-wifi-nvs) but it's presumably not getting it from there now. :S
I doesn't get this working, have MDJ FroYo HD v.4.4 KERNEL: hastarin r8.5.3
RADIO: 2.15.50.14, how do i get my wifi working?!
UPDATE, replaced the *.ko files and wifi is working like a charm! Thx for fix.
Bartjuh_4 said:
I doesn't get this working, have MDJ FroYo HD v.4.4 KERNEL: hastarin r8.5.3
RADIO: 2.15.50.14, how do i get my wifi working?!
UPDATE, replaced the *.ko files and wifi is working like a charm! Thx for fix.
Click to expand...
Click to collapse
What ko files did you change?
thanks
Desire HD Builds workaround
Hi,
it seems that the Desire HD builds are using /etc/calibration instead of /proc/calibration file to get its params.
It could be that the module is loaded with module param nvram_path = /etc/calibration
in addition each time the wifi device is turned off/on, the calibration file is copied from /system/etc/calibration to /etc/calibration.
In case the MAC address param is fixed in the /system/etc/calibration every thing will work fine.
Possible fixes (as I see it, but not sure yet how to do it):
1. during system init, delete /system/etc/calibration and create a link to /proc/calibration.
1. during system init, edit the /system/etc/calibration and change the MAC address based on the cmdline.
hope this is helpful.
OSM said:
Hi,
it seems that the Desire HD builds are using /etc/calibration instead of /proc/calibration file to get its params.
Click to expand...
Click to collapse
Thanks. I'd hit the button but on my phone atm
That will be very handy. I can modify my init.kernel.sh to also update /etc/calibration from /proc/calibration or the update script to delete the file and create a symlink.
I'll definitely sort something out before releasing my next kernel update.
Sent from my HTC HD2
hastarin said:
Thanks. I'd hit the button but on my phone atm
That will be very handy. I can modify my init.kernel.sh to also update /etc/calibration from /proc/calibration or the update script to delete the file and create a symlink.
I'll definitely sort something out before releasing my next kernel update.
Sent from my HTC HD2
Click to expand...
Click to collapse
I think you should update the /system/etc/calibration, and not the /etc/calibration.
it seems that each time the wifi is enabled, the /system/etc/calibration is copied to the /etc/calibration.
ofcource you can simple copy the /proc/calibration to the /system/etc/calibration
OSM said:
I think you should update the /system/etc/calibration, and not the /etc/calibration.
it seems that each time the wifi is enabled, the /system/etc/calibration is copied to the /etc/calibration.
ofcource you can simple copy the /proc/calibration to the /system/etc/calibration
Click to expand...
Click to collapse
Thanks I've had a quick look and there are various differences between the proc and etc files, so I may start out by just updating the macaddr via the init script.
I downloaded the cab xdandroid from here http://forum.xda-developers.com/showthread.php?t=627997 and use this as STARTUP:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 board-htcrhodium.is_cdma=1 msmvkeyb_toggle=off pmem.extra=1 rel_path=andboot force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 physkeyboard=rhod400"
boot
Now it starts and gets stuck at the internet browser saying to update "Launcher Pro" but it has no wifi or internet. How can I solve this? What do I have to do?
Should we guess at the model of phone/rhodium you have? Is it GSM CMDA?
Davidtjuh said:
Now it starts and gets stuck at the internet browser saying to update "Launcher Pro" but it has no wifi or internet. How can I solve this? What do I have to do?
Click to expand...
Click to collapse
Based on your startup.txt, I'd guess RHOD400, CDMA.
But that's not the problem - I'd hazard a guess that you downloaded the BLAZN version from Sept.28... that version is very oudated, I would recommend using FRX04 AKA "Reference". Don't get the CAB either, just extract the RAR (or ZIP, can't remember... the compressed file ) to the root of your SD and go. No CAB mess.
Sorry for the unclear explanation.
I have this HTC TP2: http://regmedia.co.uk/2009/06/22/htc_touch_pro2_3.jpg
on the Android Startup Menu it is the Rhod100 UK, but I doubt it's that version.
I have the Energy Blue Glass Rom something 6.5, I will look it up asap..
I just can't get out of the webbrowser to setup my wifi, it stays on "No Service", it's the Blazn indeed. Ill try the reference.
Yea for some reason the version of launcher pro is out of date so you cant return to home they should add another home or include the stock one just in-case but the OC makes its really fast.
you could always update launcher pro too, thats what i did
noodles21o2 said:
you could always update launcher pro too, thats what i did
Click to expand...
Click to collapse
I don't have any wifi or mobile internet my phone won't connect
DroidFreek said:
I don't have any wifi or mobile internet my phone won't connect
Click to expand...
Click to collapse
Use reference build, as I mentioned above...
By the picture you posted of your phone, it is a rhod100.
If so (you can see it underneath your battery), you need to change the board line to =0 and force_cdma to 0. Also you need to change keyboard to rhod100_uk. If your wifi still doesn't work, try to find the wifi fix.
Greetz,
Steyn
Here is the altered startup:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 board-htcrhodium.is_cdma=0 msmvkeyb_toggle=off pmem.extra=1 rel_path=andboot force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 physkeyboard=rhod100_uk"
boot
Hope this helps you
Also, wifi fix:
This will fix your problem. Find your MAC ADDRESS on your phone and write it in the WIFI-NVRAM.TXT then place the WIFI-NVRAM.TXT in the root of your storage card. Now replace your FROYO.USER.CONF with the one in this zip. The FROYO.USER.CONF is in this folder ANDBOOT/CONF. Now boot android and you'll have wifi working.
www.4shared.com/file/UXS_y76U/WIFI-NVRAM.html
Greetz (again)
Steyn
I've been trying for thee past couple of hours to get Haret to work, to no avail.
Whenever I click on Haret, it will go into the process:
Haret: Booting Linux...
And load through that screen. Once it finishes that though, it just freezes. Notification LED still works if I had something beforehand. It won't vibrate twice like it normally does when normally booting Linux. To my knowledge I haven't changed anything at all. I'll post my startup.txt incase that might be the problem
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2"
boot
Do you have all of the files in the andboot folder at the root of your SD card?
You have some strange options in there, but nothing that would prevent booting.
I have highlighted the commands you should remove in red/bold (deprecated).
I have also highlighted some in blue/bold - no reason to have 'em if they're set to 0. Plus, hw3d is on whether you turn it on or off in the startup.txt IIRC.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 [/B][/color]msmvkeyb_toggle=off [B][color=red]pmem.extra=1[/color] [/B]gsensor_axis=2,1,3 rel_path=andboot [B][color=blue]north_am_dialing=0 force_cdma=0 hw3d.force=0[/color][/B] physkeyboard=tilt2"
boot
What build are you using? You should post in that build's thread instead of creating a new thread - thanks!
arrrghhh said:
You have some strange options in there, but nothing that would prevent booting.
I have highlighted the commands you should remove in red/bold (deprecated).
I have also highlighted some in blue/bold - no reason to have 'em if they're set to 0. Plus, hw3d is on whether you turn it on or off in the startup.txt IIRC.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 [/B][/color]msmvkeyb_toggle=off [B][color=red]pmem.extra=1[/color] [/B]gsensor_axis=2,1,3 rel_path=andboot [B][color=blue]north_am_dialing=0 force_cdma=0 hw3d.force=0[/color][/B] physkeyboard=tilt2"
boot
What build are you using? You should post in that build's thread instead of creating a new thread - thanks!
Click to expand...
Click to collapse
I always forget to mention that XD
I am using FRX05 if that helps in any way.
QuentinX5 said:
I always forget to mention that XD
I am using FRX05 if that helps in any way.
Click to expand...
Click to collapse
Try what I have suggested.
Post in the build thread please .
I had this same problem before but I think it was due to a corrupted build . . . . . I forget exactly how I fixed the problem but first id recopy Haret to the sd as if had it corrupt before.
Next make sure you have the right kernal where it should be, pay particular attention to the 'zimage' file.
Do you use an Overclock on Win-Mo?
Having the same problem with the march 11 kernal.
Files are on the root folder. Simple startup file. No overclock in win-mo or android.
I'll try reformating with HP format tool again and re-load the files.
Whats does it take to port a 1.1BL ROM to 1.2BL? I want to start working on my own ROM and want to use an existing 1.1 ROM as a base, but want to stay on 1.2. I hope this isn't too difficult.
What flavour of ROM? Froyo/GB/HC?
Assuming you already have a flavour in mind, only the kernel changes between 1.1 and 1.2 for each type (the kernel used in the recovery image will also, of course, need to change). You will have to compile a kernel for each version of the bootloader.
This is the config file for an pershoot Android kernel which will be loaded by a 1.1 bootloader:
pershoot_tegra_harmony_android_defconfig
And this is for a kernel loaded by a 1.2 bootloader:
pershoot_tegra_harmony_android-newbl_defconfig
What's the difference between the two?
Code:
$ [B]diff -u pershoot_tegra_harmony_android_defconfig pershoot_tegra_harmony_android-newbl_defconfig[/B]
--- pershoot_tegra_harmony_android_defconfig 2011-09-12 23:55:56.273108334 +0530
+++ pershoot_tegra_harmony_android-newbl_defconfig 2011-09-12 23:55:46.973108334 +0530
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.46
-# Wed Aug 31 13:11:33 2011
+# Wed Aug 31 13:12:20 2011
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -252,7 +252,7 @@
CONFIG_TEGRA_ODM_HARMONY=y
# CONFIG_TEGRA_ODM_VENTANA is not set
# CONFIG_TEGRA_ODM_WHISTLER is not set
-# CONFIG_NEWBL is not set
+CONFIG_NEWBL=y
#
# Processor Type
CONFIG_NEWBL is set for 1.2 kernels.
Cool thanks. I am planning on doing a GB ROM, based off the original Vanilla AOSP ROM. Probably nothing public, unless I think it is really good.
Still having a problem with this. I have unpacked the boot.img and re-packed with 1.2 kernels from both clemsyn and pershoot. I have also taken the wifi drivers and added them to the system folder for deployment with the ROM and set the permissions in the updater-script. ROM flashes fine, but gets the the first Android screen and just sits. Not sure what else i am doing wrong.
Obvious queston is: Is the bootloader 1.2 or 1.1?
Next: When you say 1st Android screen, is the
a) the VS birds (boot bitmap)
b) the Android logo (or plain white letters) which appears after that (/initlogo.rle)
c) the boot animation (bootanimation.zip)
Hanging at each stage is indicative of different sorts of problems.
You could also talk to gojimi, tjohnsonjr or craigacgomez here. All have AOSP based ROMs that run on 1.2.
It is b. The plain text Android logo.
markmac said:
It is b. The plain text Android logo.
Click to expand...
Click to collapse
That means that the kernel booted and was able to run /init OK. /init produces that Android logo in the absence of an /initlogo.rle file. This also means that you may be able to attach adb and look at log messages to find out what the problem is.
Thanks. I am not very familiar with adb yet, so i guess its time to learn.