Database Users

Android now wont run!

Ok well i was using android on my phone with out flashing any thing r doing any thing to my phone. and ways i now used HSPL and flashed my phone and now when i try and run android it loads like four lines and then stops.. any ideas?

It would probably be a good idea to copy your android build (and anything else) off of your SD card, format it in your computer via a card reader to FAT32, and try just putting your android build back on (without a data.img) to see if it successfully boots. I have had this happen with a friends HD2 and this was the only way I found to solve it.
If this stage works, you can put your original data.img back on and it should boot back exactly as you had it before.
I hope someone else can give you a less laborious answer but that was the only one I found that worked.

Reno_79 said:
It would probably be a good idea to copy your android build (and anything else) off of your SD card, format it in your computer via a card reader to FAT32, and try just putting your android build back on (without a data.img) to see if it successfully boots. I have had this happen with a friends HD2 and this was the only way I found to solve it.
If this stage works, you can put your original data.img back on and it should boot back exactly as you had it before.
I hope someone else can give you a less laborious answer but that was the only one I found that worked.
Click to expand...
Click to collapse
thanks i give it a shot

[Q] Why wont my HD2 Accept ANYTHING?

Hi,
I have been on this forum for the past 2-3 days trying to get android on my gf's HD2 and it just wont have it.
I have tried MCCM's HD v4 Desire one
I have tried Froyo 1.5
I have tried DL Desire Series, both SD and MAGLAR.
The ones where you click CLRCAD.exe then haret.exe either say it doesent have certificates to run or parts are missing. Or it goes to a black scree and gets stuck on "Jumping To Kernel" and it stays like that for ages (tested for 1 hour, never budged)
The DL desire series via MAGLAR wont work either, I need HSPL (sp?) to install MAGLAR but HSPL keeps reporting back that the file Rapi.dll is missing.
My SPL version is 1.42**** so technically thats right ( from what I have read )
I have tried formatting the SD card via PC and device, also tried a factory reset and an additional 2 other SD cards. Still nada.
What else can it be? Someone mentioned the radio but there is so many questions being asked in a specific thread that mine gets lost and since this is more of a global issue I thought a thread of its own is deserved
I really want this and will go to any length to get it ( not keen on ROM flashing thought, would like to avoid turning the handset into a hammer rather than a phone)
Hope I havent busted any rules
Cheers,
Gib

You need radio 2.14 or more for Android.
aka, upgrade your ROM.

You are not alone
You are not alone here.
I have been having this problem too, I get stuck on the HTC white screen. though I haven't tried much ROM but I have tried formating and reflahing of my WM ROM.
I once did a stock ROM official update with: (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2 .15.50.14_LEO_S_Ship)
ever since I have not been able to find how to flash using SPL, I have been flashing using SSPL_RU and my radio is 2.15.50.14.
Could this reason be the problem.
I need help please I want to have a feel of droid.

Know the feeling
I have been trying all the different android magldr sd roms and everytime its the same story. First boot fine. Second boot and on it just hangs at the green htc logo. I have tried so many things i don't know what to do next.

Have you tried one of the Energy ROM's? I found on my unlocked HD2 that these were the only roms (going back a while now) that I could get Android running off an SD card. I've since heard that there is a basically blank rom for people who want to run nothing but android. It's a small rom, only about 30mb.
It's in a few places around the board. I can't remember what the name of that one is off the top of my head, but any of the Energy series, or the Miri ROM's apparently work too.
Good luck!
Gibbo3771 said:
Hi,
I have been on this forum for the past 2-3 days trying to get android on my gf's HD2 and it just wont have it.
I have tried MCCM's HD v4 Desire one
I have tried Froyo 1.5
I have tried DL Desire Series, both SD and MAGLAR.
The ones where you click CLRCAD.exe then haret.exe either say it doesent have certificates to run or parts are missing. Or it goes to a black scree and gets stuck on "Jumping To Kernel" and it stays like that for ages (tested for 1 hour, never budged)
The DL desire series via MAGLAR wont work either, I need HSPL (sp?) to install MAGLAR but HSPL keeps reporting back that the file Rapi.dll is missing.
My SPL version is 1.42**** so technically thats right ( from what I have read )
I have tried formatting the SD card via PC and device, also tried a factory reset and an additional 2 other SD cards. Still nada.
What else can it be? Someone mentioned the radio but there is so many questions being asked in a specific thread that mine gets lost and since this is more of a global issue I thought a thread of its own is deserved
I really want this and will go to any length to get it ( not keen on ROM flashing thought, would like to avoid turning the handset into a hammer rather than a phone)
Hope I havent busted any rules
Cheers,
Gib
Click to expand...
Click to collapse

