Related
I'm really sorry to be starting a new thread, but I've been racking my brains over this problem and haven't got anywhere yet. I know it's not the application so it must be something I've done, just not sure what!
Until today I have been able to use the BuildOS.exe in both Pandora and Core's kitchens without problem. Haven't tried using it for a few weeks, but with the new OS build today tried Pandora. Unfortunately, when I try to open BuildOS, it reports it has encountered a problem and needs to close. It offers the choice of reporting to Microsoft or not (reporting produces no suggested fixes).
Have uninstalled .NET Framework 3, 2, 1.1 and 1 and then re-installed them from Microsoft Update but at each stage the error message has been the same. I've also tried Googling for problems with BuildOS, but each just suggests installing .NET Framework 2. Searching for the error message codes didn't producing anything either.
I'm attaching the first screen of the error message but cannot work out how to copy and paste the actual error (it's unselectable).
If anyone has any ideas at all, I'd really appreciate them as I'm out. Thanks for reading this post and please don't flame unless they're REALLY funny!
The attachment doesnt really give much information..
Try print-screening the error and paste it into paint then cut out just the error and post it.. though im guessing it just says something lke unhandled exception or something like that..
You can also try looking around the system error logs in Control Panel\Administrative Tools\Event Log where you might find some details of the error.
have you installed or uninstalled anything in those few weeks?
the only thing I get from that log file is the mscorelib - .NET Framework...
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...
Step by step
Lets try to isolate the problem:
Step 1: Try to use an older version of pandora, if its working something is wrong with your download of the latest version.
Step 2: You said that you haven't use the kitchen for some weeks. What have you installed and/or deinstalled since the last use of the kitchen? Maybe another program on your desktop computer is in conflict with .net or the kitchen.
Problem located, just got to fix it now!
Thanks for the suggestions guys, should've thought of the event viewer myself! D'oh!
The report viewer shows the problem is in my .NET 2 installation, so at least I know where to concentrate now.
Time for the big stick with the nail in it, I think!
Thanks again Sam and matt. I know you're both very busy and really do appreciate you taking the time to help.
EDIT: Sorry Gerald, your post showed up while I was typing. Thank you very much for the suggestion and bringing me back to sanity! Will try an older version first, just in case, and then going to play around with my .NET installations.
mattk_r said:
Maybe try MS .NET Compact FW? I have 1.0 SP3 and 2.0 SP1...
Click to expand...
Click to collapse
Uhh, in my world .NET CF runs on a device.
The problem continues...
Bugger - tried a shortcut and it didn't work! Copied the Pandora setup files and installed them on my laptop, only for that to come up with the same error message!
The laptop has very little installed on it and has only been up and running from a fresh install for two weeks. I've got basic drivers, AVG Anti-virus, Spybot and MS Office 2003 installed and that's about it. It's also completely up to date on MS Updates (I'm anal like that) so has .NETs up to 3.0 installed.
I also tried downloading Core's kitchen onto the laptop but again the BuildOS in that reports the same error.
The error shows under Event Viewer > Application as:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 14/08/2007
Time: 21:07:36
User: N/A
Computer: MINI-LAPTOP
Description:
EventType clr20r3, P1 buildos.exe, P2 0.0.0.0, P3 45fef3bf, P4 mscorlib, P5 2.0.0.0, P6 461eee3d, P7 331e, P8 119, P9 system.io.directorynotfound, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 62 00 75 00 69 00 .b.u.i.
0018: 6c 00 64 00 6f 00 73 00 l.d.o.s.
0020: 2e 00 65 00 78 00 65 00 ..e.x.e.
0028: 2c 00 20 00 30 00 2e 00 ,. .0...
0030: 30 00 2e 00 30 00 2e 00 0...0...
0038: 30 00 2c 00 20 00 34 00 0.,. .4.
0040: 35 00 66 00 65 00 66 00 5.f.e.f.
0048: 33 00 62 00 66 00 2c 00 3.b.f.,.
0050: 20 00 6d 00 73 00 63 00 .m.s.c.
0058: 6f 00 72 00 6c 00 69 00 o.r.l.i.
0060: 62 00 2c 00 20 00 32 00 b.,. .2.
0068: 2e 00 30 00 2e 00 30 00 ..0...0.
0070: 2e 00 30 00 2c 00 20 00 ..0.,. .
0078: 34 00 36 00 31 00 65 00 4.6.1.e.
0080: 65 00 65 00 33 00 64 00 e.e.3.d.
0088: 2c 00 20 00 33 00 33 00 ,. .3.3.
0090: 31 00 65 00 2c 00 20 00 1.e.,. .
0098: 31 00 31 00 39 00 2c 00 1.1.9.,.
00a0: 20 00 73 00 79 00 73 00 .s.y.s.
00a8: 74 00 65 00 6d 00 2e 00 t.e.m...
00b0: 69 00 6f 00 2e 00 64 00 i.o...d.
00b8: 69 00 72 00 65 00 63 00 i.r.e.c.
00c0: 74 00 6f 00 72 00 79 00 t.o.r.y.
00c8: 6e 00 6f 00 74 00 66 00 n.o.t.f.
00d0: 6f 00 75 00 6e 00 64 00 o.u.n.d.
00d8: 20 00 4e 00 49 00 4c 00 .N.I.L.
00e0: 0d 00 0a 00 ....
I know this now definitely isn't a WM6 problem but I'm adding this info in case one of the great XDA Dev minds knows the solution, and in case another user like me experiences the same problem - you're not alone and I'll update the thread when I find the solution!
Here's a stab at it (albeit a simple one). When using Pandora, do you have everything in the proper folder structure? The following applies:
(in this example, everything is thrown into a main folder "Pandora")
- Pandora (parent folder)
- BuildOS.exe (file)
- CreateROM.bat (file)
- pkgcommon.dll (file)
- OEM (sub folder)
- ROM (sub folder)
- SYS (sub folder)
- TOOLS (sub folder)
If you don't follow this hierarchy, Windows will shoot an error out at you.
Good luck!
Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.
You run buildOS from the command line, make sure you cd to the folder containing OEM/SYS/ROM and TOOLS .... THEN run buildOS from wherever it is by typing the full path into cmd, or even better add buildOS to the PATH variable .
so you need to follow this kind of procedure:
Code:
cd c:\ROMFOLDER (ENTER)
then...
c:\ROMTOOLSFOLDER\BuildOS (ENTER)
remember ROMFOLDER and ROMTOOLSFOLDER should be replaced by the paths you use.....its a PITA but thats how it runs.
Confused Stu said:
Thanks Taurus, good suggestion. I've also got an inconsequential Readme.txt file in there too, but other than that - all present and correct!
Again, thanks for all your suggestions guys and once I find the solution I'll be sure to post it up.
Click to expand...
Click to collapse
No problem. I just wanted to clarify what I meant, as I don't know if I was that clear.
I've attached a shot of everything the way it should look. Anyhow, it sounds like you have it right already, but I thought I'd just float that your way.
vp3G said:
Uhh, in my world .NET CF runs on a device.
Click to expand...
Click to collapse
It gets installed with VS Team Suite 2k5, probably since it has the CE mobile device emulators included.
Confused Stu - if you're still having trouble with .NET, let me know. I supported this stuff for M$, and know a few tricks to getting it cleaned up and installed.
Only common factor - interface between keyboard and chair!
OK, I've spent this evening wiping and rebuilding my laptop. It's got XP SP2 on it, then added the laptop drivers, the Kitchen and ran all the Microsoft Updates until only the .NETs were left.
Tried running BuildOS with no .NETs installed, and it came up with a message telling me the application wasn't in the correct state and re-installing it might help.
Installed .NET 1 (same message on trying to open BuildOS), then installed the updates for .NET 1 - same message. Installed .NET 2 and immediately got the original error I was getting on my home PC and other laptop! Went on to install the updates for .NET 2 and finally .NET 3 - but the same error kept coming up.
I've now got this same error coming up my Home PC (self-built), my Dell laptop, and my newly rebuilt Medion one! I've got no common files besides the MS Updates and no common components. Beginning to think maybe it's just plain personal!
Matt - if you can help at all with my .NET problems, I'd be ridiculously grateful. Alternatively, if anyone can suggest another avenue I can try please post it up - I'm almost out of ideas!
I've got another fresh install going on at work (Dell desktop this time) so tomorrow I'm going to try installing only .NET 1 and .NET 2 - not even any other MS Updates. Then if i install the updates one at a time I might be able to work out the problem one. Still not sure why I'm the only person affected by this though?
First of all, you are not alone, have a look at:
http://www.google.at/search?hl=de&q...time+2.0+Error+Reporting+Event+ID:+5000&meta=
Now for the bad news: I checked the first ten posts or so, they recommend to debug the code. But as its running on other machines without any problems it must be something within your .net installion.
man, this is strange.
I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).
FIXED!!!!
Allan1 - you're a star!!!!
I've just deleted out the OEM (and SYS) folders, unzipped the v6 kitchen again and it's worked perfectly! Looks like my problem was I was unzipping the v6.1 (beta) OEM over the top of the existing OEM and that was causing my problems.
Don't I feel like a complete doughnut!
Sorry for wasting everyone's time, and THANK YOU very, very, very much for everyone's help and suggestions on this. It's really touching that so many people were willing to try to help me out.
Now commence the "what an idiot" flaming if anyone wants to - it's justified!
No probs!!
allan1 said:
I had a similar problem with BuildOS but with me it happened anytime I tried to add a package to the OEM folder.
Have you made any changes to anything from the Kitchen?
Matt said that you can't just add a package because its signed ( or something).
Click to expand...
Click to collapse
good looking out...just encountered this problem in HYPERCORE....driving me insane why it wasn't working cuz I just built 3 .nb's in the last few hours.
thanks alot
In 850_gax_sd.bin (ENG 4.15 version)
address 0x038C118F
30 34 30 34 00 FF FF FF FF FF FF FF 31 39 C7 63
control for GSM.BIN but this not CRC32, Adler32 or CHECKSUM(32)
What is this ??????
M10 and A10 have such similar hardware, hopefully, the A10's ROM would be an ideal candidate for dual booting android in M10.
Anyone who has the same thoughts?
If someone could get the A10 ROM, I can try creating a kitchen and an android ROM for M10. I am no expert, but I think my linux knowledge should help.
can this help?
kindly google for software update of A10. i was not allowed to post the link.
i am new to windows mobile but i will certainly like too see android on m10.
these are my 2 cents
hope this helps.
http://www.garminasus.com/zh_TW/support/a10-updates.html
Thanks guys. The update link gave me a ext2fs file system image. Which after unpacking has 4 files:
1. 512_A10_PACKAGE.raw (probably the most iteresting part, 284MB)
2. system_version.sig
3. 512_A10_PACKAGE.raw.sig
4. system_version
I am still trying to dig and figure out what the raw file is. All comments and tips are welcome.
I hope you succeed
http://forum.xda-developers.com/showthread.php?t=455648
Really looking forward to run android on my M10, it will be super cool!
Here is a hex dump of the first few kbs of the raw file:
00000000 50 61 63 6b 61 67 65 20 6f 66 20 53 44 20 44 6f |Package of SD Do|
00000010 77 6e 6c 6f 61 64 00 ff ff ff ff ff ff ff ff ff |wnload..........|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000040 4d 6f 6e 20 4f 63 74 20 31 38 20 31 34 3a 31 39 |Mon Oct 18 14:19|
00000050 3a 30 37 20 32 30 31 30 0a 00 ff ff ff ff ff ff |:07 2010........|
00000060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000080 0a 00 00 00 b0 ed 5b 1c ff ff ff ff ff ff ff ff |......[.........|
00000090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000001f0 70 61 72 74 69 74 69 6f 6e 2e 6d 62 6e 00 ff ff |partition.mbn...|
00000200 ff ff ff ff ff ff ff ff 00 04 00 00 d0 01 00 00 |................|
00000210 71 63 73 62 6c 68 64 5f 63 66 67 64 61 74 61 2e |qcsblhd_cfgdata.|
00000220 6d 62 6e 00 ff ff ff ff d0 07 00 00 84 2c 00 00 |mbn..........,..|
00000230 71 63 73 62 6c 2e 6d 62 6e 00 ff ff ff ff ff ff |qcsbl.mbn.......|
00000240 ff ff ff ff ff ff ff ff 54 36 00 00 f0 df 00 00 |........T6......|
00000250 6f 65 6d 73 62 6c 2e 6d 62 6e 00 ff ff ff ff ff |oemsbl.mbn......|
00000260 ff ff ff ff ff ff ff ff 44 18 01 00 e8 b8 0e 00 |........D.......|
00000270 61 6d 73 73 2e 6d 62 6e 00 ff ff ff ff ff ff ff |amss.mbn........|
00000280 ff ff ff ff ff ff ff ff 2c d3 0f 00 28 e0 2d 01 |........,...(.-.|
00000290 61 70 70 73 62 6f 6f 74 2e 6d 62 6e 00 ff ff ff |appsboot.mbn....|
000002a0 ff ff ff ff ff ff ff ff 54 b5 3d 01 5c d9 00 00 |........T.=.\...|
000002b0 61 70 70 73 2e 6d 62 6e 00 ff ff ff ff ff ff ff |apps.mbn........|
000002c0 ff ff ff ff ff ff ff ff b0 90 3e 01 28 98 36 00 |..........>.(.6.|
000002d0 72 65 63 6f 76 65 72 79 2e 69 6d 67 00 ff ff ff |recovery.img....|
000002e0 ff ff ff ff ff ff ff ff d8 2a 75 01 00 00 42 00 |.........*u...B.|
000002f0 75 73 65 72 64 61 74 61 2e 6e 61 6e 64 69 6d 67 |userdata.nandimg|
00000300 00 ff ff ff ff ff ff ff d8 2c b7 01 80 10 00 00 |.........,......|
00000310 73 79 73 74 65 6d 5f 65 78 74 33 2e 69 6d 67 00 |system_ext3.img.|
00000320 ff ff ff ff ff ff ff ff 58 3f b7 01 00 00 00 10 |........X?......|
00000330 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000003f0 53 69 6e 67 68 6f 6d 65 5f 4c 65 65 00 ff ff ff |Singhome_Lee....|
00000400 53 52 31 00 ff ff ff ff ff ff ff ff ff ff ff ff |SR1.............|
00000410 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
....
I see two headers. Followed by a section which may be some signature? And then a file list. The rest of the contents is possibly files. I am not sure what the number at the end of each file name means. The file name "recovery.img" got my hopes high.
Linux does not directly recognize this format. It may be custom. Will try extracting recovery.img assuming the rest of the file is somehow delimited. If someone can recognize the format, that would be great. As usual, all comments are welcome.
i think same with you
m10 may be use android
you are cool
Howabout using A50 updated Rom since M10 and A50 share the same screen size.
Link: http://www.garminasus.com/en_AU/support/nuvifone-a50-software-updates.html
hey akku good work. keep going. yaar i dont know any thing but i think u should ask guy who ported android on p 535 asus pda.
hope this helps.
dude plzzzz port android to m10. m dying for it.
Hello! The following links are useful?
http://www.godevice.com/2010/08/19/convert-your-windows-mobile-into-android-device/
Thanks for all the tips guys. Just managed to extract the following files from the update package:
system_ext3 file system image:
http://hotfile.com/dl/83156994/76dbe38/system_ext3.img.zip.html
recovery.img and the extracted components:
http://hotfile.com/dl/83167576/975a3e1/recovery.img.d.zip.html
the recovery.img package contains the extracted contents as well, thanks to split_booting.pl posted on the other forum.
Did not bother extracting the other files in the update package. Not sure if they are important.
Disclaimer: There was no licence when I downloaded the original file. I own an M10 and so I hope I have the right to do whatever I am doing. You are responsible to check your own license rights.
Trying to put these together with haret next.
Great man,
Please, continue working on this. I think a lot of people will be very grateful if you succeed.
If you need any support or donation to continue, just say.
Cool~~
Could you find the following files in recovery.img??
another doc says..if you can find zImage, at least you can boot into linux command line mode.
-rootfs.img
-system.ext2 (system_ext3??)
-zImage
multi888 said:
Howabout using A50 updated Rom since M10 and A50 share the same screen size.
Click to expand...
Click to collapse
Its bed idea. M10s screen has size 800x480 but screen on A50 has size 480x320 and A50s screen supports multitouch. So, I don't think that A50 image is sutable for M10.
aaaku
Keep going!
Have you tried to boot image on M10? And could you please share with us your progress. I mean, what have you done and what is to be done.
Guys, my current attempts are to
1. pick up one of the htc dual boot android roms
2. Replace the fs, kernel and initrd
3. try to boot.
Haret always crashes with some unknown exception. If I know linux, screen size shouldn't be a big issue. There should be params to change this. The reason for picking up A10 rom is the processor match and the rest of device driver compatibility. Please let me know if anyone thinks otherwise.
Feel free to cook things yourself too. As I said, I am no android or mobile expert. I just know some linux. If you want me to extract something from a different update file, I can do that.
Does anyone know how to extract anything from an update exe. Is it some kind of self extracting zip ?
Dear aaaku,
What tools do you use to extract files from 512_A10_PACKAGE.raw? Could you explain this part?? Thanks~
After reserched some documents, i think the problem is haret itself. Haret don't seem to support MSN7227 cpu, so it misrecognize msm7227 as an ARMv6 cpu.
Here are some relative posts..
http://forum.xda-developers.com/showthread.php?p=7834782
http://lists.linuxtogo.org/pipermail/haret-devel/2010-February/000006.html
Was there any luck in porting android to M10? I am interested in it.
sad to know that ... even htc hd mini has no android 4 it.... m10 n htc mini share same processor... too bad to hear that....
i suggest lets put up a bounty to develop a haret for both phones... any one in?
My problem ; no adb connection in booted OS nor in recovery .
everything else works fine; sdcard, bluetooth , mounting sd on PC all ok.
my handset : pvt4, oxygen Hboot, S-off
I allready tried "fastboot oem eraseconfig"
but stil no adb connection possible..
before I do anything stupid I want to make sure if I have the usb-brick
cause it seems I haven't apart from the not working adb.
I can adb with my other pvt3 desire so my pc setup is ok.
Is it possible to have usb brick whilst everything else apart from adb is working fine?
Is there something that can be checked? I have uploaded my misc.img
for the specialists amongst us to see if its ok or not
Hope anyone can shed some light on this.
ps similar post of me in usb brick thread in developer section but I thought
I had more chance on an answer here.
grtz lanbase
well you dont have USB brick
what happens when you do adb devices ?
also make sure your ADB is installed properly (try reinstalling?) and maybe try with diffrent ROM ?
hi,
just edit your misc img =>
00000000:48 54 43 5f 5f 33 30 34 00 ff ff ff ff ff ff ff HTC__304.ÿÿÿÿÿÿÿ
00000010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020:44 65 76 69 63 65 57 61 72 6d 42 6f 6f 74 00 ff DeviceWarmBoot.ÿ
00000030:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00000040:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00000050:43 45 20 53 65 72 69 61 6c 20 49 6e 55 73 65 00 CE Serial InUse.
00000060:44 65 62 75 67 20 43 61 62 6c 65 20 45 6e 61 00 Debug Cable Ena.
00000070:43 45 20 20 20 55 53 42 20 20 49 6e 55 73 65 00 CE USB InUse.
00000080:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090:43 6c 65 61 72 41 75 74 6f 49 6d 61 67 65 20 00 ClearAutoImage .
000000a0:32 2e 32 39 2e 34 30 35 2e 32 00 00 00 00 00 2.29.405.2.....
so to my point of veiw your file is right (see first line)
compare to mine it s all right (mine is HTC_204)
i won't say it s usb brick, when plug did you look at device manager??
know that your comp is fine but maybe the also right just sof issue.
just to be sure
hoe tis help
dzumagos said:
what happens when you do adb devices?
Click to expand...
Click to collapse
You should a serial number followed by "device" - this confirms your PC is recognizing your device.
thanx dzumagos for confirming my misc.img is ok, that's what I thought; no usb brick, then why the hell is adb not working on this device and working fine on my other one???
adb devices command doesn't
give me anything.
I have 2 desires, one of them is ok and gives me the serial as it should.
the one with non working adb just returns with command promt.
Sent from my HTC Desire using Tapatalk
hi,
i won't say it s usb brick, when plug did you look at device manager??
know that your comp is fine but maybe the also right just sof issue.
just to be sure
Click to expand...
Click to collapse
Thanx mate, for making me look at device manager when I plug in the phone. I noticed "adb with an exclamation mark" when plugging in my pvt4 and "android adb interface" when plugging in my pvt3
in device manager.
I reinstalled the adb driver with the pvt4 plugged in and now both devices have working adb!!! who would have thought that adb driver was corrupted somehow and able to recognize one phone and not the other....
Anyhow problem solved! thanx guys!
Sent from my HTC Desire using Tapatalk
I think msm_nand.c is broken because i got 56 bytes garbage from MEMREADOOB ioctl.
example code snippet:
memset(oobbuf, 0x55, 64);
oob.start = offs;
oob.length = 64;
oob.ptr = oobbuf;
if (ioctl(fd1, MEMREADOOB, &oob) != 0) {
perror("ioctl: ");
return -1;
}
page 0:
00000007E0: FF FF FF FF FF FF FF FF │ FF FF FF FF FF FF FF FF ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙
00000007F0: FF FF FF FF FF FF FF FF │ FF FF FF FF FF FF FF FF ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙
oob:
0000000800: 13 FD 23 69 75 23 8B 70 │ 52 8A A8 CF 56 CF FA 43 ‼ý#iu#<pRŠ¨ĎVĎúC
0000000810: 09 9F 79 FF A8 CF 56 CF │ FA 43 09 9F 79 FF 01 10 ○źy˙¨ĎVĎúC○źy˙☺►
0000000820: 00 00 01 00 00 30 00 00 │ 00 80 00 00 00 00 88 49 ☺ 0 _ _I
0000000830: 10 E2 F0 4E 39 B0 20 59 │ 55 55 55 55 55 55 55 55 ►âđN9° YUUUUUUUU
page 1:
0000000840: 03 00 00 00 01 00 00 00 │ FF FF 61 70 70 00 00 00 ♥ ☺ ˙˙app
Is it a driver bug? Anyone could fix it please?
htc wildfire buzz - Linux version 2.6.35.13-nFinity ([email protected]) (gcc version 4.4.3 (GCC)
Could it be caused by bad blocks on the nand? Can you provide a binary so I can test?
The blocks are good on this area. Thank you for testing.
You could download the source and binary at:
http://gnet.hu/memreadoob/memreadoob.c
http://gnet.hu/memreadoob/memreadoob
Other problem, I think we can't switch to MTD_MODE_RAW
i got this message in kernel log: msm_nand_read_oob: unsupported ops->len, 2112
but it doesn't contains MTD_OOB_RAW so we are not in raw mode.
cm-kernel/drivers/mtd/devices/msm_nand.c:
if (ops->datbuf != NULL &&
(ops->len % (mtd->writesize + mtd->oobsize)) != 0) {
pr_err("%s: unsupported ops->len,"
" %d for MTD_OOB_RAW\n", __func__, ops->len);
return -EINVAL;
}
}
if (ops->mode != MTD_OOB_RAW && ops->ooblen != 0 && ops->ooboffs != 0) {
pr_err("%s: unsupported ops->ooboffs, %d\n",
__func__, ops->ooboffs);
return -EINVAL;
}
phr3ak128 said:
Other problem, I think we can't switch to MTD_MODE_RAW
i got this message in kernel log: msm_nand_read_oob: unsupported ops->len, 2112
Click to expand...
Click to collapse
I have no such message in my kernel log.
I also ran memreadoob on my phone, and this is the output I got.
memreadoob
size: 262144000
erase size: 131072
write size: 2048
oob size: 64
2048 bytes readed
oob.start: 56
oob.length: 64
2048 bytes readed
oob.start: 56
oob.length: 64
Hi arco68,
Can we access the radio NAND after HBOOT has started AMSS (the radio OS?) I guess it is blocked by the radio? But I've read elsewhere that CWM 2.x can flash a radio.img, so it seems it does have access?
yes because in this test you read 2048 byte not 2112. it's other bug.
so if you see your /sdcard/test.img you will see the 56 bytes garbage on 0x800 instead of 64 bytes correct oob data.
xdbg said:
Hi arco68,
Can we access the radio NAND after HBOOT has started AMSS (the radio OS?) I guess it is blocked by the radio? But I've read elsewhere that CWM 2.x can flash a radio.img, so it seems it does have access?
Click to expand...
Click to collapse
CWM2 can flash radio yes, CWM3 can not. I don't think you want to mess with the radio part though.
phr3ak128 said:
yes because in this test you read 2048 byte not 2112. it's other bug.
so if you see your /sdcard/test.img you will see the 56 bytes garbage on 0x800 instead of 64 bytes correct oob data.
Click to expand...
Click to collapse
Well I have no idea what's correct or not to be honest. I'm sure if it was a major bug that it would have been fixed upstream a long time ago.
Have you tested with kernel 2.6.32, if it's the same?
Which kernel branch used from git for current nightly?
It's based on original HTC sources released on http://developer.htc.com/
My patched version, if you want to download and compile it yourself, is here:
https://github.com/arco/buzz-kernel-2.6.35
So, Are these bad for buzz? git://github.com/CyanogenMod/cm-kernel.git
What do you think who is the maintainer of msm_nand.c ?
When will be available 2.6.37 for buzz?
So, Are these bad for buzz? git://github.com/CyanogenMod/cm-kernel.git
Click to expand...
Click to collapse
Yes, it's for snapdragon devices.
phr3ak128 said:
What do you think who is the maintainer of msm_nand.c ?
When will be available 2.6.37 for buzz?
Click to expand...
Click to collapse
Google/Code Aurora, and probably some code done by HTC.
2.6.37 won't be available for the Tattoo. Anything higher than 2.6.35 I don't think will happen, unless some new phone with similar specs as the wildfire comes out with a newer kernel. And even then it could be impossible.
I see the msm-2.6.35 mtd driver is newer than yours. How possible this? I tried to complie that with msm_defconfig without success.
It's not compatible with our phone.
What is the problem with that, Is that not support MSM7225?
Think of it like this, you can't use the drivers for a Nvidia GeForce 9 card on an old GeForce 2 card, can you? If you understand what I mean?
phr3ak128 said:
What do you think who is the maintainer of msm_nand.c ?
When will be available 2.6.37 for buzz?
Click to expand...
Click to collapse
It's possible, but a huge amount of work. Porting all the hardware and making sure it works fine is really not trivial. It's time consuming, and the benefit right now of using 2.6.37 instead of 2.6.35 is unclear to me.