Hello.
Friends I have a strange problem. wifi don't work on android os.....but it work on wp7 and wp6.5 as well.
I tried : cm....miui...and other android roms on clk and magldr.......
plz help
Hi imanaab, are you using NAND android roms? Only thing I can think of is that there is a bad block in your nand right where the OS wifi commands are.
Try NativeSD, or an SD build to check, or increase the size of your /system partition might do it.
Robbie P said:
Hi imanaab, are you using NAND android roms? Only thing I can think of is that there is a bad block in your nand right where the OS wifi commands are.
Try NativeSD, or an SD build to check, or increase the size of your /system partition might do it.
Click to expand...
Click to collapse
yes I tried sd but wifi still not work
Related
I was wondering if it would be possible to either Boot Windows Phone 7 through MAGLDR from the SD Card like you can Android by maybe partitioning the SD Card so it cn have it's own space?
Or a more realistic option which would be to have a NAND ROM that includes both Android and WP7 installed to the NAND and partition the SD card for storage? This second option I believe could be possible if the NAND is partitioned correctly to allow them both to run and then you could select them in the MAGLDR!
I would like some dev feedback on this as I would try building a ROM myself but I don't know the workings of the partitioning system in MAGLDR well enough to try!
Thanks in Advance for any help!
Maby this is what you are looking for?
http://forum.xda-developers.com/showthread.php?t=913815
Cheers
Fabian1985 said:
Maby this is what you are looking for?
http://forum.xda-developers.com/showthread.php?t=913815
Cheers
Click to expand...
Click to collapse
I've seen that but what I want is to boot Android and WP7 from NAND NOT run android from the SD Card like that guy done because that makes android run slow and I want android as my primary OS!
microang said:
I've seen that but what I want is to boot Android and WP7 from NAND NOT run android from the SD Card like that guy done because that makes android run slow and I want android as my primary OS!
Click to expand...
Click to collapse
I run Android from SD as my primairy OS, WP7 is on NAND just to play with and test it. I tried Android on NAND, but to me it wasn't noticably faster then when running from SD.
Cheers,
/Cacti
Snap I'm using sd build of Android from magldr and it runs fine even boots ok, there might be a little lag when doing something the first time but other than that its great
DJGurth said:
Snap I'm using sd build of Android from magldr and it runs fine even boots ok, there might be a little lag when doing something the first time but other than that its great
Click to expand...
Click to collapse
Well the thing is I like to use a fully fledged Desire HD ROM and it's stupidly slow from the SD card... my current build is squashfs'd so only takes up about 200mb for the actual OS and I'm sure WP7 could be fitted in the rest of the space and like I'm doing now I can use EXT4 on the sd for data! Now what's needed is if someone can build a hybrid ROM!
le_cactus said:
I run Android from SD as my primairy OS, WP7 is on NAND just to play with and test it. I tried Android on NAND, but to me it wasn't noticably faster then when running from SD.
Cheers,
/Cacti
Click to expand...
Click to collapse
Hi, anyone can share how to u do this ? is it through the method that uses 2 sd cards during the formatting stage ?
Btw, what if i dont mind swapping sd cards for diff os ? Can this be done and how ? I tried to insert another sd card which I previously use for my android sd build, tried the sd boot , it gave an error of sd kernel . anyone can advise ?
Thanks !!
Hi all
Is there any way to boot android from NAND through WM?
F.E. in this Super Lite ROM we have 396 MB free space on NAND
data.img + rootfs + kernel ~ 280 MB
So, can we point haret to boot android from internal storage? may be with some cmd line option? Or we need special drivers for NAND support?
Thank you
mascew said:
Hi all
Is there any way to boot android from NAND through WM?
F.E. in this Super Lite ROM we have 396 MB free space on NAND
data.img + rootfs + kernel ~ 280 MB
So, can we point haret to boot android from internal storage? may be with some cmd line option? Or we need special drivers for NAND support?
Thank you
Click to expand...
Click to collapse
Huh... I think you misunderstood something (or perhaps it's me). If you put android in NAND, you don't need WM or haret. The problem is that at this point we (well, the devs... ) don't know how to initialize hardware, that's why we need WM.
Perhaps it would be possible to load WM, then haret+android from NAND, but don't know it that can be done.
is haret starts from internal memory? if we have 396MB of free space it is enough for android. maybe battery life will be improved when it won't be started from SD?
haret starts from any location and needs startup.txt in the same folder
then it looks for "rel_path" value, if it's empty haret tries to find all files in the root of sdcard
if it's f.e. "andboot" => sdcard/andboot
and there is one more value: "root" (used in neopeek builds)
f.e. "root=/dev/mmcblk0p2" makes haret load all files from 2nd partition on sdcard..
This is interesting, maybe I will try it later with a very lite ROM and XDAndroid
EDIT: I suppose XDAndroid has been written to start from SD. I saw "FAT Error" in haret lines and it didn't boot. Since I'm not a dev and I don't know what to edit I'll be waiting for s.o. else to try..
Cheers!
Is there anybody capable and willing to try and rewrite the paths of a haret-started android to start it from NAND. Yesterday when I tried it Haret started but since every path is pointing to SDcard folders it couldn't load anything. I confirm that I also had 396Mb free on NAND with the above mentioned Very Lite ROM.
radichev said:
Is there anybody capable and willing to try and rewrite the paths of a haret-started android to start it from NAND. Yesterday when I tried it Haret started but since every path is pointing to SDcard folders it couldn't load anything. I confirm that I also had 396Mb free on NAND with the above mentioned Very Lite ROM.
Click to expand...
Click to collapse
You cannot do this, there's just a lot of work!
The dev-s are trying to build a NANDroid for the Blackstone. What is the point to have a win and android on the NAND if you have a native Android system flashed to the NAND, WinMo is useless. So be patient and follow this thread!
Best regards, FLeX!
nasko_spasko said:
You cannot do this, there's just a lot of work!
The dev-s are trying to build a NANDroid for the Blackstone. What is the point to have a win and android on the NAND if you have a native Android system flashed to the NAND, WinMo is useless. So be patient and follow this thread!
Best regards, FLeX!
Click to expand...
Click to collapse
Generally you are right, but if it is a matter of just a few lines rewriting paths this could be a good alternative for an everyday Android port, while waiting for genuine NAND boot.
BTW I am watching all threads regarding this issue Pozdravi!
radichev said:
Generally you are right, but if it is a matter of just a few lines rewriting paths this could be a good alternative for an everyday Android port, while waiting for genuine NAND boot.
BTW I am watching all threads regarding this issue Pozdravi!
Click to expand...
Click to collapse
But i think that nand file system it's not fat32,so haret wouldn't recognize it
Achieving nand flashing it's harder but i think it's better than wm + android
HELICOPTER88 said:
But i think that nand file system it's not fat32,so haret wouldn't recognize it
Achieving nand flashing it's harder but i think it's better than wm + android
Click to expand...
Click to collapse
I agree with you! But do you think these lags in menus and apps will be eliminated when some day, somehow android is booted from NAND??? I'm just wondering, or its from the drivers, etc.
HELICOPTER88 said:
But i think that nand file system it's not fat32,so haret wouldn't recognize it
Achieving nand flashing it's harder but i think it's better than wm + android
Click to expand...
Click to collapse
Maybe you are right, I had the message "FAT Error" as I said a few posts above. Good luck with NAND, I am ready for testing if you need a Blackstone device
Cheers!
from this thread:
What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.
Click to expand...
Click to collapse
I'm wondering if we could boot android with all files (or at least data.img) on NAND with haret on this stage..
mascew said:
from this thread:
I'm wondering if we could boot android with all files (or at least data.img) on NAND with haret on this stage..
Click to expand...
Click to collapse
The answer is simple: NO! Android wouldn't boot at all.
As you can see in similar threads, the developers are trying to build NANDroid(there is no "data.img"; "system.ext2", etc. on SD, the target is the contents of this images to be writen to the NAND like mount points, for example: "/data" or "/system", etc.), wich means the Reading/Writing time will be reduced. Loading from image file on SD card is much more slower.
If you want to try loading with HaRET from NAND, just give up! It wont work.
Best regards, FleX!
Edit: @g3rm0
Sorry mate i didn't saw your post.
Part of the beauty of having WP7 on NAND and Android on SD is that you can have as many Android ROMs as you can fit on your card and you can boot into any of them as you please. But say I want to install Android on NAND. Can I still be able to have that one Android ROM on NAND, but multiple other Android ROM's on SD?
Simple... If I want to be able to boot into more than one OS, must I have WP7 on NAND? If so, is there any guide for this? I cannot find one in the main sticky.
Good question, It would be good if you could switch and chang based on mood.
You can have Android on NAND and as many sd builds as you want, same as with WP7. Until my HD2 broke a few days ago, thats just what II did, a DHD build, a MIUI build, and a CM7 build on sd, with UD on NAND. Just have to choose your AD SD directory in magldr's 'services', and then boot AD SD.
Sent from my T-Mobile myTouch 3G Slide
I do not think you can due to the fact that you have to run the HARET program. It only runs under Windows Mobile as Android does not run .EXE files.
Yes you definitely can. Check my sig
Sent from my T-Mobile myTouch 3G Slide
how_weird said:
I do not think you can due to the fact that you have to run the HARET program. It only runs under Windows Mobile as Android does not run .EXE files.
Click to expand...
Click to collapse
Well, I saw several builds in the NAND Android forum that specify they support MAGLDR. No need for haret. Here's some of them: LeoRCMix, JW MIUI, HardDroid2. So I didn't think that was a limitation.
huggs said:
You can have Android on NAND and as many sd builds as you want, same as with WP7. Until my HD2 broke a few days ago, thats just what II did, a DHD build, a MIUI build, and a CM7 build on sd, with UD on NAND. Just have to choose your AD SD directory in magldr's 'services', and then boot AD SD.
Click to expand...
Click to collapse
How do you partition your card for this setup? Is there a guide somewhere you can link here please? Or is it the same procedure you use to partition your card when you're running WP7 on NAND and Android on SD (which I've followed before)?
Any advise whether NAND build or SD build is better? In terms of performance I mean.
NAND builds will usually be faster.
As far as partitioning your card, with Android it's not necessary, you can do everything on a single Fat32 partition, unless you want to use A2SD then you'll want a single (primary) Fat32 and a single (primary) ext3 or ext4 partition for your apps/dalvik-cache. I recommend using DarkTremor's A2SD script with your NAND ROM, and if you use the DHD build in my sig, then it will automatically detect your ext3 and you'll automatically have the installed apps from your NAND on your sd build.
Sent from my T-Mobile myTouch 3G Slide
sd android builds for magldr will work if you have another android in nand,but the kernel for sd build must not be a nand kernel.for example if you have a sense build in nand and you go to start from sd a build that has tytung r10 or rafpigna kernel the kernel will start but for some strange reason it will load the nand build and not the sd build.then if you go to settings you`ll see that the kernel is changed and you have error wifi because of different kernel modules.this at least happens to me,every time i tried to start a magldr sd build with another android in nand.at first times i thought that i was pushing wrong button on magldr
Great advise, guys. I'm going to play with this soon. Thank you!
I currently have a dual-boot system with WP7 on NAND and several Android ROM's on SD. Even though the storage for all SD ROM's is the same (for example, you take a picture in one and it's visible in the gallery of another), there is absolutely no file sharing between my NAND OS and my SD OS's.
Well, I am now planning to get rid of WP7 and I want to have an Android ROM on NAND and one or more Android ROM's on SD and I want the same thing: to partition my SD card in a way that the NAND build only sees, say, 3GB of my 8GB card and the SD builds see the other 5GB.
Is this possible? How can I achieve this?
well i guess we can do everything with our hd2 ...but not something like this ... once u install android in nand it's the only os in ur phone ...and u can run another rom only if u delete the one before
mootmetal said:
well i guess we can do everything with our hd2 ...but not something like this ... once u install android in nand it's the only os in ur phone ...and u can run another rom only if u delete the one before
Click to expand...
Click to collapse
What? No, that's not correct. Using MAGLDR, you can have a NAND Android ROM and as many Android ROM's as you want on SD. That's not what I'm asking.
Razor1973 said:
What? No, that's not correct. Using MAGLDR, you can have a NAND Android ROM and as many Android ROM's as you want on SD. That's not what I'm asking.
Click to expand...
Click to collapse
never heard about something like this ... if u get the solution post so we can try it
Hello folks, having issues with android on my hd2..
currently running
NexusHD2-JellyBean-CM10_V1.2 (nativesd) flashed with recovery 4ext
2.15.50.40 radio (always used this radio)
16gb class 10 samsung microsd
at present getting this error constantly when trying do anything
android.process.acore has stopped
...and being very laggy
i was getting similar problems with a the NexusHD2 ICS rom i was using which was a NAND rom flashed with ad recovery
I always task29 etc after every new rom install.
can anyone help with this as it has been driving me crazy!
Regards
Anthony
there's no need to "always task29" when you install a new rom either in nand or nativesd, you could already have bad blocks or a failing HW.
re-do it again & try changing your sd, also try a more stable ROM first like GB, if the problem persist then it might be HW problem
mengfei said:
there's no need to "always task29" when you install a new rom either in nand or nativesd, you could already have bad blocks or a failing HW.
re-do it again & try changing your sd, also try a more stable ROM first like GB, if the problem persist then it might be HW problem
Click to expand...
Click to collapse
when you say bad blocks... do you mean on the NAND? and if so..wouldnt a task 29 fix this?
also... if I were to use a NAND rom..is changing my sd likely to help? as i thought everything was installed on the phone memory itself when using NAND rom...??
Also forgot to mention im using a HTC extended battery...but never had a problem previously
Thanks for your quick reply
ah! AFAIK there are kernels that are not compatible with some extended batteries, as for task29 the more you read-write to nand the more likely you will have bad blocks. I have flashed maybe more than a hundred times but i task29 only twice or trice since i got the phone.
even if you flashed to nand some files are placed in sd, anyways you could try NATIVESD, see the links below & give it a try
mengfei said:
ah! AFAIK there are kernels that are not compatible with some extended batteries, as for task29 the more you read-write to nand the more likely you will have bad blocks. I have flashed maybe more than a hundred times but i task29 only twice or trice since i got the phone.
even if you flashed to nand some files are placed in sd, anyways you could try NATIVESD, see the links below & give it a try
Click to expand...
Click to collapse
for age
i know about the issues with the extended batterys.. i used to have a problem when i first got the battery where the phone would not boot up and just go in a loop but this was years ago... and since then roms have been sorted... and never had an issue since so i dont think its the battery
already tried NATIVESD as mentioned in my first post
this phone has only been task29 a few times... is there anyway to check for bad blocks
sd card is pretty new too so id be surprised if its the sd card...but I will get another and try flashing again
Okay so i went out and got a verbatim class 4 4gb microsd before...
obviously being class 4 its not fast enough for nativesd...
i created ext4 partition 2GB
and what space was left was allocated to fat32 partition
so i flashed NexusHD2-Gingerbread_V3.3a-(Android-2.3.7).zip to NAND as per instructions here....
http://forum.xda-developers.com/showthread.php?t=905060
using cLK_1.4.0.1_bootloader_for_NexusHD2_135M.zip also mentioned in the thread
Rom seems to be okay...no errors and no lag... but it says i have 0.00b of internal memory
why is this happening?
Regards
Anthony