Solution!
Instructions :
- Download the Android SD version of your choice. Unzip, Extract the 'Android' folder to root of your SD Card. (Make sure to Format the SD card before doing this.)
- After you have done all steps go into Android folder and tap CLRCAD (for working sound), and after that just tap HaRET
-Booting ..
-Enjoy

kottaho said:
You are not alone here.
I have been having this problem too, I get stuck on the HTC white screen. though I haven't tried much ROM but I have tried formating and reflahing of my WM ROM.
I once did a stock ROM official update with: (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2 .15.50.14_LEO_S_Ship)
ever since I have not been able to find how to flash using SPL, I have been flashing using SSPL_RU and my radio is 2.15.50.14.
Could this reason be the problem.
I need help please I want to have a feel of droid.
Click to expand...
Click to collapse
Ater trying some nand roms i came back to the orignal firmware( the same as you).
And i also have this problem , it just load into a picture with htc on it.

Have you tried using a different SD card? My Sandisk 8gb didn't accept anything. I had an old 512mb laying around that came with my E90, loaded SuperRAM on it (aprox 450mb including data.img) and it booted straight away.

2.15.50.* is the right radio for most SD builds, make sure you have enough free space on SD. most builds have at least 512mb if not 1gb data.img which gets created when first boot. If runs out of space it will get stuck on boot screen. No hspl required with 3.14 HTC winmo rom

I also try to get Android in my HD2 (energy ROM). I am somewhat puzzled however: I want to flick back and forth between WM and Android and many programs I have reside onto my SD card. I have read in an earlier post that before attempting Android I should format my card - does this mean that I cannot have WM data (programs etc) in the same SD card I run android? or that I can transfer them back AFTER I manage (if) to load Android?. Thank you

The SD card has to be formatted in FAT32. Just to make sure the card is clean I copy all my data to my pc, format the card and transfer it all back.

Aesthetic said:
The SD card has to be formatted in FAT32. Just to make sure the card is clean I copy all my data to my pc, format the card and transfer it all back.
Click to expand...
Click to collapse
OK thank you - got it!

Unfortunately I cannot get passed the green HTC splash screen - my HD2 stays there for time no end and the only solution is to take battery out. Any suggestions?

Assuming you've got everything set up properly (right radio, hspl, ...) which you can find on the Android forum. I think you'll have to try using a different brand of sd card. Some cards simply don't play nice with Android.

Got uber annoyed with the SD method, just ended up doing a full scale flash to ROM. Was easier lol

MrAskani said:
Have you tried one of the Energy ROM's? I found on my unlocked HD2 that these were the only roms (going back a while now) that I could get Android running off an SD card. I've since heard that there is a basically blank rom for people who want to run nothing but android. It's a small rom, only about 30mb.
It's in a few places around the board. I can't remember what the name of that one is off the top of my head, but any of the Energy series, or the Miri ROM's apparently work too.
Good luck!
Click to expand...
Click to collapse
I am using Energy ROM (Energy Serie: Energy.Leo.28244.Sense2.5.Cookie.2.0.Feb.12)
My phone just hangs on the white HTC screen when I try to boot into Android from the SD card. I flashed my ROM with SSPL_RU after an update with the Stock ROM (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship)

