Related
Fellow Android fans. I am out of ideas and could use a benevolent lending hand of help. I have been searching this site for three days now and have attempted everything I can think of (and have found in searches) to get my phone back up again. I have found a couple of posts where people were stuck at the splash screen but just wiping/reflashing typically fixed their issue. I however cannot get past the G1 screen after each boot regardless of the ROM NOR can I even access my SD card which I suppose are two different problems all together.
HISTORY: I have had every modified ROM since JF released his first version last year. I have flashed, backed up, changed radios, put apps/cache/data to my SD (8gb Class 6) with rare issues. The couple times I did get stuck at the splash screen, I would just use Fastboot to go back to a backed up nandroid ROM. But then I decided to go to the latest JF Lucid 1.5 ROM. That’s when it all went downhill. (Certainly no one's fault but my own I know) Though I wiped initially, it seemed that some links were still stuck on the phone for I couldn’t get my apps to SD. The ROM was working fine and I could install market apps without issue, but I wanted to have 100+ apps for absolutely no good reason other than “because I could.” So I was talking with Marcus who suggested I repartition my SD card. This is where the noob came out of me. My trial period had ended with Partition Manager so I used Window’s Device Manager to delete the partition (I backed everything up thankfully) After I did so I powered down the phone to see if all was ok. It wasn’t. It just gets stuck on the G1 screen.
Attempts to Restore:
• I can access the Recovery tool and wipe/flash an older known working update.zip file and it says that it loads successfully, but when I reboot I get stuck at the G1 screen.
• I can access Fastboot and flash a backed up ROM (known working backups that have worked before mind you), it says loaded successfully, but when I reboot it gets stuck at the G1 screen.
• When I insert my SD card into a card reader I cannot access the card as it says “insert disc”.
• I went into Windows Device Manager and it shows that have a memory card but says “Unreadable”.
• I put an older 2gb SD card in the phone and loaded an older RC33 ROM and flashed it. It flashed just fine but gets stuck at the G1 screen.
• So I downloaded the Ubuntu Live CD and attempted to reformat my SD card via Gparted. No dice. It won’t even recognize it as an available disk. (I tried both with it in my phone connected via USB and in the micro SD card adapter and card reader)
I have Windows XP, a Ubuntu Live Cd, JF Lucid 1.5, and a headache after the numerous failed attempts at getting this straight.
I am completely out of ideas. I am not however, familiar with ADB so I am really hoping that there are some commands or something out there can bring my phone back from the dead. If I have to buy a new SD card, so be it, but I am trying to avoid having to buy a new phone. Long story short, I suppose my question is two fold:
1) By deleting my partition did that ruin the SD card and ultimately cause these boot loop issues? I just can't figure that out how that is possible since a partition isn't even a requirement of flashing a ROM
2) Is it possible to reclaim my phone and if so, how?
Thank you very much for your time and any suggestions...
Haters Need Not Post
Interesting problem you got there. Not that i have any answers for ya, but a few ideas. I've read the boards here for a lil while at least, and i know that if you had custom boot images, the second one can cause hangs when switching to certain roms. You didn't say, have you tried flashing the original dreamimg.nbh? When you formatted your sdcard, did you have apps to sd and that dalvic cache to sd card too? possibly pointers on the main partition pointing to a non existing mount point. Hope you get it up and running again
what spl were you on? have you tried the sapphire spl? or hardspl?
I've done this before too. Easiest way to fix it is to flash DREAIMG.NBH, and then re-install test keys and the SPL of your choice and reflash JF1.5
I forgot to mention that yes I had apps, data, and dalvik all moved to the SD card but NO custom boot images. I am assuming the data or dalvik move is what caused the initial problems when I flashed to ADP 1.5. I currently am running the HardSPL (HSPL10.95.3000)
I haven't tried flashing the DREAIMG.NBH yet but assumed it wouldn't work as I have flashed numerous other ROMs to no avail. I suppose I shouldn't assume. I will try that today. On the other hand, any ideas on how to reformat (or just make it recognizable for that matter) my SD card?
Thanks gang!
bahnburner said:
I've done this before too. Easiest way to fix it is to flash DREAIMG.NBH, and then re-install test keys and the SPL of your choice and reflash JF1.5
Click to expand...
Click to collapse
How do I go about reinstalling the test keys? And do I need to flash to an SPL other than the HardSPL (which I have now) for the DREAIMG.NBH to flash appropriately?
Thanks man
gPhunk said:
I forgot to mention that yes I had apps, data, and dalvik all moved to the SD card but NO custom boot images. I am assuming the data or dalvik move is what caused the initial problems when I flashed to ADP 1.5. I currently am running the HardSPL (HSPL10.95.3000)
I haven't tried flashing the DREAIMG.NBH yet but assumed it wouldn't work as I have flashed numerous other ROMs to no avail. I suppose I shouldn't assume. I will try that today. On the other hand, any ideas on how to reformat (or just make it recognizable for that matter) my SD card?
Thanks gang!
Click to expand...
Click to collapse
flashing the nbh should be the way to go .. it basically images the whole phone .. whereas flashing the ROM files does not .. each update.zip only deletes the /system portion of the phone .. performing ALT+W deletes the /system AND /data portions of the phone
flash the nbh like you were starting from scratch with the root process .. go back thru all the steps .. put the new recovery.img etc blah blah blah
odd
I'm not real sure as far as the test keys go. But as long as your phone is rooted with a hard spl (which is just a edited engineering spl) you should be able to reflash any rom including rc29 (dreamimg.img) just rebember to go thourgh the bootloader to do so not recovery. The very way you originally rooted you dream.
Have you tried simply doing a wipe yet? Sounds like you need to clear out the /data partition, and be patient when it boots up the first time after a wipe - it can take a while.
LucidREM said:
flashing the nbh should be the way to go .. it basically images the whole phone .. whereas flashing the ROM files does not .. each update.zip only deletes the /system portion of the phone .. performing ALT+W deletes the /system AND /data portions of the phone
flash the nbh like you were starting from scratch with the root process .. go back thru all the steps .. put the new recovery.img etc blah blah blah
Click to expand...
Click to collapse
Thanks guys - The DREAMIMG flash worked. You truly are life savers. (My wife has been on my ARSE the last 4 days for this.. lol) I do have a quick question for Lucid.
First, thank you for ALL the fine work you have done. Basically all of my ROMs have been yours (and JF's of course). So my question is with the linking of the data and dalvik cache. Even though I wiped when flashing to 1.5 it seemed I still had file folders stuck in my partition which were preventing me from updating the links again. What should I have done to re-link them appropriately? I tried your "undodata / dalvik" scripts but still couldn't get them linked.
Again guys - Thank you
daveid said:
Have you tried simply doing a wipe yet? Sounds like you need to clear out the /data partition, and be patient when it boots up the first time after a wipe - it can take a while.
Click to expand...
Click to collapse
Ya I wipe with every flash. I even let it boot up overnight (as I read that it can take a while) but when I woke up it was still at the G1 screen. Have no idea what caused this but the DREAMIMG.nbh flash worked.
great news
Good to hear you got your dream up and running again. I'm happy to see the community so willing to help. Keep posting issues, keep responding to those who you think you can help. This is the reason why xda-devlopers site is the go to site for xda issues.
SDcard probs....
Did you ever get your SD Card working again?
If not, download the free version of killdisk from http://software.lsoft.net/KillDiskSuiteFree-Setup.exe and use it to wipe the entire sd card with zeros. After that, remove the card from your windows box then reinsert it. Windows should ask you to format it and you should be golden. I've seen this problem happen with flash drives as well and this always gets them back.
I suspect that the disk is dead. In any case, windonkey isn't the right thing to use to try to recover it. Boot on the livecd, insert the disk, type 'dmesg', which should output the device file, i.e. 'sdb', then as root do a "dd if=/dev/zero of=/dev/sd?" where ?=whatever that was from 'dmesg', wait until it finishes, pull the card, push the card, run gparted. More than likely, the output of 'dmesg' will show a problem with the card, in which case, melt it, burn it, break it in half, throw it out, warranty it, whatever makes you happy that results in you not accidentally trying to use the thing.
ipaqkiller said:
Did you ever get your SD Card working again?
If not, download the free version of killdisk from http://software.lsoft.net/KillDiskSuiteFree-Setup.exe and use it to wipe the entire sd card with zeros. After that, remove the card from your windows box then reinsert it. Windows should ask you to format it and you should be golden. I've seen this problem happen with flash drives as well and this always gets them back.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried it but it couldn't write to it. I suppose it's hosed. Just ordered another. Thanks for your help though!
Can flash DREAMIMG.nbh - but not a modded ROM
I was able to regain my phone by flashing DREAMIMG.nbh. (thank you all) I followed all of the directions (to the "T") from this post (http://www.kyubinc.org/files/AndroidMod.zip) that I saw Lucid recommended in an April post. I was able to get through the steps and rooted the phone successfully (made sure I could get "#" when typing "su" into Term Em) BUT when I go to flash RC33, I get hung up at the freaking G1 screen AGAIN !!! <<I'd pull my hair out if I had any>>
I let it boot for 90min before I decided to request suggestions so I don't think it's a patience thing. The only error I noticed while rooting was when I entered the recovery console, at the top it said "Can’t open /cache/recovery/command". Can't remember if that was normal or not as it's been so long but it let me successfully flash the update.zip from the SD card so didn't think much of it. But when I rebooted it is stuck at the G1 screen.
Now I know that my 8gb SD card is hosed so am using the 1gb that came with the phone until I get my new one. So I am using a completely different SD card but am getting the same "stuck at the splash screen" issue. Anyone have an idea what in my phone is surviving all of these wipes/flashes that is perpetuating this issue? It just doesn't make since that I can flash an OEM ROM (DREAMIMG.nbh) just fine but not a modded one (RC33). I certainly am not ruling out user error, but it just seems like a directory or file or WHATEVER inside the phone has been corrupted or something because it's the only constant in this whole process.
Thanks again
dunno
When you went through the root process again did you reinstall the hard spl again. And then protect it
gPhunk said:
I was able to regain my phone by flashing DREAMIMG.nbh. (thank you all) I followed all of the directions (to the "T") from this post (http://www.kyubinc.org/files/AndroidMod.zip) that I saw Lucid recommended in an April post. I was able to get through the steps and rooted the phone successfully (made sure I could get "#" when typing "su" into Term Em) BUT when I go to flash RC33, I get hung up at the freaking G1 screen AGAIN !!! <<I'd pull my hair out if I had any>>
I let it boot for 90min before I decided to request suggestions so I don't think it's a patience thing. The only error I noticed while rooting was when I entered the recovery console, at the top it said "Can’t open /cache/recovery/command". Can't remember if that was normal or not as it's been so long but it let me successfully flash the update.zip from the SD card so didn't think much of it. But when I rebooted it is stuck at the G1 screen.
Now I know that my 8gb SD card is hosed so am using the 1gb that came with the phone until I get my new one. So I am using a completely different SD card but am getting the same "stuck at the splash screen" issue. Anyone have an idea what in my phone is surviving all of these wipes/flashes that is perpetuating this issue? It just doesn't make since that I can flash an OEM ROM (DREAMIMG.nbh) just fine but not a modded one (RC33). I certainly am not ruling out user error, but it just seems like a directory or file or WHATEVER inside the phone has been corrupted or something because it's the only constant in this whole process.
Thanks again
Click to expand...
Click to collapse
and you followed these steps precisely?
http://files.lucidrem.us/jf/ROOT/g1_root.txt
just making sure
O dear, I am experiencing the same issue - I pulled my SD out this morning was not able to get it recognized, and upon reboot got stuck on the splash screen. I have wiped several times and am still stuck at splash 2. I am at work so cannot try to access my card thru my PC to see if I am having the same problem as gPhunk, but can only assume that i fried my SD card. I am a n00b, so really nervous of my ability to get myself back up and running.
To install the dreaming.nbh, is it the same as any other flash - rename it update.zip and ctrl-s from the recovery screen? Does that bring back to an RC build so i have to re-root?
Help! And thank you so much!
LucidREM said:
and you followed these steps precisely?
http://files.lucidrem.us/jf/ROOT/g1_root.txt
just making sure
Click to expand...
Click to collapse
Similar - but the ones I followed were these
http://www.kyubinc.org/files/AndroidMod.zip
I will try this set this time..
Hello again everyone, I recently purchased a used HTC hd2, it has android on it now with clockworkmod recovery app also, But I want to put CM7 on it, So I reboot....Hold down power....select number 8 for the recovery, and it says go go go......but does nothing, I have a slide 3g my touch as well, but I am not comfortable with this phone yet....2 questions....I want to install cm7....can someone link me the exact file I need?...I'll worry about diff roms and themes later.....AND...How do I get into recovery to flash this cm7 rom?...I have mgcldr 1.3 on the phone now, a 8 gig sd card...I want to install the apps to the sdcard as well.....I have searched all over the forums and google, but like I said, I am confused on this only cause it is so new to me, and a bit different than mt3g......Help?...Thanks so much for reading.......Larry
find a good CM rom, and there you will find all instructions, usually it tells you how to.
but you can always reflash magldr and then go by ROM flashing instructions to reflash CWM recovery.
If choosing 'ad recovery' stops at 'go go go', i'd first try it a couple more times. I've had recovery fail a time or two the exact same way, only to work fine the next time I tried it.
If it just won't go into cwm recovery after trying a few times, re-flash cwm recovery with the appropriate system partition size for the rom you intend to flash. Do this by hooking your phone up to your pc by the usb cable and choosing 'usb flasher' in the magldr menu and then flash the recovery image. There is a thread to find your cwm recovery image in the 'hd2 android nand development' forum. Each nand rom thread usually says in the first post what size recovery image is preferred for that particular rom.
The hd2 may seem a bit confusing coming from a native android device, but compared to the mt3gslide, it's pretty straightforward, what with the slide's s-off procedure and the old rooting methods (I rooted back before rooting the slide was super easy lol). Once you can load up cwm, you'll feel right at home, it's just like flashing your old slide from that point on.
Sent from my HTC HD2 using XDA App
dirtylarry10 said:
Hello again everyone, I recently purchased a used HTC hd2, it has android on it now with clockworkmod recovery app also, But I want to put CM7 on it, So I reboot....Hold down power....select number 8 for the recovery, and it says go go go......but does nothing, I have a slide 3g my touch as well, but I am not comfortable with this phone yet....2 questions....I want to install cm7....can someone link me the exact file I need?...I'll worry about diff roms and themes later.....AND...How do I get into recovery to flash this cm7 rom?...I have mgcldr 1.3 on the phone now, a 8 gig sd card...I want to install the apps to the sdcard as well.....I have searched all over the forums and google, but like I said, I am confused on this only cause it is so new to me, and a bit different than mt3g......Help?...Thanks so much for reading.......Larry
Click to expand...
Click to collapse
Hey
You may have a older version of CWM on your HD2. Go to option #2 Boot AD SD and see if that boots CWM If that works you are good but I do recommend going to the CWM threadcand downloading the newer version of CWM, just check the thread on your ROM to see what partion size you need with CWM. If it does not work you might have to flash the newer version anyway as the oder version required you to place two files for CWM on your SD card. The new CWM just flashes to NAND memory like a ROM would. You can either click on the link to CWM in my sig to go to the thread on CWM or you can click on my guide I wrote on MAGLDR and CWM that I have linked in my sig also. I Really recommended you read my guidecas you said you are new to the HD2. It will tell you exactly how to flash both versions new and old of CWM and all kinds of stuff that will help you out. All you need to do when downloading anew ROM is make sure you get the ROM download that says for MAGLDR or has MAGLDR in the file download link in the ROM thread. The ROM download links are usually in the first or secound post of the ROM thread. There are several CM7 based ROMs in the HD2 Android NAND Development forum. Just look for the Cyanogen 7 or CM7 in the thread title. Here is a link to the forum.
http://forum.xda-developers.com/forumdisplay.php?f=928
Thanks guys....SO I have the nand rom for 250Mb..(opr whatever its called), I then push to sd card, after unzipping the file....I then hit option 4 on phone, and run daf.exe...but I get this error
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (736)
Now I googled that and found people saying go to control panel...then active sync, and disable usb etc....but...What control panel?....and..I dont have active sync either......layman terms?....lol thanks guys...getting close....Larry
dirtylarry10 said:
Thanks guys....SO I have the nand rom for 250Mb..(opr whatever its called), I then push to sd card, after unzipping the file....I then hit option 4 on phone, and run daf.exe...but I get this error
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (736)
Now I googled that and found people saying go to control panel...then active sync, and disable usb etc....but...What control panel?....and..I dont have active sync either......layman terms?....lol thanks guys...getting close....Larry
Click to expand...
Click to collapse
Are you talking about flashing Clockwork Mod Recovery or A ROM?
it is something...
LOOK FOR FLASHING INSTRUCTIONS INSIDE YOUR ROM THREAD
Got it....the hard way...lol I did some extensive reading 101, and realized i needed to flash roms a diff way because of nand....lol.....after I reinstalled mgcldr ....thanks guys......Now....to find some awesome nand roms that will help me save the damn battery life......what a hog this is, but I am loving it bigtime.....Dirty
Hey guys, I need some help with my shiny new brick. So I had android running on the phone from nand. So one day while using it, I decided to clear my information from it within android (Settings>Privacy>Factory Data reset). Anyway, this completely F'd my phone. So what I did was try to install a new nand android rom, but that did'nt work either. So then I said let me go back to windows mobile. THAT WONT WORK EITHER!!!
Where I am now:
HSPL installation is successful when I try it (spl version 2.0.8)
Windows mobile stock 6.5 gets stuck at 8%
Task 29% gets stuck at 0%
flashing any rom from the sd card doesnt work either
I feel like I've tried every approach, to no avail. I've read over every thread known to man with this problem, no answer. They all say either task 29 or flash the stock rom, neither of which are working here.
Currently the phone gets stuck on the Stick together screen, then just resets again.
Any ideas? Any help would be much appreciated.
Thanks!
Question... was it a recovery zip or direct nand rom?
Try reformatting the SD card fat32 from the computer, write a fresh image file to it and try to flash from SD again. I don't know why but if I don't reformat the SD card each time, my HD2 never takes a flash. It might not work for you, but it's worth a try. I hope it helps.
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.
I have followed post 1 to install this rom http://forum.xda-developers.com/showthread.php?t=101385 as it looks really nice, but all I get is the splash screen and then nothing happens. It's my first time...
I installed 2.08.HSPL, Radio 2.15...?, MgDLR1.13 and the Recovery 3.xx in post 1. I couldn't make the changes that were suggested as the installer said something about cfg not found so I used the original version from the download link.
I copied the .zip file onto my SD card (still has all the winMo 6.5 stuff on it, waiting for another sd card to arrive).
I then started the ad recovery, installed the zip and it was done successfully, but on reboot all I get is the splash screen (htc hd2, NDT series by langthang) and nothing happens. I've waited 40 mins...
What am I doing wrong ?
Any help appreciated.
Did you set the system partition correctly?
I thought so as I had followed the instruction.
However, I just downloaded the HD2 complete toolkit from elsewhere on this forum and repartitioned. It now works.
Thank you !
No problem