I have been having trouble lately booting any sd build or nativeSD rom from sd card.
I have tried formatting cards in windows (including sdformatter) and linux (gparted), re-installing hspl, wm6.5 then magldr, but to no avail.
I get a message in 4ext sd recovery saying that the sdcard has only 1 partition of size "null", it doesn't recognize sdext or swap partitions.
When i try to run an sd build, it reboots (attached dmesg).
All this is despite the fact that wp7 is installed in nand and runs without any problems, this i think means the sdcard reader is not at fault.
I first reported this in here (and up to post #727).
Any ideas?
I have realized that WP7 works even without an SD-card inserted, so a working WP7 is not a proof that a card is functioning well. I don't have anything more, sorry
magldr's clear sd. have you tried that?
also, try using minitool partition wizard bootable disc to erase and wipe everything on the card, and recreate partitions and try again
I have copied the posts in that thread and posted them here, if the problem is resolved, I will delete those posts, to keep that dev thread tidy, as has gilbert32 (I might do it anyway)
Post 1
Hi securecrt, it booted first time and after upgrading apps (not fresh install) it rebooted to bootanimation then went to lockscreen. I was able to play around with it for a bit and even managed to record a video (it doesn't play back on pc btw) but then gallery FCed and i got a reboot to magldr. Since then it doesn't want to boot past htc screen (attached dmesg).
I will try a fresh formatted sdcard and fresh install. Have to backup stuff first.
WP7 not affected though
attachment- http://forum.xda-developers.com/attachment.php?attachmentid=2014818&d=1370285990
Click to expand...
Click to collapse
Post 2
Since trying securecrt's kernel on nativeSD, i have been unable to boot any nativeSD rom or any sd build on any of my sdcards.
However wp7 does boot ok, so it can't be my sdcard slot, which i thought might be the problem.
I am at a loss to explain it.
My 4ext sd recovery says that it can't mount the sdcard and does not show any partitions apart from fat32 of null size and B under free.
Please can anyone confirm this, and pretty please do not try to boot this until someone can explain what has happened
Click to expand...
Click to collapse
Post 3
gilbert32 said:
not sure but maybe while you were recording a video, the sdcard fat32 partition got somehow corrupted? can you try running diskcheck on your pc to make sure it's correct?
and as i understood, after trying to shoot video, gallery FC'ed and it rebooted?
Click to expand...
Click to collapse
I have 3 cards, for nativeSD. None of them are working. that is 3 sd recoverys, 1 on each. all show the same. sd builds dont boot either. Something in phone is wrong.
I can try re-installing magldr or wm6.5. But would like to try and work out what is wrong first, for others
Click to expand...
Click to collapse
marco.palumbi replied
I guess that you tryed to remove the battery and let the phone stay for some minutes before inserting it again.....
Click to expand...
Click to collapse
Post 4
Trying that while i type this. Last night i managed to boot a couple of nativeSD roms but after rebooting they refused to boot again. Also one of the cards showed normal partitions in recovery, then later i looked again and all 3 were only showing fat32 of null size.
Really confusing.
After leaving battery out for 5 mins, i looked in recovery and saw all 3 partitions. But couldn't boot sd build, nor nativeSD.
Another odd thing is the led on my card reader doesn't seem to want to stay steady, it keeps flashing intermittantly as if being accessed, i have to wait for it to settle before removing. After swapping out initrd.gz and zimage for another nsd rom to test, i look at recovery and get fat32 null again. Perhaps the problem is in pc, idk. New nsd rom doesn't boot either.
Edit; have attached dmesg of last nsd attempt, tytung's ics
Attachment- http://forum.xda-developers.com/attachment.php?attachmentid=2016224&d=1370337872
Click to expand...
Click to collapse
Post 5
gilbert32 said:
I'd say it's time to go back to stock wm rom and try booting an sd or nativesd rom. if it fails, maybe try formatting a card with wm's format utility (which unlocks wp7's sd card) and try again. i'd say the kernel + initrd.gz have affected magldr and the card's mbr somehow
Click to expand...
Click to collapse
I think you are right gilbert32, something is wrong.
I just booted into ubuntu on pc and swapped out initrd.gz and zimage for another nsd rom, not booting. No flashing led this time. I had the phone battery out whilst changing OS on pc, recovery shows null still.
WM6.5, here i come again
Edit; I installed wm6.5 (had to do it twice, first time had an error box appear, not seen that before)
2 out of 3 cards were not seen by wm6.5, 3rd card was seen and i managed to boot a nativeSD rom, but after reboot recovery showed fat32 null and couldn't boot after.
I installed magldr and used fourth card i used for wp7. After formatting with sdformatter, deleting mbr, creating partitions with minitool installing sd 4ext recovery, recovery shows fat32 null again.
Tried to install twrp2.2.1.4 but it doesn't boot.
I think i am going to have to re-install hspl.
Sorry marc1706 for hijacking your thread with all this
Click to expand...
Click to collapse
securecrt posted
...It will not break anything. ...
Click to expand...
Click to collapse
(I believe securecrt BTW, it is what makes this so puzzling to me)
Post 6
Thanks gilbert32, I flashed hspl, now i cant flash wm6.5, or reflash magldr, or run any nativeSD build (if i get one to boot it just hangs), so you could say it is serious
I have put my sim in an old(er) phone for now since waiting on calls.
I had formatted the card fat32 32kb clusters.
Gonna give it a break for now, i have been at it on and off all day. need to get things done.
It is odd that 4ext sd always boots regardless of whether anything else does.
Anyway, i am conscious of the fact that it is probably my hardware that is at fault. Until someone else posts in this thread with similar problems I will refrain from further posts here.
Thanks again.
Click to expand...
Click to collapse
gilbert32 said:
magldr's clear sd. have you tried that?
also, try using minitool partition wizard bootable disc to erase and wipe everything on the card, and recreate partitions and try again
Click to expand...
Click to collapse
I used clear sd (and last 24mb nand) when re-installing wp7 after hspl etc.
Not sure about a bootable disk, I used minitool on windows 7 (I dual boot pc win7/ubuntu)
Marvlesz said:
I have realized that WP7 works even without an SD-card inserted, so a working WP7 is not a proof that a card is functioning well. I don't have anything more, sorry
Click to expand...
Click to collapse
But it is fully functional, i can even view contents of sdcard fat16 partition which has an android sdbuild on it (which also doesn't boot)
Robbie P said:
I used clear sd (and last 24mb nand) when re-installing wp7 after hspl etc.
Not sure about a bootable disk, I used minitool on windows 7 (I dual boot pc win7/ubuntu)
Click to expand...
Click to collapse
well i'd try minitool bootable disc. only 40mb. and i always use it when coming from wp7. sd would usually not get recognized on wm without using it so try it.
just delete all volumes on the sd (DO NOT DELETE THE HARD DISC's VOLUMES, ONLY SD )and create one fta32 partition and try 4ext recovery
Robbie P said:
But it is fully functional, i can even view contents of sdcard fat16 partition which has an android sdbuild on it (which also doesn't boot)
Click to expand...
Click to collapse
with my experience, android needs fat32 partition not wp's 200mb fat16 partition
gilbert32 said:
well i'd try minitool bootable disc. only 40mb. and i always use it when coming from wp7. sd would usually not get recognized on wm without using it so try it.
just delete all volumes on the sd (DO NOT DELETE THE HARD DISC's VOLUMES, ONLY SD )and create one fta32 partition and try 4ext recovery
Click to expand...
Click to collapse
I tried minitool bootable disk and formatted the whole card with FAT32 (32Kb clusters, aligned to cylinder (also tried aligned to Mb) with same result, null in 4ext recovery, and an sd build doesn't boot.
with my experience, android needs fat32 partition not wp's 200mb fat16 partition
Click to expand...
Click to collapse
I know, but it (usually) works on that partition. I posted a thread on it here, it was a proof of concept (no formatting/repartitioning needed) and also charges extended batteries in wp7.
it seems more and more about hardware problem.....
can you post a few more dmesg's ?
gilbert32 said:
it seems more and more about hardware problem.....
can you post a few more dmesg's ?
Click to expand...
Click to collapse
1. Leo king sd build (reboots)
2. PA beta v1.992 sd build (reboots)
3. jellycarbon nativesd (hangs on splashscreen)
4. miuiv15b nativeSD (hangs on splashscreen)
5. miui THANHVO31 nativesd(hangs on splashscreen)
6. Sense4a sdbuild (reboots)
...
Robbie, you're located in London right? I'm in Portugal, i can send you a hd2 motherboard for you to test, this motherboard is fully functional, the problem is that it overheats if you stress it too much, but at least you can check if the problem is your motherboard or not.
Cheers
Sent from my GT-I9300 using Tapatalk 2
yugoport said:
Robbie, you're located in London right? I'm in Portugal, i can send you a hd2 motherboard for you to test, this motherboard is fully functional, the problem is that it overheats if you stress it too much, but at least you can check if the problem is your motherboard or not.
Cheers
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I've seen a video of disassembling and reassembling of hd2 and it makes my palms sweat thinking about it
I have a cracked screen on my phone and was thinking of replacing the digitiser anyway. So I might take you up on your kind offer. I will see if anyone else has any ideas first:fingers-crossed:
Thanks mate.:good:
Robbie P, can you try installing a nand rom like cm7 only on nand?
and nativeSD roms hang on splash screen right? if so, maybe you can use adb. try mounting system manually and data too, then type stop and start
maybe sd isn't mounting well.
also use cd to /dev/block . is mmcblk0pX present there?
It seems that on first android boot after coming from wp7, i am more likely to be able to boot into nativeSD android. Subsequent boots don't work. But it only works sometimes. And the time i managed to boot into tytung's ics, i got a bsod after a call (attached dmesg, seems i lost sdcard).
It looks more to me like a hardware issue with my sdcard port.
I haven't tried nandroid yet. And when it isn't working, i can't connect to phone with QTadb.
Robbie P said:
It seems that on first android boot after coming from wp7, i am more likely to be able to boot into nativeSD android. Subsequent boots don't work. But it only works sometimes. And the time i managed to boot into tytung's ics, i got a bsod after a call (attached dmesg, seems i lost sdcard).
It looks more to me like a hardware issue with my sdcard port.
I haven't tried nandroid yet. And when it isn't working, i can't connect to phone with QTadb.
Click to expand...
Click to collapse
Code:
[ 2.930053] @@@ SD power 17 @@@
[ 2.999237] @@@ SD power 15 @@@
[ 3.141662] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 3.141723] mmc1: new high speed SDHC card at address e624
[ 3.142150] mmcblk0: mmc1:e624 SU32G 29.7 GiB
.........................................
[ 126.136596] FAT: Directory bread(block 29848915) failed
[ 126.143280] auo_panel_cfg_setup exit
[ 126.954467] EXT4-fs error (device mmcblk0p2): ext4_find_entry: reading directory #409602 offset 0
[ 126.954650] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
you are right i think. sd card slot is probably somehow loose and sd is getting disconnected. maybe after booting tytung's ics, after the call, holding the phone and moving it in hand made the sd card get lost again. try booting multiple times, each time removing and reinserting the sd. ig it works more often, then that's your problem
I've sussed it
I found somewhere that says you can clean the sdcard slot with a piece of card wetted with alcohol (remove battery first). I tried it dry first and found dirt corresponding to the outside contacts of the card. It started booting, but gave a few errors and not all my SDcards showed correct partitions. So i tried wetting a new piece of paper card with GF's nail polish remover and inserting it in and out of slot (paper card should be same width as contact end of sdcard (if it is smaller, it could move from side to side and snag one of the phones contacts)).
It all seems good now.
Thanks gilbert32, yugoport & marvelz for your contributions. Much appreciated.
Looking at the dirt on the dry paper card, most dirt was on pin 8, some on pin 1 (see wikipaedia, tech details,transfer mode), so they only get used in 4-bit bus mode. Perhaps this is the reason why android wouldn't work, but wp7 does.
Lastly, i noticed that my wp7 card (16gb "old" card) has the sides worn down and metal is showing. The plastic from this could have covered the phone pins 1 & 8, or it could have been fluff
Back on android again:highfive:
Robbie P said:
I've sussed it
I found somewhere that says you can clean the sdcard slot with a piece of card wetted with alcohol. I tried it dry first and found dirt corresponding to the outside contacts of the card. It started booting, but gave a few errors and not all my SDcards showed correct partitions. So i tried wetting a new piece of paper card with GF's nail polish remover and inserting it in and out of slot (paper card should be same width as contact end of sdcard (if it is smaller, it could move from side to side and snag one of the phones contacts)).
It all seems good now.
Thanks gilbert32, yugoport & marvelz for your contributions. Much appreciated.
Looking at the dirt on the dry paper card, most dirt was on pin 8, some on pin 1 (see wikipaedia, tech details,transfer mode), so they only get used in 4-bit bus mode. Perhaps this is the reason why android wouldn't work, but wp7 does.
Lastly, i noticed that my wp7 card (16gb "old" card) has the sides worn down and metal is showing. The plastic from this could have covered the phone pins 1 & 8, or it could have been fluff
Back on android again:highfive:
Click to expand...
Click to collapse
That's great! i'm glad you got it sorted out
Regards
gilbert32 said:
That's great! i'm glad you got it sorted out
Regards
Click to expand...
Click to collapse
It seems i posted too soon earlier, and it is back to showing null in recovery
Looking at the sd port, there seems to be a piece of metal sticking up around the area of pin 1 (rhs), so i think it has broken (possibly not helped by me prodding it with bits of card). Wp7 still works though. I took the case off and the port is soldered to the motherboard, so no chance of fixing it, for me at least.
Anyway, I have bought a second hand hd2 from one very careful lady owner (wm6.5 user), never been flashed, no scratches, looks brand new, no bad blocks and cheap. I showed my hd2 with cracked screen to the seller with wp7.8 on it and booted an sd android on the new one to check for connections etc. they were impressed but sold it nonetheless (they said "how did you do that?", I said that it was extremely complicated)
I now have a hd2 with wp7.8 and a hd2 with slim jb on nand dataonext, and I am a happy bunny again
Robbie P said:
It seems i posted too soon earlier, and it is back to showing null in recovery
Looking at the sd port, there seems to be a piece of metal sticking up around the area of pin 1 (rhs), so i think it has broken (possibly not helped by me prodding it with bits of card). Wp7 still works though. I took the case off and the port is soldered to the motherboard, so no chance of fixing it, for me at least.
Anyway, I have bought a second hand hd2 from one very careful lady owner (wm6.5 user), never been flashed, no scratches, looks brand new, no bad blocks and cheap. I showed my hd2 with cracked screen to the seller with wp7.8 on it and booted an sd android on the new one to check for connections etc. they were impressed but sold it nonetheless (they said "how did you do that?", I said that it was extremely complicated)
I now have a hd2 with wp7.8 and a hd2 with slim jb on nand dataonext, and I am a happy bunny again
Click to expand...
Click to collapse
that's good
a friend gave me an hd2 without screen/digitizer. it was supposedly fully working but misses those 2 components.
took it to a local store that is an EXPERT in fixing htc phones (called htc solutions ). they said they had to check if the motherboard was working. it was supposed to be okay. sadly, nope.
they sad it was damaged, so i'm taking it back for the battery
gilbert32 said:
that's good
a friend gave me an hd2 without screen/digitizer. it was supposedly fully working but misses those 2 components.
took it to a local store that is an EXPERT in fixing htc phones (called htc solutions ). they said they had to check if the motherboard was working. it was supposed to be okay. sadly, nope.
they sad it was damaged, so i'm taking it back for the battery
Click to expand...
Click to collapse
I know of a very nice person in Portugal with a spare motherboard :fingers-crossed:
Related
Hi folks,
I've tried two different builds (a hero and donut with the proper flash for the resolution) and two different microsd cards in my vogue, but I can't get either of them to boot. They usually lock up somewhere around "copying rootfs to nand" or "copying systemfs to nand".
I've read and re-read through a ton of posts on here, and I think I'm following the directions exactly, but nothing has worked so far. I'm hoping someone here can offer up some suggestions on why I can't seem to get this going.
For the record I've been running nfsfan's roms for the last few months without any hitch.
Thanks for any info.
Shado
Just an update, I reinstalled winmo 6.5, and thats working fine. So I decided to take the sensehero build and run it under haret, and that works perfectly.
Hopefully someone here will have some idea as to why it crashes writing to nand...
had size microsd card are you using?
Its the 512mb microsd that came with my vogue....
Assuming you've followed all the guides and have all of the files on your card etc you may just have one of the incompatible phones. Several people have reported these issues as well. Only fix would be for someone to send one to DZO so as he can determine what the hardware change is that's causing the issue.
shadoslayer said:
Its the 512mb microsd that came with my vogue....
Click to expand...
Click to collapse
thats odd....ill look into it.
I've love to send my phone, but then I'd have to use rabbit ears and a tinfoil hat to get my calls
I can take it apart to give some info on the internal components if that would help, or if there is anything I can run/do to provide any sort of debug information. Please let me know.
At this point the only thing I can say after flashing and booting a few dozen times is that it is something related to reading/writing/mounting the SD card. I also found another 256mb microsd and tried that with the same result (so I've ruled out the card). The majority of the time it just hangs on writing to nand, but occasionally it will segfault in that same area of the boot sequence and sometimes it will just hang mounting the sd card right shortly after it initializes bluetooth.
Cheers
Shado
shadoslayer said:
I've love to send my phone, but then I'd have to use rabbit ears and a tinfoil hat to get my calls
I can take it apart to give some info on the internal components if that would help, or if there is anything I can run/do to provide any sort of debug information. Please let me know.
At this point the only thing I can say after flashing and booting a few dozen times is that it is something related to reading/writing/mounting the SD card. I also found another 256mb microsd and tried that with the same result (so I've ruled out the card). The majority of the time it just hangs on writing to nand, but occasionally it will segfault in that same area of the boot sequence and sometimes it will just hang mounting the sd card right shortly after it initializes bluetooth.
Cheers
Shado
Click to expand...
Click to collapse
well mind breaking down what you did to where it got stuck, as in each step beforehand.
I am having the same problem as well. It has to be hardware in my phone. I've tried the two different methods of flashing and both freeze up in linux when it is trying to flash. I've also tried two different micro sd cards and the same result happened on both. I flash windows mobile roms no problem.
gigermunit said:
well mind breaking down what you did to where it got stuck, as in each step beforehand.
Click to expand...
Click to collapse
Sure.
(keep in mind the phone is already unlocked, so I'll skip all the unlocking stuff)
1) Downloaded Sensehero from http://forum.xda-developers.com/showthread.php?t=603028 and also grabbed the hero.user.conf from that thread as well
2) Formatted the 512mb microsd in win 7. I did a full format (not quick format) and used fat32 (I also tried formatting fat)
3) Copied everything that came with Sensehero to the root of the sd (data.img, datafstonand, rootfs.img, rootfstonand, system.sqsh, systemfstonand), created a conf folder and copied the hero.user.conf there.
4) Ejected the SD card in Windows, popped it into my vogue.
5) Grabbed voguimg-320x480-17-12-09.nbh, renamed it to RUU_signed.nbh and flashed it (also tried VOGUIMG.NBH and flashing from sd). When I flashed from Windows, I put the phone in bootloader mode first.
6) After flashing, the phone restarted, and the kernel started its thing. The first time it locked up on writing rootfs to nand (it got to 4% I believe and locked up), I went to bed, so I know it wasn't because I didn't wait long enough.
After that, it was pretty much just a combination of resetting and popping the battery out and back in to restart it. Sometimes it would progress past writing rootfs and get to systemfs or datafs but it would always fail at some percentage along the way. Sometimes after just hitting the reset button (the little one on the bottom of the phone) it would freeze trying to mount the SD card. In ALL cases though, it made it to that point - it would never crash, segfault, etc. before it got to the SD card part of the kernel.
Also, thinking it might be something with Sensehero, I tried the Donut ASOP build from http://forum.xda-developers.com/showthread.php?t=591104 along with voguimg-240x320-17-12-09.nbh. Exact same result.
The only thing I haven't tried is using any of the voguimg's with earlier dates, but I'm not sure what has changed between the different revisions that would make any difference. If you think I should, I can try those other builds to see what happens.
Hope this helps, let me know if you need any more info!
Cheers
Shado
BTW When I get home later tonight, I'll reflash and write out exactly what it says during the kernel loading process (or try to take a picture).
shadoslayer said:
BTW When I get home later tonight, I'll reflash and write out exactly what it says during the kernel loading process (or try to take a picture).
Click to expand...
Click to collapse
I've done that, it doesn't help dzo said. Usually it processes further than it shows on the screen. I've pmed dzo and offered to send him my phone since I'm only a few towns away.
shadoslayer said:
Sure.
(keep in mind the phone is already unlocked, so I'll skip all the unlocking stuff)
1) Downloaded Sensehero from http://forum.xda-developers.com/showthread.php?t=603028 and also grabbed the hero.user.conf from that thread as well
2) Formatted the 512mb microsd in win 7. I did a full format (not quick format) and used fat32 (I also tried formatting fat)
3) Copied everything that came with Sensehero to the root of the sd (data.img, datafstonand, rootfs.img, rootfstonand, system.sqsh, systemfstonand), created a conf folder and copied the hero.user.conf there.
4) Ejected the SD card in Windows, popped it into my vogue.
5) Grabbed voguimg-320x480-17-12-09.nbh, renamed it to RUU_signed.nbh and flashed it (also tried VOGUIMG.NBH and flashing from sd). When I flashed from Windows, I put the phone in bootloader mode first.
6) After flashing, the phone restarted, and the kernel started its thing. The first time it locked up on writing rootfs to nand (it got to 4% I believe and locked up), I went to bed, so I know it wasn't because I didn't wait long enough.
After that, it was pretty much just a combination of resetting and popping the battery out and back in to restart it. Sometimes it would progress past writing rootfs and get to systemfs or datafs but it would always fail at some percentage along the way. Sometimes after just hitting the reset button (the little one on the bottom of the phone) it would freeze trying to mount the SD card. In ALL cases though, it made it to that point - it would never crash, segfault, etc. before it got to the SD card part of the kernel.
Also, thinking it might be something with Sensehero, I tried the Donut ASOP build from http://forum.xda-developers.com/showthread.php?t=591104 along with voguimg-240x320-17-12-09.nbh. Exact same result.
The only thing I haven't tried is using any of the voguimg's with earlier dates, but I'm not sure what has changed between the different revisions that would make any difference. If you think I should, I can try those other builds to see what happens.
Hope this helps, let me know if you need any more info!
Cheers
Shado
Click to expand...
Click to collapse
wow....im speak less, i don't know what the problem could be.
Well, thanks for trying to help out giger. Hopefully with Scizzle's phone dzo can discover whats causing our vogues to act up and we can finally get droid running from nand. And if anyone comes up with anything, I have no problem testing, so drop me a pm.
Thanks everyone!
I have very similar problems as reported here when trying to do this with one of the latest Hero builds. After many resets (due to lockups during the NAND writing process), I am able to get past the writing to get to the Hero/HTC animation screens, but if I'm lucky enough to get that far, it will lockup sometime during those as well.
Back to HaRET for me I guess.
Hey guys!
Here are the events leading to the demise of my perfect dual-boot setup!
1. Installed MAGLDR, WP7 - worked great alone.
2. Setup dual-boot with Cyanogen 7 and worked great. Both are very fast.
3. Contacted Microsoft to get my live activation key. Put it in, now every time i power down my phone and come back into WP7, it is factory reset. Why wont it hold any settings? I have the phone partitioned right, and there are NO problems on the android side. I've searched and searched and can't even find something remotely close.
This might be due to my inability to phrase the scenario right for the search bar.
d16soda said:
Hey guys!
Here are the events leading to the demise of my perfect dual-boot setup!
1. Installed MAGLDR, WP7 - worked great alone.
2. Setup dual-boot with Cyanogen 7 and worked great. Both are very fast.
3. Contacted Microsoft to get my live activation key. Put it in, now every time i power down my phone and come back into WP7, it is factory reset. Why wont it hold any settings? I have the phone partitioned right, and there are NO problems on the android side. I've searched and searched and can't even find something remotely close.
This might be due to my inability to phrase the scenario right for the search bar.
Click to expand...
Click to collapse
Maybe, you should just have WP7 alone and then activate it.
Then set-up dual boot. That might work.
Otherwise, you should read through the dual boot thread for any other people with the same problem.
:/ so much work to undo... I hope that isn't necessary.
Sent from my HTC HD2 using XDA App
I hope it isn't either, but that's what I had done before changing SD cards and it worked fine
XPiemaster said:
I hope it isn't either, but that's what I had done before changing SD cards and it worked fine
Click to expand...
Click to collapse
you had the same problem?
Well I just figured out that when I am in WP7, it isn't soft reset like i though - it just isn't recognizing my SD. Says I have 7 MB of memory. :O
Just redid all of the partitioning, reinstalled WP7, reinstalled Android... and STILL after I change the unallocated partition to Primary as directed, when I boot into WP7 it says I have 10mb of memory.
What happened to me
I am still not clear on what is happening to you but here is what I have found. I set up wp7 using my 8 gb card It worked flawlessly. I wanted to dual boot so....half of my 16 gb t-mobile provided sd card became my windows partition and half became a fat partition. excellent life was good. I got sd android and wp7 nand. However, one day from android i selected the reboot option to get back to wp7,,,mistake. I discovered that reboot jacks up the windows side of the card, must write to it during the reboot. lucky for me it was just a matter of recopying the 8gb cards content back to the 16 gb card to get back the data I had there. but a word to the wise, choose shut down not reboot from android on a dual booting wp7 setup.
What happens is things are fine, but android boots fine, but when I boot into WP7 it shows 10 mb of disk space.... not the 8gb i have it set as. Android, however, runs well and shows 8gb.
did you start with a smaller card when you installed wp7? I might be a little behind because I did the install in january but as far as i know you need 2 sd cards to dual boot. I had to use a smaller card to install wp7 then copy the contents to the blank space on the larger card.
whycali said:
did you start with a smaller card when you installed wp7? I might be a little behind because I did the install in january but as far as i know you need 2 sd cards to dual boot. I had to use a smaller card to install wp7 then copy the contents to the blank space on the larger card.
Click to expand...
Click to collapse
I used partitions, not two SD. It is the same principle, though. The WP7 partition is smaller. I just redid everything, and so far it is working Where I think it was getting hung up was in the guide, I was supposed to set the unpartitioned space as Primary instead of Logical. This meant 2 Primaries on the SD.... I skipped this step so I have my Fat32 as Primary and Unpartitioned as Logical. Both WP7 and Android are running well and WP7 saves all settings.... so far.... lol. I'll definitely keep this thread updated. Thanks for the input guys.
I actually think I like the 2 sd card method a little better since it provides a backup if your sd card decides it doesnt love you any more.
whycali said:
I actually think I like the 2 sd card method a little better since it provides a backup if your sd card decides it doesnt love you any more.
Click to expand...
Click to collapse
Lol that is what a hard disk and back-up utilities are for ^^
you backed up the unallocated space on your sd card to your hard disk?
whycali said:
you backed up the unallocated space on your sd card to your hard disk?
Click to expand...
Click to collapse
Yes.
Also, now Android is having issues booting... Trying one more thing and hoping it doesn't mess up WP7 :/
[Q] Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report"
Hi,
First let me say - YES, i have searched all of the forums here (and a number of other sites) and seem to have tried almost every option.
I have Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report" problems. The farthest I get guaranteed is the cyanogenmod boot and menu (if I try and bring it up). I'm simply trying to get the SD card with cm7 to boot reliably and not eventually loose the boot partition.
Off and on since spring I was able to burn a CM7 image (verygreen's size agnostic, and one or two others I have since lost track of) to a SD card; have had it boot to cm7 and it work for awhile - but then eventual degraded into the no partition found error. the majority of the time it just doesn't work and results in that annoying purple black screen.
When it does work, it only works for awhile and then the boot partition can't be found; a few very small 3 of times - if I copied a new update it woke back up ad worked for a couple of reboots then lost the partition again.
Anybody got time to take pity on my melted brain and take a few guesses?
Clearly I'm not only missing something - but as things have gotten worse, am now missing more (if that is possible) as I'm going backwards to see why it no longer works at all.
At this point wrong has happened so often, I'm just lost on what even worked way back when I started.
I'm trying to backtrack to where it at least worked a little for a few days...but noob world is decaying into worse world.
I tried a couple of other, older processes and a multiboot menu one that seemed promising (plus could handle the new naming conventions for 7.2 CM7); but that one never even got past the missing boot partition.
I have tried approx 10 2gb SDCards, Sandisk, Kingston, Unknown; Class 4 and mixed.
I have tried 3 8GB SD Cards, Sandisk, class 4
I have tried 1 16gb SD Card, Sandisk, class 4
I have tried a Vivitar Micro SD Card Reader
I have tried the micro SD card Adapters in a laptop, and then in a sandisk USB adapter.
I even tried doing it all using the Nook color via a USB cable.
I even tried leaving the nook color off and connecting the USB cable to the PC to initiate a boot.
Using Windskimager
Using SD formatter
Have formatted Full erase and overwrite.
Tried leaving partition size alone
Tried partition resizing up to 250mb
Tried cm7 zip alone and with gapps
WinXP on 2 desktops and a laptop
It sounds like you have run the gamut of attempted resolutions.
That message is part of the verygreen partitioning script that runs every time the verygreen recovery is run. So, that means the normal boot kernel for CM7 is not loading.
The way the verygreen SD should operate is it starts with uImage and uRamdisk on the boot partition. Those are verygreen's recovery files. The first time it is booted, it looks at your emmc to be sure it is a nook. Then it looks at the SD to see if it has been partitioned yet. If it is not, it partitions it into those partitions necessary for installing ROMs. After partitioning, it looks for a zip to install. If it does not find one, it shuts down and the next time it boots it does the same thing until it finds the first ROM zip to install. If it finds one, it installs it. The first time it installs a ROM, it renames those uImage and uRamdisk verygreen files to uRecImg and uRecRam and they become the verygreen recovery files. And it installs new uImage and uRamdisk files from the zip to become your CM kernel and ramdisk. These are what normally will load in the future to start CM.
Now, with the disk partitioned and CM installed, ordinarily, after the cyanomod logo comes up, it boots by default to CM via the uImage and uRamdisk files. If you intercede with the boot menu and tell it to boot to SD recovery, it looks for uRecImg and uRecRam to load the verygreen recovery. If that is loaded, the verygreen script does all its checking again, it verifies that emmc is a nook, then tries to verify if the SD is partitioned. If it is, it looks for a new zip to install. If, in checking to see if it is partitioned, it cannot find partition 1, it gives that message that has been bugging you.
So I see two things that are happening to you.
First, it is booting to the verygreen recovery first instead of CM. That could be due to a recovery bootloop happening. Look at my tips thread linked in my signature to see an explanation as to what that is and how to possibly get out of it.
Second, after it boots to the verygreen recovery, it does its checking and cannot find partition 1 of the SD and gives you that message.
What I cannot understand is, if you have no partition 1 on your SD, how is it booting to the verygreen recovery?
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Ditto on that - especially as it boots happily to that error message time after time after the green cyanomod screen appears and I can also do the menu trick to get it to go into recovery.
Just as a clarifier: A number of times it tried to do the install (text flowing by) and at the end claims it can't find the boot partition - odd (unless I have less of an idea of what I am doing than I think) as isn't all that running from that partition? A fairly even number of times it doesn't even run the install and just errors out right up front.
Once in a great while it all works, and I'm good for a few days - but eventually upon rebooting to get it back to normal (either by menu choice or by pulling the sd card) - all I get is that lack of partition again.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Yes with the SD card out it boots to stock, although a few time what looked like the CWMod menu came up after I shut down and started up without the SD card installed. Maybe only 2 or 3 times out of WAY to many boots to stock so the kids could read their books while I went to work.
I have even tried resetting the nook to factory on the off chance I did something dumb while mucking about to cause that.
leapinlar said:
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
Click to expand...
Click to collapse
Will do so later tonight and will read the notes in your signature as well.
I saw something go by about the boot partition having to start at the 63 block or something - I can't believe ALL my SDcard adapters / writers are bad, but could the nook reader be screwy? Anyway to do a real test? I've been using the Easeus Partition Manager, but will try the Mini-Tool Partition Manager.
Thanks for the step by step explanation of exactly what happens in the process so I can again get a handle on what it's all doing. That all makes sense to what it looks like it tries to do. Deeply appreciate the time!.
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
leapinlar said:
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Click to expand...
Click to collapse
I had thought of that too - at stock it seems to have no problems reading consistently; I've done surface tests using partition manager - but haven't located any real other options of hard testing like once done for hard drives.
Plus the fact that sometimes, it will work for days before it craps out.
j8048188 said:
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
A number of times - I went through and wiped all my downloads for the latest try.
Okay So As I mentioned I went back and wiped everything I had downloaded and restarted (again).
Current status is it's working BUT:
suspiciously too easy this time, worked first shot
- (having said that, I've had looking stupid and asking suddenly means it all starts working - so if it's that I'm good with this)
I've only rebooted into CM7, not back to stock at any time
Have not removed the SD card
I've not had time to load up the apps I like, just the kids games
- (sometimes I think it's the more wanted, the less reliable)
Obviously because I haven't removed the SD card, i haven't been able to retry things enough to recreate the other problems of boots right, yet can't find the partition when it really counts.
Changes (listing stupid things too, just because):
-Went back to my sandisk class 4 16gb HC card
-changed USB adapter back to sandisk one, using a sandisk micro to SD adapter that specifically says sdhc (although I think that is really just marketing
-Formatted the SD in the Nook x2, and did not use SDformatter
-Looked at the partition on the card with MiniTool not Easeus partition manager
-There is a step in verygreen's where you pop the card out and reconnect to the PC BEFORE adding the cm zip, made sure to do that - but could swear I had done it before.
Full painful boring steps that SO far has gotten it past the first stage of creation (again the full test is when I boot into stock a few times, or remove the SDcard for anything, or load my really wanted apps on the android side):
--Also note my lack of class 4 Sandisk cards, I only had one after all. BUT I have had this all work to this point with the 16gb only to have it go south.--
Painful details is so I can catch what is really worthwhile different as even WHEN I get it to work, I'm going back to try all the other cards because it worked so oddly and failed so oddly and differently - but that's just me.
> The 2GBs are:
6 Sandisk SD, don't see any class Rating
2 no brand SD, don't see any class Rating
1 Kingston SD, don't see any class Rating
> The 8gb are SDHC "Adata" Class 4 SDHC
> The 16gb is a Sandisk Class 4 SDHC
Using the 16GB Sandisk Class 4
--------------------------------
> Nook booted to stock
Inserted SD Card
Unmounted
Formatted sucessfully
unmounted and removed
> Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
> Mounted as E Drive
E Drive shows standard Nook Folders:
.amdroid_secure
B&N Downloads
LOST.DIR
My files
> MiniTool Partition Wizard
Surface test = all good.
>Write the image on your SD card
Used Win 32 Disk Imager
After done with writing, eject and then re-insert the uSD card into your computer.
Two Partitions - 118 and 14.72gb
>Copied to card:
update-cm-7.1.0-encore-signed.zip
Installed correctly
configured wireless
Rebooted = OK
Rebooted = OK
>Turned off
Removed SD Card
Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
copied gapps
>Boot into Recovery
Gapps installed
> boot
all good
did all set ups like before
added apps (7 games for kids)
rebooted twice
started using
added one app I really like (newshog)
Listening for drumming... nothing so far (Dr. Who reference)
I'm going to go the weekend before rebooting to stock as I can do some adding, and rebooting to android.
Maybe backup the droid side this time around.
THEN the death tests on Monday
-thanks for listening_
p.s. - Yes, I still suspect the card reader somewhat as REMOVING may be where it breaks down.
However, once or twice when I had the Unexpected lack of boot partition error - I was able to bring it back by doing a CM7 update via recovery, despite it refusing to find the boot partiton immediately previously - of course that means the SDcard was removed and reinserted. Most time reinsertion = no help.
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
leapinlar said:
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
Click to expand...
Click to collapse
Yes, I know - but it's two separate tests to see which one caused the problem.
Turns out that neither was needed - it was easier to create; my son simply turned it off (not a reboot cycle as I had been doing which worked).
When it was turned on, it no longer boots - it goes straight to BSOD (actually deep purple).
Booting into recovery gets me:
Penguin Logo
rcS!
Populating /dev using udev: done
Initializing random number generator.... done.
modprobe: chdir(2.6.32.9): No such file or directory
Starting Network...
Detected Standard B&N nook layout, emmc first
Error! Unexpected lack of boot partition on the SDCARD!
Please Report!
Poweroff when ready
Since I'm till held to the noob reposting limit of once every 5 minutes and the captha I can barely read - I'll post MiniTool result in about 5 minutes. I'll link a screen capture if i can here.
I tried to boot per menu to the EMMC stock; Clockworkmod Recovery v3.2.0.1 came up. I know I did emmc and what ever the second default is (which should be normal) - I'm pretty sure it was normal.
I offed it and did the same and confirmed it was the default; THIS time it came up Nook stock.
Is there some way I installed something to the stock NOOK and didn't remove it when I restored to factory? The other day I did the restore from that same clockworkmod screen NOT from the stock Nook environment.
I'm wondering if I somehow created my own monster way back when I first started this and was playing in the android environment.
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Just for Ha, Ha's I hooked the Nook via USB to the PC.
G Drive "Removable Disk G" (wants a disk to be inserted)
E Drive "MyNookColor" ( Lots of what I assume to be standard Nook folders.
See my edit above.
Attachement # 1 SD Card from Mycomputer:
Attachment # 2 MiniTool View of SD Card
Boot Partition
Properties using Minitool Partition Wizard (attached):
Used
Partition Info
File System Info
Surface Test of Boot Partition:
Perfect - so no picture.
This is SO aggravating - I almost would accept just knowing why rebooting wrecks something if I knew WHAT).
leapinlar said:
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Click to expand...
Click to collapse
Sorry, apparently not closely enough - got lots of time again.
....didn't expect that anyone would be watching, was busy posting pictures so I could go away and read and think...
Probably is hardware - wish I had some way to vigorously test that, I get that basic use in Nook Stock doesn't really prove everything is good.
Plus I bought refurbished and I have to go dig up the warranty, it was months ago, so not too hopeful and boxes long gone. Don't know how nice B&N is, free replacement charger and cord is one thing - whole another refurb unit is different if I can't show stock SD card reading is an issue, not sure how much they check, but I don't think they care about CM7 off a SDcard not working!
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
If you registered your nook, the serial number is all you need. Refurbished usually have a one year warranty. Mine did. Just tell them card reading is intermittent. Which it is. They are pretty generous. You still have stock on there.
Edit: Try just an ordinary SD and power off, reboot, and repeat many times and in between check card reading ability.
leapinlar said:
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
Click to expand...
Click to collapse
Yup, it's really the only thing that hasn't been able to be changed through all of this.
I've mostly gotten these results - I've managed to make it worse as I redid things and apparently got sloppy. But when going back to methodically following instructions I have what I had months ago. I had hoped buying other cards would make it at least act differently.
Thanks for all of the reviews and double checking, at least I now it's not something obvious (but wasn't obvious to me) that I missed along the way!
I'll have to call B&N and see how strict they are and if they take the "It just has trouble reading any SD card consecutively".
Now where was that review of the Nexxus 7.... and I wonder how all the tablet prices are going to drop especially for the Galaxy Tab. Buying is not as fun but I am completely beat with modding failures.
We are too fast with each other. Lol. See my edit above.
Ok, here's my case laid out. I've searched the forum to death, so I'm pretty sure what I have here is a head scratcher so I'm hoping someone can help me out.
I bought a used HD2 off craigslist. It came with WP7.5. When I plugged in the data cable (i.e. USB cable), I didn't get a prompt for mounting to SD card. I installed Zune and got all the drivers (going through the MS troubleshooting list), and the phone was able to mount to Zune with only 200 mb. No problem, right? This error is common. I find out that if I use an SD Formatter, I can clear the card, which is 16gb, back to it's original state by mounting the card through MAGDLR.
After restarting the phone, I still couldn't get more storage than the allotted 200 mb, except it had decreased to ~150 mb. My phone was filling up quickly. I researched that, under WP7+, there should be a "connections" option under settings for mounting the SD card through the cable, so I thought "Hey, maybe it's because this flash of WP is missing something." so I reflashed my HD2 to stock rom using a guide.
While as a stock HD2 (T-mobile), I had now 600 mb of space on the phone to use, but I noticed that the HD2 still wasn't sensing my card. Bad card, maybe? So I tried an 8 gb I had, a 2 gb I had, and a 32 gb I KNOW works from my tablet (and still works on my tablet). I decided maybe it was the ROM's fault, so I decided to flash android on it, since I'm used to android from my other phones.
So I follow Jayce's guide and put on the proper HSPL, MAGDLR, the right Radio, and CWM to flash a new android ROM and banish my problems once and for all.
PROBLEM, I'm stuck here because (dope!) even MAGDLR and CWM DO NOT SENSE MY CARD(S). Now I'm stuck and I don't know what to do. Is there a way to get it running at the very least? I know the microSD slot is pretty much the most reliable piece on the phone, so I don't think it's broken.... but maybe it is?
So either a) somebody help me get the phone running with any ROM or b) somebody help me figure out how to get the SD cards working.
Sh*t out of ideas here.
[edit] OK! I FLASHED IT USING THE OL' HOLD DOWN THE "DOWN VOLUME BUTTON AND FLASH THE STOCK" Could still really use help with the SD card sensing thing though....
it wouldn't be the first bad sd card slot reported here, so, reliable it may be, break proof it isn't.
samsamuel said:
it wouldn't be the first bad sd card slot reported here, so, reliable it may be, break proof it isn't.
Click to expand...
Click to collapse
Okay, following what has to be my 5th reformat of the same card, it worked!!!!! I quickly installed android on it. I'm not taking that card out anymore. It'll stay inside
xubii said:
Okay, following what has to be my 5th reformat of the same card, it worked!!!!! I quickly installed android on it. I'm not taking that card out anymore. It'll stay inside
Click to expand...
Click to collapse
I had a bad SDCard too, it doesn't work in recovery but does in the ROM... I think you should really think about replacing your card. Flash memory has a limited amount of writes, so I wouldn't be surprised if you lose your data or find it unusable one day.
Hi,
I intended to post this question to the [3.Nov.2012][ROM] NexusHD2-JellyBean-4.1.2-CM10 V1.2 [NativeSD] thread, but not allowed to (http://forum.xda-developers.com/showpost.php?p=32624318)
Can someone help me redirect the question? Thanks!
First thanks for the great ROM, tytung. It looks great and easy to install.
I have a HD2 and wanted to dual boot WP7 and Android. Found this new method NativeSD and decided to try it. But once I installed the ROM (through MAGLDR 1.13 and Recovery 4Ext 2.2.7), everything works fine, except that the camera app (and other apps) says that it cannot find the external SD card to save the pictures. It does not give me options to save on phone. But since both system and data are on external SD, and that partition is treated as /mnt/sdcard0, I am not sure if I am supposed to have an external SD card from the perspective of Android.
Cannot seem to find similar post with this issue, so I must be doing something wrong with partitioning. Could you help??? Thanks so much! I am inches away from having a great Android JellyBean experience on my HD2.
Thanks!!!
-----------------------------------
Details:
4 partitions on my 16GB SD card:
1) FAT32, 3GB (this is the boot partition, where I installed Recovery 4Ext and through it, installed the boot files in /NativeSD)
2) Ext4, 8GB (this is the system/data partition, where installation put all Android files)
3) Ext4, 2GB (this is current empty, reserved for another ROM that requires two partitions)
4) Other, 2GB (this is a WP7 partition)
I formatted these using Mini Partition Tool on Windows (not via Recovery 4Ext)
I think you need to run CHKDSK on your FAT32 partition of the card with fix option, once, using a card reader and computer. Once done, put the card back to your phone and boot to your preferred Native SD rom. Then check whether you applications are able to trace the SD card. Should work, since the same worked for me, when I had a similar issue. Hope that helps.
dheerajk27 said:
I think you need to run CHKDSK on your FAT32 partition of the card with fix option, once, using a card reader and computer. Once done, put the card back to your phone and boot to your preferred Native SD rom. Then check whether you applications are able to trace the SD card. Should work, since the same worked for me, when I had a similar issue. Hope that helps.
Click to expand...
Click to collapse
Hi dheerajk27, thanks for your quick reply. Was wondering
1) should Android JB think that I have an external SD?
2) where will this external SD be mapped to? The Fat32 partition? The same Ext4 partition as system & data?
3) what would chkdsk do? I just want to make sure that it doesn't mess up the Win 7 stuff as well.
Thanks!
Hi braveliquid, welcome to the forum.
Did you set all your partitions as primary using minitool?
1. yes
2. depends photos/music => fat part, apps=>ext part
3. not sure either
Robbie P said:
Hi braveliquid, welcome to the forum.
Did you set all your partitions as primary using minitool?
1. yes
2. depends photos/music => fat part, apps=>ext part
3. not sure either
Click to expand...
Click to collapse
Thanks for your reply. Upon multiple trial and error, I found out that the logical partition is the culprit. When I have 3 primary (FAT32, Ext4, Ext4), Android can recognize the ext SD card. However, when I have 3 primary and 1 logical (the Win Phone 7 partition is made logical by windows), then Android does not recognize the ext SD card anymore.
Any thought on how I can resolve this? Or else I will have to keep 2 SD cards, one for WP7, and one for Android. Doable, but a bit of a hassle.
Thanks!
use minitool and set your wp7 partition as primary too.
Problem solved.
you could use two cards, i am at the moment (I keep spare card in a cellotape pocket on inside of battery cover). You can also dual boot without partitioning see http://forum.xda-developers.com/showpost.php?p=34009754&postcount=1126 but only really as a backup phone in case wp7 goes wrong and you are away from pc.
Robbie P said:
use minitool and set your wp7 partition as primary too.
Problem solved.
you could use two cards, i am at the moment (I keep spare card in a cellotape pocket on inside of battery cover). You can also dual boot without partitioning see http://forum.xda-developers.com/showpost.php?p=34009754&postcount=1126 but only really as a backup phone in case wp7 goes wrong and you are away from pc.
Click to expand...
Click to collapse
Thanks Robbie. Yes, I have set the WP7 partition as primary and then it works! I am liking the Android experience (have been using iPhone).
Btw, in WP7, it is asking me to update software (I have a very old WP7 installation, migrated to dual boot in early 2011 i think). Can I just upgrade WP7 like normal (i.e. by connecting to Zune)? Or will that destroy MAGLDR? If that won't work, how can I upgrade WP7 to 7.5 or later 7.8? I cannot use Windows Market Place apparently with the old WP7 OS.
Thanks again!
braveliquid said:
Thanks Robbie. Yes, I have set the WP7 partition as primary and then it works! I am liking the Android experience (have been using iPhone).
Btw, in WP7, it is asking me to update software (I have a very old WP7 installation, migrated to dual boot in early 2011 i think). Can I just upgrade WP7 like normal (i.e. by connecting to Zune)? Or will that destroy MAGLDR? If that won't work, how can I upgrade WP7 to 7.5 or later 7.8? I cannot use Windows Market Place apparently with the old WP7 OS.
Thanks again!
Click to expand...
Click to collapse
I would just flash one of the new wp7.8 roms, your choice which. Ansar's does not seem to be able to use the new wpbackup app at the moment.
With Hd2o and pdaimatejam you can backup your phone and restore apps sms calls etc. Sooo much better for trying out new roms.
Robbie P said:
I would just flash one of the new wp7.8 roms, your choice which. Ansar's does not seem to be able to use the new wpbackup app at the moment.
With Hd2o and pdaimatejam you can backup your phone and restore apps sms calls etc. Sooo much better for trying out new roms.
Click to expand...
Click to collapse
:good: Will be another weekend "project" =)
Thanks!