ehh
Aesthetic said:
Assuming you've got everything set up properly (right radio, hspl, ...) which you can find on the Android forum. I think you'll have to try using a different brand of sd card. Some cards simply don't play nice with Android.
Click to expand...
Click to collapse
I would almost agree with that except, i have 2 exactly the same 16 gb cards, each with a 3 gb fat32 primary partition. 1 loads android but wont allow me to do things like take pictures[it says there isn't an sd card.] The second card just hangs at the green htc screen. Even if I copy the working partition to the other card, it still hangs.

evo1rs said:
2.15.50.* is the right radio for most SD builds, make sure you have enough free space on SD. most builds have at least 512mb if not 1gb data.img which gets created when first boot. If runs out of space it will get stuck on boot screen. No hspl required with 3.14 HTC winmo rom
Click to expand...
Click to collapse
Thanks for this Info. I didn't take into consideration that the file will be enlarged during booting. The copied Android folder was 508MB in size but this got enlarged to about 1.3GB during boot up. I thought if I just leave about 1.2GB in all the SD card I have been trying that it should be enough. But I was wrong.
Thanks a lot I have done multiple reboot without any problem.
I am enjoying my first Android feel.
Thanks once again.

Android on HD2 hates most SD Cards
From my own limited experience to also having read many posts I can say that most sd cards prevent Android from running properly on the hd2. Mine works fine with radio 2.14/2.15 and the stock Sandisk 16gb card that came with my tmous hd2, but I recently tried a wintec 16gb card that made Android run like a broke-wheel-cart and other sd cards I have laying around make it fail.
I think everyone needs to add what card they are using to their signature, or else we might all just end up howling in the wind.
Based on some feedback from another post I just ordered this Sandisk 16gb card from Newegg. It is Model # SDSDQ-016G-A11M . It is reported that that model# provides class10 speeds even though it is sold as a class2. It's use with Android is supposed to be good.

[Q] Help pls: Nook booted from SD w/CM7 good 4 3 days then started to boot to stock

Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!

You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.

Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.

I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.

Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.

OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL

LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?

The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".

It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.

You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.

I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.

Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.

Internal file system gets corrupted

Hi,
I think I didn't post too often here but now I need your help.
I also did some searching first but in threads like http://forum.xda-developers.com/showthread.php?t=1143949 I did not finy a good solution, yet.
I am owning a HD2 and used CoreDroid 1.6 till yesterday. I connected my phone via USB to my computer to load it and left office. When I came back, I noticed my phone was still on. I touched it but nothing happened. The surface was frozen. Not even the off-button showed any effect. Thus, I removed the battery, waited a bit and inserted it again.
Unfortunately the phone did not boot any more. Just hangs at the first "Coredroid Screen". I tested around and when I removed the SD card and rebooted again, it worked. I checked the card and it had some file system problems. Thus, I saved all data and formatted it. However, my HD2 did not boot also with any of the other SD cards I tested (no difference how it is formatted). The system starts booting from NANE and shows the first CoreDroid screen and then just angs.
Then I noticed, that it said after booting "internal memory is full" (I checked it: 0 kb free). I searched for the reason and I found in the internal memory root a folder /bin. Observing it I saw, that nearly ALL executables have a size of 1.5 MB. I am talking about the executables that usually have some few kB.
In panic mode, I used Task29 to completely clear NAND. Then I installed MAGLDR and the appropriate CWM for CoreDroid. I downloaded the newer version 1.7 and flashed it. Same result. Did not boot with SD card but without it worked. However, I had that strange /bin folder with only 1.5MB files. Then I used MAGLDR to clean the system partition again and installed 1.6 again but same problem. I also used not the CWM provided by CoreDroid but also the "generic" downloadable and changed settings accordingly. Same effect. I even tried a CWM with 400 MB system partition instead the proposed 390 MB but same effect. 0 Bytes free. I also tried the latest Hyperdroid and Cyanogen ROMs with the same effect.
So I wonder if there is some tool for "checking" the internal memory for possible problems? Resetting it with Task29 did not bring any benefit.
Hope someone can give me a hint what I would do in this case.

I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.

If you were able to boot magldr and reflash roms and install cwms, I think your internal memory should be fine.
Try flashing some other rom, preferably with no sense. I'd say hyperdroid, i remember it as quick and light.
It might be problem with your phone SD card reader hardware...

samsamuel said:
I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.
Click to expand...
Click to collapse
Thanks for your answers.
The strange thing is: it does not boot if ANY SD-card is inside. If I remove the SD-card, it at least boots. In other words: it boots as long as there is NO SD-card at all.
I must admin I prefer Coredroid since I think it supports many nice features like all the options when connecting it via USB cable (going online over computer connection, usb tethering, etc). However, on the weekend I try flashing again some other roms to check. Still I would like to check what is going on :/

Yeah, I believe you.
Just hope it's not a hardware problem...

[Q] Fault in sdcard reader? WP7 works though

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: